Select Transport for IP Phones from Web Interface

[johnvam]

Hello my friends,

I have a problem while I select the transport (UDP,TCP,TLS) for the provisioned IP phone from the 3CX web interface and also the RTP (secure, normal, etc) instead of going to the IP Phones web interface and make the changes.
If I select an IP Phone from Phones and click on reprovision, TLS conf with secure RTP are lost !!!
After hard reboot of the IP Phone all the secure settings for TLS/SRTP are lost because the phone gets fresh settings from 3CX!
Do you have any other solution instead of NOT provision the phone from 3CX?

I also opened a new idea here. I would appreciate if you find this solution useful to vote for that idea!
https://www.3cx.com/community/threads/select-transport-for-ip-phones-from-web-interface.85726/

Thank you

 

[JohnS_3CX]

Hi @johnvam

Do you have any other solution instead of NOT provision the phone from 3CX?

You could write custom templates to achieve this if your goal is to auto-provision via 3CX with SIP TLS + SRTP.

This is not currently supported so it was a good move to post it in the Ideas section.

 

[johnvam]

Hi @johnvam


You could write custom templates to achieve this if your goal is to auto-provision via 3CX with SIP TLS + SRTP.

This is not currently supported so it was a good move to post it in the Ideas section.

Yes custom template would be a good idea and thanks for that! But custom templates are not against 3CX support guides?

 

[JohnS_3CX]

Since you are configuring the devices in SIP TLS / SRTP mode they are already in an unsupported scenario, so it doesn't make much of a difference in this case, you might as well make a custom template to serve your purpose.

Regarding 3CX Support in case you need to contact them you can treat the issue dynamically before you escalate it:

1. Try to replicate the issue with the default template+provisioning. If it persists then escalate it

2. Try to replicate the issue with the default template+provisioning (but manually switching phone to TLS+SRTP). If it persists then escalate it tentatively - meaning that if it turns out to be a 3CX issue we might be able to do something about it.

3. If it is an issue that can be replicated with 3CX soft clients and no deskphones involved you can still escalate it.

I think this gives a general idea of how you can handle issues without forfeiting support