Yeah, the grammar says that rr-params are just generic-params, in which case it's not. I didn't see that -- nicely spotted!
I think that may be the basis of the 400 Bad Request. I'd be shocked if it weren't. The broken clock of "Microsoft SIP" can still be right twice a day. > On Dec 29, 2022, at 10:31 AM, Kaufman <bkauf...@bcmone.com> wrote: > > In your top Record-Route you have: > > socket=; > > Not sure if that is legal. > > Kaufman > > -----Original Message----- > From: Alex Balashov <abalas...@evaristesys.com> > Sent: Thursday, December 29, 2022 9:02 AM > To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org> > 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 > >> On Dec 29, 2022, at 9:51 AM, Brandon Armstead <bran...@cryy.com> wrote: >> >> Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) always >> result in a 400 BAD REQUEST. >> Example invite below: >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpast >> ebin.com%2FF1G1Ce59&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739 >> a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638 >> 079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 >> luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cbff6B4gNr8 >> A9zs89smJ129y8IyNM9%2B3zVkGhlzpa54%3D&reserved=0 >> I've taken care to make sure numbers are all E.164 format in >> From/To/Contact. I've also taken care to make sure that FQDN is used in >> Contact and Record-Route header. >> I've tried many different variations and have followed the SIP information >> here: >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flear >> n.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols-si >> p&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9b0c >> 9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531%7C >> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h >> aWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GO26A9FOOoS42yMCWPPGo5PkKo75c >> kjSJSkjAeYRsU0%3D&reserved=0 I've also tried several different clients >> (Bria, Polycom CCX 600, Grandstream, etc) to see if maybe it was something >> in the SDP or otherwise causing an issue. >> SIP Transport is TLS, RTP is SRTP >> I might also add that OPTION pings are active and Direct Routing 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. >> Any help is appreciated, thank you! >> >> - Brandon >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions To >> unsubscribe send an email to sr-users-le...@lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to the >> sender! >> Edit mailing list options or unsubscribe: > > -- > 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.evaristesys.com%2F&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ItYjjYmm0QcD0vuQ4KamCrHtIF7UiukxxAp6zfrEgXQ%3D&reserved=0, > > https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswitch.com%2F&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DRWZOre6j7XZQhkCcKUvD%2B5dXH%2B4i3M2S5kz%2FleEJuo%3D&reserved=0 > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe > send an email to sr-users-le...@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-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the > sender! > Edit mailing list options or unsubscribe: -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
