[asterisk-users] Asterisk-11 loop behaviour

[Matthew Jordan]

On Mon, Jun 24, 2013 at 2:37 PM, James B. Byrne <byrnejb at harte-lyne.ca>wrote:

> Arch = x86_64
> OS = CentOS-6.4 (freepbx)
> Asterisk = 11.4.0
> FreePBX = 2.11.0.2
>
> Snom870 Handsets
>
>
> We are in the process of moving to an Asterisk based PBX.  At the
> moment most things work as we wish.  However, I have just notices that
> when I force a reload using 'amportal a reload' I see this loop start
> in 'asterisk -rvvvvvvvvvv':
>
>        > Channel Local/s at tc-maint-000002a4;1 was answered.
>        > Launching NoCDR() on Local/s at tc-maint-000002a4;1
> [2013-06-24 15:22:32] NOTICE[32678]: pbx_spool.c:402 attempt_thread:
> Call completed to Local/s at tc-maint
> [2013-06-24 15:22:32] NOTICE[32678]: pbx_spool.c:402 attempt_thread:
> Call completed to Local/s at tc-maint
>   == Spawn extension (tc-maint, s, 5) exited non-zero on
> 'Local/s at tc-maint-000002a4;2'
>     -- Attempting call on Local/s at tc-maint for application NoCDR()
> (Retry 1)
>     -- Executing [s at tc-maint:1] NoCDR("Local/s at tc-maint-000002a6;2",
> "") in new stack
>     -- Executing [s at tc-maint:2] Set("Local/s at tc-maint-000002a6;2",
> "TCMAINT=RETURN") in new stack
>     -- Executing [s at tc-maint:3] Gosub("Local/s at tc-maint-000002a6;2",
> "timeconditions,1,1()") in new stack
>     -- Executing [1 at timeconditions:1]
> GotoIfTime("Local/s at tc-maint-000002a6;2",
> "08:00-17:00,mon-fri,*,*?truestate") in new stack
>     -- Goto (timeconditions,1,9)
>     -- Executing [1 at timeconditions:9]
> GotoIf("Local/s at tc-maint-000002a6;2", "0?falsegoto") in new stack
>     -- Executing [1 at timeconditions:10]
> ExecIf("Local/s at tc-maint-000002a6;2", "0?Set(DB(TC/1)=)") in new
> stack
>     -- Executing [1 at timeconditions:11]
> Set("Local/s at tc-maint-000002a6;2",
> "DEVICE_STATE(Custom:TC1)=NOT_INUSE") in new stack
>     -- Executing [1 at timeconditions:12]
> ExecIf("Local/s at tc-maint-000002a6;2",
> "0?Set(DEVICE_STATE(Custom:TCSTICKY)=INUSE)") in new stack
>     -- Executing [1 at timeconditions:13]
> GotoIf("Local/s at tc-maint-000002a6;2", "0?ext-group,417,1") in new
> stack
>     -- Executing [1 at timeconditions:14]
> Set("Local/s at tc-maint-000002a6;2", "TCSTATE=true") in new stack
>     -- Executing [1 at timeconditions:15]
> Return("Local/s at tc-maint-000002a6;2", "") in new stack
>     -- Executing [s at tc-maint:4] System("Local/s at tc-maint-000002a6;2",
> "/var/lib/asterisk/bin/schedtc.php 60 /var/spool/asterisk/outgoing
> 1") in new stack
>     -- Executing [s at tc-maint:5] Answer("Local/s at tc-maint-000002a5;2",
> "") in new stack
>        > Channel Local/s at tc-maint-000002a5;1 was answered.
>        > Launching NoCDR() on Local/s at tc-maint-000002a5;1
> [2013-06-24 15:22:32] NOTICE[32681]: pbx_spool.c:402 attempt_thread:
> Call completed to Local/s at tc-maint
> [2013-06-24 15:22:32] NOTICE[32681]: pbx_spool.c:402 attempt_thread:
> Call completed to Local/s at tc-maint
>
> It is not an infinite loop but it does go on for an inordinately long
> time.  Does anyone here recognize what is happening and can provide me
> with an explanation?
>

Since it is pbx_spool doing the processing, you probably have something
creating a callfile in /var/spool/asterisk/outgoing on startup (or
periodically).

I did a quick Google search and found out that this particular context is
used by FreePBX 2.9's Time Conditions feature - see
http://www.freepbx.org/forum/freepbx-distro/distro-discussion-help/odd-failed-calls-in-logs
for
more information.

-- 
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130625/fdd7ceb9/attachment.htm>