[cisco-voip] Caller-ID name

[Bell, Joe]

Theoretically, yes.  As long as the format of the data in the display
field is agreed upon by CCM and the sending switch (i.e. ASCII, hex,
text, Klingon, etc).  I have yet to hear of a telco switching the data
from one field (facility) to the other (display).  Also, it could take a
long time before you get to someone at the telco who understands what
you're saying and who would know how to accomplish that request. 

The basic issue is that caller-ID name in the analog world is defined
and standardized thanks to Bellcore.  That's why your customer gets
caller-ID name just fine at home.  Meanwhile, caller-ID name in the
digital world has no specification around it, so telcos are allowed to
do whatever they believe is correct.  As you can imagine, there are many
versions of "correct".  That is the base of the issue.  Lack of
standards regarding data elements in the digital protocols that are
trying to emulate analog protocols.


Joe

-----Original Message-----
From: Bill Riley III [mailto:BRiley at jackhenry.com] 
Sent: Monday, January 23, 2006 2:45 PM
To: Bell, Joe; Turpin, Mark
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Caller-ID name

If the telco does send it to me in the Display IE field then will it
work with H.323? 

-----Original Message-----
From: Bell, Joe [mailto:Joe_Bell at adp.com] 
Sent: Monday, January 23, 2006 3:22 PM
To: Turpin, Mark; Bill Riley III
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Caller-ID name

If you're using H.323 and any flavor of CallManager, then caller-ID name
no worky.  Cisco will tell you the same thing if you open a TAC case.
You must use MGCP to get caller-ID name to work.  Don't be fooled by the
fact the CME can handle caller-ID name just fine.  The issue is CCM
wants that information delivered to it in the Display IE field and
almost all telco's send it in the Facility IE.

Joe

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Turpin, Mark
Sent: Monday, January 23, 2006 12:10 PM
To: Bill Riley III
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Caller-ID name


So in your q931 debug, I only see the number presented in the SETUP
message.

I would check with the phone company to see whether or not they offer
name delivery because it doesn't appear you have it today.

-Mark

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill Riley III
Sent: Monday, January 23, 2006 2:07 PM
To: pwalenta at wi.rr.com
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Caller-ID name

I am using H.323 for the gateway.

-----Original Message-----
From: pwalenta at wi.rr.com [mailto:pwalenta at wi.rr.com]
Sent: Monday, January 23, 2006 2:06 PM
To: Bill Riley III
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Caller-ID name

Incoming caller-id name should work be default on the CallManager,
assuming you're using MGCP as your gateway protocol.

THe phone companies by default don't send it across PRI lines.  You can
have them turn it on.  I believe you must be using an NI type PRI for
this to work.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

This electronic message is from a law firm. It may contain confidential
or privileged information. If you received this transmission in error,
please reply to the sender to advise of the error and delete this
transmission and any attachments.

IRS Circular 230 Disclosure: To ensure compliance with requirements
imposed by the IRS, we inform you that any U.S. federal tax advice
contained in this communication (including any attachments) is not
intended or written to be used, and cannot be used, for the purpose of
(i) avoiding penalties under the Internal Revenue Code or (ii)
promoting, marketing, or recommending to another party any transaction
or matter addressed herein.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or an authorized representative of the intended recipient, you are
hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by e-mail and delete the message and any
attachments from your system.



NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information. Any unauthorized review,
use, printing, saving, copying, disclosure or distribution is strictly
prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.




This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.