I was searching for help on how to handle the errors that are returned
from the MeetMe application.
for instance.
1) if a user tries to join a conference that is locked, allison says that
the conference is locked and then comes back to the dialplan, however it
does not continue down the dialplan.
I have a meetme command on Priority 8, and the CLI says that it returned
non zero (as the wiki states it would be -1).
I tried to use 109 priority thinking it is 101+n, but i cannot have it go
back in time to priority 7, becaue it would just loop.
How does one handle this?
When i'm in a conference, and I press the pound key, it does exit out
nicely and continue down the dialplan, i have some NoOp on the next
priority after the MeetMe command and it flows nicely from there.
-- Accepting a maximum of 4 digits.
-- Playing 'conf-getconfno' (language 'en')
-- User entered '1234'
-- Executing NoOp("SIP/2001-e4e7", "user entered conf no:
1234")
-- Executing MeetMe("SIP/2001-e4e7", "1234|p")
-- Playing 'conf-locked' (language 'en')
== Spawn extension (ivr-join-conf, s, 8) exited non-zero on
'SIP/2001-e4e7'
I also get the error if they enter a conf # that is not configured.
Allison says that that is an invalid conference number, please try again,
and the same error:
-- Accepting a maximum of 4 digits.
-- Playing 'conf-getconfno' (language 'en')
-- User entered '5678'
-- Executing NoOp("IAX2/4000@192.168.1.141:4569-4", "user
entered conf
no: 5678")
-- Executing MeetMe("IAX2/4000@192.168.1.141:4569-4",
"5678|p")
== Parsing '/etc/asterisk/meetme.conf': Found
-- Playing 'conf-invalid' (language 'en')
== Spawn extension (ivr-join-conf, s, 8) exited non-zero on
'IAX2/4000@192.168.1.141:4569-4'
-- Hungup 'IAX2/4000@192.168.1.141:4569-4'
However my dialplan has an 8 and a 109 priority both are NoOp.. and they
are never triggered.
Thanks for some help on this in advance...
