Environment
PBX firmware version: 30.10.0.17
Android client version: 2.0.19
iOS client version: 2.0.19
1. Linkus Server or Client version is too low
Make sure to use the latest version on both server and client-side.
2. No port forwarding set on the Router
Port forwarding is required on the Router if LCS is not enabled.
- Port 8111 UDP for Linkus service
- Port 5060 UDP/TCP for SIP registration
- Port 10000-12000 for RTP transmission
Please refer this article to configure the port mapping for Linkus: Set up linkus server without LCS
Please noted if you change any of the ports on the PBX should also change the port number on the router.
3. SIP ALG feature enabled on the router
The SIP ALG feature will manipulate the value in the sip SDP message and cause the Linkus client to send RTP to an incorrect IP address or port.
4. Incorrect NAT settings on the PBX
When you login Linkus remotely like with the cellular network, the NAT settings is used to tell Linkus client where to send the voice stream.
Local Network Identification is used to let PBX know the local IP segment like the IP segment for PBX or IP phones.
For example, the local IP address of the PBX or IP Phones is 192.168.9.x so you put 192.168.9.1/255.255.255.0 in the setting.
Also, we need to check this configuration when you have a 30s call disconnected issue with Linkus.
If you use domain or DDNS you can select the NAT Type to external host
5. Codec translation issue
If it shows No Translation Path to G729 or ulaw, ulaw codec please submit a ticket to Support@CloudOne.co
6. RTP has been blocked by the router or the provider
You could try our LCS service.
Enable Linkus Cloud Service(LCS) on the Linkus Server. LCS uses the tunnel to transmit data it does not needs to set port forwarding on the router and more secure.
References:
How to connect to Asterisk CLI
