Getting a not a valid conference no
Added by Juan Kaper almost 12 years ago
Hi,
I'm new to goautodial and installed by following http://goautodial.org/projects/goautodialce/wiki/64bit. I'm using a vps.
Initially my server ip was set to 127.0.0.1Mask:2, and cannot register any softphone. i've run the server update ip pointing it to my vps ip.
I've checked in mysql the conference table and it is showing the correct IP. Ran asterisk -r and saw "Unable to open DAHDI pseudo device". Below is my CLI log
[Jun 19 21:07:51] > Channel SIP/8001-00000002 was answered. [Jun 19 21:07:51] == Manager 'sendcron' logged off from 127.0.0.1 [Jun 19 21:07:51] -- Executing [8600052@default:1] MeetMe("SIP/8001-00000002", "8600052|F") in new stack [Jun 19 21:07:51] == Parsing '/etc/asterisk/meetme.conf': [Jun 19 21:07:51] Found [Jun 19 21:07:51] == Parsing '/etc/asterisk/meetme-vicidial.conf': [Jun 19 21:07:51] Found [Jun 19 21:07:51] WARNING[8490]: app_meetme.c:829 build_conf: Unable to open DAHDI pseudo device [Jun 19 21:07:51] -- <SIP/8001-00000002> Playing 'conf-invalid' (language 'en') [Jun 19 21:07:55] == Spawn extension (default, 8600052, 1) exited non-zero on 'SIP/8001-00000002' [Jun 19 21:07:55] -- Executing [h@default:1] DeadAGI("SIP/8001-00000002", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack [Jun 19 21:07:55] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
Thanks for any help.
Replies (3)
RE: Getting a not a valid conference no
-
Added by Demian Biscocho almost 12 years ago
VPS doesn't have timer devices (or reliable timer devices) that DAHDI needs. Dedicated hardware is recommended.
RE: Getting a not a valid conference no
-
Added by striker 247 almost 12 years ago
make sure you have installed dahdi driver properly
type
dahdi_cfg -vvvv
note: not sure about VPS and dahdi compaitability
br
Striker
www.striker24x7.blogspot.com