Unable to ring mobile simultaneously

[TTBruce]

When using the ring mobile simultaneously feature, calls to my mobile are failing with the following error:

Call or Registration to XXXXXXXXXX@([email protected]) has failed. 192.175.96.72 replied: 503 Service Unavailable; from IP:192.175.96.72:5060

I am able to call this # from my desk phone, and if I set up the forwarding rules to call this number after my desk phone, the call goes through fine. This issue only arises when I am trying to ring my mobile phone simultaneously.

This problem exists for all extensions and for all mobile numbers. This feature worked fine previously, but suddenly stopped working. I don't think I've changed any of the settings on 3cx or Voip.ms to trigger this issue.

 

[eddv123]

503 Service Unavailable; from IP:192.175.96.72:5060

A 5xx style error is normally a server side error, however this above IP, do you know what it is as it could be something local (such as a PSTN gateway for example - not 100% on the subnetting) more information required about your outbound dialling required.

For this issue commonly the 2 things that crop up mostly are:

* Not enough Sim calls on your licence (I dont think this is your error).
* Insufficient outbound rule set for mobile calls.

 

[TTBruce]

That IP would be the voip.ms trunk. I've tried selecting a different trunk (changed config on both voip.ms and on the trunk settings in 3cx).

I have 2 outbound rules:
1) Apply to: Calls to Numbers with a length of 10
Make outbound calls on: voip.ms

2) Apply to: Calls from extension group(s) (DEFAULT: group containing all extensions)
Make outbound calls on: voip.ms

I've also tried creating a rule with no filters that points to the same trunk... same result. Again, I can still call mobile #s from my desk, and I can still forward calls when there is no answer. Only mobile ringing is affected.

Thanks

 

[eddv123]

Be certain the rule captures calls with the cell phones digits (for example 07 if here in the UK) and that there are no other rules above which supersede it.

 

[leejor]

Be certain that your outgoing caller ID is in the correct format. Countries are now requiring providers to block calls where the caller ID is not in the correct format. (valid number). In North America that will be XXX xxx-xxxx, or 1 XXX xxx-xxxx. If you add an access digit to incoming caller ID (so that number re-dial can be used), that may be sent on the outgoing leg, making the number invalid.

 

[TTBruce]

Thanks leejor, caller ID seems to be the issue here. When I pass caller ID from 3cx I get the issue, but when I force the callerID on the voip.ms side the calls go through.

 

[leejor]

I believe that Voip.ms (and other providers) was required to change their caller ID policy back in December. Depending on your location, that time frame may be different. Mobile companies are also (required?) now enforcing proper caller ID format/valid numbers, as an attempt to thwart phone scammers.

 

[TTBruce]

That's interesting because I remember when that change happened in December and I fixed everything so it worked again. Not sure what triggered it to break again, but it's working now anyways.

Will have to dig into the 3cx settings to see what caller id is being passed that is failing when I have a bit more time to dedicate to the issue.