09-18-2024 11:18 AM
Hello,
We have an issue for outgoing calls through a PRI (MGCP).
Call Manager is sending the Display (Caller ID), instead of the ASCII Display (Caller ID) for all external calls.
Do you have an idea?
09-18-2024 11:40 AM
That is expected behavior. The only time CUCM uses the ASCII is if it is interfacing with a system that requires fields be in ASCII format (which I haven't seen in nearly a decade). If you are using MGCP, CUCM is communicating with MGCP which is more sophisticated and uses the Display (Caller ID) field.
Maren
Maren
09-18-2024 12:21 PM
Hello Maren,
So in that case, what is our best option to send the company name for outgoing calls?
Thanks!
09-18-2024 12:55 PM
There is a spot on the MGCP gateway config in CUCM that allows you to override the number portion of CLID, but not the name portion.
That said, are you looking to override the name portion of caller ID for all calls with a single name (your company name), or is your system not sending the name portion of caller ID at all and you'd like it to do so?
Maren
09-19-2024 05:31 AM
Hello,
Our goal is to send the company name instead of the user name, for all (or portion) of the users.
At this time, the user name & number is displayed
Thank you!
09-19-2024 06:01 AM - edited 09-19-2024 08:36 AM
If this is a real ISDN circuit to the PSTN, without a carrier on-prem gateway converting the PRI to SIP over Ethernet, it's worth stating that calling name (CNAM) data is not transmitted with the call. Each carrier maintains their own CNAM database that the called party's carrier queries (or maintains a cached copy of) using the calling number (ANI) when they receive the call. Your carrier would need to create CNAM records in their database for your DIDs. This remains accurate with SIP unless the call is VoIP end-to-end. Even then, conveying calling/connected name info may not be passed if the calling and called parties are using different carriers. The classic CNAM database serves as the fallback method.
Also, if the carrier is converting this PRI into SIP immediately after the handoff (common these days), you'd be much better off to use SIP all the way and eliminate the ISDN cross-connect.
Even if this is a real ISDN PRI, I'd convert it from MGCP to SIP between CUCM and the gateway. The SIP Trunk in CUCM has a field to do exactly what you're asking here. It's also a far more modern protocol.
PS- The ASCII Alerting & Display Name fields were intended to be equivelent to their UTF-8 equivalents; they should say the same thing. For example, a user's name in English (ASCII) vs. Japanese (UTF-8). You should not use the ASCII fields for company name; however, if only for trivia purposes: unchecking "Transmit UTF-8 for Calling Party Name" on the MGCP circuit in CUCM should result in the ASCII fields being used; SIP trunks also have this checkbox. CUCM will also use the ASCII fields when the calling/called party Device Pools have different User Locales (e.g. Japanese vs. English).
09-20-2024 10:02 AM
The Telco have told us that they can only set this settings ON/OFF, and they can't force the Caller name base on the DID.
From there, we will try to set un a Sip Trunk between CUCM and the Gateway, and test it out, to see if we can control the Caller ID
Thanks!
09-19-2024 06:46 AM
+5 to @Jonathan Schulenberg for a thorough explanation!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide