SOLVED

Microsoft Teams Direct Routing - Non Media Bypass Mode

%3CLINGO-SUB%20id%3D%22lingo-sub-1581173%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20Direct%20Routing%20-%20Non%20Media%20Bypass%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1581173%22%20slang%3D%22en-US%22%3E%3CP%3ETrying%20to%20enable%20SBC%20working%20with%20Microsoft%20Teams%20Direct%20routing%20in%202%20modes%20of%20operation%20%22Media%20Bypass%22%20configured%20as%20TRUE%26nbsp%3B%2F%20FALSE.%3C%2FP%3E%3CP%3EWhen%20SBC%20is%20working%20towards%20Teams%20configured%20with%20%22Media%20Bypass%22%20as%20true%2C%20calls%20establish%20OK.%3C%2FP%3E%3CP%3EBut%2C%20when%20Teams%20configured%20with%20%22Media%20Bypass%22%20as%20false%2C%20calls%20fail.%3C%2FP%3E%3CP%3EScenario%20a%3A%26nbsp%3BSBC%20sends%20INVITE%20and%26nbsp%3Breplied%20with%26nbsp%3B488%26nbsp%3B%20%22sdp%20parse%20error%22.%3C%2FP%3E%3CP%3EScenario%20b%3A%26nbsp%3BSBC%20replies%20with%20200OK%20on%20INVITE%20and%20receives%20a%20BYE%20message%20from%20Teams.%3C%2FP%3E%3CP%3EOn%20both%20mode%20of%20operation%20of%20%22Media%20Bypass%22%2C%20SBC%20sends%20exactly%20the%20same%20messages.%3C%2FP%3E%3CP%3EIs%20there%20a%20difference%20in%20the%20SIP%2FSDP%20messages%20between%20these%202%20modes%20of%20operations%3F%3C%2FP%3E%3CP%3EAre%20there%20Teams%20LOGs%20pointing%20out%20the%20root%20cause%20of%20the%20difference%20between%20the%20two%20modes%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1581173%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1589458%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Direct%20Routing%20-%20Non%20Media%20Bypass%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1589458%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F755826%22%20target%3D%22_blank%22%3E%40Ehud_Bart%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BI'm%20going%20to%20ask%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259632%22%20target%3D%22_blank%22%3E%40Satish2805%3C%2FA%3E%26nbsp%3Bto%20look%20at%20your%20question.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591023%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Direct%20Routing%20-%20Non%20Media%20Bypass%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591023%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F755826%22%20target%3D%22_blank%22%3E%40Ehud_Bart%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20isn't%20much%20on%20the%20Teams%20side%20you%20can%20look%20at%2C%20but%20you%20should%20be%20able%20to%20look%20at%20the%20logs%20from%20the%20SBC%20side.%26nbsp%3B%20What%20SBC%20are%20you%20using%3F%26nbsp%3B%20Depending%20on%20the%20SBC%20there%20are%20additional%20configurations%20required%20there%2C%20such%20as%20on%20the%20AudioCodes%20line%2C%20you%20need%20to%20enable%20ICE%20Lite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20terms%20of%20operational%20differences%20between%20the%20two%2C%20there%20will%20be%20ICE%20information%20in%20the%20messages%20that%20will%20announce%20media%20bypass%20support%20along%20with%20candidates.%26nbsp%3B%20These%20are%20not%20in%20the%20headers%2C%20but%20in%20the%20SIP%20body.%26nbsp%3B%20This%20is%20a%20sample%20of%20an%20INVITE%20that%20has%20the%20necessary%20headers%20for%20media%20bypass.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EINVITE%20sip%3A%2B1234567890%40sbc1.provider.tld%3A5061%3Buser%3Dphone%3Btransport%3Dtls%20SIP%2F2.0%20%0AFROM%3A%20MYUSER%20%26lt%3Bsip%3A%2B1098765432%40sip.pstnhub.microsoft.com%3A5061%3Buser%3Dphone%26gt%3B%3Btag%3D3f2a4ff9b10449cfb8cd9d9f43a8e77b%0ATO%3A%20%26lt%3Bsip%3A%2B1234567890%40sbc1.provider.tld%3A5061%3Buser%3Dphone%26gt%3B%0ACSEQ%3A%201%20INVITE%0ACALL-ID%3A%20abc123%0AMAX-FORWARDS%3A%2070%0AVIA%3A%20SIP%2F2.0%2FTLS%2052.114.132.46%3A5061%3Bbranch%3Dz9hG4bK195f743f%0ARECORD-ROUTE%3A%20%26lt%3Bsip%3Asip-du-a-us.pstnhub.microsoft.com%3A5061%3Btransport%3Dtls%3Blr%26gt%3B%0ACONTACT%3A%20%26lt%3Bsip%3Aapi-du-c-usea.pstnhub.microsoft.com%3A443%3Bx-i%3Daaa-bbb-ccc-ddd%3Bx-c%3Dabc123%2Fd%2F8%2Fabc123%26gt%3B%0ACONTENT-LENGTH%3A%201138%0AMIN-SE%3A%20300%0ASUPPORTED%3A%20timer%0AUSER-AGENT%3A%20Microsoft.PSTNHub.SIPProxy%20v.2020.3.2.6%20i.USEA.1%0ACONTENT-TYPE%3A%20application%2Fsdp%0AALLOW%3A%20INVITE%2CACK%2COPTIONS%2CCANCEL%2CBYE%2CNOTIFY%0ASESSION-EXPIRES%3A%203600%0A%0Av%3D0%0Ao%3D-%2093204%200%20IN%20IP4%20127.0.0.1%0As%3Dsession%0Ac%3DIN%20IP4%2052.114.152.110%0Ab%3DCT%3A10000000%0At%3D0%200%0Am%3Daudio%2052592%20RTP%2FSAVP%20104%20117%209%20103%20111%2018%200%208%2097%20101%2013%20118%0Ac%3DIN%20IP4%2052.114.152.110%0Aa%3Drtcp%3A52593%0Aa%3Dice-ufrag%3A9X9v%0Aa%3Dice-pwd%3A123abc%0Aa%3Drtcp-mux%0Aa%3Dcandidate%3A1%201%20UDP%202130706431%2052.114.152.110%2052592%20typ%20srflx%20raddr%2010.0.136.99%20rpor%20%5BTime%3A06-03%4012%3A21%3A00.391%5D%0At%2052592%20%0Aa%3Dcandidate%3A1%202%20UDP%202130705918%2052.114.152.110%2052593%20typ%20srflx%20raddr%2010.0.136.99%20rport%2052593%0Aa%3Dcandidate%3A2%201%20tcp-act%202121006078%2052.114.152.110%2049152%20typ%20srflx%20raddr%2010.0.136.99%20rport%2049152%0Aa%3Dcandidate%3A2%202%20tcp-act%202121006078%2052.114.152.110%2049152%20typ%20srflx%20raddr%2010.0.136.99%20rport%2049152%0Aa%3Dlabel%3Amain-audio%0Aa%3Dmid%3A1%0Aa%3Dcrypto%3A1%20AES_CM_128_HMAC_SHA1_80%20inline%3AXFBdTTZaQ4YRASWBQzNDuh4eN5ztKQfMJYJMWE1Q%7C2%5E31%0Aa%3Dsendrecv%0Aa%3Drtpmap%3A104%20SILK%2F16000%0Aa%3Drtpmap%3A117%20G722%2F8000%2F2%0Aa%3Drtpmap%3A9%20G722%2F8000%0Aa%3Drtpmap%3A103%20SILK%2F8000%0Aa%3Drtpmap%3A111%20SIREN%2F16000%0Aa%3Dfmtp%3A111%20bitrate%3D16000%0Aa%3Drtpmap%3A18%20G729%2F8000%0Aa%3Dfmtp%3A18%20annexb%3Dno%0Aa%3Drtpmap%3A0%20PCMU%2F8000%0Aa%3Drtpmap%3A8%20PCMA%2F8000%0Aa%3Drtpmap%3A97%20RED%2F8000%0Aa%3Drtpmap%3A101%20telephone-event%2F8000%0Aa%3Dfmtp%3A101%200-16%0Aa%3Drtpmap%3A13%20CN%2F8000%0Aa%3Drtpmap%3A118%20CN%2F16000%0Aa%3Dptime%3A20%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20a%20non-media%20bypass%20world%2C%20the%20ICE%20and%20candidates%20will%20be%20missing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Trying to enable SBC working with Microsoft Teams Direct routing in 2 modes of operation "Media Bypass" configured as TRUE / FALSE.

When SBC is working towards Teams configured with "Media Bypass" as true, calls establish OK.

But, when Teams configured with "Media Bypass" as false, calls fail.

Scenario a: SBC sends INVITE and replied with 488  "sdp parse error".

Scenario b: SBC replies with 200OK on INVITE and receives a BYE message from Teams.

On both mode of operation of "Media Bypass", SBC sends exactly the same messages.

Is there a difference in the SIP/SDP messages between these 2 modes of operations?

Are there Teams LOGs pointing out the root cause of the difference between the two modes?

1 Reply
Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

@Ehud_Bart 

 

There isn't much on the Teams side you can look at, but you should be able to look at the logs from the SBC side.  What SBC are you using?  Depending on the SBC there are additional configurations required there, such as on the AudioCodes line, you need to enable ICE Lite.

 

In terms of operational differences between the two, there will be ICE information in the messages that will announce media bypass support along with candidates.  These are not in the headers, but in the SIP body.  This is a sample of an INVITE that has the necessary headers for media bypass.

 

 

INVITE sip:+1234567890@sbc1.provider.tld:5061;user=phone;transport=tls SIP/2.0 
FROM: MYUSER <sip:+1098765432@sip.pstnhub.microsoft.com:5061;user=phone>;tag=3f2a4ff9b10449cfb8cd9d9f43a8e77b
TO: <sip:+1234567890@sbc1.provider.tld:5061;user=phone>
CSEQ: 1 INVITE
CALL-ID: abc123
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bK195f743f
RECORD-ROUTE: <sip:sip-du-a-us.pstnhub.microsoft.com:5061;transport=tls;lr>
CONTACT: <sip:api-du-c-usea.pstnhub.microsoft.com:443;x-i=aaa-bbb-ccc-ddd;x-c=abc123/d/8/abc123>
CONTENT-LENGTH: 1138
MIN-SE: 300
SUPPORTED: timer
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.3.2.6 i.USEA.1
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600

v=0
o=- 93204 0 IN IP4 127.0.0.1
s=session
c=IN IP4 52.114.152.110
b=CT:10000000
t=0 0
m=audio 52592 RTP/SAVP 104 117 9 103 111 18 0 8 97 101 13 118
c=IN IP4 52.114.152.110
a=rtcp:52593
a=ice-ufrag:9X9v
a=ice-pwd:123abc
a=rtcp-mux
a=candidate:1 1 UDP 2130706431 52.114.152.110 52592 typ srflx raddr 10.0.136.99 rpor [Time:06-03@12:21:00.391]
t 52592 
a=candidate:1 2 UDP 2130705918 52.114.152.110 52593 typ srflx raddr 10.0.136.99 rport 52593
a=candidate:2 1 tcp-act 2121006078 52.114.152.110 49152 typ srflx raddr 10.0.136.99 rport 49152
a=candidate:2 2 tcp-act 2121006078 52.114.152.110 49152 typ srflx raddr 10.0.136.99 rport 49152
a=label:main-audio
a=mid:1
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:XFBdTTZaQ4YRASWBQzNDuh4eN5ztKQfMJYJMWE1Q|2^31
a=sendrecv
a=rtpmap:104 SILK/16000
a=rtpmap:117 G722/8000/2
a=rtpmap:9 G722/8000
a=rtpmap:103 SILK/8000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:97 RED/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:13 CN/8000
a=rtpmap:118 CN/16000
a=ptime:20

 

In a non-media bypass world, the ICE and candidates will be missing.