<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5848" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=680490516-12082009><FONT face=Arial
color=#0000ff size=2>Yes, sorry, it's MGCP. So it's as simple as changing
the dropdowns, then? Good news!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=680490516-12082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=680490516-12082009><FONT face=Arial
color=#0000ff size=2>Thanks</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=680490516-12082009><FONT face=Arial
color=#0000ff size=2>jeff</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Wes Sisk [mailto:wsisk@cisco.com]
<BR><B>Sent:</B> Wednesday, August 12, 2009 11:04 AM<BR><B>To:</B> Jeff
Ruttman<BR><B>Cc:</B> Fuermann, Jason;
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] Outgoing Caller
ID, My Router, Telco's PRI<BR></FONT><BR></DIV>
<DIV></DIV>If MGCP gw then CM's parameters make all the difference. With
"CallManager" value CM inspects the number and attempts to guess proper
plan/type. Some switches accept 1 plan/type for all calls. Other
switches require differentiated plan/type per call
(international/national/...).<BR><BR>If h.323 gateway the config on the gateway
controls the values.<BR><BR>/Wes<BR><BR>On Wednesday, August 12, 2009 11:30:03
AM , Jeff Ruttman <A class=moz-txt-link-rfc2396E
href="mailto:ruttmanj@carewisc.org"><ruttmanj@carewisc.org></A> wrote:<BR>
<BLOCKQUOTE
cite=mid:07365C3161D8D8419EE51C3834C02205B84DD8@ma1-exc01.ec2802.elderc.org
type="cite">
<META content="MSHTML 6.00.2900.5848" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.EmailStyle17 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.HTMLPreformattedChar {
COLOR: black; FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</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 dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=859571115-12082009>Well I had great success with AT&T looking at
this with me, and indeed we have to send ISDN for plan and National Number
for type. We're currently sending "unknown" for type and
plan. Unknown is fine for our other 2 AT&T PRIs, but not
the one in question. Has to do with the switch type said the
tech.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=859571115-12082009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=859571115-12082009>I see in CM 6.1 where to change these on the PRI port
on the GW: <FONT face="Times New Roman" color=#000000 size=3>Calling
party IE number type unknown <FONT color=#0000ff>and</FONT> Calling Numbering
Plan.<FONT color=#0000ff> Can I just change these and restart the GW
without any other repercussions? Right now they're set to "Cisco
CallManager" and the help page says basically to leave it alone unless you
know about national dialing plans and such--which I don't
really.</FONT></FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Times New Roman" color=#0000ff
size=3><SPAN class=859571115-12082009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face="Times New Roman" color=#0000ff
size=3><SPAN class=859571115-12082009>So will this change be as simple as
changing the drop down and restarting the GW? And should I also change
the <FONT color=#000000>Called party IE number type unknown <FONT
color=#0000ff>and</FONT> Called Numbering Plan?</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Times New Roman" color=#000000
size=3><SPAN class=859571115-12082009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=859571115-12082009>Thanks</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=859571115-12082009>jeff</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Fuermann, Jason [<A
class=moz-txt-link-freetext
href="mailto:JBF005@shsu.edu">mailto:JBF005@shsu.edu</A>] <BR><B>Sent:</B>
Tuesday, August 11, 2009 4:35 PM<BR><B>To:</B> 'Wes Sisk'<BR><B>Cc:</B> Jeff
Ruttman; <A class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B>Subject:</B>
RE: [cisco-voip] Outgoing Caller ID, My Router, Telco's
PRI<BR></FONT><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'">We
were ok sending them “unknown”, but 911 didn’t work. We have to override with
national ISDN<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'"><O:P></O:P></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">
Wes Sisk [<A class=moz-txt-link-freetext
href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</A>] <BR><B>Sent:</B>
Tuesday, August 11, 2009 3:16 PM<BR><B>To:</B> Fuermann, Jason<BR><B>Cc:</B>
'Jeff Ruttman'; <A class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B>Subject:</B>
Re: [cisco-voip] Outgoing Caller ID, My Router, Telco's
PRI<O:P></O:P></SPAN></P></DIV></DIV>
<P class=MsoNormal><O:P></O:P></P>
<P class=MsoNormal>only other CPE variable is the calling party number plan
and type. you may try overriding those. <BR><BR>On Tuesday, August 11,
2009 10:53:41 AM , Fuermann, Jason <A href="mailto:JBF005@shsu.edu"
moz-do-not-send="true"><JBF005@shsu.edu></A>
wrote:<BR><BR><O:P></O:P></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'">Definitely
an ATT problem if you see it in q391. I know ATT charges us extra to let us
present our DID’s. On a side note, good luck getting ATT to believe you. We
deal with them all the time and it’s constantly “you need to check the
programming on your side” as if we hadn’t already done that and told
them.</SPAN><O:P></O:P></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'"></SPAN><O:P></O:P></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: windowtext 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <A
href="mailto:cisco-voip-bounces@puck.nether.net"
moz-do-not-send="true">cisco-voip-bounces@puck.nether.net</A> [<A
href="mailto:cisco-voip-bounces@puck.nether.net"
moz-do-not-send="true">mailto:cisco-voip-bounces@puck.nether.net</A>] <B>On
Behalf Of </B>Jeff Ruttman<BR><B>Sent:</B> Tuesday, August 11, 2009 9:45
AM<BR><B>To:</B> <A href="mailto:cisco-voip@puck.nether.net"
moz-do-not-send="true">cisco-voip@puck.nether.net</A><BR><B>Subject:</B>
[cisco-voip] Outgoing Caller ID, My Router, Telco's
PRI</SPAN><O:P></O:P></P></DIV></DIV>
<P class=MsoNormal><O:P></O:P></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Greetings,</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">If, when doing a
"debug isdn q391" on my voice router, I see the Calling Party presenting 10
digits to the PRI, then what else on my side of the Caller ID equation
might I alter to have those 10 digits show up on the Called Party's
phone?</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">As it stands now,
the Called Party sees the number assigned to the PRI itself and not the
external mask configured on the phone, not the 10 digits I see being presented
to the PRI via the debug.</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Other points of
interest:</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">We have 2 other
PRIs from AT&T, and I see the same 10 digits presented to those 2 other
PRIs, and those numbers DO show up on the Called Party's
phone.</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">When I send a
call out through the problem PRI and call an AT&T cell phone, I
DO SEE the proper caller id on the Called Party phone, but I do NOT when I
call, say a Sprint phone or a Verizon phone.
</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">AT&T's response
to my questions on the problem PRI:</SPAN><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: rgb(31,73,125); FONT-FAMILY: 'Calibri','sans-serif'">We
would pass the T16OX number for caller id. It is up to the customer to program
their equipment with the DID number they want to display. I would have him
check with his vendor on his programming. I don’t know what else to suggest to
him.</SPAN><O:P></O:P></P>
<P class=MsoNormal>So anything I can try? Push back on
AT&T?<O:P></O:P></P>
<P class=MsoNormal>Thanks, jeff<O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P></DIV>
<P class=MsoNormal>CONFIDENTIALITY NOTICE: The information contained in this
email including attachments is intended for the specific delivery to and use
by the individual(s) to whom it is addressed, and includes information which
should be considered as private and confidential. Any review, retransmission,
dissemination, or taking of any action in reliance upon this information by
anyone other than the intended recipient is prohibited. If you have received
this message in error, please reply to the sender immediately and delete the
original message and any copy of it from your computer system. Thank
you.<O:P></O:P></P><PRE><O:P> </O:P></PRE><PRE style="TEXT-ALIGN: center"><HR align=center width="90%" SIZE=4>
</PRE><PRE><O:P> </O:P></PRE><PRE>_______________________________________________<O:P></O:P></PRE><PRE>cisco-voip mailing list<O:P></O:P></PRE><PRE><A href="mailto:cisco-voip@puck.nether.net" moz-do-not-send="true">cisco-voip@puck.nether.net</A><O:P></O:P></PRE><PRE><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-voip</A><O:P></O:P></PRE><PRE> <O:P></O:P></PRE>
<P class=MsoNormal><O:P></O:P></P></DIV>
<DIV> </DIV>CONFIDENTIALITY NOTICE: The information contained in this
email including attachments is intended for the specific delivery to and use
by the individual(s) to whom it is addressed, and includes information which
should be considered as private and confidential. Any review, retransmission,
dissemination, or taking of any action in reliance upon this information by
anyone other than the intended recipient is prohibited. If you have received
this message in error, please reply to the sender immediately and delete the
original message and any copy of it from your computer system. Thank
you.</BLOCKQUOTE><BR><DIV> </DIV>CONFIDENTIALITY NOTICE: The information contained in this email including attachments is intended for the specific delivery to and use by the individual(s) to whom it is addressed, and includes information which should be considered as private and confidential. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you have received this message in error, please reply to the sender immediately and delete the original message and any copy of it from your computer system. Thank you.</BODY></HTML>