19 Dec
2023
19 Dec
'23
midnight
Voila, that's likely your problem.
*.onmicrosoft.com <http://onmicrosoft.com>* domains are not eligible for
Direct Routing.
When activating the SBC, the UPN's domain part must be the same as the FQDN
of the SBC you're adding.
Essentially, you have to do it all within the *abcsbc.com
<http://abcsbc.com>* AAD tenant, logged in as a superuser part of the
same *abcsbc.com
<http://abcsbc.com>* domain, matching the SBC's FQDN.
Regards,
Sergiu
--
*Teams PBX connector with full MS Direct Routing automation for service
providers**Web*: https://teamsphone.net
On Mon, Dec 18, 2023 at 3:47 PM faisal.jamil.khan--- via sr-users <
sr-users(a)lists.kamailio.org> wrote:
Kamailio is installed on AWS obviously behind NAT.
Cert signed: Let's ecncrypt
However, I have a questions here:
I have a registered account at faisal(a)7v840c.onmicrosoft.com but the
domain for which we created SBC is abcsbc.com and we have an active user
faisal.ahmad(a)abcsbc.com under the domain.
We have created the SBC under voice routing on this account
faisal(a)7v840c.onmicrosoft.com.
SBC Network effectiveness
TLS connectivity status SIP OPtions status
abcsbc.com 0%
Inactive Warning
Is this the correct way to setup SBC under the main account or should I
have to create the sbc by logging in to the account of
faisal.ahmad(a)abcsbc.com.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe: