<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Yes just enter it right away, you can
activate any time after the due date and the timers expire. It
eventually goes away after I think 30 days after FOC? And you can
always edit the FOC date.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-Paul<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 1/9/25 14:44, Mike Hammett via
VoiceOps wrote:<br>
</div>
<blockquote type="cite"
cite="mid:981067626.204.1736451817421.JavaMail.mhammett@Thunderfuck2">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<style type="text/css">p { margin: 0; }</style>
<div
style="font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000">We
have a process that seems to work with everyone we've tried
except Level 3 and Sinch. We have more detail internally, but
more or less it's:
<div><br>
</div>
<div>1. Verify the TN is in our LATA.</div>
<div>2. Look up their OCN and verify we're set up with their
port out portal.</div>
<div>3. Enter the TN(s) into their port out portal, choosing the
FOC date of customer installation.</div>
<div>4. On FOC date, create the port-out in Neustar SOA.</div>
<div>5. Activate it.</div>
<div>6. Done</div>
<div><br>
</div>
<div><br>
</div>
<div>The last ports we did with both Level 3 and Sinch, we
weren't able to activate the port because the timers hadn't
expired. Both required reaching out to their port-out
departments to get them to push it through.</div>
<div><br>
</div>
<div>What are we doing wrong, or was it simply one-time glitches
on the other carrier's side?</div>
<div><br>
</div>
<div>Something is telling me that maybe we need to create the
port-out in Neustar SOA as soon as we get the FOC, not on the
FOC date. However, we sometimes run into hiccups with the
install and may not want it to port that day. Is it as simple
as just not doing the activation step until it's actually
ready? Create the port, let the timers expire, then activate
when ready, assuming it's after the FOC date? I assume there's
a time limit to that and at some point in the future, the FOC
date would time out and we'd have to start all over.<br>
<br>
<div><span name="x"></span><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
<a class="moz-txt-link-freetext" href="http://www.ics-il.com">http://www.ics-il.com</a><br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
<a class="moz-txt-link-freetext" href="http://www.midwest-ix.com">http://www.midwest-ix.com</a><br>
<br>
<span name="x"></span><br>
</div>
<br>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<p><br>
</p>
<p><br>
</p>
</body>
</html>