May 31 2021 11:43 PM
May 31 2021 11:43 PM
Hi There Forum,
I have one question and I hope I can be proven wrong.
Has anyone here actually without the help of Westcon or AudioCodes gotten the MS-Teams Multi Tenant configuration working from an AudioCodes SBC perspective.
When following their and MS documentation for the customer tenants all you need to do is to manipulate the contact header to their tenant SBC FQDN and the call will go to that client. (Calls to the primary/base/sp tenant works like a charm, that is the one you enable the proxy set with on Audiocodes)
I have tried that call gets no where, BUT if I do a Call-id header manipulation and add the client FQDN into the call-id I actually get the MS-Teams client to be alerted, but then I get the message the call cannot be completed at this time, and in the syslog files it comes up with a warning that it cannot find a matching transaction for response 100, 180 and 183.
If I follow the explanation below and example below and I only manipulate the contact header for say sbc1.customer.adatum.biz the call don't even get to that teams tenant.
So if I only change the contact header the call gets canceled from the providers side.
If I change the contact header to firstname.lastname@example.org. customer.adatum.biz as well as with a regex manipulation change the call-id from CALL-ID: email@example.com to CALL-ID: firstname.lastname@example.org the call actually alerts the teams client but you get the Microsoft voice telling you the call cannot be completed right now, the client gets to call alerts you answer the first one you get the ladies voice, you answer the second one it seems like teams is trying to call the calling number back.
Incoming call with contact header and call-id changed to sbc1.customer.adatum.biz
Jun 05 2021 09:58 PM
I've worked with a couple of vendors/telcos that have this kind of configuration without any issues.
I've looked over the details on doing this, but most of my customers self-host so I've not had to go through the details.
A couple of things worth looking at:
Do you have more details from the logs? While the SIP flow is handy, there's sometimes details in the logs that show more details. Have you turned up logging in AudioCodes to see if there are any additional log details?
What about outbound calling from Teams?