- Joined
- Jan 8, 2025
- Messages
- 4
- Reaction score
- 0
I have multiple instances v18 and v20 with the current trunk providers and do not have any issue with the existing instances, even running the same Version 20.0 Update 4 (Build 487 Release) AKA 20.0.4.487. The only difference is that the existing v20 instance that work great were updated from v18.
With new instances deployed from the portal we can make calls to the DID directly, but any number forwarded to the DID is rejected. It seems 3CX has an issue with the diversion header. It looks like 3CX is changing the forwarded calls as if the forwarded DID was assigned to the trunk.
1469809XXXX is added to the trunk in 3CX and can make and receive calls.
1469642XXXX is forwarded from another service provider to 1469809XXXX
I made the call from 713XXXXXXX to 1469642XXXX and the call forwarded to 1469809XXXX but 3CX rejected it.
I have been advised to add the diversion header value to their trunk, but require some confirmation on if this is the issue and how to go about correcting it.
With new instances deployed from the portal we can make calls to the DID directly, but any number forwarded to the DID is rejected. It seems 3CX has an issue with the diversion header. It looks like 3CX is changing the forwarded calls as if the forwarded DID was assigned to the trunk.
1469809XXXX is added to the trunk in 3CX and can make and receive calls.
1469642XXXX is forwarded from another service provider to 1469809XXXX
I made the call from 713XXXXXXX to 1469642XXXX and the call forwarded to 1469809XXXX but 3CX rejected it.
I have been advised to add the diversion header value to their trunk, but require some confirmation on if this is the issue and how to go about correcting it.