[OpenSIPS-Users] OpenSIPS and Teams - Route headers and FQDN

Karsten Wemheuer kwem at gmx.de
Tue Feb 21 15:48:03 UTC 2023


Hi Daren,

because you mention MS Teams: do you know the blogpost "OpenSIPS as MS
Teams SBC" [1]? Maybe the description will help you.

Have a nice day,
Karsten

[1] https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/

Am Dienstag, dem 21.02.2023 um 15:30 +0100 schrieb Daren FERREIRA:
> Hello,
>
> According to my understanding of OpenSIPS Route headers management
> with loose_route function, it is only able to test matching between
> local listening IP addresses and Route headers, not with FQDN.
>
> In other words, if FQDN are presents in Route headers, they are
> compared to local IP addresses (well visible in logs), so, this never
> matches and you get a "WARNING:rr:after_loose: no socket found to
> match 2nd RR"
>
> This has never been a limitation until I had to work with Microsoft
> TEAMS, that requires the use of FQDN in Route headers.
>
> I tried using aliases, Route headers tags, and lots of other things,
> without success…
>
> Even if aliases would have been a solution, that is not a scalable
> solution when using OpenSIPS as a multi-tenant SBC for Teams (as
> aliases changes require an OpenSIPS restart).
>
> The only workaround I found was rewriting $du and $socket (so
> partially reimplement loose_route() ) based on context values stored
> in dialog variables (that’s working quite well anyway).
>
> Many people seems to use OpenSIPS successfully with TEAMS and nobody
> seems to have publicly complained about such limitations on forums.
>
> I may have missed something, and so I wonder what can be done to
> better work with Route headers.
>
> Do anybody have any idea on what I may have missed?
>
> Thank you for your advices and comments.
>
> Daren
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users




More information about the Users mailing list