cfg#sport 2000
UDP port changed from 0 to 2000
cfg#sport
UDP port : 2000
cfg#
The
”sreply”
command can be used for specification of
back-channel communication
settings (see paragraph
”
Setting of module parameters from remote computer by using of back channel”). In some NB-IoT networks/services
there is possible to send back channel messages only from different IP address, than preset standard IP address of
target server used for sending of INFO messages. If the setting is ”Reply to server : no”, the module reply to back
channel requests regularly - that means send answers to the address from which the request came. If the setting is
”Reply to server : yes”, the module always replies to the preset IP address of target server (see ”server” command
setting). For setting ”yes” use ”1” parameter, for setting ”no” use ”0” parameter of the command.
Example of setting back-channel communication and follow-up checking of the setting:
cfg#sreply
Reply to server : no
cfg#sreply 1
Reply to server : yes
cfg#
If the GSM operator providing NB-IOT services transfers data from the modules to the IoT service provider through
the virtual network, the
name of the communication gateway
between GSM and Internet (Access Point Name
- APN) should be entered to the module configuration by using of
”apn”
command. APN is assigned by GSM
operator. Setting of APN can be deleted by entering of ”.” value (dot).
Example of setting of APN-name to ”cms.softlink” value:
cfg#apn cms.softlink
APN changed from ’’ to ’cms.softlink’
cfg#apn
APN is : ’cms.softlink’
cfg#
Current setting of target server and communication gateway displays in the configuration summary as follows:
Server IP : ’92.89.162.105’
Server port : 2000
My src port : 2000
APN :
’cms.softlink’
The ”My src port” value is a number of module UDP port. This value is read only and cannot be changed.
By using of
”sess”
command the
maximum session time
with GSM network server can be set. The timeout
should be set in minutes. As some operators charge each creating of session, setting of session before each trans-
mitting of message could significantly increase service expenses (and it also increases broadcasting time). On the
other hand, if the network server interrupts (loses) session, the module is not notified about it and all broadcasted
messages after that moment are lost. The ”sess” parameter can be used to set the time after which the module
checks the functionality of the IP-connection using the ”ping” function (see using the ”testip” command below). If
functionality of connection is not verified by ”ping” test, the IP-session is canceled and re-established again with the
next broadcasting. Factory setting of this parameter is
two days
(172800 seconds, 2880 minutes), what is reason-
able compromise between expenses and reliability of message delivery. If GS operator does not charge each session,
the parameter can be set to lower value (even to zero, when the session is set-up before each broadcasting), but it
is recommended to keep factory setting always in this situation because creating of session increases broadcasting
time.
Current setting of maximum session time appears in the in the configuration summary as follows:
Max session time 172800 sec - 2d, 0:00:00
Example of setting of maximum session time to 2880 minutes:
NB-K868
18