[VoiceOps] Porting Process

[Ben Fullerton]

Ben Fullerton  |  Director, Portability Ops  |  Sinch Voice  |  406-532-3603

From: Ben Fullerton
Sent: Thursday, January 16, 2025 9:44 AM
To: voiceops at voiceops.org; voiceops at ics-il.net
Subject: RE: [VoiceOps] Porting Process

Morning Mike,

A couple chains were forwarded to me. It appears you were having issues with porting form us.  Hopefully I can simplify it for you, but feel free to give me a call it may be easier talk over the phone. I have also attached out TPP which explains this as well.

We do not provide concurrence, neither does Level 3 and many carriers out there. When you get an foc from a carrier that doesn't provide it, its up to you to build it ahead of time so its cleared timers before the FOC date.  We offer a grace period of 5 business days.  If you need to change the date anytime before the foc date you can do that via the portal.  If its after the foc date and you realize you will need to port later than the 5 day grace then you can email portout at voice.sinch.com<mailto:portout at voice.sinch.com> we do not remove translations until we see the spid changes.

We do caution you to not build your side until you have FOC, if we see something built our system will put a conflict on it unless we have a valid FOC'd order.

Thanks,

Ben Fullerton  |  Director, Portability Ops  |  Sinch Voice  |  406-532-3603

From: Brian Knight <brian at knight-networks.com<mailto:brian at knight-networks.com>>
Sent: Thursday, January 16, 2025 8:43 AM
To: Brian Knight <Brian.Knight at sinch.com<mailto:Brian.Knight at sinch.com>>
Subject: Fwd: [VoiceOps] Porting Process




-------- Original Message --------
Subject:
[VoiceOps] Porting Process
Date:
2025-01-09 13:44
From:
Mike Hammett via VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
To:
voiceops <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Reply-To:
Mike Hammett <voiceops at ics-il.net<mailto:voiceops at ics-il.net>>


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:

1. Verify the TN is in our LATA.
2. Look up their OCN and verify we're set up with their port out portal.
3. Enter the TN(s) into their port out portal, choosing the FOC date of customer installation.
4. On FOC date, create the port-out in Neustar SOA.
5. Activate it.
6. Done


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.

What are we doing wrong, or was it simply one-time glitches on the other carrier's side?

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.


-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com<http://www.ics-il.com/>



Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>


_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20250116/6937a00d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Sinch-TPP 8-10-23.pdf
Type: application/pdf
Size: 115939 bytes
Desc: Sinch-TPP 8-10-23.pdf
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20250116/6937a00d/attachment-0001.pdf>