<?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 Detect start of new call for media forking in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/detect-start-of-new-call-for-media-forking/m-p/3451874#M448</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way (native to the API and its built-in providers) to detect the beginning of a new incoming SIP call on a CUBE and send that information to a registered application so that the application can automatically request media forking?&amp;nbsp; Or do I have to run a debug and pipe the output somewhere, and then pick up on the new calls and request the media forking once the debugs show the call ID?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 May 2014 18:22:10 GMT</pubDate>
    <dc:creator>eric.butcher</dc:creator>
    <dc:date>2014-05-13T18:22:10Z</dc:date>
    <item>
      <title>Detect start of new call for media forking</title>
      <link>https://community.cisco.com/t5/call-control/detect-start-of-new-call-for-media-forking/m-p/3451874#M448</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a way (native to the API and its built-in providers) to detect the beginning of a new incoming SIP call on a CUBE and send that information to a registered application so that the application can automatically request media forking?&amp;nbsp; Or do I have to run a debug and pipe the output somewhere, and then pick up on the new calls and request the media forking once the debugs show the call ID?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 May 2014 18:22:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/detect-start-of-new-call-for-media-forking/m-p/3451874#M448</guid>
      <dc:creator>eric.butcher</dc:creator>
      <dc:date>2014-05-13T18:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Detect start of new call for media forking</title>
      <link>https://community.cisco.com/t5/call-control/detect-start-of-new-call-for-media-forking/m-p/3451875#M449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Please have a look at the document in this URL- &lt;A href="https://supportforums.cisco.com/document/93881/cisco-mediasense-and-cisco-unified-border-element-cube-network-based-media-recording" title="https://supportforums.cisco.com/document/93881/cisco-mediasense-and-cisco-unified-border-element-cube-network-based-media-recording"&gt;Cisco MediaSense and Cisco Unified Border Element (CUBE) for Network based Media Recording Solution | Cisco Technical Su…&lt;/A&gt; for related information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Geevarghese&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2014 12:26:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/detect-start-of-new-call-for-media-forking/m-p/3451875#M449</guid>
      <dc:creator>Geevarghese Cheria</dc:creator>
      <dc:date>2014-05-19T12:26:05Z</dc:date>
    </item>
  </channel>
</rss>

