[resolved] Unable to connect to remote asterisk

[darkwin]

Hi Everyone,

I need some help regarding vicibox 6.0 preload x86_64. installing database was ok, installing vici web was ok but after installing telephony server i was not able to connect asterisk. Here was my step by step installation summary.

--- ViciBox v.6.0 Install Summary ---

Expert : Yes
Legacy : Yes
Database : No
Web : No
Telephony: Yes
First Srv: Yes
Have Arch: No
Archive : No
Firewall : Disabled

--- Configuration Information ---
- Database -
SVN Rev : 2164
IP Addr : 192.168.10.65
Name : asterisk
User : cron
Password : 1234
Cust User: custom
Cust Pass: custom1234
Port : 3306

After rebooting i'm not able to connect asterisk cli "Unable to connect to remote asterisk"

Please help...

[Rudolfmdlt]

Hi Darkwin,

execute "service vicidial start" and tell me what happens?

Please post more details about this install, is it clustered ect?

Rudolf

[darkwin]

Hi Rudolf,

Thanks very much for your reply... I already solve it by typing this command echo "noload => chan_ooh323.so" >> etc.asterisk.modules.conf

Regards
Dark

[williamconley]

Hi Rudolf,

Thanks very much for your reply... I already solve it by typing this command echo "noload => chan_ooh323.so" >> etc.asterisk.modules.conf

Regards
Dark

Good postback

[darkwin]

I mean echo "noload => chan_ooh323.so" >> /etc/asterisk/modules.conf

Hi Wiliamconley and Rudolf

The asterisk cli is resolve but upon checking when I type this "/bin/systemctl" I saw this error below

vicidial.service loaded failed failed LSB: Vicidial Call Center Suit
-.slice loaded active active Root Slice
system-getty.slice loaded active active system-getty.slice
system-network.slice loaded active active system-network.slice
system.slice loaded active active System Slice
user-0.slice loaded active active user-0.slice
user.slice loaded active active User and Session Slice
dbus.socket loaded active running D-Bus System Message Bus Socket
lvm2-lvmetad.socket loaded active listening LVM2 metadata daemon socket
syslog.socket loaded active running Syslog Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe

[williamconley]

cool. but did you reboot? if the service failed on start and you fixed the problem ... that does not travel back in time and fix it during boot.

[Rudolfmdlt]

HI Darkwin,

Please post the output of "screen -r"

Also please post your crontab. If the screens are running and the corn jobs are fine then your system should be fine.

William, is there anything else that I'm missing?

Thanks,

Rudolf

[darkwin]

Hi William,

After I issued that command. I restart the asterisk and reboot the system then after rebooting, the asterisk did not start automatically. I just started it manually by /etc/init.d/asterisk start but the vicidial services still failed and when I reload the asterisk, the only output is 15 lines with warnings and error. I cannot post the error here because when i submitted my post it says ( Your post looks too spamy for a new user, please remove off-site URLs.) something like that.

Hi Rudolf,

Here you go......

viciask:~ # screen -ls
There are screens on:
27184.ASTVDremote (Detached)
27181.ASTVDauto (Detached)
27178.ASTlisten (Detached)
27175.ASTsend (Detached)
27172.ASTupdate (Detached)
1512.ASTfastlog (Detached)
6 Sockets in /var/run/screens/S-root.

I canot post the crontab it says (Your post looks too spamy for a new user, please remove off-site URLs.)

by the this is asterisk 1.8.29.0-vici with new version of vicibox

Regards,
Dark

[williamconley]

Asterisk should not be "started" by you. It is expected to be run in a screen created by the Vicidial service.

If that screen is not running, it's likely your Vicidial service failed. If the screen is running but asterisk is not in it ... either asterisk failed to start, started and crashed, or was never told to start.

When in doubt: kill the vicidial service so it won't load at boot and reboot .. and manually start the vicidial process and dig down to find out what is actually failing.

Before that, of course, check logs and see if you can find the failing process without the need for a deep dig.

[Rudolfmdlt]

Hi Darkwin,

When you're on the console of the machine that asterisk is not starting up, type "asterisk -cvvvvvv". This will start asterisk in the foreground like an application. There will be a lot of outbput, but asterisk should clearly complain why it is not loading.

Also, under the admin->servers->yourserver there is an option at the bottom to auto restart a crashed asterisk. Just see whether this works for you?

Regards,

Rudolf

[darkwin]

Hi Rudolf,

Using restart under system setting wont work too. I already solved the problem by using v.6 vicibox w/ asterisk 1.8.28.2-vici. My previous vicibox was running asterisk 1.8.29.0-vici and i'm not sure if this is version related or something bug from
newer version of asterisk.

I will post A NEW TOPIC for adding a new leads because when I add a new leads it wont show my field in "LIST ID OVERRIDE FOR THIS FILE" from /vicidial/admin_listloader_fourth_gen.php.

Thanks,
Dark