Send called party information to CUCM from external system

[8ctorres]

Hi

I have a situation that I'm trying (and failing) to recreate.

When a call is placed to a Hunt Pilot, the receiving user's Jabber shows the calling party ID and the called number (the hunt pilot number), like in the following picture. The caller is 647445536, and they dialed 3585009, which is a hunt pilot that directed the call to the user.

 

Now the issue: I have an external system (Asterisk) that receives calls from our SIP provider, applies some logic and then directs the call to the user via CUCM. I would like Jabber to display the original called number, so the users can know if the call was made directly to them or if went through Asterisk.

Which SIP headers do I have to send CUCM when placing the call from Asterisk, so this information gets sent to the end user?

Thanks

[Jonathan Schulenberg · Accepted solution]

Direct calls to the user’s DN instead of the Hunt Pilot won’t show the “Para 3585009” banner. That’s how the user can tell. AFAIK the only way you can get Jabber to show the line info is when it has multiple DNs/lines.

PS- Reminder that the Webex app is the long term replacement for Jabber, including with CUCM.

[8ctorres]

Thank you for your answer Jonathan, I was kind of afraid that would be the case. During my testing I did a packet capture and discovered the SIP INVITE message actually has the 3585009 in the "To" header, which I can't overwrite beforehand since then CUCM wouldn't know how to route the call.

For future users that may find this useful: I found a compromise solution which is to use a Diversion SIP header. The banner in Jabber is not exactly the same, it says "Forwarded to 3585009" instead of "For 3585009", but it's the closest thing I could find, and is good enough for what I need, since it allows the user to know this call is coming from Asterisk and not into their DID. For CUCM to pass the Diversion headers, this has to be enabled in the Device>Trunk configuration, option "Redirecting Diversion Header Delivery - Inbound".

Kind regards

[Roger Kallberg]

For what it’s worth, CM doesn’t route on the To header, it uses the URI in the invite for this.