Solved VoIP.ms Setup...

[jmh-itsjessnetworks]

Hi,

I have registered a Voip.ms account and have gotten it to register with 3CX. I can receive calls, I cannot place calls. I believe that I have setup outbound rules properly.

Any help is greatly appreciated.

 

[ChrisC_3CX]

Do you get a specific error in the Dashboard?

To check if it's an Outbound Rule issue, best thing to do is simply create an Outbound Rule that would allow all calls to go through. Just create an outbound rule that only has a prefix defined that matches all digits. Set the prefix to 0-9. Set the first route to be the VOIP.MS SIP Trunks and save. Move the rule to the very top of the list and then try making a call from an extension to an external number that contains only digits(no + sign,etc), does it work?

You might also want to take a look at our guide for configuring VOIP.MS and make you haven't missed anything: https://www.3cx.com/docs/voip-ms-canadian-sip-trunk/

 

[jmh-itsjessnetworks]

Do you get a specific error in the Dashboard?

To check if it's an Outbound Rule issue, best thing to do is simply create an Outbound Rule that would allow all calls to go through. Just create an outbound rule that only has a prefix defined that matches all digits. Set the prefix to 0-9. Set the first route to be the VOIP.MS SIP Trunks and save. Move the rule to the very top of the list and then try making a call from an extension to an external number that contains only digits(no + sign,etc), does it work?

You might also want to take a look at our guide for configuring VOIP.MS and make you haven't missed anything: https://www.3cx.com/docs/voip-ms-canadian-sip-trunk/

I've just tried it. The error I'm getting is this: Call or Registration to ########54@([email protected]) has failed. 158.85.70.148 replied: 503 Service Unavailable; from IP:158.85.70.148:5060

I have indeed taken a look at the guide. I can receive, but cannot place calls. I am truly stumpped.

 

[ChrisC_3CX]

Provided that IP 158.85.70.148 is the provider's IP, they are the ones replying with the error so your 3CX PBX is actually sending out the call, meaning that your Outbound Rules should be fine.

There are instances where provider's may not allow calls with Caller IDs set to anything other that the numbers associated with an account. To test this, you can try editing your Outbound Rule and populate Route's 1 "Outbound Caller ID" field with your main trunk number to make sure that this is the number getting sent outward(try only digits as special characters are sometimes not supported).

If that fails too, you might actually need to reach out to your provider to get more information on why they are replying with that error message.

 

[jmh-itsjessnetworks]

Provided that IP 158.85.70.148 is the provider's IP, they are the ones replying with the error so your 3CX PBX is actually sending out the call, meaning that your Outbound Rules should be fine.

There are instances where provider's may not allow calls with Caller IDs set to anything other that the numbers associated with an account. To test this, you can try editing your Outbound Rule and populate Route's 1 "Outbound Caller ID" field with your main trunk number to make sure that this is the number getting sent outward(try only digits as special characters are sometimes not supported).

If that fails too, you might actually need to reach out to your provider to get more information on why they are replying with that error message.

That doesnt seem to be the issue. After looking at the error, 3CX might be trying to use the wrong SIP URI; I think it's trying to use [email protected] when it should be using 431#####38(trunk#)@sip.voip.ms . Could that be possible?

 

[leejor]

If you suspect that information is incorrect, then that will be in the VoIP trunk settings, in 3CX. VoIP.ms has a number of servers. In your initial set up, on their website, you would have chosen a particular server. That is the one you will use in the trunk settings.

 

[YiannisH_3CX]

After looking at the error, 3CX might be trying to use the wrong SIP URI; I think it's trying to use [email protected] when it should be using 431#####38(trunk#)@sip.voip.ms . Could that be possible?

That error is for you, to tell you which trunk the error came from. The 10001 is the internal extension of the trunk assigned by the PBX and it is not sent out. To see what the is sending out you should be looking in the Activity Log. Set the logging level to verbose for more details and try another call. Filter by that call and you will see all the details.

 

[jmh-itsjessnetworks]

That error is for you, to tell you which trunk the error came from. The 10001 is the internal extension of the trunk assigned by the PBX and it is not sent out. To see what the is sending out you should be looking in the Activity Log. Set the logging level to verbose for more details and try another call. Filter by that call and you will see all the details.

Thank you for your reply. I have fixed the issue.

 

[jmh-itsjessnetworks]

If you suspect that information is incorrect, then that will be in the VoIP trunk settings, in 3CX. VoIP.ms has a number of servers. In your initial set up, on their website, you would have chosen a particular server. That is the one you will use in the trunk settings.

Thank you for your reply. I have fixed the issue.