porting locked rate centers

[Colorado VoIP]

I've got a customer interested in coming on to my services but they are in a very small locked rate center and would like to keep their number. i've been doing a lot of research and even spoke to one of my go-to trunk providers, and they weren't sure if this would work but are willing to try. So I wanted to ask here too.

Have any of the other partners successfully done a port away from a locked rate center to a supported wireless provider first (like verizon or at&t), an then 2-4 weeks later re-ported to the sip trunk of your choosing? Internet searches indicate this may work, but I wanted to know if anyone has done this successfully first.

obviously we could just do a permanent call forward, but with the tighter restrictions on spoofed outbound caller ID no passing STIR/SHAKEN authentication, it would be most ideal to just port their numbers entirely.

thanks a bunch!

 

[CentrexJ]

There aren't any real "good" options when this happens. Here are what i use:

1. Forward to a local number, and spoof the CID (like you said there are issues with STIR/SHAKEN)
2. Have the customer transition to a new phone number slowly, where the current number is forwarded to the new number so that they still receive calls, but the outbound number is with your SIP carrier. Have them start publishing the new number.
3. Get a sip trunk from the carrier that owns the number for this customer. Likely at a non-competitive price as they are aware that the number isn't portable.

 

[Guillaume Bourgeois]

spoofed outbound caller ID no passing STIR/SHAKEN authentication

Most providers that have adopted STIR/SHAKEN, which should be the case for the majority, normally offer a « Third-Party DID validation» for CallerID service.

In short, you prove that your customer is the rightful owner of the phone number. Each provider has its own verification policies, but once ownership is confirmed, the CallerID can receive a Level “B” Attestation, which is perfectly respectable and should not cause any issues.

This is a very acceptable solution while waiting to find a way to port the number or, as CentrexJ suggested, gradually inform customers of a number change to make the transition as smooth as possible.