<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'><br>Mike, <br><br>I've been tempted to use this for the exact reason you say. However, I've been hesitant to use something for a purpose it was not intended for. Last thing I want is to have to remove a feature because it's been changed or removed, etc.<br><br>Too bad we just can't have a field that says, "external" callerID or something like that, either on the phones themselves or the gateways.<br><br>Lelio<br><br><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Data Centre and Communications Facilities<br>Computing and Communications Services (CCS)<br>University of Guelph<br><br>519‐824‐4120 Ext 56354<br>lelio@uoguelph.ca<br>www.uoguelph.ca/ccs<br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Mike Norton" <mikenorton@pwsd76.ab.ca><br><b>To: </b>"Jason Aarons (AM)" <jason.aarons@dimensiondata.com>, "cisco-voip (cisco-voip@puck.nether.net)" <cisco-voip@puck.nether.net><br><b>Sent: </b>Thursday, May 16, 2013 5:12:54 PM<br><b>Subject: </b>Re: [cisco-voip] Display and ASCII Display ? Why fill any ASCII values in 2013?<br><br>
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.content
{mso-style-name:content;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">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.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">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.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">-mn</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> cisco-voip [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Jason Aarons (AM)<br>
<b>Sent:</b> May-16-13 2:50 PM<br>
<b>To:</b> cisco-voip (cisco-voip@puck.nether.net)<br>
<b>Subject:</b> [cisco-voip] Display and ASCII Display ? Why fill any ASCII values in 2013?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-US">I don’t see a reason to populate ASCII XXXXXX in a new CallManager 9.x (3905,89xx, 69xx, 7945/65 and newer)</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Are there any Cisco phones/devices that need ASCII because they don’t support Internationalization (sp?).</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="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" target="_blank">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</a></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Display - <span class="content">This field supports internationalization. If your phone does not support internationalization, the system uses the text that displays in the Label ASCII field.</span></span><span class="content"></span></p>
<p class="MsoNormal"><span class="content"><span lang="EN-US">ASCII Display – </span>
</span></p>
</div>
<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>