Multi Site - Revision history

Webmaster at 00:50, 8 December 2009

2009-12-08T00:50:08Z

← Older revision		Revision as of 00:50, 8 December 2009
Line 6:		Line 6:

	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, but before outbound routing. So if you need to transform extensions use the '''before inside routing''' type. See also [[Routes#Transformations\|Transformations]].		There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, but before outbound routing. So if you need to transform extensions use the '''before inside routing''' type. See also [[Routes#Transformations\|Transformations]].
		+
		+	The multi-site feature will also synchronize all internal contacts across all servers.

	== Configuring Multi Site ==		== Configuring Multi Site ==

Webmaster: /* Configuring Multi Site */

2009-09-29T11:43:34Z

Configuring Multi Site

← Older revision		Revision as of 11:43, 29 September 2009
Line 13:		Line 13:
	To access the multi site configuration click on '''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.		To access the multi site configuration click on '''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.

-	Take note that your configuration needs to be able to accept unauthenticated calls. If you plan to use IAX make sure you have an IAX guest entry on each system:	+	Take note that your configuration needs to be able to accept unauthenticated calls. The default dialplan context for incoming calls is '''incoming'''. If you plan to use IAX make sure you have an IAX guest entry on each system:

	[guest]		[guest]

Webmaster: /* Configuring Multi Site */

2009-09-29T11:41:25Z

Configuring Multi Site

← Older revision		Revision as of 11:41, 29 September 2009
Line 20:		Line 20:
	context = incoming		context = incoming

		+	[[Image:warning.gif]]Please be aware of the security implications when using Multi Site. It is generally recommended to use Multi Site within a VPN not only for security reasons but also to better control QoS.

	=== Adding Peers ===		=== Adding Peers ===

Webmaster at 03:33, 29 September 2009

2009-09-29T03:33:07Z

← Older revision		Revision as of 03:33, 29 September 2009
Line 5:		Line 5:
	Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.		Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.

-	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, before ~~any~~ outbound routing. So if you need to transform extensions use the '''before inside routing''' type. See also [[Routes#Transformations\|Transformations]].	+	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, but before outbound routing. So if you need to transform extensions use the '''before inside routing''' type. See also [[Routes#Transformations\|Transformations]].

	== Configuring Multi Site ==		== Configuring Multi Site ==

-	It is recommended to carefully plan your diaplan to avoid overlapping digit patterns across your locations.	+	It is recommended to carefully plan your diaplan to avoid overlapping digit patterns across your PBX locations.

	To access the multi site configuration click on '''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.		To access the multi site configuration click on '''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.

Webmaster at 03:29, 29 September 2009

2009-09-29T03:29:14Z

← Older revision		Revision as of 03:29, 29 September 2009
Line 5:		Line 5:
	Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.		Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.

-	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, before any outbound routing. So if you need to transform extensions use the '''before inside routing''' type.	+	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, before any outbound routing. So if you need to transform extensions use the '''before inside routing''' type. See also [[Routes#Transformations\|Transformations]].

	== Configuring Multi Site ==		== Configuring Multi Site ==

Webmaster: /* Master Failure */

2009-09-29T03:28:25Z

Master Failure

← Older revision		Revision as of 03:28, 29 September 2009
Line 45:		Line 45:
	=== Master Failure ===		=== Master Failure ===

-	If for some reason the master becomes unreachable, slaves default to cached information and revert back to live information as soon as it becomes available again.	+	If for some reason the master becomes unreachable, slaves default to cached information and revert back to live information as soon as it becomes available again. Cached information will be retained until the system is rebooted or shutdown.

Webmaster: /* Adding Peers */

2009-09-29T03:26:27Z

Adding Peers

← Older revision		Revision as of 03:26, 29 September 2009
Line 24:		Line 24:

	Click on '''add slave peer''' and enter the remote ip Address as well as descriptive name and extension pattern. Patterns always start with a '_' underscore. In the peer configuration make sure you have your peer set to operate as '''slave''' and configured to use the master's IP address. Select the type of connection, either '''SIP''' or '''IAX2'''.		Click on '''add slave peer''' and enter the remote ip Address as well as descriptive name and extension pattern. Patterns always start with a '_' underscore. In the peer configuration make sure you have your peer set to operate as '''slave''' and configured to use the master's IP address. Select the type of connection, either '''SIP''' or '''IAX2'''.
		+
		+	Take note that peers will accept extension patterns for all configured PBXs. If the extension pattern is not local the call will be forwarded to the correct destination.

	====Special Characters for Pattern Matching====		====Special Characters for Pattern Matching====

Webmaster: /* Configuring Multi Site */

2009-09-29T03:24:52Z

Configuring Multi Site

← Older revision		Revision as of 03:24, 29 September 2009
Line 11:		Line 11:
	It is recommended to carefully plan your diaplan to avoid overlapping digit patterns across your locations.		It is recommended to carefully plan your diaplan to avoid overlapping digit patterns across your locations.

-	To access the multi site configuration click on ''''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.	+	To access the multi site configuration click on '''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.

	Take note that your configuration needs to be able to accept unauthenticated calls. If you plan to use IAX make sure you have an IAX guest entry on each system:		Take note that your configuration needs to be able to accept unauthenticated calls. If you plan to use IAX make sure you have an IAX guest entry on each system:

Webmaster at 03:24, 29 September 2009

2009-09-29T03:24:40Z

← Older revision		Revision as of 03:24, 29 September 2009
Line 3:		Line 3:
	Manage multiple sites from a single master server and simplify communications across all ipbx servers. ipbx's multi site support let's you add cost saving interconnects (trunks) with very little effort.		Manage multiple sites from a single master server and simplify communications across all ipbx servers. ipbx's multi site support let's you add cost saving interconnects (trunks) with very little effort.

-	Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.	+	Multi Site support allows you to configure a dialplan master server and up to 200 slaves that synchronize dialplan information. This system is independent from other services and provides failover capabilities between operating sites even if the master system is down.
		+
		+	There is no need to configure routing when using the Multi Site feature. Multi Site extensions are looked up after all internal options have been exhausted, before any outbound routing. So if you need to transform extensions use the '''before inside routing''' type.

	== Configuring Multi Site ==		== Configuring Multi Site ==

Webmaster: /* Configuring Multi Site */

2009-09-29T03:21:28Z

Configuring Multi Site

← Older revision		Revision as of 03:21, 29 September 2009
Line 10:		Line 10:

	To access the multi site configuration click on ''''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.		To access the multi site configuration click on ''''Advanced Setup''' → '''Multi Site'''. On the master server select '''Currently operating as Master''' (default setting). The master IP address is taken from the '''Advanced Setup''' → '''Configuration''' → '''[[Advanced_Setup:_Configuration\|ipbx IP Address]]'''. This is the IP address used by the slaves to synchronize dialplan information.
		+
		+	Take note that your configuration needs to be able to accept unauthenticated calls. If you plan to use IAX make sure you have an IAX guest entry on each system:
		+
		+	[guest]
		+	type = user
		+	host = dynamic
		+	context = incoming
		+

	=== Adding Peers ===		=== Adding Peers ===

-	Click on '''add slave peer''' and enter the remote ip Address as well as descriptive name and extension pattern. Patterns always start with a '_' underscore. In the peer configuration make sure you have your peer set to operate as '''slave''' and configured to use the master's IP address.	+	Click on '''add slave peer''' and enter the remote ip Address as well as descriptive name and extension pattern. Patterns always start with a '_' underscore. In the peer configuration make sure you have your peer set to operate as '''slave''' and configured to use the master's IP address. Select the type of connection, either '''SIP''' or '''IAX2'''.

	====Special Characters for Pattern Matching====		====Special Characters for Pattern Matching====