<?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 &amp;quot;refused&amp;quot; an incoming call in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751913#M48613</link>
    <description>&lt;P&gt;I agree that a Call Forward Busy destination would be ideal; however, I’m not sure that’s required. I haven’t tested this recently but would have expected CUCM to send a 486 Busy Here to the origin if all line appearances decline the call. It would be interesting to see CUCM traces of the call, although they&amp;nbsp;probably contain too much PII to post here.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Jan 2023 10:35:04 GMT</pubDate>
    <dc:creator>Jonathan Schulenberg</dc:creator>
    <dc:date>2023-01-10T10:35:04Z</dc:date>
    <item>
      <title>Unable to "refused" an incoming call</title>
      <link>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751673#M48611</link>
      <description>&lt;P&gt;User reported issue for&amp;nbsp; Jabber client&lt;/P&gt;&lt;P&gt;Unable to "refused" an incoming call. When we push the button "Refused" the incoming call is still there (still ringing)&lt;/P&gt;&lt;P&gt;Advice please&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 03:45:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751673#M48611</guid>
      <dc:creator>sanjayapanda881</dc:creator>
      <dc:date>2023-01-10T03:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to "refused" an incoming call</title>
      <link>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751787#M48612</link>
      <description>&lt;P&gt;Have you defined with a voicemail profile, where the call should go to?&lt;BR /&gt;You need to specify a destination, where the call is diverted, if you press "refuse". You cannot just "disconnect" the call.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 06:57:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751787#M48612</guid>
      <dc:creator>b.winter</dc:creator>
      <dc:date>2023-01-10T06:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to "refused" an incoming call</title>
      <link>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751913#M48613</link>
      <description>&lt;P&gt;I agree that a Call Forward Busy destination would be ideal; however, I’m not sure that’s required. I haven’t tested this recently but would have expected CUCM to send a 486 Busy Here to the origin if all line appearances decline the call. It would be interesting to see CUCM traces of the call, although they&amp;nbsp;probably contain too much PII to post here.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 10:35:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/unable-to-quot-refused-quot-an-incoming-call/m-p/4751913#M48613</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2023-01-10T10:35:04Z</dc:date>
    </item>
  </channel>
</rss>

