<div dir="ltr"><div>John,</div><div><br></div><div>This is great, especially along side Alexey's blog post. I'm having a problem related to multi-tenant configuration. I suspect it's the result of something basic I've overlooked since I don't see it covered in your article.</div><div><br></div><div></div><div>An ancillary issue that I have is where I must use the FQDN <i>and</i> the IP in the added Record-Route header even though it's the same interface in both cases, and the domain resolves to the IP of the local interface. Something goes awry in the call setup, I believe something with replies. I haven't isolated it specifically yet. Calls do set up properly if I use something like <span style="font-family:monospace">record_route_preset( “SBC_FQDN:5061;transport=tls”, “SBC_IP:5061; transport=tls”);</span> however.<br></div><div><br></div><div>The more significant issue is related to <span style="font-family:monospace">alias=</span> definitions and customer tenant domains. I've been testing by with aliases defined for my carrier tenant and a single customer tenant domain. So far there's been a reasonable amount of success. The problem occurs when I send a call to Teams on a customer domain I don't have an alias defined for, using that domain in the Record-Route header as is required. Sequential requests' routing fails when OpenSIPS tries to route the call to the domain, which is really to itself but OpenSIPS doesn't realize it's local, and then...badness. Am I missing a way to define a wildcard alias of sorts? I was hoping the <span style="font-family:monospace">dns=yes</span> option would resolve those domains in real time and match the defined IP, but that didn't seem to work either.</div><div><br></div><div>I feel like I'm missing something simple.</div><div><br></div><div><br></div><div>Regards,</div><div>Jeff</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 6, 2021 at 5:44 AM John Quick <<a href="mailto:john.quick@smartvox.co.uk">john.quick@smartvox.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Hello all,<br>
The article I published last week talks about common issues you might<br>
encounter when commissioning a Microsoft Teams SBC solution built using<br>
OpenSIPS.<br>
It is designed to be read alongside the article by Alexey Vasilyev.<br>
<br>
<a href="https://kb.smartvox.co.uk/opensips/opensips-as-ms-teams-sbc/" rel="noreferrer" target="_blank">https://kb.smartvox.co.uk/opensips/opensips-as-ms-teams-sbc/</a><br>
<br>
John Quick<br>
Smartvox Limited<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>