<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Here is a thought Ed .... <br>
</p>
<p><br>
</p>
<p>I used to work for a CLEC and this was the bane of my existence .... getting carriers to admit fault CAN be like shaving a yak while wearing a meat suit in lion's den ...</p>
<p><br>
</p>
<p>If Carrier A is the LEC for the area that the POTS lines are in, they may (likely) still have local routes on their local switches. The net effect is that when caller local to the area hits these switches, the call is routed by Carrier A using the old (now
stale) route, rather than going out to the PSTN.</p>
<p><br>
</p>
<p>In other words, Carrier A may still be treating those POTS numbers as an ONNET call, for the subscribers it services. If this is the case, I have dealt with this in two ways;</p>
<p><br>
</p>
<ul>
<li>Escalate to engineering and explain the issue, in detail</li><li>Have a subscriber of Carrier A call the carrier and say, "when I dial XYZ number, it takes me to the wrong person". This usually gets the carrier to trace the call and then they find the route and remove it.<br>
</li></ul>
<p><br>
</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
= Ryan =
<p><br>
</p>
<p><br>
</p>
<p>Email: ryanhuff@outlook.com</p>
<p>Spark: ryanhuff@outlook.com</p>
<p>Twitter: <a title="Ctrl+Click or tap to follow the link" id="LPNoLP" href="http://twitter.com/ryanthomashuff">
@ryanthomashuff</a><br>
</p>
<p>LinkedIn: <a id="LPNoLP" href="http://linkedin.com/in/ryanthomashuff">ryanthomashuff</a><br>
</p>
<p>Web <a id="LPNoLP" href="http://ryanthomashuff.com">ryanthomashuff.com</a></p>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Ed Leatherman <ealeatherman@gmail.com><br>
<b>Sent:</b> Friday, June 24, 2016 8:03 AM<br>
<b>To:</b> Cisco VOIP<br>
<b>Subject:</b> [cisco-voip] Porting numbers between carriers</font>
<div> </div>
</div>
<div>
<div dir="ltr">Good morning,
<div><br>
</div>
<div>Is anyone familiar with the process of porting telephone numbers between carriers?</div>
<div><br>
</div>
<div>I've recently ported 40 numbers from "Carrier A" to "Carrier B". Carrier B now has the numbers in their system and most callers to those numbers are getting to us via our SIP trunk with Carrier B. </div>
<div><br>
</div>
<div>However, callers on local POTS lines with Carrier A are still reaching us via our existing PRI with Carrier A. </div>
<div><br>
</div>
<div>Carrier B says the porting is complete; Carrier A says B has not completed the process and that is why the numbers are still active with them. </div>
<div><br>
</div>
<div>Aside from me riding Carrier B every day to figure it out, what magic is involved behind the scenes here? I miss BGP.<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Ed Leatherman<br>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>