<?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: timer bug ends application in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511993#M1213</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your clarification, is there any specific reason or any use case for calling stop call_timer after named timer.&lt;/P&gt;&lt;P&gt;Looks like this happens only when ev_session_indication event occur, i don't see this happen when ev_setup_indication occur.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Raghavendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 May 2015 05:06:41 GMT</pubDate>
    <dc:creator>Raghavendra G V</dc:creator>
    <dc:date>2015-05-05T05:06:41Z</dc:date>
    <item>
      <title>timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511990#M1210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another unexpected behavior when the application's timer handling is less than perfect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See code below. When timer stop call_timer0 is executed without a call_timer0 running, even the named_timer, that should not be affected, is stopped. So the application will never reach named_timer event as it would be more correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;proc sessInd {} {&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt; timer start named_timer 30 TEST&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt; timer stop call_timer0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;proc doNothing {} {}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;set fsm(INIT,ev_session_indication) "sessInd same_state"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;set fsm(INIT,ev_named_timer)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "doNothing same_state"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;fsm define fsm INIT&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 May 2015 19:32:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511990#M1210</guid>
      <dc:creator>paolo bevilacqua</dc:creator>
      <dc:date>2015-05-02T19:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511991#M1211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The timer stop command stops the timer associated with the name.&lt;BR /&gt;Syntax&lt;BR /&gt;timer stop type [name]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example :&lt;BR /&gt;&lt;STRONG&gt;timer stop named_timer&amp;nbsp;&amp;nbsp; timer_1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Raghavendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 May 2015 07:38:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511991#M1211</guid>
      <dc:creator>Raghavendra G V</dc:creator>
      <dc:date>2015-05-04T07:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511992#M1212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe I need to clarify my posting.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;A script is supposed to be running as long there are timer(s) running.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;As you say, "timer stop" is supposed to stop exclusively the related type and name..&lt;/P&gt;&lt;P&gt;What happens, is that doing "timer stop call_timer0", that stops also any named_timer running, making the application terminate. &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Hope the issue is more clear now.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 May 2015 22:39:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511992#M1212</guid>
      <dc:creator>paolo bevilacqua</dc:creator>
      <dc:date>2015-05-04T22:39:24Z</dc:date>
    </item>
    <item>
      <title>Re: timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511993#M1213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your clarification, is there any specific reason or any use case for calling stop call_timer after named timer.&lt;/P&gt;&lt;P&gt;Looks like this happens only when ev_session_indication event occur, i don't see this happen when ev_setup_indication occur.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Raghavendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2015 05:06:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511993#M1213</guid>
      <dc:creator>Raghavendra G V</dc:creator>
      <dc:date>2015-05-05T05:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511994#M1214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I was explaining, this can happen when an application blindly calls "stop call_time0" without a _call_timerl0 running. thing which with other types of timers is harmless.&lt;/P&gt;&lt;P&gt;I provided an example with sess_indication for simplicity only. I see that it happen no matter how the application is started.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 May 2015 08:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511994#M1214</guid>
      <dc:creator>paolo bevilacqua</dc:creator>
      <dc:date>2015-05-05T08:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: timer bug ends application</title>
      <link>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511995#M1215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will check on this issue, as I said earlier don't see this happen when ev_setup_indication occur.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Raghavendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2015 07:02:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/timer-bug-ends-application/m-p/3511995#M1215</guid>
      <dc:creator>Raghavendra G V</dc:creator>
      <dc:date>2015-05-06T07:02:52Z</dc:date>
    </item>
  </channel>
</rss>

