1. Enable the Captive Portal mode. To do this, select Captive Portal. Global in the Configuration tab, click Edit and select On for Captive Portal Mode option. Specify Roaming service URL in the next format: ws://host:port/apb/broadcast. Click Accept.
Figure 1 – Captive Portal. Global setting
This setting can be done by creating a configuration template in the Wireless settings/Configuration template manager and applying it to one or more access points.
2. Open the SSID manager and create a new SSID. Specify the following settings:
Type = Hotspot User mobility domain = root2 |
|---|
Note
VLAN-ID = 1000 is used as an example. It should be specified here the service VLAN that is actually used on Your network and comes to the access point. The DHCP server must be accessible for VLAN users.
Select the Radio interfaces to which the generated SSID will be assigned. If you assign an SSID to all radio interfaces simultaneously ("Radio" - "All"), it is recommended to enable" Band steer " (select check box) for priority connection to the 5 GHz network by devices that support both bands. When you assign SSID on one radio interface, Band steer mode should be off.
To optimize roaming, the minimal signal mechanism is used.
Figure 2 – SSID settings
In order for the client to be redirected to a specific page for authorization when connecting to Hotspot SSID, it is necessary to select the name of this page in the Virtual portal name field. Pages are pre-created in the portal, and then appear in the list and become available for selecting.
Figure 3 – Settings of SSID Captive portal
After clicking Accept button, the created SSID will appear in SSID table (Figure 4).
Figure 4 – SSID manager
3. Assign the SSID to the access point via the Add SSID link button.
The SSID will be assigned to the first disabled VAP on the access point. You can see the result in the Configuration/Virtual access points tab (see Figure 5).
Figure 5 – Virtual access points
4. Add a tariff plan.
In the RADIUS/New tariff settings menu, click Add button and specify the basic tariff plan settings:
Name: tarif1;
Code: 2;
Domain: root.
Set the Portal auth check box.
Examples of using tariff plans can be found in the article "SoftWLC. Tariff plan configuration for portal authorization" that is available on v1.14_Setting tariffs for portal authorization (EN)
Figure 6 – New tariff settings
5. Activate the tariff plan on the portal.
To activate, follow the link 192.168.50.1:8080/epadmin.
| Login: admin Password: password |
|---|
In the left panel, select the portal to which the redirection is configured in the created SSID (by default). Read more about creating and customizing new portals in the section v1.14_Portal Constructor
Open Tariff plans tab, click Add button and set flag against the created tariff plan tarif1.
Figure 7 – Selecting a tariff plan
Enter its name which will be displayed to the client on the authorization page in case of using several tariff plans. Click Save button.
Figure 8 – Activation of the tariff plan
Portal operation modes and confirmation of phone numbers are configured in the menu "General settings" (see sections of the "Operation Mode" and "Confirm phone number" ). The register and authorize mode is used by default. To confirm the phone number in portal authorization, two ways are used: Demo mode и Incoming SMS. The demo mode is intended for testing, after entering the phone number, a code is generated and automatically inserted into the form. When putting the system into operation, deselect the Demonstration Mode check box.
Outgoing call and outgoing SMS confirmation methods become available for inclusion after they are configured in the configuration files.
Configure the /etc/eltex-ngw/notification.properties file for real SMG sending.
Configuring the phone number confirmation by incoming messages when the smsc.ru gateway is used
Depending on the interfacing protocol used, specify the required configuration file in the line of sms.gate.outgoing.sms.config:
- smsc_gate.conf for HTTP
- smpp_gate.conf for SMPP (v 3.4)
sms.gate.outgoing.sms.config=smsc_gate.conf
Contents of the notification.properties file:Use this file also for configuring message transmission.
#Common gates settings #Current gate used for each type (config name, for example smpp_gate.conf) sms.gate.outgoing.sms.config=smsc_gate.conf #For incoming sms/calls fields for numbers in configs should be set sms.gate.incoming.sms.config= sms.gate.incoming.call.config= #Gate pool settings sms.gate.pool.size=50 sms.gate.pool.wait.millis=5000 #Port to listen for requests server.port=8040 #============================= #=======database settings===== #============================= #mongodb.uri=mongodb://192.168.1.1,192.168.1.2:27017/notification-gw mongodb.host=localhost mongodb.port=27017 #mongodb.user=user #mongodb.password=password mongodb.name=notification-gw fsfiles.store.period=7 #============================= #=======email settings======== #============================= mail.smtp.submitter=test@email.com mail.smtp.password= mail.smtp.auth=true mail.smtp.host=email.com mail.smtp.port=587 mail.smtp.sendpartial=true mail.smtp.starttls.enable=false mail.smtp.connectiontimeout=5000 mail.gate.pool.size=20 mail.pool.wait.millis=10000 Next, edit the selected configuration file.
1. When using HTTP, it is smsc_gate.conf
Fill in SMSC_LOGIN and SMSC_PASSWORD, that are obtained on smsc.ru website, and SMSC_PROTOCOL (http or https).
Contents of the smsc_gate.conf file:
# SMSC settings SMSC_USE_TRANSLIT=false # smsc accounting (api) settings SMSC_LOGIN= # password for smsc account. If also using this account with smpp, password should be no longer # that 8 symbols according to specification of smpp protocol. Russian symbols are not allowed SMSC_PASSWORD= # encoding for transferring sms via http protocol SMSC_CHARSET=utf-8 SMSC_DEBUG=false SMSC_USE_POST=false # choosing protocol (http|https) SMSC_PROTOCOL=http SMSC_SENDER=
2. If SMPP is used, you should fill in the following data in the smpp_gate.conf configuration file: login, password, server address, port and other settings required to use SMPP.
Contents of smpp_gate.conf file:
# SMSC settings SMSC_USE_TRANSLIT=false # smsc accounting (api) settings SMSC_LOGIN= # password for smsc account. If also using this account with smpp, password should be no longer # that 8 symbols according to specification of smpp protocol. Russian symbols are not allowed SMSC_PASSWORD= # encoding for transferring sms via http protocol SMSC_CHARSET=utf-8 SMSC_DEBUG=false SMSC_USE_POST=false # choosing protocol (http|https) SMSC_PROTOCOL=http SMSC_SENDER= vagrant@vagrant-ubuntu-trusty-64:~$ cat /etc/eltex-ngw/smpp_gate.conf # SMPP Gate settings # smsc accounting (api) settings SMSC_LOGIN= # password for smsc account. should be no longer than 8 symbols according # to specification of smpp protocol. Russian symbols are not allowed SMSC_PASSWORD= # for enabling smpp via smsc.ru need to enable smpp-sending in smsc.ru # private account settings and connect with smsc.ru support and tell them # ip-address(es) from which connection(s) will be established and # which port to open: regular or secured (ssl) (or both) # host - name or IP SMSC_SMPP_HOST=smpp.smsc.ru SMSC_SMPP_PORT=3700 # reserved host for sending sms SMSC_SMPP_RESERV_HOST=smpp2.smsc.ru SMSC_SMPP_SSL_PORT= # numbers for receiving incoming messages # comma is a separator NUMBERS_FOR_INCOMING_SMS= # numbers for receiving incoming calls # comma is a separator NUMBERS_FOR_INCOMING_CALLS= # seconds between sending ENQUIRE_LINK packet to maintain connection with SMPP server # for SMSC SMPP 15 seconds is OK SMSC_SMPP_ENQUIRE_LINK_INTERVAL=15 # Seconds waiting response from SMPP server on SUBMIT_SM packet SMSC_SMPP_TRANSACTION_INTERVAL=5 # type of number for ESME address - better use UNKNOWN (UNKNOWN|INTERNATIONAL| # NATIONAL|NETWORK_SPECIFIC|SUBSCRIBER_NUMBER|ALPHANUMERIC|ABBREVIATED) SMSC_ESME_TYPE_OF_NUMBER=UNKNOWN # numbering plan indicator for ESME address - better use UNKNOWN (UNKNOWN|ISDN| # DATA|TELEX|LAND_MOBILE|NATIONAL|PRIVATE|ERMES|INTERNET|WAP) SMSC_ESME_NUMBERING_PLAN_INDICATOR=UNKNOWN # service type - better leave empty for default (|CMT|CPT|VMN|VMA|WAP|USSD) SMSC_SERVICE_TYPE= # source address type of number when sending (UNKNOWN stands for 0|INTERNATIONAL stands for 1| # NATIONAL - 2|NETWORK_SPECIFIC - 3|SUBSCRIBER_NUMBER - 4|ALPHANUMERIC - 5|ABBREVIATED - 6) SMSC_SOURCE_ADDR_TYPE_OF_NUMBER=ALPHANUMERIC # source address numbering plan indicator when sending (UNKNOWN stands for 0|ISDN - 1| # DATA - 2|TELEX - 3|LAND_MOBILE - 4|NATIONAL - 5|PRIVATE - 6|ERMES - 7|INTERNET - 8|WAP - 9) SMSC_SOURCE_ADDR_NUMBERING_PLAN_INDICATOR=ISDN # source address to indicate in smsc.ru log, can give any name or leave empty, max length is 20 symbols # russian symbols will be converted to translit SMSC_SOURCE_ADDRESS= # destination address type of number when sending (UNKNOWN stands for 0|INTERNATIONAL - 1|NATIONAL - 2| # NETWORK_SPECIFIC - 3|SUBSCRIBER_NUMBER - 4|ALPHANUMERIC - 5|ABBREVIATED - 6) SMSC_DEST_ADDR_TYPE_OF_NUMBER=INTERNATIONAL # destination address numbering plan indicator when sending (UNKNOWN stands for 0|ISDN - 1|DATA - 2| # TELEX - 3|LAND_MOBILE - 4|NATIONAL - 5|PRIVATE - 6|ERMES - 7|INTERNET - 8|WAP - 9) SMSC_DEST_ADDR_NUMBERING_PLAN_INDICATOR=ISDN # replace message prefix with another one or nothing SMSC_DEST_ADDR_REPLACE_PREFIX= SMSC_DEST_ADDR_REPLACE_PREFIX_WITH= # protocol ID SMSC_PROTOCOL_ID=0 # flag shows priority of sms in smsc queue (0|1|2|3) 3 - the highest SMSC_PRIORITY_FLAG=3 # encoding (1 stands for 8-bit ASCII|2 for UCS2 (UTF-16)|0 for 7-bit in data coding, but for text will be used UTF-8). # For sending messages with cyrillic text use 2 SMSC_ENCODING=2 # encode text in win1251, but send data coding marker as defined above SMSC_ENCODE_WIN1251=FALSE # concat long text on smpp server into 1 message (TRUE|FALSE). May pay less money of concatting SMSC_CONCAT_LONG_TEXT_ON_SMPP_SERVER=TRUE # ESME settings # MessageMode (DEFAULT stands for 0|DATAGRAM - 1|TRANSACTION - 2|STORE_AND_FORWARD - 3) SMSC_MESSAGE_MODE=DATAGRAM # MessageType (DEFAULT|ESME_DEL_ACK|ESME_MAN_ACK|SMSC_DEL_RECEIPT|SME_DEL_ACK|SME_MAN_ACK|CONV_ABORT|INTER_DEL_NOTIF) SMSC_MESSAGE_TYPE=DEFAULT # GSMSpecificFeature (DEFAULT|UDHI|REPLYPATH|UDHI_REPLYPATH) SMSC_GSM_SPECIFIC_FEATURE=DEFAULT # GeneralDataCoding settings # ignore these settings (for proper data coding 0x08, for ex.) (TRUE|FALSE) SMSC_IGNORE_OPTIONAL_DATA_CODING_SETTINGS=TRUE # compressed (FALSE|TRUE) SMSC_COMPRESSED=FALSE # messageClass (0|1|2|3) SMSC_MESSAGE_CLASS=1
Save the settings and restart the service by using command:
sudo service eltex-ngw restart
1 There is a "default" page on the portal by default. The page is customized for ELTEX Company as an example.
2 The name of the group within which roaming can be carried out in case of portal authorization. If the access point has a firmware 1.9.0, you should specify user mobility domain. This option is not available in firmware versions above 1.9.0.