Solved 3cx app registration over UDP - Network interface for provisioning

Status
Not open for further replies.

George Ts

Free User
Advanced Certified
Joined
Jul 3, 2017
Messages
184
Reaction score
12
Hello,
We need to implement the following scenario:
- Users inside the LAN can use the 3cx app and be registered
- When they leave the LAN (e.g. switch to 4g data) registration will be lost, they get unregistered and calls are forwarded to their mobile.

This has triggered a lot of questions:

1. Can the re-registration interval timer be configured for 3cx apps?
2. What is the point of the " Network interface for registration and provisioning" parameter under phone provisioning? Even if we set it to the local IP, the app tries to get provisioning data and register to the public IP
3. On a lab cloud-based 3cx, I changed all the following parameters so that they reflect the local IP of the PBX in the provisioning file of the Welcome email: PBXPUBLICIP, MYPHONE_LINK_EXT_SEC, PROVISIONING_LINK_EXT_SEC . Still, I got a notification "Handshake failed" in the app and it would not get provisioned/registered in the LAN
4. What is the point of the " SIP Transport" parameter under phone provisioning? In our lab cloud-based 3cx, the apps are still using the tunnel protocol for SIP traffic and for RTP as well.
5. What is the point if " Use 3CX Tunnel for remote connections (3CX Client only)"? Indeed, the provisioning file of the Welcome email switches the line <UseTunnel> to zero (0), but the app still used the tunnel protocol.
6. Given the above obstacles, any idea of how to implement the scenario above?

P.S. I am stressing the cloud-based lab 3cx in case this may affect the points elaborated above.
 
Hi,

I am not sure why you wish to do so and also use the app while being on the go and save on the telco charges you have to pay to frwd. the call to the mobile but there why it will not work:

The 3CX APPs do not register to the PBX as an IP Phone, incoming calls are signalled to the device via Push Messages. Also, your mobile apps do not communicate SIP with the PBX but always engage the 3CX tunnel. You may change from the 3CX APP the profile to Away and forward then the calls to the mobile number of the user, but it is not an automated task.
 
Thank you @StefanW
This request is strange indeed and arrived by a customer. But in the scope of it, the above questions were raised.
I guess your answer that 3cx apps will not use SIP for communication with the PBX, covers it all. My understanding based on some tests i just did, is that the parameters above affect the 3cx client for Windows, not the mobile apps. Please correct me if I am wrong, otherwise feel free to close this.

Regards,
George
 
then I am setting the topic to solved...
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,986
Members
164,867
Latest member
swegner