Solved 403 Forbidden auth ID/INVITE

[Ilias_Mist]

Suddenly without any change in the PBX system (v16), all outbound calls are forbidden from all extensions, from ip phones and softphones. SIP trunks are normaly registered and incoming calls are going throught normaly. I played around with the from User Part in the SIP Outbound Parameters with no luck. Restored previous backups also with no result. Deleted and recreated trunks and extensions with zero results. No blacklisted IPs. Outbound rules work fine as shown below.
Can you make anything out of the logs to help me identify the problem?

Thank you beforehand.
Ilias

 

[cobaltit]

So first of all, you'll want to provide more information as per this thread:

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Secondly, if nothing was changed in the PBX system, it sounds like a firewall/provider issue which we can't really help you with. But I'd start with talking to whoever 213.144.173.77 is since they are rejecting your calls.

 

[AWS2P]

your sip port is set to 5070 ?
You have 2 route with same provider ?
As Cobaltit said i will call SIP provider support to ask why this 403.

 

[Ilias_Mist]

Thank you for your reply!

The version I'm runing is Standard Annual 16.0.676. The problem appears on a linux box and a Windows 2012 R2 Server, one hosted localy and the other on AWS. One system uses Fanvil X4G phones and the other only 3CX Android and Windows Desktop Apps. One is Localy provisioned and the other uses STUN. One has Static and the other Dynamic IP.
On each system the provider is different (one user 5060 and the other 5070) but both reject outbound calls with thoses messages respectively:
403 Forbidden auth ID and
403 Forbidden; warning: Invalid User

You see, the setup is very different but the problem is the same on both. The firewall checker is passed on both. Other setups I manage that are running still the v15.5 with the same providers are working fine.

The only change I'm aware of, since yesterday that the problem appeared, is the android app major update that requires v16 to work.

 

[AWS2P]

Only Android Phone are affected ? deskphone works fine ?

 

[Ilias_Mist]

I experimented with the Outbound parameters of SIP Trunk "Contact : User Part" and "From : User Part", played around with various combinations of "Default value" and "AuthId Athentication" and it worked.
What's curious is that those parameters were left on their default values, unchanged for more than a year and the system worked. That triggered the situation is unclear...
Thank you all for you replies.

 

[AWS2P]

Perhaps something change on sip provider this should be the common point, ask your provider?

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution. In the future when posting logs please try to hide sensitive information like FQDN's, public IPs and phone numbers.