New SMB install. Using VOIP.MS. Calls come in, but cannot go out

[Dan Jennings]

Calls are routing in fine, but calls placed out only get Forbidden message in 3CX app, call fails, busy signal. I have checked the trunk number and have it at 575XXXYYYY but also added a "1" in front as well as tried with a "+1". Nothing I have tried on 3CX or VOIPMS side fixes problem.
Opened a ticket with 3CX. Since there is no visible logging in this SMB version I cant use my typical troubleshooting. 3CX support found the log shows
----Failed. 208.100.60.30 replied: 403 Forbidden; from IP:208.100.60.30:5060----
But essentially directed me to open a ticket with VOIP.MS

Has anyone used VOIPMS with 3CX SMB? And if so do you have any tips I can try to make outgoing calls work?

Thanks for any help.

 

[Charles_3CX]

Have you contacted VoIP.ms If so, what was their reply?

 

[Dan Jennings]

Created a ticket with VOIPMS. No reply yet.

 

[Charles_3CX]

Ok, let us know what they say when they reply.

 

[YiannisH_3CX]

Has anyone used VOIPMS with 3CX SMB? And if so do you have any tips I can try to make outgoing calls work?

While waiting for a reply check that you are using the correct caller ID and not a caller ID from a different provider.

 

[Dan Jennings]

Was directed via 3CX documentation to set VOIPms to "I use a system capable of passing its own Caller ID".

After testing all day and into today I have found the issue to be sporadic. For a block of time, calls actually can be placed and they do so fine. And after some unknown amount of time, calls cannot go out and have the busy signal and Forbidden. Then randomly later, calls can go out.

VOIPMS support is not seeing those calls that are not able to go out. They never even hit their servers. Thus it seems our 3CX instance is not getting those calls up to VOIP MS during that time.

I've also got a ticket open with 3CX support and I'm just copying and pasting each others' replies to try to get to the bottom of this.

Odd because I have used VOIPms on 3CX before (the original hosted environment, not the StartUP or SMB as its called now) just fine. Usually use Skyetel though

 

[Charles_3CX]

When sent out to them, we can still see your calls being forbidden from the VOIP—MS side.

Additionally, the calls are not ringing into the system as per tests performed from our side.

Can you please recheck with them? I have included a Wireshark capture of the outbound call in the ticket that you may send them for them to review.

 

[Dan Jennings]

Last thing I have tried which seems to have fixed the issue...

1) In VoipMS subaccount advanced settings enabled G.722 (don't know if this was just a coincidence), ensured device type is set to IP PBX
2) In 3CX trunk, changed the number to "+1575XXXYYYY" format.
3) Re-registered the subaccount and everything turned green
4) after testing multiple times over several hours, everything seems working now.