Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)

Question

Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)

Brandon Armstead 26

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

Any help is appreciated, thank you!

Brandon Armstead 26 Reputation points

2022-12-29T05:19:50.903+00:00

@Sharon Zhao-MSFT perhaps you may be able to help me here, it would be much appreciated! Thank you.
Brandon Armstead 26 Reputation points

2022-12-29T05:29:07.59+00:00

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.
chubb 1 Reputation point

2022-12-29T18:38:28.613+00:00

Try setting fqdn in the request to and from headers

Given this thread title matches one in the kamailio user list, set $rd to your fqdn, set a record route prefix of your fqdn, and set $du to sip.pstnhub....

400 error is usually caused by something obvious I overlook and face-palm later, also check the reason in the 400 response MS put very clear reasons and causes in their error responses
Brandon Armstead 26 Reputation points

2022-12-29T18:44:40.303+00:00

FQDN is in the request uri, to, and from.

I've tried both of these variations.

From: <e164.number@FQDN>
To: <e164.number@Sip .pstnhub.microsoft.com>

And

From: <e164.number@FQDN>
To: <e164.number@FQDN>

There is no reason clause in the 400 Bad Request response.

Accepted answer

1 additional answer

Your answer

Brandon Armstead 26 Reputation points

2022-12-29T05:19:50.903+00:00

@Sharon Zhao-MSFT perhaps you may be able to help me here, it would be much appreciated! Thank you.
Brandon Armstead 26 Reputation points

2022-12-29T05:29:07.59+00:00

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.
chubb 1 Reputation point

2022-12-29T18:38:28.613+00:00

Try setting fqdn in the request to and from headers

Given this thread title matches one in the kamailio user list, set $rd to your fqdn, set a record route prefix of your fqdn, and set $du to sip.pstnhub....

400 error is usually caused by something obvious I overlook and face-palm later, also check the reason in the 400 response MS put very clear reasons and causes in their error responses
Brandon Armstead 26 Reputation points

2022-12-29T18:44:40.303+00:00

FQDN is in the request uri, to, and from.

I've tried both of these variations.

From: <e164.number@FQDN>
To: <e164.number@Sip .pstnhub.microsoft.com>

And

From: <e164.number@FQDN>
To: <e164.number@FQDN>

There is no reason clause in the 400 Bad Request response.

Answer 1

Hi @Brandon Armstead

Great to know that you've already thought of a solution and really appreciate it for your sharing!

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others. You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. And according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)

Issue Symptom: Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) always result in a 400 BAD REQUEST. Also, it was ensured that the phone numbers were all formatted correctly, and several variants and clients were tried, but the problem persisted.

The Solution: Issue was resolved, socket= param/attribute in top level Record-Route header was not liked by Teams SBC.

Thank you for your understanding and patience!

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

SokiGuo-MSFT 31,221 Reputation points Microsoft External Staff

2023-01-03T02:01:57.42+00:00

Hi @Brandon Armstead
I am checking the status of this case. Please try to mark it as an answer to close the thread, it will help others who encounter the same issue and read this thread.
Thank you for your understanding and patience!

Answer 2

Brandon Armstead 26

Issue was resolved, socket= param/attribute in top level Record-Route header was not liked by Teams SBC.

Share via

Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)

1 additional answer

Your answer