Troubleshooting

From Taridium

(Difference between revisions)
Jump to: navigation, search
(New page: == Installation == === Ioncube Loader === Failed loading /usr/local/php-ioncube/ioncube/ioncube_loader_lin_5.1.so: /usr/local/php-ioncube/ioncube/ioncube_loader_lin_5.1.so: cannot resto...)
Line 13: Line 13:
   [root@pbx ~]#  setenforce 0
   [root@pbx ~]#  setenforce 0
 +
 +
 +
== Conferencing ==
 +
 +
 +
=== Invalid Conference Room ===
 +
 +
Ipbx claims the conference room number is invalid. This is usually a problem with the conferencing timing source.
 +
 +
requires a timing device, either in the form of a Zaptel compatible
 +
timing source or using the pseudo timing device ztdummy.
 +
 +
  [root@ipbx ~]# service asterisk stop
 +
  [root@ipbx ~]# modprobe ztdummy
 +
  [root@ipbx ~]# cat /var/log/messages
 +
 +
and check for any errors, if you get an error message regarding the
 +
kernel version, you will have to re-compile the zaptel source for your
 +
kernel. Use our pre-compilation package zaptel-compile by entering
 +
 +
  [root@ipbx ~]# yum install zaptel compile
 +
 +
and try the modprobe command again. If there are no error you can start
 +
Asterisk again.
 +
 +
  [root@ipbx ~]# service asterisk start
 +
 +
To configure zaptel to start the timing source at boot edit /etc/sysconfig/zaptel and uncomment the appropriate line.

Revision as of 17:09, 2 December 2008

Contents

Installation

Ioncube Loader

Failed loading /usr/local/php-ioncube/ioncube/ioncube_loader_lin_5.1.so: /usr/local/php-ioncube/ioncube/ioncube_loader_lin_5.1.so: cannot restore segment prot after reloc: Permission denied


Try disabling SELinux in /etc/selinux/config

 SELINUX=disabled

To make this active you can either re-start your server or enter the following command:

 [root@pbx ~]#  setenforce 0


Conferencing

Invalid Conference Room

Ipbx claims the conference room number is invalid. This is usually a problem with the conferencing timing source.

requires a timing device, either in the form of a Zaptel compatible timing source or using the pseudo timing device ztdummy.

 [root@ipbx ~]# service asterisk stop
 [root@ipbx ~]# modprobe ztdummy
 [root@ipbx ~]# cat /var/log/messages

and check for any errors, if you get an error message regarding the kernel version, you will have to re-compile the zaptel source for your kernel. Use our pre-compilation package zaptel-compile by entering

 [root@ipbx ~]# yum install zaptel compile

and try the modprobe command again. If there are no error you can start Asterisk again.

 [root@ipbx ~]# service asterisk start

To configure zaptel to start the timing source at boot edit /etc/sysconfig/zaptel and uncomment the appropriate line.

Personal tools
Namespaces
Variants
Actions
Toolbox