Hi John, Everything I read, even in the opensips source code (grep_sock_info_ext function) shows it is only comparing Route headers values to its local IP addresses. Whatever I set, comparison is always made with IPs not FQDN.
I do use domain modules for other tests and functions but according to my tests, domain module is not linked nor « consumed » by loose_route(), so that doesn’t solve my issue. I wonder if the reason I face this problems is not because: - I use the same IP address to talk to Microsoft as to talk to my internal devices => If IP would be different on the « WAN » and « LAN » side, maybe that would be much easier for opensips to match? - I use UDP TLS with Microsoft and UDP with my internal devices => If protocol would be the same, there won’t have to switch between sockets? Maybe a mix of both… Or maybe most people using OpenSIPS with Teams don’t use it for multi-tenant, use it statically or have done the same « cooking » I made without complaining ;-) Thank you for you reply :-) > Le 21 févr. 2023 à 15:40, John Burke via Users <[email protected]> a > écrit : > > Hey Daren, > > Aliases should work I believe, however, you can also use the domain module[1] > to dynamically maintain “local” FQDNs. > > [1] https://opensips.org/docs/modules/devel/domain.html > > Sent from my iPhone > >> On Feb 21, 2023, at 8:33 AM, Daren FERREIRA <[email protected]> wrote: >> >> 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 >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> -- >> Please be cautious! This email was sent from outside of Voxtelesys. > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
