Backup and Restore - Revision history

Webmaster at 12:26, 26 August 2014

2014-08-26T12:26:04Z

2011-12-07T19:35:53Z

← Older revision		Revision as of 19:35, 7 December 2011
Line 101:		Line 101:
	Relevant configuration files for Sangoma interface cards are stored in:		Relevant configuration files for Sangoma interface cards are stored in:

-	/etc/wanpipe/	+	/etc/wanpipe/ for Sangoma cards
-	/etc/zaptel.conf	+
-	/etc/sysconfig/zaptel	+	/etc/zaptel.conf for Digium and compatible cards using Zaptel drivers
		+	/etc/sysconfig/zaptel
		+
		+	/etc/dadhi/system for Digium and compatible cards using DAHDI drivers

2010-02-15T17:24:36Z

Call Recording

← Older revision		Revision as of 17:24, 15 February 2010
Line 95:		Line 95:
	=== Call Recording ===		=== Call Recording ===

-	Recorded calls, except for one-touch recordings are stored in the '''monitor''' MySQL database (recording table).	+	[[Call Recording\|Recorded calls]], except for [[User_Call_Recording\|one-touch]] recordings are stored in the '''monitor''' MySQL database (recording table).

	=== PSTN Interface Cards===		=== PSTN Interface Cards===

2010-02-15T17:24:14Z

Voicemail

← Older revision		Revision as of 17:24, 15 February 2010
Line 91:		Line 91:
	=== Voicemail ===		=== Voicemail ===

-	Voicemail files including one-touch recordings are stored in /var/spool/asterisk/voicemail	+	Voicemail files including [[User_Call_Recording\|one-touch]] recordings are stored in /var/spool/asterisk/voicemail

	=== Call Recording ===		=== Call Recording ===

2010-02-15T17:20:06Z

← Older revision		Revision as of 17:20, 15 February 2010
Line 91:		Line 91:
	=== Voicemail ===		=== Voicemail ===

-	Voicemail files are stored in /var/spool/asterisk/voicemail	+	Voicemail files including one-touch recordings are stored in /var/spool/asterisk/voicemail
		+
		+	=== Call Recording ===
		+
		+	Recorded calls, except for one-touch recordings are stored in the '''monitor''' MySQL database (recording table).

	=== PSTN Interface Cards===		=== PSTN Interface Cards===

2010-02-15T17:17:50Z

Other Files

← Older revision		Revision as of 17:17, 15 February 2010
Line 79:		Line 79:
	== Other Files ==		== Other Files ==

-	These files are usually not created on the system, but rather uploaded or created through customizations. It might still make sense to back them up, though.	+	These files are usually not created on the system, but rather uploaded or created through customizations and during use. It might still make sense to back them up, though.

	=== Custom Prompts ===		=== Custom Prompts ===
Line 88:		Line 88:

	Music on hold is stored in /var/lib/asterisk/moh-native/[class name]		Music on hold is stored in /var/lib/asterisk/moh-native/[class name]
		+
		+	=== Voicemail ===
		+
		+	Voicemail files are stored in /var/spool/asterisk/voicemail

	=== PSTN Interface Cards===		=== PSTN Interface Cards===

2010-02-15T17:16:09Z

PSTN Interface Cards

← Older revision		Revision as of 17:16, 15 February 2010
Line 91:		Line 91:
	=== PSTN Interface Cards===		=== PSTN Interface Cards===

-	Relevant configuration files are stored in:	+	Relevant configuration files for Sangoma interface cards are stored in:

	/etc/wanpipe/		/etc/wanpipe/
	/etc/zaptel.conf		/etc/zaptel.conf
	/etc/sysconfig/zaptel		/etc/sysconfig/zaptel

2010-02-15T17:15:45Z

← Older revision		Revision as of 17:15, 15 February 2010
Line 43:		Line 43:
	== Restore ==		== Restore ==

-	To restore ipbx, we recommend that you install a fresh copy of ipbx using the supplied ISO image. If you are restoring from a standard CentOS or RedHat compatible OS, use the repository package [http://web6.taridium.com/taridium-repo-1.0-a.noarch.rpm taridium-repo] and follow standard installation instructions before proceeding with a database restore.	+	To restore ipbx, we recommend that you install a fresh copy of ipbx using the supplied ISO image. If you are restoring from a standard CentOS or RedHat compatible OS, use the repository package [http://web6.taridium.com/taridium-repo-1.0-a.noarch.rpm taridium-repo] and follow standard [[Installing_ipbx\|installation instructions]] before proceeding with a database restore.

	=== Database Restore ===		=== Database Restore ===

2010-02-15T17:15:20Z

Restore

← Older revision		Revision as of 17:15, 15 February 2010
Line 43:		Line 43:
	== Restore ==		== Restore ==

-	To restore ipbx, we recommend that you install a fresh copy of ipbx using the supplied ISO image. If you are restoring from a standard CentOS or RedHat compatible OS, use the repository package [http://web6.taridium.com/taridium-repo-1.0-a.noarch.rpm taridium-repo].	+	To restore ipbx, we recommend that you install a fresh copy of ipbx using the supplied ISO image. If you are restoring from a standard CentOS or RedHat compatible OS, use the repository package [http://web6.taridium.com/taridium-repo-1.0-a.noarch.rpm taridium-repo] and follow standard installation instructions before proceeding with a database restore.

	=== Database Restore ===		=== Database Restore ===

2010-02-15T17:14:35Z

← Older revision		Revision as of 17:14, 15 February 2010
Line 41:		Line 41:
	Note that depending on your CDR deletion schedules this file can have a considerable size.		Note that depending on your CDR deletion schedules this file can have a considerable size.

-	== Database Restore ==	+	== Restore ==
		+
		+	To restore ipbx, we recommend that you install a fresh copy of ipbx using the supplied ISO image. If you are restoring from a standard CentOS or RedHat compatible OS, use the repository package [http://web6.taridium.com/taridium-repo-1.0-a.noarch.rpm taridium-repo].
		+
		+	=== Database Restore ===

	On a clean install from scratch, always run ipbx-config with option '''1''' to configure DB users and permissions.		On a clean install from scratch, always run ipbx-config with option '''1''' to configure DB users and permissions.