Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) always result in a 400 BAD REQUEST.
Example invite below:
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://learn.microsoft.com/en-us/microsoftteams /direct-routing-protocols-sip
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
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 brandon@cryy.com wrote:
Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) always result in a 400 BAD REQUEST. Example invite below: https://pastebin.com/F1G1Ce59 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://learn.microsoft.com/en-us/microsoftteams/direct-routing-protocols-si... 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-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov abalashov@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 brandon@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-leave@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.evarist..., https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
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 bkaufman@bcmone.com wrote:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov abalashov@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:
- 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.
- 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.
- 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 brandon@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-leave@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.evarist..., https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@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@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 & Kaufman,
Appreciate the feedback. The pastebin is one example of about 1000+ iterations literally of changes. So I'm finally reaching out :). I haven't tested the socket attribute in record-route change, I will try this now. As for the angle brackets I've tried with and without, etc (already) to no effect. The SDP unknown media type seems to be a Poly thing, so I *want* to rule this out as its not in my other SDP's and still receive 400 bad request.
One more iteration here we go... please feel free to let me know if you have any other thoughts on the matter :).
Thanks!
- Brandon
On Thu, Dec 29, 2022 at 8:08 AM Alex Balashov abalashov@evaristesys.com wrote:
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 bkaufman@bcmone.com wrote:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov abalashov@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:
- 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.
- 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.
- 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 brandon@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-leave@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.evarist...,
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave@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@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-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hello,
as mentioned before, have a look to the 400 reply reason phrase. This was done quite good from their side, better than many other vendors. Usually, Teams is not too bad if you are using a defined infrastructure that do not introduce too many variables. We are usually using a B2BUA in our customer projects for that purpose.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: Brandon Armstead brandon@cryy.com Sent: Thursday, December 29, 2022 7:52 PM To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)
Alex & Kaufman,
Appreciate the feedback. The pastebin is one example of about 1000+ iterations literally of changes. So I'm finally reaching out :). I haven't tested the socket attribute in record-route change, I will try this now. As for the angle brackets I've tried with and without, etc (already) to no effect. The SDP unknown media type seems to be a Poly thing, so I *want* to rule this out as its not in my other SDP's and still receive 400 bad request.
One more iteration here we go... please feel free to let me know if you have any other thoughts on the matter :).
Thanks!
- Brandon
On Thu, Dec 29, 2022 at 8:08 AM Alex Balashov <abalashov@evaristesys.commailto:abalashov@evaristesys.com> wrote: 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 <bkaufman@bcmone.commailto:bkaufman@bcmone.com> wrote:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov <abalashov@evaristesys.commailto:abalashov@evaristesys.com> Sent: Thursday, December 29, 2022 9:02 AM To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.orgmailto: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:
- 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.
- 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.
- 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 <brandon@cryy.commailto:brandon@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.comhttp://ebin.com%2FF1G1Ce59&data=05%7C01%7Cbkaufman%40bcmone.comhttp://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.comhttp://n.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols-si p&data=05%7C01%7Cbkaufman%40bcmone.comhttp://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-leave@lists.kamailio.orgmailto:sr-users-leave@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.evarist..., https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.orgmailto:sr-users-leave@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@lists.kamailio.orgmailto:sr-users-leave@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-leave@lists.kamailio.orgmailto:sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Henning,
There was no reply (reason) available in my case.
- Brandon
On Thu, Dec 29, 2022 at 11:48 AM Henning Westerholt hw@gilawa.com wrote:
Hello,
as mentioned before, have a look to the 400 reply reason phrase. This was done quite good from their side, better than many other vendors.
Usually, Teams is not too bad if you are using a defined infrastructure that do not introduce too many variables. We are usually using a B2BUA in our customer projects for that purpose.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* Brandon Armstead brandon@cryy.com *Sent:* Thursday, December 29, 2022 7:52 PM *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)
Alex & Kaufman,
Appreciate the feedback. The pastebin is one example of about 1000+ iterations literally of changes. So I'm finally reaching out :). I haven't tested the socket attribute in record-route change, I will try this now. As for the angle brackets I've tried with and without, etc (already) to no effect. The SDP unknown media type seems to be a Poly thing, so I *want* to rule this out as its not in my other SDP's and still receive 400 bad request.
One more iteration here we go... please feel free to let me know if you have any other thoughts on the matter :).
Thanks!
- Brandon
On Thu, Dec 29, 2022 at 8:08 AM Alex Balashov abalashov@evaristesys.com wrote:
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 bkaufman@bcmone.com wrote:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov abalashov@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:
- 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.
- 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.
- 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 brandon@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-leave@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.evarist...,
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To
unsubscribe send an email to sr-users-leave@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@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-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
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 bkaufman@bcmone.com Sent: Thursday, December 29, 2022, 4:11 PM To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org 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 abalashov@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 brandon@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-leave@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.evarist..., https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@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@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Tim,
I don't think this matters in this case. It is currently working as-is with the minor adjustment of removing socket= param from the Record-Route header.
- Brandon
On Thu, Dec 29, 2022 at 11:54 AM Tim Chubb tim.chubb@voicesimplified.com wrote:
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 bkaufman@bcmone.com *Sent:* Thursday, December 29, 2022, 4:11 PM *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *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 abalashov@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:
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.
- 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.
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 brandon@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-leave@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.evarist...,
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@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@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@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 & Kaufman,
This resolved the issue. It did not like the socket=; param / attribute. Please let me know when you are in SoCal, I owe you a lot of beer and vodka :). I can't say this enough, but THANK YOU!
- Brandon
On Thu, Dec 29, 2022 at 8:33 AM Kaufman bkaufman@bcmone.com wrote:
In your top Record-Route you have:
socket=;
Not sure if that is legal.
Kaufman
-----Original Message----- From: Alex Balashov abalashov@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:
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.
- 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.
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 brandon@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-leave@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.evarist...,
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csrpswi...
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@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@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 -
Brandon Armstead -
Henning Westerholt -
Kaufman -
Tim Chubb