Call forbidden by the administrator and internal calls not ringing on the other end

[Ibo]

I upgraded to V20 two days ago. I recently gained access to my Chime SDK after being flagged. The system was compromised and we rotated security credentials and such.

Now after getting unblocked all outgoing calls are forbidden by the administrator even though none of the settings have changed and internal calls are being rang from agent to another but doesn't show up as ringing in the reaching end.

They do show up as missed calls after.
I am a beginner to 3CX and I would appreciate the help. Also outbound rules are right, voice connector and everything.

 

[Alphabetic]

If your internal calls arent working, i would look to sort that first.

Have you restarted the PBX?

Make a test call and review the logs.

 

[Ibo]

Internal calls work if I register the extension to the PBX. The only way to do that that I've found out since upgrading to V20 is by scanning a QR code on the phone application.

I've restarted the PBX but it's still the same. I used to be able to make calls from a desktop / browser application now I'm limited to an actual phone. None the less internal calls are not an issue as much as outbound calls are.

I'm getting this voicemail " Forbidden by Administrator" despite not changing any settings from v18 to v20 and I cannot figure out what is forbidding outbound calls. From the logs, calls are getting intercepted within the PBX. The connection to the voice connector is blocked from within the PBX

 

[Alphabetic]

What do you use on the desktop?

are you using the correct URL now as the jump from v18 to 20 drops the default port 5001 to 443.

Are you able to call using the web client?

the forbidden message could be that your SIP provider is blocking your calls again.

Try a trace and check to see whats happening.

you could also set logging to verbose and check.

 

[Ibo]

I was able to fix the problem with logging to verbose. It was giving a 443 error so the voice connector was blocking it.

Thank you for your help

 

[Ferrell C Fuller]

I was able to fix the problem with logging to verbose. It was giving a 443 error so the voice connector was blocking it.

Thank you for your help

What was the exact fix? We have the same issue.

 

[Ibo]

whitelist the ip in the voice connector ips. It switched for me after I updated.

The problem is at your voice connector if it's 403

 

[Ferrell C Fuller]

Can you send me a screenshot? Thanks!

whitelist the ip in the voice connector ips. It switched for me after I updated.

The problem is at your voice connector if it's 403