[SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)

The request domain is wrong should be your Fqdn not a pstnhub domain, Set $du to the pstnhub url, also make sure you present the matching tls cert based on the sni of your fqdn You would probably have a decent reason appended to the 400 response, for all its lack of clear documentation the one thing team's does well is its error responses, if your not getting a reason your generally failing at the tls handshake stage (and that's usually not explicitly setting the sni value for tls to use on the way out to teams) its a tls issue and you need to explicitly set the domain to use for sni in your config. The record-route header is pretty forgiving inside the teams black box, I regularly append custom key value pairs to it in production when tracing flows through system, not tried it with a null value though but in my experience teams don't care. ------------------------------ *From:* Kaufman &lt;bkaufman(a)bcmone.com&gt; *Sent:* Thursday, December 29, 2022, 4:11 PM *To:* Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.org&gt; *Subject:* [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) In your top Record-Route you have: socket=; Not sure if that is legal. Kaufman -----Original Message----- From: Alex Balashov &lt;abalashov(a)evaristesys.com&gt; Sent: Thursday, December 29, 2022 9:02 AM To: Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.org&gt; Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) Sorry to hear you're having to interoperate with Teams. It's a unique form of sadism I wouldn't wish upon anyone. A few theories: 1) Microsoft doesn't like the "bare" Contact header-value here: Contact: sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE :5061;transport=tls Unlike the careted one right above: P-Asserted-Identity: <sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE> A bare URI absent other header-params is of course completely legal, but I'm really trying to get inside the imaginary world of antisocial "Microsoft SIP" here. 2) Could it be that antisocial "Microsoft SIP" sends 400 as a way of objecting to something in the SDP, e.g. where a non-demented SIP stack would send "488 Not Acceptable Here" or "415 Unsupported Media Type"? I know you've said you tried multiple clients to rule that out, but I wonder if the thing it's objecting to hasn't been ruled out that way. 3) I saw this media line in the SDP: m=application 41356 <unknown media type> What's that? -- Alex result in a 400 BAD REQUEST. From/To/Contact. I've also taken care to make sure that FQDN is used in Contact and Record-Route header. information here: something in the SDP or otherwise causing an issue. Endpoint is active, so this is successful. I also am able to receive calls FROM teams to my IP phone(s) without issue. It is only when I try and call INTO teams (INVITE -> Microsoft Teams) that I always receive a 400 BAD REQUEST to my INVITE. the sender! -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.evaris…p;reserved=0, https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpsw… __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: