ViciBox_Redux.i686-3.1.12.iso StartUp Issues

[Geil21]

ViciBox_Redux.i686-3.1.12.iso
(downloaded yesterday 9/29/11)

Per your site config is as follows and options selected are:
OpenSuSE v.11.3 32-bit w/ PAE
Asterisk v.1.4.39.2-vici
DAHDI v.2.4.1.2
LibPRI v.1.4.11.5
Sangoma VoiceTime v.1.0.11
MFCR2 via OpenR2 v.1.3.0
ViciDial SVN Trunk v.2.4-334a build 110831-2038
ZoiperWeb v.2.4.0

Dell R410 2 x 2.4GHz Xeon Processors (16 cores)
8 GB LV RDIMMS
RAID 10 - 4 x 250Gb SATA HDD (H700 Hardware Controller with 512k cache)

Fresh Install Stand Alone Server (SVN Trunk)

Install Runs fine except for default-server.conf path error previously described as fixed but not as of yesterday.

Sangoma VoiceTime USB Stick Installed.

Here's the issues:
To get dahdi to load had to manually add wanpipe_voicetime to /etc/dahdi/modules

"/etc/init.d/dahdi start" now works

then run start_asterisk_boot.pl and everything runs fine.

When I reboot I must start dahdi and asterisk manually again

Dahdi does not load on boot
Asterisk does not start on boot

Checked /var/log/messages and did not find any errors re: startup of dahdi or asterisk after reboot.

I tried adding those 2 commands to /etc/rc.d/boot.local and still no luck

As I am not getting any errors, it makes me wonder if the startup scripts are running at all.

Any ideas?

[Geil21]

Side Note:

Same result with or without OS Update

[Geil21]

Ok the issue is with your voicetime installation option.

I reinstalled as if I didn't have a timer, with os updates.

Once installed everything started up just fine.

Then I tried to "zypper install wanpipe-voicetime" and it was already installed (even tho I said not to include it)

Then I simply added "wanpipe_voicetime" to the "/etc/dahdi/modules" list and it fired right up.


So to get the result I wanted for the voice timer I had to do the opposite of what I needed and it worked.

[Kumba]

The DAHDI init script should not be running. The modules are loaded from the /etc/init.d/vicidial init script from the ZAP_MOD variable definition.

It sounds like you didn't do the phase-2 install or something. Not really sure given then info I have.