<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Webex Calling - Dropped Calls in Webex Calling</title>
    <link>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4809597#M1379</link>
    <description>&lt;P&gt;Here is a SIP trace from CUCM. LMK if this helps.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="call trace.JPG" style="width: 614px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/181099iDF4FB38441E65C86/image-size/large?v=v2&amp;amp;px=999" role="button" title="call trace.JPG" alt="call trace.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Apr 2023 15:50:32 GMT</pubDate>
    <dc:creator>PATRICK HARRIS</dc:creator>
    <dc:date>2023-04-06T15:50:32Z</dc:date>
    <item>
      <title>Webex Calling - Dropped Calls</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4805703#M1369</link>
      <description>&lt;P&gt;Recently migrated to Webex Calling and user are reporting calls dropping mid call throughout the day mostly calls placed to the our PSTN provider. Our external&amp;nbsp; call flow is Endpoint - CUBE - CUCM - PSTN. We have contacted the provider and they state that the only issue they see in the call flow is it sending SDP invites. Could this be causing call drops?. Any assistance would be appreciated. Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 01 Apr 2023 00:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4805703#M1369</guid>
      <dc:creator>PATRICK HARRIS</dc:creator>
      <dc:date>2023-04-01T00:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Webex Calling - Dropped Calls</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4806006#M1370</link>
      <description>&lt;P&gt;You’re going to need look at the SIP traces to understand what is happening here - and which hop decided to kill the call (i.e. first to send a BYE). I suggest starting at the PSTN gateway since that will tell you whether it’s your fault or the provider. If it’s you then work your way upstream: CUCM, then the LGW.&lt;/P&gt;</description>
      <pubDate>Sun, 02 Apr 2023 11:57:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4806006#M1370</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2023-04-02T11:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: Webex Calling - Dropped Calls</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4809597#M1379</link>
      <description>&lt;P&gt;Here is a SIP trace from CUCM. LMK if this helps.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="call trace.JPG" style="width: 614px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/181099iDF4FB38441E65C86/image-size/large?v=v2&amp;amp;px=999" role="button" title="call trace.JPG" alt="call trace.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 15:50:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4809597#M1379</guid>
      <dc:creator>PATRICK HARRIS</dc:creator>
      <dc:date>2023-04-06T15:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: Webex Calling - Dropped Calls</title>
      <link>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4809628#M1380</link>
      <description>&lt;P&gt;Here is the trace.&lt;/P&gt;&lt;P&gt;Message Details MSGTAG: 229509791 MSG_TYPE: UCM_CTRACE SENDER: [ATL_SIP_SBC] xx.xx.xx.xx TIMESTAMP: 2023/04/06 10:15:23.141 CORRELATIONID: 1,100,255,1.4338621^xx.xx.xx.xx^* GUID: 168612569_99976834@xx.xx.xx.xx^*^* MSG_LABEL: INVITE RECEIVER: xx.xx.xx.xx MAC_ADDRESS: ATL_SIP_SBC Detailed Sip Message INVITE sip:+1404XXXXXXXX@xx.xx.xx.xx:5060 SIP/2.0 Via: SIP/2.0/UDP xx.xx.xx.xx:5060;branch=z9hG4bK0cB5fe445c9a7206215 From: " xx.xx.xx.xx,MA" &amp;lt; sip:+xx.xx.xx.xx@xx.xx.xx.xx:5060&amp;gt; ;tag=gK0c42e45c To: &amp;lt; sip:+1404XXXXXXX@xx.xx.xx.xx:5060&amp;gt; Call-ID: 168612569_99976834@xx.xx.xx.xx CSeq: 205973 INVITE Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,UPDATE,OPTIONS Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed Contact: " xx.xx.xx.xx,MA" &amp;lt; sip:+xx.xx.xx.xx@xx.xx.xx.xx:5060&amp;gt; Recv-Info: x-broadworks-client-session-info Content-Length: 309 Content-Disposition: session; handling=required Content-Type: application/sdp v=0 o=Sonus_UAC 799155 832302 IN IP4 xx.xx.xx.xx s=SIP Media Capabilities c=IN IP4 xx.xx.xx.xx t=0 0 m=audio 13054 RTP/AVP 0 8 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 Message In Log File 2023/04/06 10:15:23.141|SIPT|0|UDP|IN|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,255,1.4338621^xx.xx.xx.xx^*|229509791|168612569_99976834@xx.xx.xx.xx^*^*|INVITE 2023/04/06 10:15:23.142|SIPT|0|UDP|OUT|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,255,1.4338621^xx.xx.xx.xx^*|229509792|168612569_99976834@xx.xx.xx.xx^*^*|100 Trying 2023/04/06 10:15:23.144|CC|SETUP|20001689|20001690|+xx.xx.xx.xx|+xx.xx.xx.xx|+xx.xx.xx.xx|217e12d4c821f7e5370125ab75758853|* 2023/04/06 10:15:23.146|CC|OFFERED|20001689|20001690|+xx.xx.xx.xx|+xx.xx.xx.xx|+xx.xx.xx.xx|ATL_SIP_SBC|Trunk_to_Local_Gateway|217e12d4c821f7e5370125ab75758853|* 2023/04/06 10:15:23.146|SIPT|20001690|TCP|OUT|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,255,1.4338621^xx.xx.xx.xx^*|229509793|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^217e12d4c821f7e5370125ab75758853^*|INVITE 2023/04/06 10:15:23.157|SIPT|20001690|TCP|IN|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,251,714981.478^xx.xx.xx.xx^*|229509794|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^00000000000000000000000000000000^*|100 Trying 2023/04/06 10:15:23.633|SIPT|20001690|TCP|IN|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,251,714981.479^xx.xx.xx.xx^*|229509795|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^b2a4027000105000a00000778d34d1ee^217e12d4c821f7e5370125ab75758853|180 Ringing 2023/04/06 10:15:23.635|SIPT|20001689|UDP|OUT|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,251,714981.479^xx.xx.xx.xx^*|229509796|168612569_99976834@xx.xx.xx.xx^b2a4027000105000a00000778d34d1ee^217e12d4c821f7e5370125ab75758853|180 Ringing 2023/04/06 10:15:28.632|SIPT|20001690|TCP|IN|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,251,714981.480^xx.xx.xx.xx^*|229509808|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^25828842e8564a6ebe11f5c0a685b8f0^217e12d4c821f7e5370125ab75758853|200 OK 2023/04/06 10:15:28.876|SIPT|20001690|TCP|OUT|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,251,714981.480^xx.xx.xx.xx^*|229509809|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^217e12d4c821f7e5370125ab75758853^25828842e8564a6ebe11f5c0a685b8f0|ACK 2023/04/06 10:15:28.876|SIPT|20001689|UDP|OUT|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,251,714981.480^xx.xx.xx.xx^*|229509810|168612569_99976834@xx.xx.xx.xx^25828842e8564a6ebe11f5c0a685b8f0^217e12d4c821f7e5370125ab75758853|200 OK 2023/04/06 10:15:28.901|SIPT|20001689|UDP|IN|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,255,1.4338622^xx.xx.xx.xx^*|229509811|168612569_99976834@xx.xx.xx.xx^*^*|ACK 2023/04/06 10:15:56.365|SIPT|20001689|UDP|IN|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,255,1.4338635^xx.xx.xx.xx^*|229509889|168612569_99976834@xx.xx.xx.xx^*^*|BYE 2023/04/06 10:15:56.375|SIPT|20001689|UDP|OUT|xx.xx.xx.xx|5060|ATL_SIP_SBC|xx.xx.xx.xx|5060|1,100,255,1.4338635^xx.xx.xx.xx^*|229509890|168612569_99976834@xx.xx.xx.xx^*^*|200 OK 2023/04/06 10:15:56.376|SIPT|20001690|TCP|OUT|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,255,1.4338635^xx.xx.xx.xx^*|229509891|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^217e12d4c821f7e5370125ab75758853^25828842e8564a6ebe11f5c0a685b8f0|BYE 2023/04/06 10:15:56.381|SIPT|20001690|TCP|IN|xx.xx.xx.xx|5065|Trunk_to_Local_Gateway|xx.xx.xx.xx|5060|1,100,251,714981.486^xx.xx.xx.xx^*|229509892|76f05500-10001-265e9d-93f492a@xx.xx.xx.xx^25828842e8564a6ebe11f5c0a685b8f0^217e12d4c821f7e5370125ab75758853|200 OK 2023/04/06 10:15:56.381|CC|RELEASE|20001689|20001690|217e12d4c821f7e5370125ab75758853|25828842e8564a6ebe11f5c0a685b8f0|16&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 16:35:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/webex-calling-dropped-calls/m-p/4809628#M1380</guid>
      <dc:creator>PATRICK HARRIS</dc:creator>
      <dc:date>2023-04-06T16:35:18Z</dc:date>
    </item>
  </channel>
</rss>

