[OpenSIPS-Users] Tips for troubleshooting OpenSIPS as a Teams SBC

[Jeff Pyle]

John,

This has worked brilliantly -- the domain module took care of teaching
OpenSIPS what's local.  As far as a single versus double RR, the problem
turned out to be with a downstream SBC that couldn't resolve the domain
name properly.  Once fixed, the single RR works as expected.


Regards,
Jeff


On Tue, May 11, 2021 at 7:07 AM John Quick <john.quick at smartvox.co.uk>
wrote:

> Jeff,
>
> Regarding the first issue you mention, have you tried:
> record_route_preset(“SBC_FQDN:5061;transport=tls”);
>
> In other words, have you tried it with a single rather than a double RR
> header?
> You would need to remove the ";r2=on" parameter of course.
>
> In theory, if the SBC_FQDN resolves to the IP address and everything
> communicating with your SBC is (a) capable of resolving the FQDN and (b)
> capable of routing to the SBC, then it should work.
>
> In my script I added " AS SBC_FQDN:5061" on the end of the tls
> listen/socket statement. I cannot remember if that was essential for it to
> work, but I leave it there on the basis that it cannot do any harm and
> might do some good.
>
> John Quick
> Smartvox Limited
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210513/03d06f4f/attachment.html>