Asterisk doesn't seem to load on startup

[farmerjim]

Ignore the footer this is the setup
Dell Poweredge T110, 4Gb RAM, 2 x 500Mb HDD
VICIdial VERSION: 2.6-375a BUILD: 120831-1523
Asterisk 1.4.39.2-vici
vicibox-redux 3.1.15 from iso
No additional software

I installed this and updated to the latest SVN. I couldn't get any extensions to register and then when I run /etc/asterisk/asterisk -r I get the following

Asterisk 1.4.39.2-vici, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)

It seems asterisk isn't running as if I then run asterisk -vvvvvvc asterisk starts and I can register an extension.
Does anyone have any ides as to why asterisk won't run at startup?

[williamconley]

Asterisk is started as a part of the Vicidial service. IF the Vicidial service fails before asterisk, it may never attempt to start asterisk.

Also: Why would you install 3.1.15 instead of 4.0?

[farmerjim]

Firstly I hadn't realised v4 was out. Secondly how do I troubleshoot this issue then if it seems the vicidial service isn't working. Where and how is it started?

[farmerjim]

I've done some digging on this. The vicidial service isn't starting and if i run /etc/init.d/vicidial start I get

Loading DAHDI drivers
Starting Sangoma wanrouter driver
./vicidial: line 294: start: command not found
Sangoma failed to load! Fallback to module!
Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
/sbin/modprobe -r [-n] [-i] [-v] <modulename> ...
/sbin/modprobe -l -t <dirname> [ -a <modulename> ...]
NOT loaded

This is a SIP only system, not using an E1 card. What do I need to do to get this working.

[DomeDan]

You probably updated the OS during the install, that installs a new kernel and then
you need to recompile dahdi viewtopic.php?f=8&t=25286#p87454

[Vince-0]

I have noticed that on fresh Vicibox 3.1.15 preload ISO installs the file /etc/init.d/vicidial is not executable. chmod +x /etc/init.d/vicidial fixed that.

[farmerjim]

I did update the OS on install! Eventually I downloaded Vicibox 4.0 and installed that and it went in first time. Thanks for all the help I'll bear this in mind if I ever use 3.1.15 again. 4.0 looks good anyway!

[williamconley]

zypper refresh and zypper up require a reboot before installation of Vicidial. If you don't reboot first, the vicidial software will install with the old (still running) kernel and then when you do reboot the new kernel will not match the just installed vicidial software. now you need to recompile all the vicidial software to match the kernel just because you didn't reboot before installing. pain in the tush, but true.

[GaD]

Actually you don't necesarily need to re-install DAHDI, you need to START it. Although you could install a newer version of it, it will do nothing if it is not started first. Do this:

Code: Select all

/etc/init.d/dahdi start

Once that is done try to start asterisk

Code: Select all

/etc/init.d/asterisk -vvvvvc

(you can add more 'v's for more verbose if needed)
read the log found at /var/log/asterisk/<something> (can't remember the name now). Asterisk will not start unless DaHDI is running EVEN IF YOU DON'T USE DAHDI, or think you don't need it. The end of the matter is that you will most always need some part of DAHDI, specially the zt_dummy (not sure if it is still called that way), as this is a timing source.

If you've started DAHDI and Asterisk is now able to run, you might want to chech if DADHI is set to start on boot by doing:

Code: Select all

chkconfig --list | grep -i dahdi

You should get something like:

Code: Select all

dahdi                     0:off  1:off  2:off  3:off  4:off  5:off  6:off

In my case, given my asterisk version I actually found this:

Code: Select all

#chkconfig --list | grep -i zap
zaptel                    0:off  1:off  2:off  3:on   4:off  5:on   6:off


Zaptel is the old name for DAHDI. I believe you can simply run

Code: Select all

chkconfig dahdi on

To autostart dahdi (or zaptel). Do a Google on 'chkconfig dahdi' and see how you can automagically set dahdi to start on the correct runtime levels....