<?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: CUCM ad-hoc conference with thrird party SIP phone in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/cucm-ad-hoc-conference-with-thrird-party-sip-phone/m-p/3580379#M2186</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Third party SIP phones are not supported with the CUCM ad hoc conferencing mechanism (which is based on non-RFC standard SIP protocol extensions and behaviours).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only type of conferencing that would be able to work would be RFC SIP standard conferencing, which is managed (including audio mixing) onboard the phone itself - in which case CUCM is not aware of the conference, and there are no interactions with the CUCM ad hoc conferencing feature.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Apr 2018 17:32:17 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2018-04-04T17:32:17Z</dc:date>
    <item>
      <title>CUCM ad-hoc conference with thrird party SIP phone</title>
      <link>https://community.cisco.com/t5/call-control/cucm-ad-hoc-conference-with-thrird-party-sip-phone/m-p/3580378#M2185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been trying to set up an ad-hoc conference with a third party sip-phone as a host. But I am getting 403 Forbidden with "unknown calling DN" after I send an Invite to conference factory URI to initiate the conference. From SIP trunk messaging guide, "The conference initiator calls the conference server using INVITE(Conference Factory URI) to begin a conference. The AS-SIP-EI conference factory URI lookslike @. The UCM routes the request via normal DA dialplan routing using confFactoryDigitString.". Any idea?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2018 17:59:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-ad-hoc-conference-with-thrird-party-sip-phone/m-p/3580378#M2185</guid>
      <dc:creator>rajarshi.basak</dc:creator>
      <dc:date>2018-04-03T17:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM ad-hoc conference with thrird party SIP phone</title>
      <link>https://community.cisco.com/t5/call-control/cucm-ad-hoc-conference-with-thrird-party-sip-phone/m-p/3580379#M2186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Third party SIP phones are not supported with the CUCM ad hoc conferencing mechanism (which is based on non-RFC standard SIP protocol extensions and behaviours).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only type of conferencing that would be able to work would be RFC SIP standard conferencing, which is managed (including audio mixing) onboard the phone itself - in which case CUCM is not aware of the conference, and there are no interactions with the CUCM ad hoc conferencing feature.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2018 17:32:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-ad-hoc-conference-with-thrird-party-sip-phone/m-p/3580379#M2186</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2018-04-04T17:32:17Z</dc:date>
    </item>
  </channel>
</rss>

