<?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 Attendant Console not working with Jabber in IP Telephony and Phones</title>
    <link>https://community.cisco.com/t5/ip-telephony-and-phones/attendant-console-not-working-with-jabber/m-p/5145440#M416235</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We have an on-premises Cisco VOIP system (which I still do not anywhere near fully understand) and are trying to complete our migration&amp;nbsp;from IP Communicator to Jabber. We have a switchboard system that uses Attendant Console and all works fine with IP Communicator. When a user tries to use Jabber as their phone and Attendant Console, AC reports an error message.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;Your extension #### is out of service. You will not be able to make or receive calls."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;So far based on my searches I have attempted the following which have NOT fixed it:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Associating the end user with the line on the Jabber device in CUCM.&lt;/LI&gt;&lt;LI&gt;Giving the AXL user the Standard CCM Super Users permission in CUCM.&lt;/LI&gt;&lt;LI&gt;Giving all application users control over the relevant Jabber device in CUCM.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;CUCM&amp;nbsp;&lt;/SPAN&gt;System version:&amp;nbsp;14.0.1.13900-155&lt;/P&gt;&lt;P&gt;CUAC&amp;nbsp;System Version: 12.0.5.10-13 Administration Version: 12.0.5.1823&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PS: We also have a call queue system using Finesse and that is working normally with Jabber as far as I know, although users are still testing it with full adoption to come.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jul 2024 09:15:22 GMT</pubDate>
    <dc:creator>Thomas1982</dc:creator>
    <dc:date>2024-07-16T09:15:22Z</dc:date>
    <item>
      <title>Attendant Console not working with Jabber</title>
      <link>https://community.cisco.com/t5/ip-telephony-and-phones/attendant-console-not-working-with-jabber/m-p/5145440#M416235</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We have an on-premises Cisco VOIP system (which I still do not anywhere near fully understand) and are trying to complete our migration&amp;nbsp;from IP Communicator to Jabber. We have a switchboard system that uses Attendant Console and all works fine with IP Communicator. When a user tries to use Jabber as their phone and Attendant Console, AC reports an error message.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;Your extension #### is out of service. You will not be able to make or receive calls."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;So far based on my searches I have attempted the following which have NOT fixed it:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Associating the end user with the line on the Jabber device in CUCM.&lt;/LI&gt;&lt;LI&gt;Giving the AXL user the Standard CCM Super Users permission in CUCM.&lt;/LI&gt;&lt;LI&gt;Giving all application users control over the relevant Jabber device in CUCM.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;CUCM&amp;nbsp;&lt;/SPAN&gt;System version:&amp;nbsp;14.0.1.13900-155&lt;/P&gt;&lt;P&gt;CUAC&amp;nbsp;System Version: 12.0.5.10-13 Administration Version: 12.0.5.1823&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PS: We also have a call queue system using Finesse and that is working normally with Jabber as far as I know, although users are still testing it with full adoption to come.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 09:15:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/ip-telephony-and-phones/attendant-console-not-working-with-jabber/m-p/5145440#M416235</guid>
      <dc:creator>Thomas1982</dc:creator>
      <dc:date>2024-07-16T09:15:22Z</dc:date>
    </item>
  </channel>
</rss>

