question

DanielStra-8100 avatar image
2 Votes"
DanielStra-8100 asked ccxchatoux commented

Teams Direct Routing - SIP Options Warning

Hello,

I have set up a Ribbon SBC with Teams Direct Routing. TLS Connection is ok, but I get this Message:
The Session Border Controller exists in our database (your administrator created it using the command New-CSOnlinePSTNGateway). But we have difficulties determining SIP Options status. Please check in 15 minutes.

I checked the firewall and see that the SBC is sending SIP Options to Teams and that I get a response from Teams. But there are no connections from Teams to the SBC, so Teams doesn't send any SIP Options:
IP SBCPublicIP.27171 > 52.114.7.24.5061: Flags [P.], seq 23200:23708, ack 15521, win 12500, length 508
IP SBCPublicIP.27171 > 52.114.7.24.5061: Flags [P.], seq 23708:23925, ack 15521, win 12500, length 217
IP 52.114.7.24.5061 > SBCPublicIP.27171: Flags [.], ack 23925, win 2053, length 0
IP 52.114.7.24.5061 > SBCPublicIP.27171: Flags [P.], seq 15521:16006, ack 23925, win 2053, length 485
IP SBCPublicIP.27171 > 52.114.7.24.5061: Flags [.], ack 16006, win 12500, length 0
IP SBCPublicIP.27795 > 52.114.75.24.5061: Flags [P.], seq 23200:23925, ack 15521, win 12500, length 725
IP 52.114.75.24.5061 > SBCPublicIP.27795: Flags [P.], seq 15521:16006, ack 23925, win 2050, length 485
IP SBCPublicIP.27795 > 52.114.75.24.5061: Flags [.], ack 16006, win 12500, length 0

I opened a MS Support case, but they want me to check the Teams client connection and even worse want me to do test calls, which wont work obviously. There are no client connectivity issues.

I even deleted all the configuration, waited 48h and reconfigured everything. Same behaviour as before. Do I miss anything?

office-teams-windows-itpro
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I have a similar call logged with Microsoft. SIP options failure on one customer out of a hundred across a multi-tenant SBC.

Inbound calls work, no outbound calls are provided to the SBC. Tenancy is TeamsOnly coexistence mode.

We did a similar thing; First we waited as the error prescribes. Then we tore down the configuration and have since added two more. We've run multiple tests and this post of yours makes me think it is a tenancy based problem.

0 Votes 0 ·

Hi Daniel, I'm experiencing same issue with my Ribbon SBC SWE Configured for direct routing. What did you do to fix your issue?

0 Votes 0 ·
Khojs avatar image
0 Votes"
Khojs answered ccxchatoux commented

Similar Issue, any update on this. Even updated SBC firmware as per vendor. Appears to be a generic issue. pointing towards Firewall or static routes which are clean anyways.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,
I solved the issue by changing the public dns name of my sbc. If i remember, unsderscore Is forbidden for the certificat cn (maybe another symbole).
Hope this will help you

0 Votes 0 ·
Torsten-9070 avatar image
1 Vote"
Torsten-9070 answered

Short Update:

I could solve my issue with the help of the SBC vendor (thx again to TE-Systems for their quick support).

Originally I was connecting my (single) SBC with both of my MS Tenants, using only one Port (5067) for TLS, via only one NIC, using only one public IP.
But of course using 2 public SBC-FQDN, pointing to this single Public IP. This wouldn't work. You need to use different Ports for the Tenants.

I had to reconfigure my SBC for using different TLS Ports for each tenant (Tenant1: 5067, Tenant2: 5068) and updated the Teams Config accordingly.
After some replication time the OPTIONS Packets immediately started coming in again and calls in both directions are working fine now for both tenants.




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ccxchatoux avatar image
0 Votes"
ccxchatoux answered DanielStra-8100 commented

Hello,

We are facing the same issue.

On the WAN interface of our router, we can see our SBC communicating with Teams (sipX.pstnhub.microsoft.com on port 5061), butwe did not see any communication from Teams IP to our SBC. We have waited 48 hours after we create the SBC link on our tenant, but still no communication.
I tried to do a telnet from outside my network (any website providing online telnet ) to my SBC on TCP port 5061, and it works fine. I'm connected and i saw the communication with tcpdump on my router. So this is not a firewall nor a network issue.
It is as if Teams server does not try to communicate with our SBC.
As there is no communication, i have the TLS warning in teams.

Did you find a solution ?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, the SBC was configured with the wrong public IP in the NAT settings.
After changing that it startet working.
Seems like Teams compares the IP in the contact header with the IP of the public DNS Record.
So I would recommend checking the details in the conatct haeder of the SBC.

1 Vote 1 ·
Torsten-9070 avatar image
0 Votes"
Torsten-9070 answered

Similar issue. Two tenants connected with one SBC (TE-Systems anynode. Each tenant configured as seperate node), but for only one tenant at a time, Direct Routing is working in both directions. For the other tenant, only outbound calls to Teams are ok. No inbound calls from the Teams side! In the SBC logs I can't see anything coming from Microsoft. Not even OPTIONS Packets.
Funny thing is, that I can "switch the issue"! By disabling the node for the working tenant in my SBC, the other one immediately starts receiving OPTIONS Pakets from Microsoft and calls in both directions are possible! As if MS would have problems with sending OPTIONS to both nodes (both behind the same NIC/IP).
I've openned a ticket with the SBC vendor. They usually provide fast and reliable support. Other than Microsoft...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SharonZhao-MSFT avatar image
0 Votes"
SharonZhao-MSFT answered LarryRenzAlvarez-2451 commented

@DanielStra-8100,

Please note that you need to configure TeamsUpgradePolicy to ensure incoming calls are received in Teams. Users must be in Teams Only mode, which you can do by assigning them the "UpgradeToTeams" instance of TeamsUpgradePolicy.


If the response is helpful, please click "Accept Answer" and upvote it.

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.



· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for your Response.
I'm aware of that point and configured this accordingly.

But the connection between the SBC and Teams is not working at all. So it is not a user-related issue. Everything is checked several times including sbc and firewall configuration.
Teams says it has issues determing SIP options status. But there are no logs in the Teams Service to check for details and MS Support can't help either, which is more than frustrating.
I would also like to know if teams should send SIP options to the SBC (which is currently not the case), because that could be the cause of the issue.
The SBC sends SIP options to Teams, which are answered.

0 Votes 0 ·

@DanielStra-8100,

Due to resource limitation, we have no enterprise voice deployment. It’s hard for us to provide more help on this topic.

Perhaps, you could use Wireshark to analyze the network protocol.


If the response is helpful, please click "Accept Answer" and upvote it.

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.

0 Votes 0 ·

I'm facing the same exact problem. From the SBC's SIP logs, I can see that the SBC is sending SIP options to Teams and Teams is sending 200/OK back. I'm seeing the same from the firewall. I'm not getting any SIP options, though, from Teams for my newly created Direct Routing SBC.

@DanielStra-8100 , have you got anything back from your MS support case?

0 Votes 0 ·