Blind transfer CID issue

[BayAC]

I have a 3CX system hosted in Digital ocean with an SBC on-site. 3CX is trunked to an Avaya IP Office 500 system. When 3cx receives a call via SIP provider DID to a user's extension (into softphone windows app), and the call is blind transferred to an extension on the Avaya PBX (through SIP trunk), 3cx will pull in the SIP trunk number as the from: userpart instead of passing the original caller's extension number. Display Name is being pulled properly, though which is odd.

The Avaya is set to use the header information for call display on this trunk, and 3CX is set to send the CallerDispName / OriginatorCallerID

Everything looks good in the logs up to the refer request that gets generated. I see a refer for a call from the 3CX extension to the Avaya Extension, and then it looks like it detects the call from/to in reverse, and decides to pick up and use the external SIP trunk main number as the from part, and then decides later to use the Avaya trunk number instead.

If anyone has this working and can provide some assistance it would be greatly appreciated. I'm unable to do this from Avaya to 3cx because the Avaya refuses to pass original caller information on a transfer outside the system. So my only hope at integration is to put our receptionist on 3CX and push calls through the other way around.

 

[ltctech]

Related:
https://www.3cx.com/community/threa...ound-caller-id-from-extension-settings.72691/

 

[BayAC]

I was afraid that there might not be a fix for this. I guess seeing a name is better than nothing for affected people over the next year or so

 

[BayAC]

I've been able to work around this by adding configuration on the Avaya side.

In the IPO500 I have a short code for each 3cx extension that sends the call to an ARS that targets 3CX over SIP. On the ARS, becuase my extensions are 3 digits, I have to add a 4th in front of the number so that it can hit a DID on the 3cx side. In the ARS rule, in the Telephone Number field, changing the dialed number format from 8N to 8NSS results in the Avaya actually sending across the original caller information on the SIP trunk.