Call forwarding to mobile is always forbidden on 3CX v.20

Status
Not open for further replies.

bytesolutions

Bronze Partner
Joined
May 30, 2016
Messages
80
Reaction score
10
Good morning everyone.
I'm creating a test configuration to transfer incoming calls on Trunk A to a mobile number, via Trunk B.
I configured trunk A as the default route extension 15.
Inbound trunk1 config.JPG
In the settings of extension 15 I entered the destination mobile number and I set to transfer calls to the mobile phone if the extension is not registered.
User Forward config.JPG
In the outgoing rules I created a new rule where I declare that calls departing from extension 15 must use trunk B as the route.
Outbound trunk2 config.JPG
If I register extension 15 on the 3CX App I receive calls from Trunk A, and I can also make calls via Trunk B.
If I de-register from the 3CX App according to the rule created, calls to extension 15 should be transfered to my mobile.
Well, this feature doesn't work. 3CX gives me this message:
--
The call or registration to 34800*****@(Ln.10002@Generic VoIP Provider) failed.
sip:109.233.129.13:5060;lr responded; Forbidden (403)
--
Thinking it was a VoIP provider problem, I tested the configuration with three different providers, but all returned Forbidden.
I set up the exact same configuration on a 3CX v.18 and it works fine on that system.
I tried to do a wireshark capture to understand what doesn't work in the request to which the operators reply "Forbidden" but in v.20 the wireshark capture is not yet available.
Is anyone usin forwarding to mobile phone via a different trunk than the inbound trunk? on 3CX v.20? Works?
Thanks everyone
 
The forbidden error though is coming from the provider side which means that the call is sent from the PBX.
This has to be checked from your provider.
 
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,079
Members
164,899
Latest member
mazet