<?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: Unable to hold call in Webex Calling in Webex Calling</title>
    <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046945#M1839</link>
    <description>&lt;P&gt;That was spam; ignore it. There's nothing to check on the WxC-MT side.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Mar 2024 18:18:34 GMT</pubDate>
    <dc:creator>Jonathan Schulenberg</dc:creator>
    <dc:date>2024-03-21T18:18:34Z</dc:date>
    <item>
      <title>Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5039352#M1817</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;I have configured webex calling via local router and calling service is working fine but apparently unable to hold call, when I choose hold tab call is ended. Is there any setting need to change or amend, please help&lt;/P&gt;
&lt;H3 class="LC20lb MBeuO DKV0Md"&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2024 08:41:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5039352#M1817</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-14T08:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5039398#M1818</link>
      <description>&lt;P&gt;You need to pull debugs from the LGW to determine who isn’t happy - WxC-MT, the LGW, or the carrier. The SIP dialog will usually have a pretty clear sequence of events: something sent a request/response that something else didn’t like so the latter kills the call. Standard SIP troubleshooting. Once you understand what the triggering event is you can usually adjust the CUBE/LGW config to compensate.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2024 09:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5039398#M1818</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2024-03-14T09:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5040263#M1820</link>
      <description>&lt;P&gt;TQ Jonathan, let me pull debugs LGW and check the logs&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 02:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5040263#M1820</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-15T02:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5044954#M1827</link>
      <description>&lt;P&gt;Hi Jonathan&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;After run the debug, indicate that below error.&amp;nbsp;I have attached a log with some debugs&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;*Mar 19 05:33:11.430: //21725/DBFAD8CDB7E0/SIP/Msg/ccsipDisplayMsg:&lt;/P&gt;
&lt;P&gt;Received:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIP/2.0 403 Forbidden&lt;/P&gt;
&lt;P&gt;Via: SIP/2.0/UDP 10.22.213.68:5060;branch=z9hG4bK1FBE1276&lt;/P&gt;
&lt;P&gt;Call-ID: &lt;A href="mailto:asbcgdr6de5drjtetj66fprpis3sfjjredss@ATS.rcatshw01.ims.tm.com.my.155" target="_blank"&gt;asbcgdr6de5drjtetj66fprpis3sfjjredss@ATS.rcatshw01.ims.tm.com.my.155&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;From: &lt;A href="sip:0388939947;phone-context=ims.mnc153.mcc502.3gppnetwork.org@ims.mnc153.mcc502.3gppnetwork.org;user=phone" target="_blank"&gt;sip:0388939947;phone-context=ims.mnc153.mcc502.3gppnetwork.org@ims.mnc153.mcc502.3gppnetwork.org;user=phone&lt;/A&gt;;tag=194FD11E-1C9F&lt;/P&gt;
&lt;P&gt;To: &lt;A href="sip:Anonymous@ims.tm.com.my" target="_blank"&gt;sip:Anonymous@ims.tm.com.my&lt;/A&gt;;tag=5pj665jg-CC-155&lt;/P&gt;
&lt;P&gt;CSeq: 102 INVITE&lt;/P&gt;
&lt;P&gt;Warning: 399 198.18.9256.ATS.rcatshw01.ims.tm.com.my.155.451.0.0.0.0.0 &lt;STRONG&gt;"The user doesn't have hold ability". &lt;/STRONG&gt;I have attached the debug logs&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Content-Length: 0&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="p1"&gt;Caller: 0125597304&lt;/P&gt;
&lt;P class="p1"&gt;Callee: 0388939947 -&amp;gt; route to 0388939940&lt;/P&gt;
&lt;P class="p1"&gt;timestamp (with timezone) : 1.30pm (GMT +8 Kuala Lumpur)&lt;/P&gt;
&lt;P class="p1"&gt;Call Flow-&amp;gt; Call comes from&amp;nbsp;0125597304 PSTN to Local Gateway Webex Calling&amp;nbsp;0388939947 -&amp;gt; Route to Call Queue-&amp;gt; assign user in control hub-&amp;gt; Webex App-&amp;gt; ringing-&amp;gt; Accept Call-&amp;gt; Put on Hold-&amp;gt; Call End&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 09:46:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5044954#M1827</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-20T09:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5045599#M1830</link>
      <description>&lt;P&gt;The error you show above was generated by the upstream provider, not Webex Calling. Webex Calling sent the Local Gateway a Re-INVITE at 05:33:11.327 with a=sendonly. CUBE generates an equivalent Re-INVITE toward the provider at&amp;nbsp;05:33:11.332 which sends the 403 response you pasted above.&lt;/P&gt;
&lt;P&gt;This is a standard SIP SBC interworking issue. You need to understand what the provider expects to happen in this scenario and adjust the CUBE config - likely using a &lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/ios-xe/config/ios-xe-book/m_voi-sip-param-mod.html" target="_blank" rel="noopener"&gt;SIP profile&lt;/A&gt; - to manipulate the headers or SDP to conform with their expectations. One possible solution is to force a=sendonly back to a=sendrecv; see the &lt;EM&gt;Example: Modify Audio direction "Audio-Attribute"&lt;/EM&gt; heading in the linked document.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 17:45:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5045599#M1830</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2024-03-20T17:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046139#M1832</link>
      <description>&lt;P&gt;Hi thanks for share info, May I know where to check in Webex settings for call holding is enabled?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 06:50:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046139#M1832</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-21T06:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046143#M1833</link>
      <description>&lt;P&gt;Thanks Jonathan, Im checking with TSP to identify which parameter in the invite is not supported by them.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 06:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046143#M1833</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-21T06:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046945#M1839</link>
      <description>&lt;P&gt;That was spam; ignore it. There's nothing to check on the WxC-MT side.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2024 18:18:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5046945#M1839</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2024-03-21T18:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to hold call in Webex Calling</title>
      <link>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5047321#M1840</link>
      <description>&lt;P&gt;Hi Jonathan&lt;/P&gt;
&lt;P&gt;Call Hold is working now after ITSP enable call hold function to this 038893XXX.We are able to put call on hold 9940 but following DID’s 9941 &amp;amp; 9947 2&lt;SUP&gt;nd&lt;/SUP&gt; call hold attempt is drop. We are still checking with ITSP to validate the parameter. No changes from our end to LGW&lt;/P&gt;
&lt;P&gt;Call to 0388939940 : 1&lt;SUP&gt;st&lt;/SUP&gt; hold success, 2&lt;SUP&gt;nd&lt;/SUP&gt; hold success, 3&lt;SUP&gt;rd&lt;/SUP&gt; hold success&lt;/P&gt;
&lt;P&gt;Call to 0388939941 : 1&lt;SUP&gt;st&lt;/SUP&gt; hold success, 2&lt;SUP&gt;nd&lt;/SUP&gt; hold drop&lt;/P&gt;
&lt;P&gt;Call to 0388939947 : 1&lt;SUP&gt;st&lt;/SUP&gt; hold success, 2&lt;SUP&gt;nd&lt;/SUP&gt; hold drop&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 04:41:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-calling/unable-to-hold-call-in-webex-calling/m-p/5047321#M1840</guid>
      <dc:creator>pravin.muthu@vads.com</dc:creator>
      <dc:date>2024-03-22T04:41:51Z</dc:date>
    </item>
  </channel>
</rss>

