Caller ID not passing through

Status
Not open for further replies.

Mike_S

Platinum Partner
Joined
Sep 27, 2022
Messages
17
Reaction score
5
Hi team, looking for some help!

We have a customer that requires CLI Passthrough for their business. I have confirmed with our carrier (Vonex, Australia) that they support CLI Passthrough, yet I can't get it to work in all of my testing

  • From : Display Name, Remote Party ID and P-Asserted Identity all set to "OriginatorCallerID"
  • Have tested in V18 and V20 systems
  • As per the attached image, phone call from 0354440044 to 0344363208 and Remote-Party-ID set to OriginatorCaller ID, yet the attached shows Remote-Party-ID: "61344363204" which is the trunk phone number
  • Have tried setting Remote Party ID to default and the others to "OriginatorCallerID", and the other way
  • Have tried adding the Trunk to 3CX as "AU - Generic", "AU - Vocus" and "Worldwide - Generic" in case there were other random settings that I've got wrong

Vonex confirmed Caller ID is not being set at trunk level, and they say they have a customer with 3CX and it's successfully passing through

Really at a loss. The customer has all calls unconditionally forwarded to a call centre and not having the customer caller ID displaying at the call centre is really causing issues :(
 

Attachments

  • remote-party-id.PNG
    remote-party-id.PNG
    50.9 KB · Views: 30
This can be deleted, I have found a solution
 
Did you manage to resolve this with a configuration? It would be great if you could include the solution so if anyone else face this issue they can see how you resolved this.

From what I can see the Remote Party ID is still showing the trunk number. did you omit to define this as the OriginatorCallerID?
 
  • Like
Reactions: jed
Vonex said they needed Remote Party ID and P-Asserted Identity set to "OriginatorCallerID", but even when I chose those settings in Caller ID Control (V20 hosted), the trunk number still displayed and the .pcap file showed Remote Party ID as the trunk number (not OriginatorCallerID)

I exported the trunk to .xml and noticed that not all Remote Party ID settings were OriginatorCallerID so I asked Vonex for the .xml of their customer that had it working

In the end, I went Admin -> Advanced -> Templates -> Provider Templates and read as many as I needed to read until I found a template that had all references to Remote Party ID set to OriginatorCallerID and selected it

Turns out "AU - Breeze" had the correct options in the .xml template, and it worked "out of the box". I had previously tried AU - Vocus, AU - Aatrox, AU - Generic and all either failed to make the call or didn't pass through CLI

Interestingly, if you check out the Caller ID Control settings, it's not even set to what it should be (according to Vonex), so either the imbedded .xml template overrides the Caller ID Control settings, or only changes some (and not the one that I actually needed) - maybe worth the dev team investigating?
 

Attachments

  • Screenshot 2024-09-14 at 1.13.18 PM.png
    Screenshot 2024-09-14 at 1.13.18 PM.png
    73.4 KB · Views: 63
  • Like
Reactions: iduncan and jed
Status
Not open for further replies.

Forum statistics

Threads
111,954
Messages
589,921
Members
164,851
Latest member
DrunkeMeister