Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: Teviot on February 05, 2009, 04:54:43 AM

Title: asterisk - auto start on boot up
Post by: Teviot on February 05, 2009, 04:54:43 AM: s & all

Is asterisk supposed to start automatically on reboot/boot?

I think that this is not the case on my server.

How can I check and change to auto start if not already set to autostart?
Title: Re: asterisk - auto start on boot up
Post by: SARK devs on February 05, 2009, 07:05:41 AM: Code: [Select]
config show sark sark=service UDPPorts=4569,5060,10000:20000 status=enabled
if status is NOT set to enabled then set it

Code: [Select]
config setprop sark status enabled
S
Title: Re: asterisk - auto start on boot up
Post by: Teviot on February 05, 2009, 07:32:18 AM: Thank you for your response

It turns out that asterisk status is enabled

Thanks you again
Title: Re: asterisk - auto start on boot up
Post by: Teviot on May 18, 2009, 07:18:23 AM: I've got this problem again. It occured after a update of the SME system.

Asterisk is not starting. Tried rebooting a few times with no success.

Any ideas to solve this would be great

Code: [Select]
[root@voip ~]# config show sark sark=service UDPPorts=4569,5060,10000:20000 status=enabled [root@voip ~]# asterisk -rvvvvvvv Asterisk 1.4.21.1, Copyright (C) 1999 - 2008 Digium, Inc. and others. Created by Mark Spencer <markster@digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for detail s. 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. ========================================================================= == Parsing '/etc/asterisk/asterisk.conf': Found == Parsing '/etc/asterisk/extconfig.conf': Found Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist? ) [root@voip ~]#
Title: Re: asterisk - auto start on boot up
Post by: SARK devs on May 18, 2009, 09:06:18 AM: Does asterisk start manually? and..., if it does, is zap loaded (do "zap show status" at the asterisk console).

S
Title: Re: asterisk - auto start on boot up
Post by: Teviot on May 18, 2009, 11:39:25 AM: I am going to assume no. By manually I am guessing you mean
Quote
[root@voip ~]# asterisk

Other than that all I can tell you is above.
Title: Re: asterisk - auto start on boot up
Post by: SARK devs on May 18, 2009, 12:27:57 PM: Asterisk is refusing to start. You can try issuing a commit in sail to see if it starts.

If it doesn't start then it's probably because your SME update has installed a new kernel. The Asterisk drivers in zaptel are specific to each kernel release. If they aren't there (e.g. because you've installed a new kernel release) then you have two choices...

Install the correct zaptel-kmdl driver for your active kernel

go back to the previous kernel release

Kind Regards

S
Title: Re: asterisk - auto start on boot up
Post by: Teviot on May 18, 2009, 01:21:11 PM: Code: [Select]
I did the following which I believe is on the same track [code[root@voip ~]# uname -r 2.6.9-78.0.13.EL [root@voip ~]# /etc/init.d/sark start warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature warning: only V3 signatures can be verified, skipping V4 signature FATAL: Module zaptel not found. Waiting for udev. Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected Starting asterisk: [ OK ]
Asterisk failed to start when the command "asterisk -rvvvvvv" was issued
Does this help to fix my problem?
Title: Re: asterisk - auto start on boot up
Post by: SARK devs on May 18, 2009, 07:51:06 PM: It's telling you what I told you above.

Code: [Select]
FATAL: Module zaptel not found.
You don't have Zaptel drivers installed for kernel 2.6.9-78.0.13.EL; your choices remain unchanged...

you can run your old kernel by rebooting and pressing the space bar at the linux/sme server splash screen and choosing it, or by modifying grub.conf to select the old version (which was probably 2.6.9-78.0.8.EL)

You can install the correct zaptel-kmdl for 2.6.9-78.0.13.EL

Kind Regards

S