SOLVED System makes local call every min to Application NoCDR

[Brian Simmons]

I have the following entry in my log repeating about every 60 seconds (usually on the minute exactly). I'm not sure what it is, and a search of the forum didn't turn anything up with the kepwords I used. Any ideas what is going on here, if it is normal or not, and do I need to do anything about it?

[2013-10-23 14:10:00] VERBOSE[4138] pbx_spool.c: -- Attempting call on Local/s@tc-maint for application NoCDR() (Retry 1)
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [s@tc-maint:1] NoCDR("Local/s@tc-maint-00000d6e;2", "") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [s@tc-maint:2] Set("Local/s@tc-maint-00000d6e;2", "TCMAINT=RETURN") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [s@tc-maint:3] Gosub("Local/s@tc-maint-00000d6e;2", "timeconditions,1,1()") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:1] GotoIfTime("Local/s@tc-maint-00000d6e;2", "08:00-17:00,mon-fri,*,*?truestate") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Goto (timeconditions,1,9)
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:9] GotoIf("Local/s@tc-maint-00000d6e;2", "0?falsegoto") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:10] ExecIf("Local/s@tc-maint-00000d6e;2", "0?Set(DB(TC/1)=)") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:11] Set("Local/s@tc-maint-00000d6e;2", "DEVICE_STATE(Custom:TC1)=NOT_INUSE") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:12] ExecIf("Local/s@tc-maint-00000d6e;2", "0?Set(DEVICE_STATE(Custom:TCSTICKY)=INUSE)") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:13] GotoIf("Local/s@tc-maint-00000d6e;2", "0?ivr-2,s,1") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:14] Set("Local/s@tc-maint-00000d6e;2", "TCSTATE=true") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [1@timeconditions:15] Return("Local/s@tc-maint-00000d6e;2", "") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [s@tc-maint:4] System("Local/s@tc-maint-00000d6e;2", "/var/lib/asterisk/bin/schedtc.php 60 /var/spool/asterisk/outgoing 0") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: -- Executing [s@tc-maint:5] Answer("Local/s@tc-maint-00000d6e;2", "") in new stack
[2013-10-23 14:10:00] VERBOSE[4139][C-00000de9] pbx.c: == Spawn extension (tc-maint, s, 5) exited non-zero on 'Local/s@tc-maint-00000d6e;2'
[2013-10-23 14:10:00] NOTICE[4138] pbx_spool.c: Call completed to Local/s@tc-maint

 

[Trimline2]

Brian:

Did you ever get a resolve for this? I just installed a new system that does contain DND hours; 1 time group and 2 time conditions. The log just filled up with these messages. I temporarily deleted the time groups and conditions and all of the messages stopped. This really fills the logs as they appear every second, a lot of them. I'm wondering if there was a trace mode left on somewhere... I'll look around, but for now, mine have been deleted.

 

[islandtech]

Checked several systems that are on * 11.4 and freepbx 2.11 with tc and call flow active, but not incredible, and I don't have those log entries.

 

[Trimline2]

Deleted the conditions and the messages stopped. Re-defined and they start up again.. System("Local/s@tc-maint-000001db;2", "/var/lib/asterisk/bin/schedtc.php 60; that's 8+ message lines in the log every 60 seconds for each extension using time conditions.

What's odd is the sister system (not IncrediblePBX) of this one does not generate the messages. Same module -

• Time Conditions 2.11.0.9 Schmooze Com Inc Enabled

Very perplexing indeed.

 

[Trimline2]

Under Advanced settings, under the heading "Time Condition Module" are the following parameters you can play with:

Enable Maintenance Polling
Maintenance Polling Interval

You are my hero.

You can just disable the polling in "Time Condition Module" and the time conditions still work just fine. I believe this is as you compile when making a time condition to an extension.

Thanks!