Solved Microsoft Teams Integration V18

[Evolute IT]

I can tell you that telnet on your 5062 port does not answer. 5060 and 5061 does...

Odd. It is opened in my firewall.

Does 3CX itself have a built-in firewall? Maybe I need to allow it there.

 

[StefanW]

Just installed the SSL and did a reboot of the server (it didn't prompt for a restart of the service this time so I didn't take any chances.)

This is normal as the transport had been already created and we just need to call certificate update.

 

[Evolute IT]

This is normal as the transport had been already created and we just need to call certificate update.

Alright.

Is there a firewall built into the ISO? I think the only place the port could be closed is on the VM itself, because my ports are opened in every place before that AND I confirmed it works using another VM that I had put a website on 5062 for testing.

Everything else just works.

 

[Evolute IT]

Alright.

Is there a firewall built into the ISO? I think the only place the port could be closed is on the VM itself, because my ports are opened in every place before that AND I confirmed it works using another VM that I had put a website on 5062 for testing.

Everything else just works.

@ChrisC_3CX @JohnS_3CX @NikosT_3CX

One of you knows?

 

[NikosT_3CX]

@Frederick Marcoux check this command : nft list table inet filter
Do you see port 5062 there ?

 

[Evolute IT]

@Frederick Marcoux check this command : nft list table inet filter
Do you see port 5062 there ?

Nope.



The instance was installed using the Debian 10 ISO for V18 Alpha 4, and I just updated since then. Port 5062 isn't anywhere here.

 

[NikosT_3CX]

@Frederick Marcoux do me a favor and add it..
And lets take it simple, make an netstat on the OS to check port 5062 is listening and an external check with this : https://ping.eu/port-chk/

 

[Evolute IT]

@Frederick Marcoux do me a favor and add it..
And lets take it simple, make an netstat on the OS to check port 5062 is listening and an external check with this : https://ping.eu/port-chk/

How do I add it to the filter rules? I never used Debian 10 firewall. Only UFW and IPTABLES.

Also, will this make my installation unsupported since I am modifying the OS?

 

[Evolute IT]

So, I figured out how to modify the firewall tables. I had to edit "/etc/nftables.conf", added 5062 in the TCP part of the PBX and then saved and rebooted.

Now, calls are going through successfully. Somehow, the 3CX didn't add that rule for that port on enabling Direct Routing or in the upgrade part.

By the way, when we call voicemail, it asks for extension number and PIN, like it doesn't know who's calling.

 

[StefanW]

By the way, when we call voicemail, it asks for extension number and PIN, like it doesn't know who's calling.

I don't think we will address this in the near future für this call flow case.

 

[StevenTillson02]

That's not what Teams docs say.

So I would need a new cert just for this? Kinda redundant.

And why does the SSL docs of 3CX says it does support wildcard certs?

All this is really not clear. I know it's Alpha but the doc needs more details lol

I never knew this is even possible at all. Thanks

 

[StefanW]

I never knew this is even possible at all. Thanks

Referring that there is MS Teams Direct Routing integration?

 

[Kobo Williams]

I sue a custom FQDN with my 3CX which is a different domain (domain.com) than my teams domain (seconddomain.com). The cert I need to create is just for my sbc.seconddomain.com correct? I tried using a wildcard cert we already have for *.seconddomain.com and I get an orange triangle alert for the domain in Teams on the Direct Routing page.

 

[Evolute IT]

I sue a custom FQDN with my 3CX which is a different domain (domain.com) than my teams domain (seconddomain.com). The cert I need to create is just for my sbc.seconddomain.com correct? I tried using a wildcard cert we already have for *.seconddomain.com and I get an orange triangle alert for the domain in Teams on the Direct Routing page.

Wildcard are not supported. I tried. You need an SSL certification for the Teams SBC Domain you chose.

The reason why this is the way is because Teams SBCs are required to be under your O365 domain (which is stupid).

 

[Kobo Williams]

Wildcard are not supported. I tried. You need an SSL certification for the Teams SBC Domain you chose.

The reason why this is the way is because Teams SBCs are required to be under your O365 domain (which is stupid).

That did it, all working now!