Author Topic: Tracking Down Issue of Caller Name showing is not matching on Mitel Server  (Read 529 times)

Offline HungryHippo

  • Jr. Member
  • **
  • Posts: 74
  • Karma: +0/-0
    • View Profile
Good Sirs,

I am not sure where to start on tracking this odd issue. I have been told by two users that sometimes when they call out to external number the name showing is different from what we have setup on the Server. Both have a DID of their own and its currently setup to show as the outgoing number. Im checking the smdr logs but all I can see are numbers? Is this an issue with our carrier or the other/called party's carrier? I'm not sure how this works with mitel with the caller name.

Offline ACDeezNutz

  • Jr. Member
  • **
  • Posts: 57
  • Karma: +3/-0
    • View Profile
Re: Tracking Down Issue of Caller Name showing is not matching on Mitel Server
« Reply #1 on: February 04, 2026, 05:29:42 PM »
The name is normally handled at the carrier level and not the PBX.  Call your carrier and see what name they send based on the DID.  I've also chased this for the dumber reason of the person they called has a named saved in their cell phone which will ultimately show over any caller ID. 

Offline HungryHippo

  • Jr. Member
  • **
  • Posts: 74
  • Karma: +0/-0
    • View Profile
Re: Tracking Down Issue of Caller Name showing is not matching on Mitel Server
« Reply #2 on: February 06, 2026, 09:47:35 AM »
If that's the case, then it just got pretty complicated. We have a mixture of SIP and PRI and the way we have it right now is that particular users DID is on SIP but the outgoing route is with the PRI with the outgoing ID from the SIP. Who do I chase on this case? Would this fall on the PRI since that's where we the outgoing call route is?

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4155
  • Country: us
  • Karma: +138/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: Tracking Down Issue of Caller Name showing is not matching on Mitel Server
« Reply #3 on: February 06, 2026, 03:24:36 PM »
If that's the case, then it just got pretty complicated. We have a mixture of SIP and PRI and the way we have it right now is that particular users DID is on SIP but the outgoing route is with the PRI with the outgoing ID from the SIP. Who do I chase on this case? Would this fall on the PRI since that's where we the outgoing call route is?
That isn't really how it works... When a call goes out, it would go over your PRI or your SIP connection. If you are sending Caller ID of the SIP DID out your PRI, then your PRI carrier would need to first allow a call from a number it does not have provisioned on your account (many do not allow this and Stir/Shaken would be invalid, which is also a gray legality)... Some will allow the call, but substitute the billing number of the PRI instead of the CID sent with the call (the billing number may or may not be the "main" number), meaning the number you sent as the Caller ID doesn't matter.

How Caller ID Name traditionally works, is when the terminating carrier delivers the call to the callee, it does a dip to a Caller ID database of the Caller ID ANI number it receives and if there is a match it sends that CNAME info to the callee. In this case your SIP provider "owns" the number and they would have to update the CNAME associated with that DID in the database. However, some SIP providers use a more "modern" approach and allow CNAME passthrough (meaning they send CNAME based on what you send with the call). If they just do passthrough and don't update the Caller ID database, then if you send the number out the PRI, no one really "controls" the name associated with it and most PRI providers do not support receiving CNAME from the end user, so either no CNAME is displayed or the name associated with the primary billing TN is displayed.

Clear as mud, right?

 

Sitemap 1 2 3 4 5 6 7 8 9 10