Upgrading to 2.x - Revision history

Webmaster: /* Configuration Hints */

2010-04-08T17:31:52Z

Configuration Hints

← Older revision		Revision as of 17:31, 8 April 2010
Line 43:		Line 43:
	[applicationmap]		[applicationmap]
	nway-start = *9,self/both,agi,ipbx/nway.agi		nway-start = *9,self/both,agi,ipbx/nway.agi
		+	* Check if the system is bootproof (DAHDI/Zaptel/Wanrouter)

Webmaster: /* Configuration Hints */

2010-04-08T17:31:09Z

Configuration Hints

← Older revision		Revision as of 17:31, 8 April 2010
Line 32:		Line 32:
	* remove crontab entry for ipbx v.1.2 (old tasker process)		* remove crontab entry for ipbx v.1.2 (old tasker process)
	* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)		* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
-	* If you want to use the built-in dialplan, go to the Admin GUI and select Configuration -> Advanced Setup -> Maintenance -> '''Clear Dialplan and restore to default'''	+	* If you want to use the built-in dialplan, go to the Admin GUI and select '''Configuration''' → '''Advanced Setup''' → '''Maintenance''' → '''Clear Dialplan and restore to default'''
	* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).		* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
	* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.		* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.

Webmaster at 17:29, 8 April 2010

2010-04-08T17:29:36Z

← Older revision		Revision as of 17:29, 8 April 2010
Line 1:		Line 1:
-	This documents describes the changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x	+	This documents describes the configuration changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x. If you want to make use of Taridium's integrated features, such as IVR, Groups, Dynamic Queueing etc., make sure to 'restore' the default ipbx v.2.x dialplan.

	== Configuration Hints ==		== Configuration Hints ==

Webmaster: /* Configuration Hints */

2010-04-08T17:28:10Z

Configuration Hints

← Older revision		Revision as of 17:28, 8 April 2010
Line 29:		Line 29:
	* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)		* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)
	* Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed. E.g. rpm -e astmanproxy		* Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed. E.g. rpm -e astmanproxy
-	* Make sure that ipbx service is running service ipbx restart and that it's setup to start at boot, chkconfig ipbx on!	+	* Make sure that ipbx service is running, (service ipbx restart) and that it's setup to start at boot, chkconfig ipbx on!
	* remove crontab entry for ipbx v.1.2 (old tasker process)		* remove crontab entry for ipbx v.1.2 (old tasker process)
	* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)		* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)

Webmaster: /* Configuration Hints */

2010-04-08T17:26:48Z

Configuration Hints

Webmaster: /* Configuration Hints */

2010-04-08T17:23:54Z

Configuration Hints

← Older revision		Revision as of 17:23, 8 April 2010
Line 5:		Line 5:
	Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users. Another important change is the fact that the ipbx package itself is now architecture agnostic (aka noarch RPM).		Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users. Another important change is the fact that the ipbx package itself is now architecture agnostic (aka noarch RPM).

-	* Update repository ~~according~~ to install ipbx	+	* Update repository accordingly to install ipbx:

	[core]		[core]

Webmaster at 17:23, 8 April 2010

2010-04-08T17:23:36Z

← Older revision		Revision as of 17:23, 8 April 2010
Line 1:		Line 1:
		+	This documents describes the changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x
		+
	== Configuration Hints ==		== Configuration Hints ==

-	Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users.	+	Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users. Another important change is the fact that the ipbx package itself is now architecture agnostic (aka noarch RPM).

	* Update repository according to install ipbx		* Update repository according to install ipbx
Line 22:		Line 24:
	* Always check that database has been upgraded, running ipbx-config never hurts.		* Always check that database has been upgraded, running ipbx-config never hurts.
	* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660		* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660
		+	* On CentOS 4.x make sure you enable the CentOS plus repository and check php.ini for the correct version of the Ioncube encoder.
	* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)		* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)
	* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf		* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf

Webmaster at 01:00, 11 August 2009

2009-08-11T01:00:23Z

← Older revision		Revision as of 01:00, 11 August 2009
Line 30:		Line 30:
	* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)		* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
	* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).		* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
-	* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail!	+	* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.
	* Check that Voicemail options have been changed to \| (pipe) syntax NOT sb124@default when upgrading from Asterisk 1.2		* Check that Voicemail options have been changed to \| (pipe) syntax NOT sb124@default when upgrading from Asterisk 1.2
	* Check that correct Caller ID variables are used: e.g. CALLERID(num) and CALLERID(name) and NOT CALLERIDNAME in your dialplan.		* Check that correct Caller ID variables are used: e.g. CALLERID(num) and CALLERID(name) and NOT CALLERIDNAME in your dialplan.

Webmaster at 16:08, 5 August 2009

2009-08-05T16:08:50Z

Webmaster: /* Configuration Hints */

2009-08-05T16:05:16Z

Configuration Hints

← Older revision		Revision as of 16:05, 5 August 2009
Line 20:		Line 20:

	* perform yum upgrade (install ipbx)		* perform yum upgrade (install ipbx)
-	* Always check that database has been upgraded	+	* Always check that database has been upgraded, running ipbx-config never hurts.
	* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660		* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660
	* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)		* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)

← Older revision		Revision as of 17:26, 8 April 2010
Line 22:		Line 22:

	* perform yum upgrade (install ipbx)		* perform yum upgrade (install ipbx)
-	* Always check that database has been upgraded, running ipbx-config never hurts.	+	* Always check that the database has been upgraded, running ipbx-config never hurts.
	* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660		* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660
	* On CentOS 4.x make sure you enable the CentOS plus repository and check php.ini for the correct version of the Ioncube encoder.		* On CentOS 4.x make sure you enable the CentOS plus repository and check php.ini for the correct version of the Ioncube encoder.
	* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)		* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)
-	* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf	+	* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf, these can be usually copied over from /usr/local/ipbx/install/etc/asterisk since they are rarely customized.
	* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)		* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)
-	* Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed.	+	* Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed. E.g. rpm -e astmanproxy
-	* Make sure that ipbx service is running service ipbx restart and that it's setup to start at boot chkconfig ipbx on!	+	* Make sure that ipbx service is running service ipbx restart and that it's setup to start at boot, chkconfig ipbx on!
	* remove crontab entry for ipbx v.1.2 (old tasker process)		* remove crontab entry for ipbx v.1.2 (old tasker process)
	* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)		* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
		+	* If you want to use the built-in dialplan, go to the Admin GUI and select Configuration -> Advanced Setup -> Maintenance -> '''Clear Dialplan and restore to default'''
	* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).		* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
	* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.		* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.

← Older revision		Revision as of 16:08, 5 August 2009
Line 25:		Line 25:
	* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf		* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf
	* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)		* Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)
-	* Disable the proxy usage in `pbx` table (UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup)	+	* Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed.
-	* Make sure that ipbx service is running service ipbx restart and that it's setup to start at boot chkconfig ipbx on	+	* Make sure that ipbx service is running service ipbx restart and that it's setup to start at boot chkconfig ipbx on!
-	* remove crontab entry for ipbx v.1.2 (tasker)	+	* remove crontab entry for ipbx v.1.2 (old tasker process)
-	* Go through dialplan and make sure all user/ scripts are updated with ipbx/	+	* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
-	* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable)	+	* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
	* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail!		* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail!
	* Check that Voicemail options have been changed to \| (pipe) syntax NOT sb124@default when upgrading from Asterisk 1.2		* Check that Voicemail options have been changed to \| (pipe) syntax NOT sb124@default when upgrading from Asterisk 1.2
-	* Check that correct Caller ID variables are used: e.g. CALLERID(num) and CALLERID(name) and NOT CALLERIDNAME.	+	* Check that correct Caller ID variables are used: e.g. CALLERID(num) and CALLERID(name) and NOT CALLERIDNAME in your dialplan.
-	* Check that any G.729 codec modules have been updated if manually installed.	+	* Check that any G.729 codec modules and licenses have been updated if manually installed.
-	* Copy over /usr/local/ipbx/install/etc/asterisk/http.conf and /usr/local/ipbx/install/etc/asterisk/manager.conf to /etc/asterisk and check extconfig.conf for completeness (ensure that queue configuration is set for realtime).	+	* Copy over /usr/local/ipbx/install/etc/asterisk/http.conf and /usr/local/ipbx/install/etc/asterisk/manager.conf to /etc/asterisk and check extconfig.conf for completeness (ensure that queue configuration is set for realtime). If in doubt copy from /usr/local/ipbx/install/etc/asterisk
	* Possibly adjust sendmail masquerading if necessary, e.g.: MASQUERADE_AS(`example.com')dnl FEATURE(masquerade_envelope)dnl AND FEATURE(masquerade_entire_domain)dnl in sendmail.mc		* Possibly adjust sendmail masquerading if necessary, e.g.: MASQUERADE_AS(`example.com')dnl FEATURE(masquerade_envelope)dnl AND FEATURE(masquerade_entire_domain)dnl in sendmail.mc
	* Add the following to the Integrated Features Configuration:		* Add the following to the Integrated Features Configuration:
	[applicationmap]		[applicationmap]
	nway-start = *9,self/both,agi,ipbx/nway.agi		nway-start = *9,self/both,agi,ipbx/nway.agi