<?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: JtapiTestTool not displaying a terminal to answer call in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497929#M1075</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah yes, media terminal observers.&amp;nbsp;&amp;nbsp; Ok, I added them and it now works.&amp;nbsp; I have a call up.&amp;nbsp; Thanks again, and I'll mark this as 'answered'.&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>Thu, 19 Jun 2014 19:13:40 GMT</pubDate>
    <dc:creator>mstromske</dc:creator>
    <dc:date>2014-06-19T19:13:40Z</dc:date>
    <item>
      <title>JtapiTestTool not displaying a terminal to answer call</title>
      <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497925#M1071</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; Seeing strange behavior when using the JtapiTestTool.&amp;nbsp; I am trying to perform a basic call.&amp;nbsp; However, there is no terminal present to answer the call.&amp;nbsp; This happens when I run the tool on both Mac and linux.&amp;nbsp; Also, I get popups that mention "this function must use treeLock" and I see a ton of stack traces in the console.&amp;nbsp; Attached is a pic of the tool with a CTI port in ALERTing with no terminal to answer it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using Java version 1.7&lt;/P&gt;&lt;P&gt;JtapiTestTool 9.0.1&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>Thu, 19 Jun 2014 15:45:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497925#M1071</guid>
      <dc:creator>mstromske</dc:creator>
      <dc:date>2014-06-19T15:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: JtapiTestTool not displaying a terminal to answer call</title>
      <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497926#M1072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you try with the attached jar and let me know if the issue is resolved? (backup the current CiscoJtapi*.jar file, unzip the attached file, copy CiscoJtapiTest.jar to the same location and run this jar).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 17:50:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497926#M1072</guid>
      <dc:creator>mpotluri</dc:creator>
      <dc:date>2014-06-19T17:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: JtapiTestTool not displaying a terminal to answer call</title>
      <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497927#M1073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohan,&lt;/P&gt;&lt;P&gt;Thanks for the quick response.&amp;nbsp; The new jar works much better.&amp;nbsp; I can now see a terminal and answer the call.&amp;nbsp; However, the call doesn't stay up long.&amp;nbsp; About 12 seconds later, the call drops.&amp;nbsp; Not sure what is going on here.&amp;nbsp; Attached are 2 pics: one of the stack traces from the console, and the other showing the events that occurred during the call.&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>Thu, 19 Jun 2014 18:44:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497927#M1073</guid>
      <dc:creator>mstromske</dc:creator>
      <dc:date>2014-06-19T18:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: JtapiTestTool not displaying a terminal to answer call</title>
      <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497928#M1074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Matt,&lt;/P&gt;&lt;P&gt;&amp;nbsp; CTIPorts are used for the call which need a 'Media Terminal Observer'. Right click on the CTIPorts, select 'Add Observer' =&amp;gt; Media Terminal Observer on both the devices and retry. Let us know the result.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 18:56:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497928#M1074</guid>
      <dc:creator>mpotluri</dc:creator>
      <dc:date>2014-06-19T18:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: JtapiTestTool not displaying a terminal to answer call</title>
      <link>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497929#M1075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah yes, media terminal observers.&amp;nbsp;&amp;nbsp; Ok, I added them and it now works.&amp;nbsp; I have a call up.&amp;nbsp; Thanks again, and I'll mark this as 'answered'.&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>Thu, 19 Jun 2014 19:13:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapitesttool-not-displaying-a-terminal-to-answer-call/m-p/3497929#M1075</guid>
      <dc:creator>mstromske</dc:creator>
      <dc:date>2014-06-19T19:13:40Z</dc:date>
    </item>
  </channel>
</rss>

