Predictive Dialler / 3CX P-Asserted-Identity Help

[Graham White]

We have a predictive dialler that prior to us installing 3CX had a direct sip connection to our provider. Since upgrading to 3CX we now run the dialler calls through 3CX which has various advantages for us.


One disadvantage is that 3CX does not pass on the P-Asserted-Identity (PAI) from the dialler. For each record in the dialler we populate what we want the Outbound Caller ID to be. The dialler then puts that in the PAI to 3CX. Typically for us this is a free call number for us to be called back on. Previously this worked flawlessly when the dialler had a direct sip connection.



We have tried various configurations in the Outbound Parameters area of the SIP trunk. The only setting that works is if we set the PAI User and Display Name to Custom Field and then manually add the Outbound Caller ID that we want to broadcast. However this means that for all dialler calls we broadcast the same number which meas that the calls back to that number all go to the same team instead of the various teams that we have.



Have any of you had any success in configuring 3CX to pass on the PAI that it has been supplied rather than either strip or ignore it?



I noticed that the 15.5 update has two additional options for PAI – EnforcedOutboundCallId and EnforcedOriginatorCallerID. While these sound promising they do not work as we want them to and we are then left with a PAI with the user specified as anonymous.

 

[StefanW]

EnforcedOriginatorCallerID is just to be used if you have a req. from a Provider that on CLIR calls still a number must be shown.

In short *5Number (activate Clir)
OriginatorCallerID --> Will hide the number in the assositated field
EnforcedOriginatorCallerID --> Will NOT hide the number in the assosiated field

 

[Graham White]

Thanks for your reply, however it doesn't answer my original question "Have any of you had any success in configuring 3CX to pass on the PAI that it has been supplied rather than either strip or ignore it?"

Regards

 

[YiannisH_3CX]

Hello @Graham White

I do not think that the functionality you want can be achieved. The outbound rules of the trunk are designed to build an Invite with information from specific values. Your best option would be to use the Custom Value as you are doing now and change every time you need to change it

 

[Graham White]

Thanks YiannisH but we want to run simultaneous campaigns with different outbound caller IDs. Is there any way to achieve this?

 

[YiannisH_3CX]

Thanks YiannisH but we want to run simultaneous campaigns with different outbound caller IDs. Is there any way to achieve this?

Only with multiple trunks that you can then select using the outbound rules. Each trunk will be setup with a different caller id and you can select which trunk the call should go out from with a prefix in the Outbound rules.