<div dir="ltr">I don't believe we have gotten any sort of RCA from them yet but we noted that the User-Agent, while calls were failing, had "v.2023.08.28.1" in it and after the problem cleared the User-Agent had "v.2023.06.29.3.i" in it, so it smells like a rollback to me.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 30, 2023 at 1:11 PM Pete Eisengrein <<a href="mailto:peeip989@gmail.com">peeip989@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">It is Direct Routing, but we weren't getting the 400 Bad Request, and for us the BYE was originating from the PSTN towards Microsoft due to no audio. This magically began to clear around noon eastern.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 30, 2023 at 12:37 PM Hunt, Fred A - DOA <<a href="mailto:FredA.Hunt@wisconsin.gov" target="_blank">FredA.Hunt@wisconsin.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal">Are you using Teams Direct Routing? This morning it does appear that Teams is not cleanly terminating calls. Here’s an example response from Teams to a SIP BYE message sent<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">148249222: Aug 30 15:09:39.986: //12929228/0B60EED0B3ED/CUBE_VT/SIP/Msg/ccsipDisplayMsg:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">Received: SIP TLS message from <a href="http://52.114.132.46:5061" target="_blank">52.114.132.46:5061</a> to [REDACTED]
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black;background:yellow">SIP/2.0 400 Bad Request</span><span style="font-size:9pt;font-family:"Courier New";color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">FROM: "[REDACTED]"sip:+[REDACTED]@[REDACTED];tag=59E32C35-1282<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">TO:
<a>sip:+[REDACTED]@sip.pstnhub.microsoft.com</a>;tag=42b61721ea1d4686bf22e4b2f03384d0<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">CSEQ: 102 BYE<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">CALL-ID:
<a href="mailto:B629C8A-467E11EE-B3F38F31-9397CD96@TeamsMADSBC.wisconsin.gov" target="_blank">B629C8A-467E11EE-B3F38F31-9397CD96@[REDACTED]</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">VIA: SIP/2.0/TLS [REDACTED];branch=z9hG4bK3B67395A8<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black;background:yellow">REASON: Q.850;cause=95;text="9e76dc15-53f0-4eb9-82b0-215b7e029e87;Expected a Protocol of Reason header
as a token, got '\5cx17\5cx03\5cx03\5cx03n\5cx8BC^YB C;8t\5cx96C^]BYE <a>
sip:api-du-a-usea.pstnhub.microsoft.com:443;x-i=9e76dc15-53f0-4eb9-82b0-215b7e029e87;x-c=4c4164749a1c57e5958505fe4de5d0cb/s/1/dd4c</a>"</span><span style="font-size:9pt;font-family:"Courier New";color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">CONTENT-LENGTH: 0<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Courier New";color:black">SERVER: Microsoft.PSTNHub.SIPProxy v.2023.8.28.1 i.USEA.10<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Nothing has changed with what we are sending to MS in the SIP Reason header and I also see plenty of calls today that do terminate cleanly.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Outages <<a href="mailto:outages-bounces@outages.org" target="_blank">outages-bounces@outages.org</a>> <b>On Behalf Of
</b>Pete Eisengrein via Outages<br>
<b>Sent:</b> Wednesday, August 30, 2023 10:32 AM<br>
<b>To:</b> <a href="mailto:outages@voiceops.org" target="_blank">outages@voiceops.org</a><br>
<b>Subject:</b> [outages] Microsoft Teams outage?<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p><strong><span style="font-size:10pt;font-family:Arial,sans-serif;color:white;background:rgb(255,102,0)">CAUTION: This email originated from outside the organization.
</span></strong><br>
<strong><span style="font-size:10pt;font-family:Arial,sans-serif;color:white;background:rgb(255,102,0)">Do not click links or open attachments unless you recognize the sender and know the content is safe.</span></strong><u></u><u></u></p>
<p><u></u> <u></u></p>
<div>
<p class="MsoNormal">We are experiencing an issue with Microsoft this morning, where they initially connect but when we send a re-INVITE, Microsoft responds with a 100 Trying but then never updates the session and the call is left with dead air and eventually
the caller hangs up.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Waiting on Microsoft support.....<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div></blockquote></div>
</blockquote></div>