<?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: Terminal Connection State HELD with Conference in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/terminal-connection-state-held-with-conference/m-p/3516733#M1297</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No terminal connection doesn't come back to active state. Application should use unhold() API to get the terminal connection to TALKING state.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Nov 2014 22:50:01 GMT</pubDate>
    <dc:creator>mpotluri</dc:creator>
    <dc:date>2014-11-12T22:50:01Z</dc:date>
    <item>
      <title>Terminal Connection State HELD with Conference</title>
      <link>https://community.cisco.com/t5/call-control/terminal-connection-state-held-with-conference/m-p/3516732#M1296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I have an app that conferences several calls together on one CTI port.&amp;nbsp;&amp;nbsp; I have a CTI port with 2 calls conferenced.&amp;nbsp; When this CTI port answers a third call (from a transfer), the terminal connection state goes to HELD.&amp;nbsp;&amp;nbsp; An attempt to conference the third call fails (let's say, due to the conference bridge being full), the app drops that call.&amp;nbsp; So far, everything works correctly.&amp;nbsp; However, the terminal connection state is still in the HELD state, after the third call failed (and the other two are still happily in a conference.)&amp;nbsp; I expected the terminal connection state to be back in ACTIVE state.&amp;nbsp;&amp;nbsp; Is this expected behavior?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jtapi version is 9.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2014 20:40:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/terminal-connection-state-held-with-conference/m-p/3516732#M1296</guid>
      <dc:creator>mstromske</dc:creator>
      <dc:date>2014-11-12T20:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: Terminal Connection State HELD with Conference</title>
      <link>https://community.cisco.com/t5/call-control/terminal-connection-state-held-with-conference/m-p/3516733#M1297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No terminal connection doesn't come back to active state. Application should use unhold() API to get the terminal connection to TALKING state.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2014 22:50:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/terminal-connection-state-held-with-conference/m-p/3516733#M1297</guid>
      <dc:creator>mpotluri</dc:creator>
      <dc:date>2014-11-12T22:50:01Z</dc:date>
    </item>
  </channel>
</rss>

