Solved Outgoing calls failed in Teams with 3CX Integration

[MegabyteInfra]

Hello,

My outgoing calls not work in my Teams/3CX Integration.
Incoming calls (internal and external) worked perfectly.
It seems to be a problem with port 5062.

Errors found in Teams Console:

Direct routing:

Outbound calls:

My analyse:

1. 3CX Service is listenning on port 5062



2. Port 5062 not open



3. Check the Key and Cert file with openssl command and results are identical:
Certificate is not a wildcard and come from ssl.com



4. 3CX VM has been generated with pbxexpress wizard and heberged on OVH Infrastructure (I ask OVH if the 5062 port is open and it is ok)

Is anybody can help or have an idea ?

Thanks.

 

[NickD_3CX]

Hi!

Can you send me in a PM that FQDN so I can check the port as well?
I know you said that OVH said, it's open for TCP, but with what you have checked, that is the most likely thing in my eyes.

 

[NickD_3CX]

After checking, it seems like the TCP 5062 port is indeed closed on the Firewall.

We tried doing telnet from machine itself to its LAN IP on port 5062 and it connected.
Then tried doing telnet from an external machine to the Public IP port 5062 and it timed out.

 

[MegabyteInfra]

Hello,


OVH confirm that there are no restrictiions on the firewall but it is not really true.
I find this post on french 3cx forum explaining this problematic when you create your 3CX instance with the pbxexpress wizard: https://www.3cx.fr/forum/threads/problème-pare-feu.100054/
You have to manually add a rule to the "pbxexpress" security role to open port 5062 via the openstack horizon console.



Problem solved but remember: "Never follow what OVH technicians tell you"

 

[NickD_3CX]

I am really glad to hear that you managed to figure out the issue!