Solved Porting from one SIP Trunk to Another

[advlaser]

Tomorrow we are porting our phone numbers from AT&T to VoxTeleSys. I have both SIP trucks up and registered. According to VoxTeleSys, in advance I can setup my phone numbers and DID's on the SIP trunk and inbound rules so that when we port, it will seamlessly switch from one trunk to another. Sounds great! BUT

The problem is as soon as I add the phone numbers to VoxTeleSys the number stops working. I get a busy signal or out of service. At this point we have not ported, so the phone call will be coming through the AT&T trunk. Is there something else I need to do so that the phone number can reside on both trunk/inbound rules?

 

[SteveITS]

Did/can they set you up with temp numbers? Have AT&T forward the number, then it won’t be arriving inbound on that trunk.

 

[Kevin@voxtelesys]

Hey @advlaser,
When you say add the number to Voxtelesys do you mean on the SIP trunk on 3CX?

Is the ATT trunk also setup on the 3CX? If so does it also use E164 formatting for the numbers?

 

[advlaser]

No they said I could setup the numbers on both trunks and it will just seamless switch over. This would be perfect. I just can't figure how to pull that off. I'm sure it's something I'm doing wrong. As soon as I add the number to the DID list on VoxTeleSys trunk, it breaks. Even

Hey @advlaser,
When you say add the number to Voxtelesys do you mean on the SIP trunk on 3CX?

Is the ATT trunk also setup on the 3CX? If so does it also use E164 formatting for the numbers?

Both Trunks are setup on 3CX. We are not using E164, but national format on both.

 

[advlaser]

No they said I could setup the numbers on both trunks and it will just seamless switch over. This would be perfect. I just can't figure how to pull that off. I'm sure it's something I'm doing wrong. As soon as I add the number to the DID list on VoxTeleSys trunk, it breaks. It's not even in the inbound rules for VoxTeleSys but is for AT&T.

 

[Kevin@voxtelesys]

If you change the number on the Voxtelesys Trunk to E164 does it start to work on the ATT trunk?
Your outbound can still be in National format for calling.

* If you want to do any messaging E164 is required in the 3CX end.

FYI found the port and routing is still with ATT at this time.

 

[advlaser]

So on the 3CX end, that means prepending +1 to all of the phone numbers setup in DID on the SIP Trunk?

 

[SteveITS]

Voxtelesys requires/sends the +1 so the DID has to match.

 

[Kevin@voxtelesys]

@advlaser Yeah try setting the numbers up with E164 formatting on the 3CX, or create the duplicate inbound routes on the national format numbers and see if that takes care of the incoming route issue.

@SteveITS we actually support National (10 digit), E164 no plus (11 digit) and E164 formatting for incoming calls, you can adjust this in the portal on your inbound trunk, its recommended and default setup on the trunk for E164 formatting. For outbound trunks its recommended setting the trunk to national as national will accept 10 digit, 11 digit, and E164 formatted outbound calls, again outbound trunk is setup on national by default.

 

[Kevin@voxtelesys]

@advlaser I see you changed your trunk to E164, did changing the numbers to E164 on the Voxtelesys Trunk fix the issue?

 

[AWS2P]

Could it be possible to let Voxtelesys Trunk unregistred until you really need it and see if as a workaround it works fine?

 

[advlaser]

@advlaser I see you changed your trunk to E164, did changing the numbers to E164 on the Voxtelesys Trunk fix the issue?

Switching to E164 did seem the fix the problem. I'll have to say VoxTeleSys has fantastic support. Even when support is closed for the day someone seems to be monitoring the 3CX forum. Nice job VoxTeleSys!