Outbound Calls - Forbidden By Administrator

[jmc-tim]

I have been intermittently getting an audio error message "Forbidden By Administrator" when trying to place and outbound call. The problem is resolved if I reboot the phone from the 3CX Cloud PBX Dashboard. I spent half an hour with the 3CX AI and was finally told to come here and post the info below:

> PRO Edition, 8-SC Trial, 3CX-hosted Cloud, version 20.0.995 SP9. Hunter Communications trunk, line 10000, proxy resolving to 216.xxxxx:5060 over UDP. Outbound calls to 5418xxxxxx and 15418xxxxxx failed at approximately 11:42 AM Pacific on September 18, 2026. Event 12294 shows the provider returned SIP 403 Forbidden for both attempts. Trunk Analysis reported registration successful at 11:32 AM, while Outbound Call Test reported “No registration found.” Allowed Country Codes permits North America. Phone reboot temporarily restored calling earlier, but the cause remains unresolved.

Also this from my 3CX PBX Event Log:

Warning	12294	09/18/2026 11:47 AM	SIP Server		Call or Registration to 5414xxXXXX@(Ln.10000@Hunter Communications) has failed. sip:216.xxxxx:5060;lr replied: Forbidden (403)
Warning	12294	09/18/2026 11:42 AM	SIP Server		Call or Registration to 5418xxXXXX@(Ln.10000@Hunter Communications) has failed. sip:216.xxxxx:5060;lr replied: Forbidden (403)
Warning	12294	09/18/2026 11:42 AM	SIP Server		Call or Registration to 15418xxXXXX@(Ln.10000@Hunter Communications) has failed. sip:216.xxxxx:5060;lr replied: Forbidden (403)

Any help that can be provided would be appreciated.

Tim

 

[KyriacosS_3CX]

If you call from the same extension via the web client (at a time when it is failing from the phone), does the call go out?

 

[leejor]

Event 12294 shows the provider returned SIP 403 Forbidden for both attempts.

It sounds as if you should be talking to your provider, about why the call was forbidden, as it would appear that they are blocking it. It may be the dialled number format, but may also be the caller ID you are sending, on some calls.
The 3CX Activity Log would also confirm if this is indeed the case.