Topic: Conference Rooms stopped working [Comments: 4]
escherrer
Mon, 05/24/2010 - 20:30 | Conference Rooms stopped working
Hello,
Has anyone run into an issue where the conference rooms stopped working?
Calling into a conference room access number gets the response, "the conference room number is invalid, please try again."
-- Parsing '/etc/asterisk/meetme.conf': [May 24 21:26:10] WARNING[9008]: app_meetme.c:772 build_conf: Unable to open pseudo device
-- Playing 'conf-invalid' (language 'en')
-- Playing 'conf-getconfno' (language 'en')
"zap show status" not showing any zaptel interface found. Doing a "zap restart" did not help either.
thirdlane-02*CLI> zap show status
No Zaptel interface found.
[May 24 21:18:31] WARNING[8796]: chan_zap.c:10086 zap_show_status: Unable to open /dev/zap/ctl: Permission denied
thirdlane-02*CLI> zap restart
Destroying channels and reloading zaptel configuration.
-- Parsing '/etc/asterisk/zapata.conf': -- Automatically generated pseudo channel
If anyone has seen this behavior before and has any ideas, please let me know. I suspect it may have something to do with upgrading our kernel from 4.7 to 5.3. We didn't have anyone report the issue for about a week after the upgrade, so not sure if it's just coincidence, but I'm betting it hasn't worked since the upgrade to the new kernel.
Thanks,
Eric
foreThought.net
Tue, 05/25/2010 - 04:49 | Did you try to recompile
Did you try to recompile zaptel from source?
Tue, 05/25/2010 - 10:26 | you mean dahdi? zaptel was
you mean dahdi? zaptel was replaced nearly 2 yrs ago
Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com
Tue, 05/25/2010 - 10:33 | for the record changing
for the record changing versions of dahdi require a recompile of asterisk. If entering an already built source tree you need to issue a 'make distclean' before './configure' and 'make menuselect'.
Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com
Wed, 05/26/2010 - 15:03 | Thanks for the help. I think
Thanks for the help. I think we will for sure be switching over to Dahdi when we get our new server up and running. Another engineer inadvertently rebooted the Thirdlane server last night, and now the
ZapTel channel is working again. So that part is good. I've made notes about Dahdi to make sure we
use that going forward.
Thanks,
Eric