Jump to content
  • EN

Template:FTX Mobile network: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
→Secondary server settings: Added parameter table, updated backup and duplicate descriptions.
FTXXXX WIKI sync with 3.7.x Stage 2 - Resync + Troubleshooting in JIRA: GTPGTM-11751
 
(9 intermediate revisions by 3 users not shown)
Line 31: Line 31:
'''Data protocol'''
'''Data protocol'''
*TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. From the device side, TCP and UDP work almost the same, the only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator. For more information on the protocol differences of Teltonika devices, refer here [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
*TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. From the device side, TCP and UDP work almost the same, the only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator. For more information on the protocol differences of Teltonika devices, refer here [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
'''Encryption'''
*TLS/DTLS are security protocols that protect information sent over a network by encrypting the data so only the intended recipient can read it. These Protocols help authenticate devices communicating with the server and ensure data integrity during transmission. TLS/DTLS encryption creates a secure, private connection so sensitive data can travel safely across networks.
*In order to use TLS/DTLS encryption, server certificates must be uploaded via '''Teltonika Configurator Tool (TCT)''' or '''FOTA Web''' using '''Upload user TLS certificate''' task. For more information, refer to [[{{{model}}} Device status]].
*'''Note:''' Encryption is supported only for TCP/UDP data protocols. MQTT over TLS is not supported in the current implementation.
===Secondary server settings===
'''Mode'''
*Backup -  Records are sent to second server while main server is not available.
*Duplicate - records are sent to both servers (main and second), records are deleted from Flash storage only if both servers confirmed that the records were received from device.
===Secondary server settings===
===Secondary server settings===
'''Mode'''  
'''Mode'''  
*Backup -  Records are sent to second server while main server is not available.  
*Backup -  Records are sent to second server while main server is not available.  
Line 50: Line 61:
| Secondary server protocol || 2009 || 0 - TCP, 1 - UDP
| Secondary server protocol || 2009 || 0 - TCP, 1 - UDP
|}
|}
{{#switch: {{{model}}}
| #default =
===MQTT settings===
[[File:FTX server settings_MQTT.png|right|300px]]
Set up MQTT protocol settings. ''The settings are available when at least one server is configured to use MQTT.''
MQTT (Message Queuing Telemetry Transport) is a network protocol, designed to send messages in a publish-subscribe way. Mainly used in machine-to-machine applications, it is a lightweight protocol designed for applications with constrained resources such as embedded systems.
This implementation supports MQTT protocol versions 3.1, 3.1.1, and 5.
Device IMEI will be used as the client ID.
'''Current Limitations'''
* Compatible only with MQTT brokers supporting MQTT v3.1 / v3.1.1 / v5 over TCP (non-TLS). With current implementation MQTT over TLS is not supported, limiting compatibility with most cloud MQTT services (e.g., AWS IoT, Azure IoT).
* Only Teltonika Codec 8 Extended payload format is supported (no JSON support)
* Functionality has been tested and verified only with Mosquitto MQTT broker
'''Parameters'''
{| class="wikitable"
|+ MQTT settings parameters
|-
! Parameter !! Parameter ID !! Description !! Value(s)
|-
| Username || 2033 || Username used for the connection to the MQTT broker. When using Azure MQTT services, the username format is: "{IoT Hub}.azure-devices.net/{IMEI}/?api-version={2020-09-30 or newer}". Can be empty if broker allows anonymous access. || Max text length = 256, Default = "username"
|-
| Password || 2034 || Password used for the connection to the MQTT broker. Can be empty if broker allows anonymous access. || Max text length = 256, Default = "password"
|-
| Data topic || 67100 || MQTT topic used for receiving data from the device. When using Azure MQTT services, the topic format is: "devices/{IMEI}/messages/events/{any message properties you require}". || Max text length = 256, Default = "data"
|-
| Command topic || 67101 || MQTT topic used for sending commands to the device. When using Azure MQTT services, the topic format is: "devices/{IMEI}/messages/devicebound/{# or specific topic query parameters}". || Max text length = 256, Default = "command"
|}
'''Basic Configuration Example'''
*Primary Server Settings:
**Domain: test.mosquitto.org
**Port: 1883
**Data protocol: MQTT
**Encryption: None
*MQTT settings:
**Username: username (must be set, value does not matter if broker allows anonymous access)
**Password: password (must be set, value does not matter if broker allows anonymous access)
**Data topic: test/device/data
**Command topic: test/device/command
*Records settings:
**Server confirmation method: TCP/IP
'''Azure IoT MQTT Configuration Example'''
*Primary server settings:
**Domain: MQTT-SRV.azure-devices.net
**Port: 8883
**Data protocol: MQTT
**Encryption: TLS/DTLS
*MQTT settings (below, replace „IMEI“ with actual device IMEI):
**Username: MQTT-SRV.azure-devices.net/IMEI/?api-version=2020-09-30
**Password: teltonika (value does not matter)
**Data topic: devices/IMEI/messages/events/
**Command topic: devices/IMEI/messages/devicebound/
*Records settings:
**Server confirmation method: TCP/IP
| FTC305
| FTM305 =
}}


==Server communication settings==
==Server communication settings==
Line 111: Line 185:
'''Pinger port'''
'''Pinger port'''
*FOTA Web ping server port.
*FOTA Web ping server port.
{{#switch: {{{model}}}
| ATC700
| ATM700 =
==Network operators settings==
[[File:FTX network operators settings.png|right|500 px]]
Operator selection logic utilizes three user-defined operator lists to control network connectivity:<br>
'''Roaming network operators'''
*List of operators that have the highest priority when the home network is unavailable.
'''Blacklisted network operators'''
*List of operators that are only connected to when no other higher priority operators are available. If the device is connected to a blacklisted operator, GPRS data sending is disabled. Device should continue checking if any higher priority operators are available. To avoid device looping between blacklisted operator and higher priority operator which is not registrable, ban list should be enabled. Otherwise it’s an expected behaviour.
'''Forbidden network operators'''
*List of operators that are not allowed to be connected to. If device connects to forbidden operator, operator is placed into FPLMN list and modem reset.
'''Ban list control'''
*'''Enable''' or '''disable''' the banning of mobile operators following repeated failed connection attempts, PDP activation failures, or APN configuration issues. The ban duration is 30 minutes.
<br><br><br><br><br><br><br><br>
}}


[[Category:{{{model}}} Configuration]]
[[Category:{{{model}}} Configuration]]

Latest revision as of 13:26, 29 April 2026

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FTX_Mobile_network&oldid=112990"