<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content=text/html;charset=ISO-8859-1>
<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial size=2>OK. I'll have to open a case when I have some time
to commit. I've written down a few numbers from TAC engineers and they're
willing to help reproduce the problem. I think most of them were from 919 to
tell you the truth. But I can't remember. I'll post whatever I find out from the
TAC to the list.</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=wsisk@cisco.com href="mailto:wsisk@cisco.com">Wes Sisk</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, August 10, 2004 10:42
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] First character
missing from calling name ID on some calls from Cisco TAC engineers</DIV>
<DIV><BR></DIV>Hi Lelio,<BR><BR>Yep, you've got MGCP. Hmm, CSCdu54048
should have taken care of this for you. We're gonna need that TAC
case. Please include a CCM trace that shows an inbound call setup from a
Cisco employee. Have you noticed coming from any specific Cisco
campus/area code? RTP(392) SJ(408)...?<BR><BR>CSCdu54048<BR><PRE>When <A href="http://wwwin-metrics.cisco.com/cgi-bin/ddtsdisp.cgi?id=CSCdu18827">CSCdu18827</A> was resolved in CallManager 3.1(0.163), it was discovered
that a number of ISDN switches implementing the DMS PRI protocols do not
adhere to Nortel's specification for the Display IE.
Specifically, there is an "extra" leading character that Nortel sends at
the front of the Display IE that should not be used as part of the
actual display for the telephone set.
The problem is that now, all PRI gateways in CallManager that are configured
to use one of the DMS PRI protocols assume that this extra character is there.
If the ISDN switch is not sending this extra leading character, and rather
the first character is part of the display name, then the first real
character of the display name will be discarded from the telephone display
on the IP phone. This can happen in any of the messages where the Display IE
can be carried (e.g. SETUP, CONNECT, etc)
For example, if I call from the IP phone on 3.1(0.163) to another phone
through the gateway where my name display should be John Doe then when
the call connects and the CallManager gets Display IE = John Doe then
what actually gets displayed is:
ohn Doe
This is being filed as an enhancement so that for any time we receive a
Display IE on the PRI gateway configured with one of the DMS PRI protocols,
we should look at the most significant bit in the byte following the length
field in the Display IE.
If it is an ASCII character, then we do nothing and continue normally. If
it is a non-ASCII character, then we strip off the entire byte before handing
off the name display to the destination device.</PRE><BR><BR><BR><BR>Lelio
Fulgenzi wrote:
<BLOCKQUOTE cite=mid003401c47f4a$52887ac0$c801a8c0@deadfish type="cite">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
<DIV><FONT face=Arial size=2>Hi Wes. We are using 6608 blades in a 6500
chasis, so it's not IOS - it's CatOS, I think the bugs were for IOS in
routers. I'm pretty sure they are running MGCP, since I was told if it has
the T1 icon, it's MGCP, and it's H323 if it has H323 in the icon (all in the
gateway configuration screen on CallManager v3.3(3)sr4a).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>It's certainly wierd - it only occurs with
calls from Cisco TAC staff.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-----
-----<BR>Lelio Fulgenzi,
B.A.
<A href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>Network
Analyst (CCS)<BR>University of
Guelph
FAX:(519) 767-1060 JNHN<BR>Guelph, Ontario N1G
2W1
TEL:(519) 824-4120
x56354<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
remove the 1st letter of the canadian alphabet from my email, eh!</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal">-----
Original Message ----- </DIV>
<DIV
style="BACKGROUND: rgb(228,228,228) 0% 50%; FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; moz-background-clip: initial; moz-background-origin: initial; moz-background-inline-policy: initial"><B>From:</B>
<A title=wsisk@cisco.com href="mailto:wsisk@cisco.com">Wes Sisk</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>To:</B>
<A title=lelio@uoguelph.ca href="mailto:lelio@uoguelph.ca">Lelio
Fulgenzi</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>Cc:</B>
<A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
</DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>Sent:</B>
Tuesday, August 10, 2004 8:08 PM</DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>Subject:</B>
Re: [cisco-voip] First character missing from calling name ID on some
calls from Cisco TAC engineers</DIV>
<DIV><BR></DIV>Hi Lelio,<BR><BR>Are you using h323
gateways?<BR>CSCea76050, CSCdz86750,<BR><BR>In the Avaya implementation of
DMS trunks, they do not support<BR>the special leading character.
The Avaya PBX's are configured<BR>for DMS switch type, and for that
configuration the Avaya PBX<BR>does not insert(on outbound) or strip(on
inbound) the special<BR>leading character.<BR><BR>The possibilities:<BR>1)
some endpoints do support the DMS special leading
character<BR> on trunks configured for the DMS protocol
(Nortel PBX's)<BR>2) some endpoints do not support the DMS special leading
character <BR> on trunks confiugred for the DMS protocol
(Avaya,Cisco,other)<BR>3) it is not possibile for intermediate VOIP hops
to modify DisplayIE<BR>4) it is possbile for intermediate POTS hops to
modify the DisplayIE<BR><BR>Basic opertion:<BR>Default IOS behavior has to
be maintained. The display IE should be passed<BR>from pots->voip
and from voip->pots without modification. The DisplayIE
should<BR>not be removed and inserted in the UserUserIE RAW
data.<BR><BR>What is needed to make this work for customer EY:<BR>1. DO
NOT MODIFY DisplayIE (transparently pass DisplayIE without modification in
all cases)<BR><BR>What is needed to make this work for all possible
customer permutations:<BR>1. Do nothing (blindly pass DisplayIE, make this
default just like in previous IOS versions)<BR>2. CLI to stip leading char
going pots->voip<BR>3. CLI to insert leading char going
pots->voip<BR>4. CLI to insert leading char going voip->pots<BR>5.
CLI to strip leading char going voip->pots<BR><BR>Leading character
"0xB1" for DMS 100, or "0xB2" for
DSM_250.<BR><BR>********************<BR><BR>We have confirmed that the
originating Jax CCM did not insert the 0xB1, but the 0xB1 is present
when<BR>the call arrives at NY.<BR><BR>I believe this is due to the IOS
request CSCdx12421. This was initially requested to have a
hidden<BR>CLI to add/remove the 0x81 character. However, the final
implementation in is a hard coded insertion of <BR>0xB1 when it is not
initially present.<BR><BR>Please confirm the version of code on the Jax
36xx router.<BR><BR>We need to confirm once more that the 0xB1 is not in
the Dislpay when it leaves the Jax CCM, but is<BR>there in the Debug isdn
q931 when the call leaves the Jax router.<BR><BR>Going forward we have 2
options:<BR><BR>1. use MGCP gateways everywhere. Callmanager still
allows the option of inserting 0xB1 or not<BR>inserting it,<BR>We could
configure MGCP IOS gateways in Troy, Jax, and Hou?? to avoid this
issue.<BR><BR>2. upgrade CCM to at least 3.2(2c)spF everywhere and enabled
the
parameter<BR>"SendExtraLeadingCharacterInDisplayIE"<BR>everywhere.
CCM requires this flag be set in the gateway configuration page to check
for the 0xB1<BR>character and remove it.<BR>With this box checked,
incoming messages from MGCP gateways will be checked and stripped of
a<BR>leading 0xB1 character.<BR>However, this will also have CM send the
leading character out as well, so the far end CM will have<BR>to expect
this and remove it.<BR>Thus the need for 3.2(2c)spF and this configuration
in all locations.<BR><BR>/Wes<BR><BR><BR>Lelio Fulgenzi wrote:<BR><BR>>
In order to get calling name ID working properly, we had to check off
<BR>> the following parameter in our *Digital Access PRI*
gateway:<BR>> <BR>> [x] Send Extra Leading Character In
DisplayIE***<BR>> <BR>> Once we set that parameter, the
special character that appeared before <BR>> the calling name (usually
an ASCII graphic character) went away, and <BR>> all was
well.<BR>> <BR>> However, now, when I get a call from some
Cisco TAC engineers (this is <BR>> the only time I've seen it), the
first letter of their name is <BR>> missing. Instead of "Tom Smith", I
see "om Smith".<BR>> <BR>> Has anyone else run into
this?<BR>> <BR>> Just thought I'd send a note out before I
open a case with the TAC on <BR>> this. I'm worried that between some
CallManager-to-CallManager <BR>> communications, this parameter is
actually causing the problem and if <BR>> it's something that can be
avoided if we decide to go with some <BR>> off-site CCM
installations.<BR>> <BR>> Lelio<BR>> <BR>>
--------------------------------------------------------------------------------<BR>>
Lelio Fulgenzi, B.A.<BR>> Network Analyst (CCS) * University of Guelph
* Guelph, Ontario N1G 2W1<BR>> (519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>> <BR>> "This signature may contain traces of
nuts"<BR>>
--------------------------------------------------------------------------------<BR>>
<BR>><BR>>------------------------------------------------------------------------<BR>><BR>>_______________________________________________<BR>>cisco-voip
mailing list<BR>><A class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>><A
class=moz-txt-link-freetext
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
<BR>><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>