Troubleshooting
From Taridium
Line 1: | Line 1: | ||
== Installation == | == Installation == | ||
- | === Ioncube Loader === | + | === Ioncube Loader Permission Error === |
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 | 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 | ||
Line 17: | Line 17: | ||
== Conferencing == | == Conferencing == | ||
- | === Personal Conference Rooms | + | === Personal Conference Rooms Disabled in End-User Panel === |
The end-user interface states that personal conference rooms have been disabled. Go to Applications -> Features -> Feature Map and map the feature '''Personal Conference Rooms''' as the prefix you wish to use for the rooms. The extension format is *[selected number prefix] + [extension number] | The end-user interface states that personal conference rooms have been disabled. Go to Applications -> Features -> Feature Map and map the feature '''Personal Conference Rooms''' as the prefix you wish to use for the rooms. The extension format is *[selected number prefix] + [extension number] |
Revision as of 17:14, 2 December 2008
Contents |
Installation
Ioncube Loader Permission Error
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
Personal Conference Rooms Disabled in End-User Panel
The end-user interface states that personal conference rooms have been disabled. Go to Applications -> Features -> Feature Map and map the feature Personal Conference Rooms as the prefix you wish to use for the rooms. The extension format is *[selected number prefix] + [extension number]
Invalid Conference Room
Ipbx claims the conference room number is invalid. This is usually a problem with the conferencing timing source. Meetme conferencing requires a timing source, 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.