Solved Remote Extension Ring Mobile Simultaneously Fails

[skywaveorg]

When a remote extension calls an internal extension with ring mobile phone simultaneously enabled, it fails to call the mobile phone and I get an error:

Call or Registration to +1xxx2787xxx@(Ln.10001@Twilio) failed.
11.11.11.1 replied: 403 Forbidden; from IP:11.11.11.1:5060

What do I need to configure so remote extensions have the same functionality as internal extensions when dialing someone?

 

[leejor]

Is the extension, permitted, in it's settings, to place calls to outside numbers?
If they dial the same number, from the set, does the call go through?

 

[YiannisH_3CX]

The error comes from Twilio so for some reason the call to the external number fails in that scenario. First step is to call the mobile number directly and see if that works.
Then check the mobile number format under the extension settings and make its in the correct format to be dialed.
Lastly check the outbound caller ID used when the call to the mobile number is made and make sure its correct.

 

[leejor]

Sorry, I missed that....probably passing on the original caller ID (extension number?) , which the provider does not like.

Does the extension placing the calls have an outside caller ID defined?

If you find it is a caller Id issue (check the Activity log, or confirm with provider), you could create a separate outbound rule, just for the one mobile number, that adds the main office number as caller ID, to keep the provider happy. Place that above the regular rule.

 

[skywaveorg]

Yeah I forced a caller ID on the trunk to the default outgoing number and it's still not working. Twilio provides a tcpdump for each call so I can send that to someone to see what exactly is going on.

EDIT:
I changed Remote Party ID - Calling Party : User Part in the trunk to:
"LineNumber" external number of line
originally which causes that error. If I change it back to the default:
"OriginatorCallerID" Original Caller number will be sent

I get this error:
Call or Registration to +11112187154@(Ln.10001@Twilio) failed.
10.170.60.1 replied: 400 Invalid Caller ID.; from IP:1.1.1.1:5060

If I set it to something that uses the trunk default outgoing number, I still get the invalid caller id error (its in the correct format, +1xxxxxxx).

I originally changed that parameter since it didn't ring an extension's cell phone even with internal numbers. It resolves that issue for internal extensions but still persists on remote extensions. This may be a 3CX bug?

 

[YiannisH_3CX]

For this to be a 3CX bug it would mean that 3CX is not sending what it is configured. Since when you change something the error changes then I don't think this is the case but you can confirm by running a pcap on a call and seeing what is being sent by 3CX or by using the 3CX activity log.
You will need to set it to verbose logging to capture maximum details.

So no calls are currently working?

 

[skywaveorg]

For this to be a 3CX bug it would mean that 3CX is not sending what it is configured. Since when you change something the error changes then I don't think this is the case but you can confirm by running a pcap on a call and seeing what is being sent by 3CX or by using the 3CX activity log.
You will need to set it to verbose logging to capture maximum details.

So no calls are currently working?

All calls work with either setting for Remote Party ID - Calling Party : User Part, remote extensions can dial out with no issue either. The only issue is when a user dials an extension configured to ring their mobile phone. Then it doesn't work until I change Remote Party ID - Calling Party : User Part to "LineNumber" external number of line. Everything then works when dialing an extension internally and when a user calls in and the IVR goes to an extension. The only thing not working is when a remote extension dials any other extension, it doesn't ring that extensions mobile phone and I get the error above.

 

[YiannisH_3CX]

Ok have a look at this reply and apply the same changes. Then test all scenarios and see if something is not working.

 

[skywaveorg]

Ok have a look at this reply and apply the same changes. Then test all scenarios and see if something is not working.

I have not forgotten about this, holidays are delaying this. I made the firewall changes but have been unable to test. Will respond next week.

 

[skywaveorg]

@YiannisH_3CX Okay it did not resolve the issue, I configured our 100F firewall to disable SIP-ALG and it is still producing the same error.

 

[skywaveorg]

I changed P-Asserted Identity : User Part to "LineNumber" external number of line and it is working now.

 

[YiannisH_3CX]

Glad to see you were able to resolve the issue