Toggle sidebar Toggle sidebar

SIP TRUNKS (203) UPDATES

Status
Not open for further replies.

Sergio Fernandez

Free User
Basic Certified
Joined
Aug 31, 2018
Messages
43
Reaction score
9
Hi all

Seems to be a LOT of SIP TRUNK UPDATES (203). Can we can some details please?
 
Same on all my pbx's so this surely normal since V3
 
Hi Sergio,

We updated provider templates based on the new “Transport Protocol” and “IP Mode” parameters that came with V16U3 so they can also support those additional parameters.
https://www.3cx.com/blog/change-log/phone-system-change-log/

Note 1:
If you update these templates on V16U2 or earlier, there is no problem at all, they will work just fine because the older PBX edition ignores the extra parameters.

Note 2:
As always, trunk and voice gateway template updates will only affect newly created trunks, not existing ones. If you want to make use of the newly updated templates in this case, you need to delete and recreate your trunks. This is not necessary if everything already works correctly.
 
Or just update to U3 which includes all those changes
 
Was Telnyx omitted? I have updated to 16/3 and I no longer see them listed in the supported providers.
 
No, they are still there under the Worldwide category
 
Right, you are thanks.
 
Would be nice to search for a provider by name... instead of having to figure out what country they terminate or are listed under.
 
I am treating myself to upgrades of our estate this weekend, and must say (although not entirely relevant to the subject) that the Linux upgrade process is saving me so much more time than Windows.

Can really see why 3CX are pushing the Linux route now.

Just putting it out there!
 
JohnS_3CX said:
Hi Sergio,

We updated provider templates based on the new “Transport Protocol” and “IP Mode” parameters that came with V16U3 so they can also support those additional parameters.
https://www.3cx.com/blog/change-log/phone-system-change-log/

Note 2:
As always, trunk and voice gateway template updates will only affect newly created trunks, not existing ones. If you want to make use of the newly updated templates in this case, you need to delete and recreate your trunks. This is not necessary if everything already works correctly.
Click to expand...
Note 2 is incorrect. We tested this in our office and with several customers. I created another thread but has no traction.

we use CallCentric and these updates added the Transport Protocol to existing trunks and has it set to Any. CallCentric does not support TCP and all outbound calls will fail until it is changed to UDP. This really needs to be addressed.
 
VISA MC said:
CallCentric does not support TCP
Click to expand...


I would suggest speaking to CallCentric about this as SIP over TCP is becoming ever popular since its use by Microsoft SfB/Teams whatever you want to call it as well as the fact that if you are using SIP through firewalls, they are more "friendly" to TCP traffic that UDP (due to the handshake).

My hopes from 3CX also is they will allow TCP traffic as an option for phone provisioning (available and supported for softphone) as I think it would be very useful.
 
eddv123 said:
I would suggest speaking to CallCentric about this as SIP over TCP is becoming ever popular since its use by Microsoft SfB/Teams whatever you want to call it as well as the fact that if you are using SIP through firewalls, they are more "friendly" to TCP traffic that UDP (due to the handshake).

My hopes from 3CX also is they will allow TCP traffic as an option for phone provisioning (available and supported for softphone) as I think it would be very useful.
Click to expand...
I have. They didn’t mention if it was on the roadmap, but the issue still exists today. Any end user who updates their system will suddenly lose outbound calls.
This needs to be looked into and corrected. If the trunk doesn’t support TCP, it should default to UDP.
 
Do you have a copy of a PCAP of a full call from 3CX ? Both legs (Provider and Handset).
 
eddv123 said:
Do you have a copy of a PCAP of a full call from 3CX ? Both legs (Provider and Handset).
Click to expand...
I do not. I can get one next week if necessary, but I am not sure what we are troubleshooting.
Before the updates calls worked fine for all customers and our office. After the update that caused the Transport Protocol issue to appear with the incorrect setting calls failed. Changing the SIP Trunk setting to UDP corrected the issue on all systems. I have already confirmed with the trunk they in fact do not support TCP.

At this point we just need the template addressed. Any user that updates their system or adds a trunk from CallCentric will not function. I thought that was the point of templates is to have a functional group of settings out of the box? I cannot confirm any other trunks because we don’t utilize others, but I am sure someone else can chime in if they are having issues as well.
 
which is strange as their DNS advertises the service plus TLS...
12554

or do you use the default template Registrar: sip-anycast1.telnyx.com
 
@StefanW what would be good is just to confirm my thoughts on the "any" setting in the SIP trunk >> Transport Protocol would means that 3CX simply passes through whatever is sent/received on the trunk in a call to the provider.

I assume it is the above and not that 3CX will set and adjust based on what is supported, as this sort of functionality would normally require a provider type SBC for SIP normalisation: https://support.sonus.net/display/SBXDOC60/SIP+Normalization
 
Brilliant!
 
VISA MC said:
Note 2 is incorrect. We tested this in our office and with several customers. I created another thread but has no traction.

we use CallCentric and these updates added the Transport Protocol to existing trunks and has it set to Any. CallCentric does not support TCP and all outbound calls will fail until it is changed to UDP. This really needs to be addressed.
Click to expand...

Set it back to "any" again and check if it works. Not sure what happened in your case, but I successfully upgraded a 16U2 to16U3, the transport is set to any (by default as this field needs to be populated now) and my outbound calls still work fine. No other options were changed on this trunk from the defaults that it inherited from the previous release.

In addition, keep in mind that "any" will query Callcentric and will follow anything Callcentric responds to the system. Their record currently has UDP, so my test PBX which is set to any goes and correctly resolves this every time and the outgoing call is always successful.


You can learn more here, and see why the "any" option would not have caused the issue you described
https://www.3cx.com/docs/sip-trunk-dns-record-resolution/
 
Last edited:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,363
Messages
592,116
Members
165,536
Latest member
Wecare_ITA
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom