Troubleshooting

From Taridium

Revision as of 20:00, 15 December 2008 (view source) Webmaster (Talk | contribs) ← Older edit		Revision as of 20:00, 15 December 2008 (view source) Webmaster (Talk | contribs) (→No call ID displayed) Newer edit →
Line 5:		Line 5:
	There is no entry for '''call ID''' in the CDR viewer.		There is no entry for '''call ID''' in the CDR viewer.
-	You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages.	+	You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages. E.g.:
		+
		+	yum install asterisk-addons
	== Installation ==		== Installation ==

---

Revision as of 20:00, 15 December 2008

Contents 1 CDR 1.1 No call ID displayed 2 Installation 2.1 Ioncube Loader Permission Error 3 Conferencing 3.1 Personal Conference Rooms Disabled in End-User Panel 3.2 Invalid Conference Room

CDR

No call ID displayed

There is no entry for call ID in the CDR viewer.

You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages. E.g.:

 yum install asterisk-addons

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.