Mobile Client integration
The article was successfully sent to the email
General information about Mobile client version compatibility with TRBOnet version:
| Mobile Client version | TRBOnet version | Android version | iOS version |
|---|---|---|---|
| Use version from Google Play or App Store | 6.0 and newer | 5 and newer | 11 and newer |
| 3.3.135 | 5.2.5 - 5.7 | ||
| 1.3.0 | 5.2 and older |
Note!
Max Number active Mobile Clients per Server - 10000 Units.
Max Active talkgroups per Server - 500 Groups.
Advised maximum number of Mobile clients per Group Subscription - 100
Max Number active Mobile Clients per Server - 10000 Units.
Max Active talkgroups per Server - 500 Groups.
Advised maximum number of Mobile clients per Group Subscription - 100
TRBOnet Server ports consumption details
Note!
Starting from version 6.0, TRBOnet allows up to 100 mobile clients in a single talk group to share one VoIP port.
Starting from version 6.0, TRBOnet allows up to 100 mobile clients in a single talk group to share one VoIP port.
Mobile client connection uses UDP ports only. All ports are to be opened on the TRBOnet server side on router\firewall.
For the first connected mobile client:
- 5070 (Default port) – service port:
VoIP ports (Advised Cisco RTP port default range starts form 20000):
- 20000 – Data (contacts, attachments)
- 20001, 20002, 20003 - 3 subscriptions
- 20004 – Home group subscription
- 20005 – private call
For the second connected mobile client:
- 5070 – service port (same as the first)
- 20006 – data (contacts, attachments)
- 20001, 20002, 20003, 20004 – 4 subscriptions subscriptions (shared for all clients, see Note! above)
- 20007 – private call
Total ports: 5070 + 8 UDP from VoIP range.
For 100 connected mobile clients:
- 5070 – service port (shared)
- 20000, 20005 – 20203 – dynamically taken from VoIP range for data and private ports
- 20001, 20002, 20003, 20004 – subscriptions (shared for all clients, see Note! above)
Total ports: 5070 + 208 UDP from VoIP range.
- 101st Mobile client will open the new port for same Talk Group and next 100 Mobile clients will take another 208 UDP ports.
TRBOnet versions before 6.0 did not share ports for Group subscription between different Mobile clients, opening a +1 port for each Mobile client group subscription.
Hardware requirements
Calculation Bandwidth and System requirements for Mobile Client (external link to Interactive Google Sheet)
Network requirements
Calculation of traffic TRBOnet Server 6.0 and newer
Calculation Bandwidth and System requirements for Mobile Client (external link to Interactive Google Sheet)Calculation of traffic TRBOnet Server 5.4 - 5.7
Bandwidth Kbps = (N * 5 + 5Kbps) * Y
Where N is the bit rate for the type of Codec used:
| CODEC | Bit Rate (Kbps) |
|---|---|
| OPUS/16000 |
16 |
Example calculation for 1 Mobile Client of required outgoing bandwidth with OPUS/16000 codec:
(16Kbps * 5 + 5Kbps) * 1 = 85 Kbps
Note!
At the peak of its activity (including data sessions) 1 Mobile Client may use about 100 Kbps, depending on trigger settings and the number of groups it is subscribed to.
Mobile Client can be subscribed to 3 groups simultaneously and it may also receive a private call, i.e. 4х16 Kbps, + some data packets (synchronization, TMS, GPS, Job Tickets).
If only one subscription is in use and 'Monitor Location from other stations' feature is not ticked, then Mobile Client will use about 20 Kbps.
At the peak of its activity (including data sessions) 1 Mobile Client may use about 100 Kbps, depending on trigger settings and the number of groups it is subscribed to.
Mobile Client can be subscribed to 3 groups simultaneously and it may also receive a private call, i.e. 4х16 Kbps, + some data packets (synchronization, TMS, GPS, Job Tickets).
If only one subscription is in use and 'Monitor Location from other stations' feature is not ticked, then Mobile Client will use about 20 Kbps.
Calculation of traffic TRBOnet Server 5.3
Bandwidth Kbps = (N * 5 + 5Kbps) * YWhere N is the bit rate for the type of Codec used:
| CODEC | Bit Rate (Kbps) |
|---|---|
| G.711 µ-Law/8000 | 64 |
| G.711 A-Law/8000 | 64 |
| G.729/8000 | 8 |
| SPEEX/8000 | 8 |
| SPEEX/16000 (WB) | 16 |
Where Y is the amount of ALL mobile clients
Example calculation for 1 Mobile Client of required outgoing bandwidth with SPEEX/16000 codec:
(16Kbps * 5 + 5Kbps) * 1 = 85 Kbps
Example calculation for 10 Mobile Client of required outgoing bandwidth with SPEEX/16000 codec:
(16Kbps * 5 + 5Kbps) * 10 = 850 Kbps
Calculation of traffic from TRBOnet Server to Mobile Client
Bandwidth Kbps = (N * 5 + 5Kbps) * YWhere N is the bit rate for the type of Codec used
Where Y is the amount of ALL Mobile Clients online
Example calculation for 1 Mobile Client of required incoming bandwidth with SPEEX/16000 codec:
(16Kbps ;* 5 + 5Kbps) * 1 = 85 Kbps
Example calculation for 10 Mobile Client of required outgoing bandwidth with SPEEX/16000 codec:
(16Kbps * 5 + 5Kbps) * 10 = 850 Kbps
Mobile Client ANDROID Network Performance Requirements
Note!
Starting TRBOnet Enterprise\Plus 6.3 Mobile communication between TRBOnet Enterprise\Plus Server and Mobile clients can be secured with TLS (AES-128).
While unencrypted connection allows up to 2900ms of Delay, enabling TLS (AES-128) imposes a limitation on the quality of networks, allowed maximum Delay is up to 400ms.
Starting TRBOnet Enterprise\Plus 6.3 Mobile communication between TRBOnet Enterprise\Plus Server and Mobile clients can be secured with TLS (AES-128).
While unencrypted connection allows up to 2900ms of Delay, enabling TLS (AES-128) imposes a limitation on the quality of networks, allowed maximum Delay is up to 400ms.
| TRBOnet version | Delay (ms) | Jitter (ms) | Packet loss (%) or Reordering (%) |
|---|---|---|---|
| Current releases | <2900 | <50 | <2 |
| 5.3.5 till 5.7 | <800 | <100 | <2 |
| 5.2.5 till 5.3.5 | <200 | <100 | <2 |
3G/4G/LTE use cases with latest Android Mobile client version available
Audio quality depends on Broadband cellular network provider signal quality.
Below cases are performed in ideal conditions within full 3G/4G/LTE Network signal strength.
1. Both Mobile clients in 3G Network:
Server connection successful rate is acceptable.
Successful outgoing voice transmissions rate about 99% of overall transmissions rate.
2. Both Mobile clients in 4G/LTE Network:
Server connection successful rate is excellent.
Successful outgoing voice transmissions rate is 100% of overall transmissions rate.
Information about Mobile Network types meaning.
Below cases are performed in ideal conditions within full 3G/4G/LTE Network signal strength.
1. Both Mobile clients in 3G Network:
Server connection successful rate is acceptable.
Successful outgoing voice transmissions rate about 99% of overall transmissions rate.
2. Both Mobile clients in 4G/LTE Network:
Server connection successful rate is excellent.
Successful outgoing voice transmissions rate is 100% of overall transmissions rate.
Information about Mobile Network types meaning.
Related User Manuals
TRBOnet Mobile Client topology considerationsMobile Client user guide - Android
Mobile Client user guide - iPhone