<?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 When it shows as registered in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766832#M13677</link>
    <description>&lt;P&gt;When it shows as registered under device -&amp;gt; phone, or you could also look at the keepalives and wait for N keepalives to come from the client to consider it's registered and looking to keep its registration.&lt;/P&gt;&lt;P&gt;The CUCM traces should also show the registration process, but then again, many times if you have problems, it will keep flapping between registered and unregistered&lt;/P&gt;</description>
    <pubDate>Tue, 15 Sep 2015 21:14:49 GMT</pubDate>
    <dc:creator>Jaime Valencia</dc:creator>
    <dc:date>2015-09-15T21:14:49Z</dc:date>
    <item>
      <title>Confirmation that Jabber is registered to CUCM</title>
      <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766831#M13676</link>
      <description>&lt;P&gt;Does anyone know of a way to positively identify when Jabber for Windows (phone mode) has fully registered to the CUCM and is ready to make/take a call?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are looking to execute an automated desktop script for another application once Jabber is confirmed registered.&amp;nbsp; Having intermittent issues with using just a timer delay as registration time varies based off client and/or CUCM load.&amp;nbsp; Do not want to set a timer high just to have it sit and wait for a timer if jabber registered fast.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 00:31:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766831#M13676</guid>
      <dc:creator>joewon</dc:creator>
      <dc:date>2019-03-18T00:31:05Z</dc:date>
    </item>
    <item>
      <title>When it shows as registered</title>
      <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766832#M13677</link>
      <description>&lt;P&gt;When it shows as registered under device -&amp;gt; phone, or you could also look at the keepalives and wait for N keepalives to come from the client to consider it's registered and looking to keep its registration.&lt;/P&gt;&lt;P&gt;The CUCM traces should also show the registration process, but then again, many times if you have problems, it will keep flapping between registered and unregistered&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2015 21:14:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766832#M13677</guid>
      <dc:creator>Jaime Valencia</dc:creator>
      <dc:date>2015-09-15T21:14:49Z</dc:date>
    </item>
    <item>
      <title>If you want to do it from</title>
      <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766833#M13678</link>
      <description>&lt;P&gt;If you want to do it from another program, you might want to look at the RIS API. This allows you to get registration information for a device.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.cisco.com/site/sxml/discover/overview/risport/"&gt;developer.cisco.com/site/sxml/discover/overview/risport/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GTG&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2015 06:58:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766833#M13678</guid>
      <dc:creator>Gordon Ross</dc:creator>
      <dc:date>2015-09-16T06:58:05Z</dc:date>
    </item>
    <item>
      <title>Thanks.  We are looking to</title>
      <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766834#M13679</link>
      <description>&lt;P&gt;Thanks.&amp;nbsp; We are looking to try the RISPORT method as it is a request/response type of transaction which we can trigger off of.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Sep 2015 13:12:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766834#M13679</guid>
      <dc:creator>joewon</dc:creator>
      <dc:date>2015-09-17T13:12:39Z</dc:date>
    </item>
    <item>
      <title>Perfect.  Will try this. </title>
      <link>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766835#M13680</link>
      <description>&lt;P&gt;Perfect.&amp;nbsp; Will try this.&amp;nbsp; Seems promising.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Sep 2015 13:13:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/confirmation-that-jabber-is-registered-to-cucm/m-p/2766835#M13680</guid>
      <dc:creator>joewon</dc:creator>
      <dc:date>2015-09-17T13:13:00Z</dc:date>
    </item>
  </channel>
</rss>

