Comms Documentation - Revision history

Webmaster at 18:32, 14 September 2016

2016-09-14T18:32:06Z

← Older revision		Revision as of 18:32, 14 September 2016
Line 34:		Line 34:
	The administrator interface controls the general settings of the system. It provides status information, plan, reseller, billing and customer management. It allows you to add new customers/PBXs, called 'enterprises' and configure DID/DDIs, as well as manage the device types, such as phones and other VoIP end points.		The administrator interface controls the general settings of the system. It provides status information, plan, reseller, billing and customer management. It allows you to add new customers/PBXs, called 'enterprises' and configure DID/DDIs, as well as manage the device types, such as phones and other VoIP end points.

-	* Main Article: [[Comms Administrator Interface]]	+	* Main Article: '''[[Comms Administrator Interface]]'''

	====Enterprise Interface====		====Enterprise Interface====
Line 40:		Line 40:
	The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.		The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.

-	* Main Article: [[Comms Enterprise Interface]]	+	* Main Article: '''[[Comms Enterprise Interface]]'''

	====End User Panel Interface====		====End User Panel Interface====
Line 46:		Line 46:
	The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.		The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.

-	* Main Article: [[Comms User Panel]]	+	* Main Article: '''[[Comms User Panel]]'''

	====Console====		====Console====
Line 52:		Line 52:
	The console gives users the ability to monitor other extensions, place, receive and transfer calls.		The console gives users the ability to monitor other extensions, place, receive and transfer calls.

-	* Main Article: [[Comms Console]]	+	* Main Article: '''[[Comms Console]]'''

	====ITSP Interface====		====ITSP Interface====
Line 68:		Line 68:
	The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications. The CDR records are held in a separate 'cdr' database.		The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications. The CDR records are held in a separate 'cdr' database.

-	Main Article: [[Comms CDR]].	+	Main Article: '''[[Comms CDR]]'''.

	=== Static Configuration ===		=== Static Configuration ===

	Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].		Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].

Webmaster at 18:25, 14 September 2016

2016-09-14T18:25:21Z

← Older revision		Revision as of 18:25, 14 September 2016
Line 47:		Line 47:

	* Main Article: [[Comms User Panel]]		* Main Article: [[Comms User Panel]]
		+
		+	====Console====
		+
		+	The console gives users the ability to monitor other extensions, place, receive and transfer calls.
		+
		+	* Main Article: [[Comms Console]]

	====ITSP Interface====		====ITSP Interface====

Webmaster: /* comms Overview */

2016-07-20T15:17:31Z

comms Overview

← Older revision		Revision as of 15:17, 20 July 2016
Line 34:		Line 34:
	The administrator interface controls the general settings of the system. It provides status information, plan, reseller, billing and customer management. It allows you to add new customers/PBXs, called 'enterprises' and configure DID/DDIs, as well as manage the device types, such as phones and other VoIP end points.		The administrator interface controls the general settings of the system. It provides status information, plan, reseller, billing and customer management. It allows you to add new customers/PBXs, called 'enterprises' and configure DID/DDIs, as well as manage the device types, such as phones and other VoIP end points.

-	Main Article: [[Comms Administrator Interface]]	+	* Main Article: [[Comms Administrator Interface]]

	====Enterprise Interface====		====Enterprise Interface====
Line 40:		Line 40:
	The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.		The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.

-	Main Article: [[Comms Enterprise Interface]]	+	* Main Article: [[Comms Enterprise Interface]]

	====End User Panel Interface====		====End User Panel Interface====
Line 46:		Line 46:
	The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.		The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.

-	Main Article: [[Comms User Panel]]	+	* Main Article: [[Comms User Panel]]

	====ITSP Interface====		====ITSP Interface====

	The ITSP interface offers a subset of the administrator interface intended for use by customer service representatives and resellers.		The ITSP interface offers a subset of the administrator interface intended for use by customer service representatives and resellers.
-

	== Getting Started ==		== Getting Started ==

Webmaster at 15:15, 20 July 2016

2016-07-20T15:15:38Z

← Older revision		Revision as of 15:15, 20 July 2016
Line 1:		Line 1:
-	~~== comms Overview ==~~
	[[Image:comms-box.png\|right]]		[[Image:comms-box.png\|right]]
		+	== comms Overview ==
		+
	Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.		Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.

Webmaster at 15:15, 20 July 2016

2016-07-20T15:15:27Z

← Older revision		Revision as of 15:15, 20 July 2016
Line 1:		Line 1:
	== comms Overview ==		== comms Overview ==
-		+	[[Image:comms-box.png\|right]]
	Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.		Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.

Webmaster at 15:13, 20 July 2016

2016-07-20T15:13:02Z

← Older revision		Revision as of 15:13, 20 July 2016
Line 2:		Line 2:

	Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.		Taridium's comms is a Virtual PBX platform that leverages common Open Source projects such as Linux, Asterisk and PHP. It offers a complete hosted PBX application. It uses a partitioned naming convention that enables multiple PBXs to run on a single server instance without the need for virtualization overhead.
		+
		+	For version information and changes, please visit the [[Comms_Release_Log\|comms release log]].

	=== Components & Architecture ===		=== Components & Architecture ===

Webmaster: /* Database */

2016-07-20T13:35:16Z

Database

← Older revision		Revision as of 13:35, 20 July 2016
Line 58:		Line 58:
	=== Database ===		=== Database ===

-	The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications. The CDR records are held in a separate 'cdr' database. Main Article: [[Comms CDR]].	+	The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications. The CDR records are held in a separate 'cdr' database.
		+
		+	Main Article: [[Comms CDR]].

	=== Static Configuration ===		=== Static Configuration ===

	Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].		Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].

Webmaster at 12:52, 20 July 2016

2016-07-20T12:52:54Z

← Older revision		Revision as of 12:52, 20 July 2016
Line 42:		Line 42:

	The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.		The End User Panel controls individual extensions and their settings. It provides the end user with voicemail access, call logs, call forwarding/follow me and more.
		+
		+	Main Article: [[Comms User Panel]]

	====ITSP Interface====		====ITSP Interface====

Webmaster at 14:56, 19 July 2016

2016-07-19T14:56:08Z

← Older revision		Revision as of 14:56, 19 July 2016
Line 36:		Line 36:

	The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.		The enterprise interface controls the actual customer configuration. It is also known as the Virtual PBX interface. It provides for management of extensions, IVRs, groups, queues, conferencing and much more.
		+
		+	Main Article: [[Comms Enterprise Interface]]

	====End User Panel Interface====		====End User Panel Interface====

Webmaster at 14:16, 19 April 2016

2016-04-19T14:16:34Z

← Older revision		Revision as of 14:16, 19 April 2016
Line 54:		Line 54:
	=== Database ===		=== Database ===

-	The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications.	+	The comms configuration is held in a central MySQL database 'comms'. All database elements are edited through either the web interfaces or voice applications. The CDR records are held in a separate 'cdr' database. Main Article: [[Comms CDR]].

	=== Static Configuration ===		=== Static Configuration ===

	Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].		Some static configuration elements that apply to both switch, web and proxy packages are configured in config.php (/usr/local/comms/conf/config.php). The default values for these are stored in default.php. A complete list of configuration parameters can be found here: [[comms Configuration File]].