<?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: Request for CUCM API &amp;quot;Call-In&amp;quot; Functionality – Integrati in DevNet General Discussions</title>
    <link>https://community.cisco.com/t5/devnet-general-discussions/request-for-cucm-api-quot-call-in-quot-functionality-integration/m-p/5319255#M2863</link>
    <description>&lt;P&gt;You would perhaps need to look at solution with/using&amp;nbsp;&lt;SPAN&gt;JTAPI, this is the most common API for building CTI applications that need to monitor and control call events in real time.&amp;nbsp;&lt;A href="https://developer.cisco.com/site/jtapi/" target="_blank"&gt;https://developer.cisco.com/site/jtapi/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 10 Aug 2025 13:49:43 GMT</pubDate>
    <dc:creator>bigevilbeard</dc:creator>
    <dc:date>2025-08-10T13:49:43Z</dc:date>
    <item>
      <title>Request for CUCM API "Call-In" Functionality – Integration with Collec</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/request-for-cucm-api-quot-call-in-quot-functionality-integration/m-p/5319217#M2862</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Summary:&lt;/STRONG&gt;&lt;BR /&gt;We require the ability to capture inbound call events ("call-in") through the CUCM API (WebDialer or alternative) for operational integration with our collection system. TAC has confirmed that this is considered a custom service and is out of TAC scope, so we are escalating to the Cisco Dev team for feasibility guidance and potential implementation approaches.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Environment Details:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;CUCM Version:&lt;/STRONG&gt; 14.0.1.13900-155&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Nodes:&lt;/STRONG&gt; 4&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Feature Required:&lt;/STRONG&gt; "Call-In" capability – capturing inbound call data via API&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Current Status:&lt;/STRONG&gt; Outbound call initiation via WebDialer API is working&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Business Impact:&lt;/STRONG&gt; High – required for routing, call tracking, and operational workflows in collections.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Business Requirements:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Capture &lt;STRONG&gt;CTI logs&lt;/STRONG&gt;, call progress, and audio for inbound calls.&lt;/LI&gt;&lt;LI&gt;Integrate captured data with our &lt;STRONG&gt;collection system&lt;/STRONG&gt; for high-priority operational workflows.&lt;/LI&gt;&lt;LI&gt;Route inbound calls to &lt;STRONG&gt;specific extensions&lt;/STRONG&gt; based on predefined criteria.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Background / Timeline:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Feb 26, 2025:&lt;/STRONG&gt; Requirement first identified.&lt;/LI&gt;&lt;LI&gt;Outbound call ("callout") functionality is already operational using CUCM WebDialer SOAP API.&lt;/LI&gt;&lt;LI&gt;No existing solution for inbound ("call-in") capture via API found in documentation.&lt;/LI&gt;&lt;LI&gt;DevNet resource link provided by TAC redirects to community forums; no structured developer support path located.&lt;/LI&gt;&lt;LI&gt;TAC has confirmed this feature is outside standard support scope, hence request for developer team escalation.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Requested Action from Cisco Dev Team:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Confirm whether &lt;STRONG&gt;"call-in"&lt;/STRONG&gt; functionality can be implemented using CUCM API, JTAPI, TAPI, or other available Cisco developer tools.&lt;/LI&gt;&lt;LI&gt;Provide &lt;STRONG&gt;technical documentation, sample code, or API references&lt;/STRONG&gt; that could support capturing inbound call events, logs, and audio.&lt;/LI&gt;&lt;LI&gt;Advise if this requires a &lt;STRONG&gt;custom integration&lt;/STRONG&gt; and, if so, recommended approach or professional services engagement.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Attachments / References:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Original TAC case communication (included above for full context).&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Sun, 10 Aug 2025 09:02:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/request-for-cucm-api-quot-call-in-quot-functionality-integration/m-p/5319217#M2862</guid>
      <dc:creator>r-wahbi</dc:creator>
      <dc:date>2025-08-10T09:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: Request for CUCM API "Call-In" Functionality – Integrati</title>
      <link>https://community.cisco.com/t5/devnet-general-discussions/request-for-cucm-api-quot-call-in-quot-functionality-integration/m-p/5319255#M2863</link>
      <description>&lt;P&gt;You would perhaps need to look at solution with/using&amp;nbsp;&lt;SPAN&gt;JTAPI, this is the most common API for building CTI applications that need to monitor and control call events in real time.&amp;nbsp;&lt;A href="https://developer.cisco.com/site/jtapi/" target="_blank"&gt;https://developer.cisco.com/site/jtapi/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Aug 2025 13:49:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/devnet-general-discussions/request-for-cucm-api-quot-call-in-quot-functionality-integration/m-p/5319255#M2863</guid>
      <dc:creator>bigevilbeard</dc:creator>
      <dc:date>2025-08-10T13:49:43Z</dc:date>
    </item>
  </channel>
</rss>

