Troubleshooting - Revision history

Webmaster at 17:03, 12 December 2011

2011-12-12T17:03:40Z

← Older revision		Revision as of 17:03, 12 December 2011
Line 25:		Line 25:
	You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages. E.g.:		You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages. E.g.:

-	[root@pbx ~]# yum install ~~asterisk~~-addons	+	<pre style="font-size: 12px;">
		+	[root@pbx ~]# yum install asterisk16-addons
		+	</pre>
		+
		+	or
		+
		+	<pre style="font-size: 12px;">
		+	[root@pbx ~]# yum install asterisk18-addons
		+	</pre>
		+
		+	depending on the version of Asterisk you are using.

	== Installation ==		== Installation ==
Line 36:		Line 46:
	Try disabling SELinux in /etc/selinux/config		Try disabling SELinux in /etc/selinux/config

		+	<pre style="font-size: 12px;">
	SELINUX=disabled		SELINUX=disabled
		+	</pre>

	To activate the setting above you can either re-start your server, or enter the following command:		To activate the setting above you can either re-start your server, or enter the following command:

		+	<pre style="font-size: 12px;">
	[root@pbx ~]# setenforce 0		[root@pbx ~]# setenforce 0
		+	</pre>

	=== Ioncube File Not Permissioned ===		=== Ioncube File Not Permissioned ===
Line 61:		Line 75:
	timing source or using the pseudo timing device ztdummy.		timing source or using the pseudo timing device ztdummy.

		+	<pre style="font-size: 12px;">
	[root@ipbx ~]# service asterisk stop		[root@ipbx ~]# service asterisk stop
-	[root@ipbx ~]# modprobe ~~ztdummy~~	+	[root@ipbx ~]# modprobe dahdi_dummy
	[root@ipbx ~]# cat /var/log/messages		[root@ipbx ~]# cat /var/log/messages
		+	</pre>

	and check for any errors, if you get an error message regarding the		and check for any errors, if you get an error message regarding the
Line 69:		Line 85:
	kernel. Use our pre-compilation package zaptel-compile by entering		kernel. Use our pre-compilation package zaptel-compile by entering

		+	<pre style="font-size: 12px;">
	[root@ipbx ~]# yum install zaptel-compile		[root@ipbx ~]# yum install zaptel-compile
		+	</pre>

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

		+	<pre style="font-size: 12px;">
	[root@ipbx ~]# service asterisk start		[root@ipbx ~]# service asterisk start
		+	</pre>

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

Webmaster: /* Ioncube Loader Permission Error */

2011-12-12T17:00:44Z

Ioncube Loader Permission Error

← Older revision		Revision as of 17:00, 12 December 2011
Line 38:		Line 38:
	SELINUX=disabled		SELINUX=disabled

-	To ~~make this active~~ you can either re-start your server or enter the following command:	+	To activate the setting above you can either re-start your server, or enter the following command:

	[root@pbx ~]# setenforce 0		[root@pbx ~]# setenforce 0

Webmaster at 17:00, 12 December 2011

2011-12-12T17:00:01Z

← Older revision		Revision as of 17:00, 12 December 2011
Line 1:		Line 1:
		+	== Host Based Firewall ==
		+
		+	If you have difficulties accessing the web interface or establishing SIP/IAX traffic, make sure your host firewall does allow the desired traffic.
		+
		+	To check if your host firewall (e.g. standard CentOS/RedHat installation) is affecting traffic, try turning iptables off:
		+
		+	<pre style="font-size: 12px;">
		+	[root~]# service iptables off
		+	</pre>
		+
		+	A default iptables configuration file can be found at /usr/local/ipbx/default-iptables
		+
	== Using SIP Trunks ==		== Using SIP Trunks ==

Webmaster at 22:28, 8 June 2010

2010-06-08T22:28:02Z

← Older revision		Revision as of 22:28, 8 June 2010
Line 1:		Line 1:
-
	== Using SIP Trunks ==		== Using SIP Trunks ==

	My calls work fine, but I don't hear a ringback tone.		My calls work fine, but I don't hear a ringback tone.

-	Go to '''Advanced Setup''' -> '''Configuration''' and check the '''Force ringback tone on trunk calls'''.	+	Go to '''Advanced Setup''' → '''Configuration''' and check the '''Force ringback tone on trunk calls''' under '''Trunks'''.

	== CDR ==		== CDR ==

Webmaster at 22:27, 8 June 2010

2010-06-08T22:27:14Z

← Older revision		Revision as of 22:27, 8 June 2010
Line 1:		Line 1:
		+
		+	== Using SIP Trunks ==
		+
		+	My calls work fine, but I don't hear a ringback tone.
		+
		+	Go to '''Advanced Setup''' -> '''Configuration''' and check the '''Force ringback tone on trunk calls'''.
		+
	== CDR ==		== CDR ==

Webmaster at 20:04, 15 December 2008

2008-12-15T20:04:32Z

← Older revision		Revision as of 20:04, 15 December 2008
Line 24:		Line 24:
	[root@pbx ~]# setenforce 0		[root@pbx ~]# setenforce 0

		+	=== Ioncube File Not Permissioned ===
		+
		+	Example:
		+
		+	The encoded file /var/www/html/conf/license-XXXXXXXXXXXX.php is not permissioned for 192.168.213.124
		+
		+	Your license is locked to your network interface MAC address. Please contact Taridium licensing@taridium.com to reset your license.

	== Conferencing ==		== Conferencing ==

Webmaster: /* No call ID displayed */

2008-12-15T20:01:08Z

No call ID displayed

← Older revision		Revision as of 20:01, 15 December 2008
Line 7:		Line 7:
	You might be using a custom version of the underlying Asterisk Addons package. Please make sure you use the latest taridium packages. E.g.:		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	+	[root@pbx ~]# yum install asterisk-addons

	== Installation ==		== Installation ==

Webmaster: /* No call ID displayed */

2008-12-15T20:00:58Z

No call ID displayed

← Older revision		Revision as of 20:00, 15 December 2008
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 ==

Webmaster at 20:00, 15 December 2008

2008-12-15T20:00:33Z

← Older revision		Revision as of 20:00, 15 December 2008
Line 1:		Line 1:
		+	== 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.
		+
	== Installation ==		== Installation ==

Webmaster at 17:17, 2 December 2008

2008-12-02T17:17:19Z

← Older revision		Revision as of 17:17, 2 December 2008
Line 34:		Line 34:
	kernel. Use our pre-compilation package zaptel-compile by entering		kernel. Use our pre-compilation package zaptel-compile by entering

-	[root@ipbx ~]# yum install zaptel compile	+	[root@ipbx ~]# yum install zaptel-compile

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