goautodial install error

[kamirie]

Good Day,

I tried multiple installs with goautodial using goautodial-ce-2.1-final.iso in vBox in a windows 7 32 BIT OS with AMD II x3 425 CPU and after running post-install scripts i always have this error .



Is this some compatibility issue with my vbox/cpu or i have to re-download another installer of goautodial?

All of the installation i tried wouldn't have the "only person in the conference" voice prompt when agents log in to agent gui

Thanks

[williamconley]

Likely. Try Vicibox and if that doesn't work out for you try VMWare instead of VirtualBox.

[kamirie]

Likely. Try Vicibox and if that doesn't work out for you try VMWare instead of VirtualBox.

Thanks william , this leave me with doing it in VMware because i can't also do a clean/complete install of vicibox. Will post update after i tried it with VMware

[williamconley]

Also remember that for some virtual systems 32 bit vs 64 bit makes a difference in both the .iso image you are loading and the "specs" of the virtual container that you are trying to put the software into. Among other things. LOL

[kamirie]

still having same problem with vmware

[kamirie]

I downloaded a new ISO from
http://goautodial.com/download/
goautodial-ce-2.1-final.iso

I don't see any error while installing and it reach the post-install scripts with out any problems . but when i'm about to test ,

1. Asterisk don't auto starts like it should be
2. When i check , sip entries are "cc100" instead of "8001" which i saw from my last Install before i re-downloaded the ISO
3. I can't access any link from the index.php i'm always prompt with this
MySQL connect ERROR: Access denied for user 'cron'@'localhost' (using password: YES)

I tried this on Vbox and VMware workstation both with the same problem.
AMD II x3 425
Windows 7 32 Bit
3 GB RAM

[gardo]

Try using the 64bit version if you're having problems with the GoAutoDial CE 2.1 ISO. It uses CentOS 5.8 64-bit as base.

URL: http://goautodial.org/projects/goautodialce/wiki/64bit

[kamirie]

Try using the 64bit version if you're having problems with the GoAutoDial CE 2.1 ISO. It uses CentOS 5.8 64-bit as base.

URL: http://goautodial.org/projects/goautodialce/wiki/64bit

Good Day,
I follwed gardo's intructions for installation and bump with this error

Code: Select all

Verbosity is at least 21
[2012-11-22 00:41:49]   == Parsing '/etc/asterisk/manager.conf': [2012-11-22 00:                                    41:49] Found
[2012-11-22 00:41:49]   == Manager 'sendcron' logged on from 127.0.0.1
[2012-11-22 00:41:51] NOTICE[6810]: rtp.c:849 process_rfc3389: Comfort noise sup                                    port incomplete in Asterisk (RFC 3389). Please turn off on client if possible. C                                    lient IP: 192.168.1.10
[2012-11-22 00:41:51]        > Channel SIP/8001-00000002 was answered.
[2012-11-22 00:41:51]     -- Executing [8600051@default:1] MeetMe("SIP/8001-0000                                    0002", "8600051|F") in new stack
[2012-11-22 00:41:51]   == Parsing '/etc/asterisk/meetme.conf': [2012-11-22 00:4                                    1:51] Found
[2012-11-22 00:41:51]   == Parsing '/etc/asterisk/meetme-vicidial.conf': [2012-1                                    1-22 00:41:51] Found
[2012-11-22 00:41:51] WARNING[6821]: app_meetme.c:829 build_conf: Unable to open                                     DAHDI pseudo device
[2012-11-22 00:41:51]     -- <SIP/8001-00000002> Playing 'conf-invalid' (languag                                    e 'en')
[2012-11-22 00:41:53]   == Manager 'sendcron' logged off from 127.0.0.1
[2012-11-22 00:41:55]   == Spawn extension (default, 8600051, 1) exited non-zero                                     on 'SIP/8001-00000002'
[2012-11-22 00:41:55]     -- Executing [h@default:1] DeadAGI("SIP/8001-00000002"                                    , "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------                                    -") in new stack
[2012-11-22 00:41:55]     -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses-                                    -PRI-----NODEBUG-----16--------------- completed, returning 0
[2012-11-22 00:41:56]   == Parsing '/etc/asterisk/manager.conf': [2012-11-22 00:                                    41:56] Found
[2012-11-22 00:41:56]   == Manager 'sendcron' logged on from 127.0.0.1
[2012-11-22 00:41:56]     -- Executing [55558600051@default:1] MeetMeAdmin("Loca                                    l/55558600051@default-906d,2", "8600051|K") in new stack
[2012-11-22 00:41:56] WARNING[6843]: app_meetme.c:3134 admin_exec: Conference nu                                    mber '8600051' not found!
[2012-11-22 00:41:56]     -- Executing [55558600051@default:2] Hangup("Local/555                                    58600051@default-906d,2", "") in new stack
[2012-11-22 00:41:56]   == Spawn extension (default, 55558600051, 2) exited non-                                    zero on 'Local/55558600051@default-906d,2'
[2012-11-22 00:41:56]     -- Executing [h@default:1] DeadAGI("Local/55558600051@                                    default-906d,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----1                                    6---------------") in new stack


i have this in the CLI and have invalid conference when trying to log in to agent web gui. I read in the other thread that it was related to Dahdi and when i restarted the server i have this error :
Module dahdi not found
I tried to re-install it

Code: Select all

dahdi-linux kmod-dahdi-linux

and the prompt sed it was already installed and updated but still the same error , can i ask for a head's up on how to repair this or should i do a re-install?
still doing it with vbox

[williamconley]

Gardo I believe has "recompile dahdi" instructions on his site already.

[gardo]

Try doing the 64-bit install again. We recently updated (a week or two) our repo to include the latest CentOS kernel version for DAHDI. Installation should be seamless now.

[jamiemurray]

Hi All,

I've just rebuilt my server due to a HDD failure and am running into what I think is this issue, when running the install, everything goes fine but dahdi doesn't seem to have installed correctly resulting in the meetme rooms failing to operate rendering GAD useless.

Code: Select all

go*CLI> dahdi show status
No DAHDI interface found.
[2013-01-15 20:08:03] WARNING[15512]: chan_dahdi.c:12661 dahdi_show_status: Unable to open /dev/dahdi/ctl: No such file or directory


The scratch install guide located on the goautodial org site wiki worked just a few weeks ago when I installed for a friend and I have rebuilt several times since in case I was missing something but to no avail.

Has there been some sort of change to the repos again?

[williamconley]

1) GoAutoDial 2.1 is not the same thing as a Scratch Install. Scratch install is when you install a stock OS and then run all the necessary commands to install all the necessary software. This generally takes several hours and is a lot of fun, but not what you did if you used the GoAutoDial 2.1 .iso to install from. FYI

2) Did you see any fails during install?

3) Are there any fails during boot? Generally your syslog or boot.msg (or equivalent for CentOS) will have hints if dahdi is failing to start for some reason.

4) You can attempt a re-install of dahdi and see if that helps. There are instructions (i believe) on the goautodial site for recompiling and reinstalling dahdi. Following them may resolve your issue nicely.

[gardo]

Have you upgrade the system (by running "yum upgrade")? It might have installed a newer kernel. Try booting with the default kernel that came with the installation of GoAutoDial (kernel version 2.6.18-308.16.1.el.go). This should have the DAHDI modules.