[VoiceOps] Sending CNAM to T-Mobile

Ivan Kovacevic ivan.kovacevic at startelecom.ca
Fri Mar 24 17:01:33 EDT 2017

Interesting – does it require users to have the Name ID service?


Theoretically it should not, since they are not doing a CNAM dip and it
isn’t costing them anything.

The second question is whether it augments or overrides CNAM data.

Best Regards,

Ivan Kovacevic

Vice President, Client Services

Star Telecom | www.startelecom.ca
| SIP Based Services for Contact Centers | LinkedIn

*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Adolfo
*Sent:* March 24, 2017 4:53 PM
*To:* Carlos Alvarez <caalvarez at gmail.com>; voiceops at voiceops.org
*Subject:* Re: [VoiceOps] Sending CNAM to T-Mobile

Yes…  T-Mobile made some sort of change on how they handle CID last month…


*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org
<voiceops-bounces at voiceops.org>] *On Behalf Of *Carlos Alvarez
*Sent:* Friday, March 24, 2017 3:44 PM
*To:* voiceops at voiceops.org
*Subject:* [VoiceOps] Sending CNAM to T-Mobile

One of our customers is claiming that when they call their T-Mobile cell
phones, the CLID is correct, but they get CNAM such as "Reception1" and
"Lab2".  Those are the internal names of the phones.  This seems impossible.

Anyone heard of this being possible?

The calls were sent via Onvoy.

***** Confidentiality Notification***** Privileged/Confidential Information
may be contained in this message. If you are not the addressee indicated in
this message (or responsible for delivery of the message to such person),
you may not copy or deliver this message to anyone. In such case, you
should destroy this message and kindly notify the sender by reply email.
Opinions, conclusions and other information in this message that do not
relate to the official business of Goode Technology Group shall be
understood as neither given nor endorsed by GTG.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170324/25037ddf/attachment-0001.html>

More information about the VoiceOps mailing list