Ovidiu is right, MS follows RFC. Nothing special, no magic. Yes, blog article assumes some basic understanding of how SIP proxy works, but all the necessary steps are there. And of course, there is no single universal solution for everybody.
You don't need to touch To, From, VIA headers and especially don't touch Contact. Contact header is modified only for OPTIONS request. James, you've posted doc from MS, there is part "Contact and Record-Route headers considerations" https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip#contact-and-record-route-headers-considerations They write there, use Contact modification only for OPTIONS, otherwise use Record-Route. That's it, nothing more. And it works exactly as written. May be your FS configured wrong? At least I don't understand, how properly configured PBX can put two times the same URI parameter "transport=tls". Check this please. ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
