VOIP.MS

[jtcreate]

I am experimenting with 3CX for eventual long term service. I registed some DIDs with VOIP.MS and followed the setup instructions under 3CX. But any incoming calls to the DIDs are not being routed through 3CX to my account. All I get is a busy signal. I followed the 3CX instructions completely and confirmed all the setups in VOIP.MS Everything is correct. I finally had a chat sessions with VOIP.MS tech support who did a packet trace on the SIP trunk. This was their findings:

Brendon 10:22 AM
Ok, I see what's happening now
Your 3CX is replying to the invites with a SIP 407 Proxy Authentication required, so in other words your 3CX is asking our POP servers to authenticate to it.

This shouldn't happen as we don't have any means to authenticate to you, so you'll need to ensure incoming invites will not require authentication
I can also send you the pcap file if it has any use for you.

Since this is 3CX hosting and not an onsight PBX setup, I can't find anything in the account admin settings to deal with this, including any capability of whitelisting VOIP.MS POP IP address. Basically I am stuck. Why is 3CX allowing this policy to happen when they are supposed to be compatible with VOIP.MS and have setup instructions for that service?

 

[N_G]

VoIP.ms has only recently started supporting 3CX. It should work out of the box but support should come directly from Voip.ms. I have sent them the thread to look into it.

 

[jtcreate]

VoIP.ms has only recently started supporting 3CX. It should work out of the box but support should come directly from Voip.ms. I have sent them the thread to look into it.

I can provide the pcap file if you need. Its definitely not working out of the box. I can make outgoing calls, but incoming calls are hitting the snag. Also, another thing I didn't mention is that after extensive inbound testing, 3CX drops its connection with the VOIP.MS POP server. The break never restores. The only way to fix it is to move to a different VOIP.MS POP server. I've had to do that three times.

 

[Charles_3CX]

May I ask in which format you have added your DID numbers to your VoIP MS SIP trunk?

Did you add them in E164 international format?

 

[jtcreate]

Yes, I added them as E164. I believe that is the only way 3CX would accept the entry. I can make outgoing calls, but not receive inbound.

 

[Charles_3CX]

Does the event log under the admin console show any errors in relation to the inbound calls?

 

[jtcreate]

It shows the inbound calls for those DID as "failed". According to VOIP.MS, their service is attempting to handoff the call to 3CX, however, the handoff fails after that. VOIP.MS says 3CX server is looking for VOIP.MS POP server to authenticate. Their POP servers do not authenticate, nor require authentication.

 

[Charles_3CX]

In this case, and since the settings are correct on the other 3CX side, continue with VoIP MS as suggested by our CEO, as this will need further checking from them.