<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0in;
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.EmailStyle18
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>You have two problems here.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>One being SIP not be able to carry ISDN plan type etc.. so you can’t set those values on the European cluster and have them show up on the US cluster.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The second is it seems like ATT is stripping digits off. Do you own the SIP trunk between clusters?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The fix would be a mix of calling and called transformation patterns on each cluster.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Jason Aarons (AM)<br><b>Sent:</b> Sunday, February 19, 2012 5:30 PM<br><b>To:</b> cisco-voip (cisco-voip@puck.nether.net)<br><b>Subject:</b> [cisco-voip] Sending Calling Party type/plan from CallManager<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>ClusterEurope-PhoneA-7965 with External Mask +442075562100 goes across ICT(SIP) to ClusterUSA then out H323 gateway. Debug isdn on Cluster USA h323 gateway shows the calling party type/plan as unknown/unknown. AT&T says that is the problem and to fix CallManager. I’d rather not do IOS Translation Profiles, but not sure what the “fix” would be in CallManager. How do I tell outbound calls from phones should send calling party type/plan as international across Intercluster Trunk (SIP).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The AT&T switch is only passing 10 digits along of the calling party number. For example my cell phone should show +442075512100 (this is my desk phone in our London UK Office, Country code +44), instead Sprint is receiving +4420755121 (10 digits) from ATT. ATTs says the fix is to have CallManager send the Calling Party Number with type:ISDN plan:International.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Protocol Profile = Networking Extensions<o:p></o:p></p><p class=MsoNormal> 0xA11902013402010080114C4F4E205465737420312C446964617461<o:p></o:p></p><p class=MsoNormal> Component = Invoke component<o:p></o:p></p><p class=MsoNormal> Invoke Id = 52 <o:p></o:p></p><p class=MsoNormal> Operation = CallingName<o:p></o:p></p><p class=MsoNormal> Name Presentation Allowed Extended<o:p></o:p></p><p class=MsoNormal> Name = LON Test 1,Didata<o:p></o:p></p><p class=MsoNormal> Calling Party Number i = 0x0081, '442075562100' <<<<<<<<<span style='font-family:Wingdings'>ß</span>------------7965 with Mask +442075562100<o:p></o:p></p><p class=MsoNormal> Plan:Unknown, Type:Unknown <<<<<span style='font-family:Wingdings'>ß</span>------------------Problem<o:p></o:p></p><p class=MsoNormal> Called Party Number i = 0x80, '19043383245'<o:p></o:p></p><p class=MsoNormal> Plan:Unknown, Type:Unknown<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>