sending the original A Party number back out again on a call forwarded call from the 3CX cloud hosted PABX

[sergen]

My sip trunk provider is saying:

"For the original A Party number to be sent back out again on the outbound call forwarded leg one of our platform requirements is for the 'Diversion' header to include the B Party number. The 3CX does not allow or support sending a 'Diversion header'?

Is this true? or they don't know what they are talking about?

 

[YiannisH_3CX]

Hi @sergen

Diversion header is only supported by 3CX for 302 Diversion messages and not for normal forwarded calls.
To enable 302 Diversion:

1. Send the inbound call to an extension.
2. Set the extension status to "Away" and forward the calls for that status to an external number.
3. Enable the option "Use Call Deflection (302)"

 

[sergen]

Thank you. I will give it a try

 

[sergen]

When I change the status to away and tick the box "use call deflection (302)" call fails.
however, when I change status to available or away withouth "call deflection (302) call goes through successfully but don't see the originiating caller number.

 

[YiannisH_3CX]

So your provider does not support 302 Diversion. Who is your provider?

 

[sergen]

This is the provider response:

are 3CX Support saying they support sending a 'Diversion' header or are they indicating that generally sending the original A Party CLI back out again via a call forward is supported as long as the carrier or provider supports this?

On our platform for the original A Party number to be sent back out again on the outbound call forwarded leg one of the requirements is for the 'Diversion' header to include the B Party number.

If 3CX Support can direct you on how to configure the 'Diversion' header then we can complete some call traces to confirm it is doing this. Or if 3CX Support can provide further details on how this feature can be implemented that might be helpful but from memory I think the last time they suggested it was supported when using the '302 Moved Temporarily' message which we do not support.

 

[YiannisH_3CX]

3CX does not support the Diversion header in normal Invites. The only place the diversion header is supported is when sending a 302 Diversion message.

or are they indicating that generally sending the original A Party CLI back out again via a call forward is supported as long as the carrier or provider supports this?

Yes exactly.

So if your provider does not support 302 and requires the diversion header for forwarded calls then you cannot send the originators caller ID when forwarding a call. You will need to show your outbound caller ID.