<?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 JTAPI Event Indicating That Call Was Not Answered in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/jtapi-event-indicating-that-call-was-not-answered/m-p/4902517#M3440</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I need to detect the following scenarios in a stateless system, ideally - through a single JTAPI event:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Caller has hung-up before getting answered (i.e. while phone was Alerting/ringing).&lt;/LI&gt;&lt;LI&gt;Call was auto hung-up due to an expired timer (i.e. call was not answered for a long period of time).&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a distinct indication to these scenarios in any JTAPI event(s), possibly by the value of its&amp;nbsp;&lt;STRONG&gt;Reason&lt;/STRONG&gt; or&amp;nbsp;&lt;STRONG&gt;CallCtlCause&amp;nbsp;&lt;/STRONG&gt;fields, etc.?&lt;/P&gt;</description>
    <pubDate>Wed, 09 Aug 2023 18:49:53 GMT</pubDate>
    <dc:creator>Bliss</dc:creator>
    <dc:date>2023-08-09T18:49:53Z</dc:date>
    <item>
      <title>JTAPI Event Indicating That Call Was Not Answered</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-event-indicating-that-call-was-not-answered/m-p/4902517#M3440</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I need to detect the following scenarios in a stateless system, ideally - through a single JTAPI event:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Caller has hung-up before getting answered (i.e. while phone was Alerting/ringing).&lt;/LI&gt;&lt;LI&gt;Call was auto hung-up due to an expired timer (i.e. call was not answered for a long period of time).&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a distinct indication to these scenarios in any JTAPI event(s), possibly by the value of its&amp;nbsp;&lt;STRONG&gt;Reason&lt;/STRONG&gt; or&amp;nbsp;&lt;STRONG&gt;CallCtlCause&amp;nbsp;&lt;/STRONG&gt;fields, etc.?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2023 18:49:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-event-indicating-that-call-was-not-answered/m-p/4902517#M3440</guid>
      <dc:creator>Bliss</dc:creator>
      <dc:date>2023-08-09T18:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: JTAPI Event Indicating That Call Was Not Answered</title>
      <link>https://community.cisco.com/t5/call-control/jtapi-event-indicating-that-call-was-not-answered/m-p/4907218#M3448</link>
      <description>&lt;P&gt;I suspect it would be possible to infer those scenarios from JTAPI events/cause/reasons, however I don't have a good source on exactly what those might be, other than to suggest trying the scenarios and looking at the results to see if you can spot the specific tells...&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 16:58:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/jtapi-event-indicating-that-call-was-not-answered/m-p/4907218#M3448</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2023-08-17T16:58:47Z</dc:date>
    </item>
  </channel>
</rss>

