<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (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;}
@font-face
{font-family:LucidaGrande;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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.apple-converted-space
{mso-style-name:apple-converted-space;}
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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for that, it looks promising… It looks like I may need to upgrade to 15.4 (I’m on 15.3 right now, with CUBE 9.5.1). I guess I need to look into what
this means for me, as I think going to 15.4 brings CUBE 10 if I’m not mistaken… I don’t want to have to go through A2Q again
</span><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m probably pushing my luck here, but do you know of any “gotchas” when upgrading to 15.4 from 15.3.3m6? Right now, we use the cube for media forking (for
UCCE QA) and PSTN ingress/egress with multiple carriers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";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""> Ryan Ratliff (rratliff) [mailto:rratliff@cisco.com]
<br>
<b>Sent:</b> Friday, November 06, 2015 1:06 PM<br>
<b>To:</b> Barnett, Nick<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] solution for multiple sip carriers?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Nick, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I’ve never done it myself but according to <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cisco.com_c_en_us_td_docs_ios-2Dxml_ios_voice_cube_configuration_cube-2Dbook_inbound-2Dhdr-2Dfor-2Doutbound.html&d=BQMGaQ&c=M-KQspD_LQogCbR-BWCHOaeDEPOhF8vWqHZTaiwxT3c&r=T9uVLZucbHG2NKKKzOrp-o5cpdReHj02PkJJsCVkgfwcv7S0R5lDeFJg2VRbiNih&m=5AThMYFRQCRIgLIybeBxuza3NYKUcitqR1iVpcqbyDE&s=6hhkpEm01f2Chxka7LTw7atOKnxy-LrzHoq-0AmFGkM&e=">http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/inbound-hdr-for-outbound.html</a> you
can use inbound leg headers for outbound dial-peer matching.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">-Ryan <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Nov 6, 2015, at 1:17 PM, Barnett, Nick <<a href="mailto:Nick.Barnett@countryfinancial.com">Nick.Barnett@countryfinancial.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I’m looking for some advice on how people handle situations with multiple sip carriers. We have a mix throughout our company of DNs ported from 2 different sip providers.
If only the first provider could have ported everything, but that didn’t happen. I’m trying to NOT use a proxy as I don’t want to maintain a giant list of DNs. Also of note is that the DNs are not in ranges…<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I have a single CUCM 10.0 cluster and 2 CUBEs (one at each data center). But since I’m just labbing this up, I’m just dealing with a testbed cube and test cluster.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I have 3 ideas on how to handle this. First was to use a CSS on the line that added sig/steering digits on the front… say… 000001 for carrier 1 and 00002 for carrier 2. Then
I could peel them off and send them out to the correct SBCs for each provider. I don’t like this, it makes it confusing for support staff to see how a call SHOULD exit.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">My other idea may be a pipe dream… I’ve added a URI to the DN, so, let’s say<span class="apple-converted-space"> </span><a href="mailto:1000@carrier1.example.com"><span style="color:purple">1000@carrier1.example.com</span></a><span class="apple-converted-space"> </span>and<span class="apple-converted-space"> </span><a href="mailto:1001@carrier2.example.com"><span style="color:purple">1001@carrier2.example.com</span></a><span class="apple-converted-space"> </span>on
the 2<sup>nd</sup><span class="apple-converted-space"> </span>carrier DN. Then I changed the sip trunk to the CUBE to pass this info to CUBE. I see the correct stuff flowing through, and it works with my standard incoming called number and destination pattern
dial peers. Now, I’m trying to figure out how to write a URI dial peer that will do magic things for me. I need to be able to route based on calling party URI… is that even possible? I haven’t been able to find an example like this, so I’m beginning to grow
skeptical.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The 3<sup>rd</sup><span class="apple-converted-space"> </span>idea is to use CUSP, which I don’t want to do…<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Incoming calls is not an issue. The problem arises when making sure that an outbound call placed from a number from carrier1 goes out a sip trunk to carrier1. If it doesn’t
go to the same carrier that owns the TN, either the caller id will be overwritten with the sip trunks BTN, or I have to apply a diversion header and all calls show up as long distance (and no longer roll up into billing codes).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Is there some other preferred method that people use?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thanks in advance,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Nick<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"LucidaGrande","serif"">_______________________________________________<br>
cisco-voip mailing list<br>
</span><a href="mailto:cisco-voip@puck.nether.net"><span style="font-size:9.0pt;font-family:"LucidaGrande","serif";color:purple">cisco-voip@puck.nether.net</span></a><span style="font-size:9.0pt;font-family:"LucidaGrande","serif""><br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=BQMGaQ&c=M-KQspD_LQogCbR-BWCHOaeDEPOhF8vWqHZTaiwxT3c&r=T9uVLZucbHG2NKKKzOrp-o5cpdReHj02PkJJsCVkgfwcv7S0R5lDeFJg2VRbiNih&m=5AThMYFRQCRIgLIybeBxuza3NYKUcitqR1iVpcqbyDE&s=kNdHPPGEpLBm2kkz_OI_Q0rapOwkR_Iv1QguiCsdm8Q&e="><span style="font-size:9.0pt;font-family:"LucidaGrande","serif";color:purple">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>