Page 1 of 1

when logging out i get a odd asterisk error

PostPosted: Wed Mar 31, 2010 9:43 pm
by bobbymc
asterisk 1.4.27.1 and vicidial 2.0.5

== Manager 'sendcron' logged on from 127.0.0.1
-- Executing [55558600123@vicidial:1] MeetMeAdmin("Local/55558600123@vicidial-61d9,2", "8600123|K") in new stack
[Mar 31 19:42:02] WARNING[10034]: app_meetme.c:2985 admin_exec: Conference number '8600123' not found!
-- Executing [55558600123@vicidial:2] Hangup("Local/55558600123@vicidial-61d9,2", "") in new stack
== Spawn extension (vicidial, 55558600123, 2) exited non-zero on 'Local/55558600123@vicidial-61d9,2'
-- Executing [h@vicidial:1] DeadAGI("Local/55558600123@vicidial-61d9,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0



why does it make a call to that extension 5555XXX that dialplan deosnt even exists?

PostPosted: Wed Mar 31, 2010 11:00 pm
by mflorell
That's the kickall function and you should have it in your dialplan:

exten => _55558600XXX,1,MeetMeAdmin(${EXTEN:4},K)
exten => _55558600XXX,2,Hangup

PostPosted: Thu Apr 01, 2010 1:26 am
by bobbymc
i apologize its there but its saying it cant kill the conf room couse it deosnt exsists. can it be because the room was closed?

PostPosted: Thu Apr 01, 2010 1:52 am
by bobbymc
app_meetme.c:2985 admin_exec: Conference number '8600123' not found!

PostPosted: Thu Apr 01, 2010 7:47 am
by mflorell
that's normal unfortunately. Not sure why the Asterisk developers did that, but it's not anything to worry about.

PostPosted: Tue May 18, 2010 12:03 pm
by mcargile
The MeetMe application keeps a list of active conferences. When no one is in the conference it gets removed from the conferences list. What this error is saying is that it cannot find that conference in the active conference list because no one is in it.

Matt is issuing a kick on the conference to clear out any stray channels that may have gotten stuck in that conference so when another agent logs in and gets placed in this conference you do not have weird behavior. 99.9% of the time there is nothing in the conference so it gives that rather cryptic error.