Template:FMB GPRS settings

GPRS Settings

These settings define the main parameters for FMB1YX.
GPRS Contex can be selected disabled or enabled:

• Device ability to enable or disable GPRS connection.

APN:

• Access point name, mandatory parameter which is used connect to internet (GPRS)

APN Username:

• Access point name username (optional – depending on operator)

APN Password:

• Access point name password (optional – depending on operator). Access Point Name is a gateway between mobile operator and public internet. It can be obtained from your SIM card provider.
  

GPRS Authentication:

• Some operators use a specific type of authentication for GPRS sessions – CHAP or PAP. If any of these is used, APN should be entered as "chap:<APN>" or "pap:<APN>" respectively e.g. if the operator is using APN "internet" with CHAP authentication, it should be entered as "chap: internet". Information about APN and authentication type should be provided by your GSM operator.
  

SIM1 and SIM2 GPRS Settings can be configured separately.

Auto APN

Auto APN:

• This feature allows the device to select the correct APN from integrated into the firmware APN database. Tracker after turning ON will automatically search APN settings depending on the inserted SIM card.

This setting allows the device to automatically search for APN information based on inserted SIM card.
This feature is used form 03.25.15.Rev.32 and up, explained in more detail in this page.

Transfer APN File

APN file Upload / Download:

• Connect to the device using configurator and look for Transfer APN file section. Press the Upload button and locate your APN_list.bin file. (binary APN list can be named differently, make sure to use the correct file). This transfer APN File option is valid from 03.25.15.Rev.32 and up.

First Server Settings

Domain:

• Server or Domain adress, can be written either IP address or Domain.

Port:

• Server Port

Protocol:

• Defines GPRS data transport protocol, used for data transfers – TCP or UDP.

TLS encryption:

• An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. Also in the Domain settings, can be written either IP address or Domain.
  

Second Server Settings

Second server has 4 different modes:
Disable:

• Second server is not used.

Backup:

• Records are sent to second server if main server is not available (for example fails to open link) or when main server response timeout is reached successively 5 times.

Duplicate:

• Records are sent to both servers (main and second), records are deleted from SD-card (or Flash storage) only if both servers accepted the records.

EGTS:

• Records are sent to both servers (main and second), records are sent to the backup server using the EGTS protocol. RNIS system is supported with EGTS protocol.
  

Backup server Domain:

• Server or Domain adress, can be written either IP address or Domain.

Back up server Port:

• Server Port

Backup server Protocol:

• Defines GPRS data transport protocol, used for data transfers – TCP or UDP.

Encryption:

• An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. Also in the Domain settings, can be written either IP address or Domain.
  

Records Settings

Open Link Timeout:

• Is used to set termination timeout for link between FMB1YX and AVL application. If FMB1YX has already sent all records it waits for the new records before closing the link (except for Deep Sleep mode, for more information refer to Template:FMB Sleep modes#Deep Sleep mode). If new records are generated during the period of this timeout and the minimum count to send is reached, the records are sent to the AVL application. This option is useful when GSM operator charges for link activation.
  

Server Response Timeout:

• Is used to set a period of time waiting for the response from the server-side.

Network Ping Timeout:

• Enables network ping after timeout to prevent link close by operator.
  

FMB1YX device will send the newest records first if Newest is selected in Records Settings, and if Oldest is selected then it will sent Oldest records.
When Newest is selected it is useful in cases when the most important parameter set is the most recent one, as a result other records will be sent right after the newest records are received by AVL application.

ACK Type determines what method the device uses to receive confirmation from the server.
AVL means that the device will expect an additional AVL message from the server, TCP/IP means that the confirmation will be included in the TCP/IP layer and no additional message will be needed.

FOTA WEB Settings

These settings are used to configure FOTA WEB server connection parameters. Status:

• Enables or disables FOTA WEB functionality. If the Status is enabled then it means that CFG can be uploaded to FOTA WEB.

Domain Port:

• The address and port number of the FOTA website are entered to Domain and Port fields.

Period:

• Is used to set the timeout of repeat connections to the FOTA WEB server.
  

From 03.27.XX firmware version, FOTA WEB connection period randomizer is added. The randomizer will choose a +-2.5 period for each connection. For example, then the connection period is set to 30 minutes, device with each connection will choose a new connection (from 27.5 min to 32.5 minutes). This also applies to the "web_connect" SMS/GRRS command. This has been implemented to ensure smoother operation of FOTA WEB services by spreading out large numbers of simultaneous device connections over a longer timeframe.

TLS/DTLS

From 03.27.xx firmware version, TLS/DTLS functionality was implemented for FMB0YX, FMB9X0, FMB96X, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FM30XY, FMB2YX, FMT100 device. Note! Currently only TLS encryption functionality is fully implemented, if needed DTLS encryption is possible to implement.

Supported versions: 1.1/1.2

TLS/DTLS certificate generation

Instructions cover how to generate an encryption certificate and how the device should be configured in order to send encrypted records into the client-server can be downloaded HERE.
Server configuration and encryption certificate implementation is mandatory from the client-server side!