[cisco-voip] Display and ASCII Display ? Why fill any ASCII values in 2013?

[Norton, Mike]

In the case of the Call Display values, the ASCII one is what will get sent out your ISDN gateways. ISDN does not support internationalized caller names, I assume. (Despite the web UI's claim, in 8.6 at least, that these fields are for "Internal Caller ID" that is actually a total lie, there is nothing internal about it.) Putting different text for the non-ASCII and the ASCII makes for a handy way to have specific names displayed to internal callees, and generic business name displayed to external callees. Of course, if you live in a country where the PSTN ignores the name you send out your ISDN trunk, such as the U.S., then it doesn't matter.

For the line text label, it does seem completely useless to have the option of an ASCII value since it's not as if the model of phone will dynamically change to a model that only supports ASCII.

-mn


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: May-16-13 2:50 PM
To: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] Display and ASCII Display ? Why fill any ASCII values in 2013?

I don't see a reason to populate ASCII XXXXXX in a new CallManager 9.x  (3905,89xx, 69xx, 7945/65 and newer)

Are there any Cisco phones/devices that need ASCII because they don't support Internationalization (sp?).


http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_1_1/ccmfeat/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91_chapter_0110.html

Display - This field supports internationalization. If your phone does not support internationalization, the system uses the text that displays in the Label ASCII field.
ASCII Display -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130516/ebdb8fa4/attachment.html>