V20 Diversion Header being added

[lgray]

We have on-prem systems connected via bridging and they are using the SIP trunks on a central system for outbound calls. While the systems are V18, when a call from a phone on a remote system attempts to go out through the SIP trunks on the central system, there is no diversion header and the call works.. If we upgrade the central system to v20, a diversion header is being added to the invite. The provider is failing the call with SIP 480 Q.850 cause 20 subscriber absent.

Is there a way to prevent that diversion header from being used in v20?

 

[Charles_3CX]

Have you upgraded both the bridged systems to v20 or are you trying to bridge v20 with a v18?

Additionally, are you using generic sip trunks or supported sip trunks?

 

[lgray]

We had upgraded all to V20 and had the call failures. We've since reverted the central system back to V18 and calls started working again.

The SIP Trunks are generic and they worked before the upgrade and work now that the central system is V18. So, this is a change in the Invite sent from the 3CX after the upgrade. I suspect it is the change in bridging to SIP that is having the 3CX system add the diversion header.

 

[lgray]

I've not seen a response on this. Is 3CX reviewing how calls across a bridge using a Generic SIP Trunk on a central system might have been changed in V20.

 

[YiannisH_3CX]

Hello @lgray

The Diversion header was added in V20 and it's present in forwarded calls and since the call comes through a bridge and goes out through a trunk then it is also considered a forwarded call by the system.
Technically if your Generic SIP Trunk provider does not support the Diversion header then it should just ignore it but we will be implementing a fix for bridges. Unfortunately the fix will most probably come in Update 2 of Version 20.

 

[lgray]

Thank you! Any time frame for update 2?

 

[Charles_3CX]

Thank you! Any time frame for update 2?

Currently, we do not have an ETA for when it will be. I am afraid