<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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.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: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]-->
</head>
<body lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Have you asked either carrier if they can remove the outbound caller ID restriction? With my carrier (PRI, not SIP, but same issue) it was basically just a matter of asking them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">-mn<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> cisco-voip [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Barnett, Nick<br>
<b>Sent:</b> November-06-15 11:17 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [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"><span lang="EN-US">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>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">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>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">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>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">My other idea may be a pipe dream… I’ve added a URI to the DN, so, let’s say
<a href="mailto:1000@carrier1.example.com">1000@carrier1.example.com</a> and <a href="mailto:1001@carrier2.example.com">
1001@carrier2.example.com</a> on the 2<sup>nd</sup> 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>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The 3<sup>rd</sup> idea is to use CUSP, which I don’t want to do…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">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>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Is there some other preferred method that people use?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks in advance,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Nick<o:p></o:p></span></p>
</div>
</body>
</html>