Recent content by NormanMichaelis

good morning ccweblink. In terms of the licensing, each user in Teams needs a license: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#licensing-and-other-requirements I had/have E3 licenses, and had to add extra on the package to get it working. to get it working: For...

Hi all that are following, I have fixed/sorted by inbound problem, when the call enters fusionpbx, it did not have the correct domain_name set, so I created a new context dialplan Destination for just the calls coming from the TeamsSBC. then set domain_name as per the domain_name of the...

Hi Rob [server:default] method = TLSv1.2 verify_certificate = yes require_certificate = yes private_key = /etc/letsencrypt/archive/<FQDN>/privkey1.pem certificate = /etc/letsencrypt/archive/<FQDN>/fullchain1.pem ca_list = /etc/letsencrypt/archive/<FQDN>/bc2025.pem server_name = <FQDN>...

Hi Rob I believe this is what you are looking for: https://docs.shanehoey.com/directrouting/planning/certificate And yes, it's a trunk, I just think I am not getting my head around the context's. In asterisk terms the trunk needs to be in context from-internal.

Hi everyone, I have, last week, managed to get Teams Direct Routing running with Kamailio and a LetsEncrypt Certificate. In my setup, I have local FusionPBX extensions as 1XXX and the Teams Users on 2XXX, so a simple outbound route handles that perfectly. My problem is the inbound from Teams...