<?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 Jabber CUCM- CUPS 8.6 - Phone Status Using A SIP Encrypted Profile in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-cucm-cups-8-6-phone-status-using-a-sip-encrypted-profile/m-p/1961179#M28907</link>
    <description>&lt;P&gt;I am using CUCM 8.6 with CUPS 8.6 and Jabber.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a SIP Trunk configured between CUCM and CUPS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured the Trunk with a Secure Encrypted SIP Trunk Profile which uses TLS as the transport type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A non-secure profile uses TCP+ UDP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I use the Secure Encrypted Profile, On the Phone Status is not published and sent / not changed automatically&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I use the Unsecure Profile this works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What changes do I need to make in CUCM or CUPS to allow On the Phone Status to be updated automatically using an Encrypted SIP Secuity Profile&lt;/P&gt;</description>
    <pubDate>Sun, 17 Mar 2019 21:24:16 GMT</pubDate>
    <dc:creator>CCIESingh</dc:creator>
    <dc:date>2019-03-17T21:24:16Z</dc:date>
    <item>
      <title>Jabber CUCM- CUPS 8.6 - Phone Status Using A SIP Encrypted Profile</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-cucm-cups-8-6-phone-status-using-a-sip-encrypted-profile/m-p/1961179#M28907</link>
      <description>&lt;P&gt;I am using CUCM 8.6 with CUPS 8.6 and Jabber.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a SIP Trunk configured between CUCM and CUPS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured the Trunk with a Secure Encrypted SIP Trunk Profile which uses TLS as the transport type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A non-secure profile uses TCP+ UDP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I use the Secure Encrypted Profile, On the Phone Status is not published and sent / not changed automatically&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I use the Unsecure Profile this works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What changes do I need to make in CUCM or CUPS to allow On the Phone Status to be updated automatically using an Encrypted SIP Secuity Profile&lt;/P&gt;</description>
      <pubDate>Sun, 17 Mar 2019 21:24:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-cucm-cups-8-6-phone-status-using-a-sip-encrypted-profile/m-p/1961179#M28907</guid>
      <dc:creator>CCIESingh</dc:creator>
      <dc:date>2019-03-17T21:24:16Z</dc:date>
    </item>
    <item>
      <title>Jabber CUCM- CUPS 8.6 - Phone Status Using A SIP Encrypted Profi</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-cucm-cups-8-6-phone-status-using-a-sip-encrypted-profile/m-p/1961180#M28908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to exchange certificates between the CUCM and CUPS clusters to establish trust. Without this TLS won't come up.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/install_upgrade/deployment/guide/dgcerts.html#wp1062204"&gt;http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/install_upgrade/deployment/guide/dgcerts.html#wp1062204&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 13:23:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-cucm-cups-8-6-phone-status-using-a-sip-encrypted-profile/m-p/1961180#M28908</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2012-06-22T13:23:18Z</dc:date>
    </item>
  </channel>
</rss>

