Multi Site
From Taridium
(→Configuring Multi Site) |
|||
| (8 intermediate revisions not shown) | |||
| 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, 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 == | ||
| - | 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 | + | 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] | ||
| Line 18: | Line 22: | ||
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 === | ||
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==== | ||
| Line 41: | Line 48: | ||
=== 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. |
Latest revision as of 00:50, 8 December 2009
This optional ipbx module is installed under Advanced Setup → Modules. Registered modules are displayed with registered module.
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.
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 Transformations.
The multi-site feature will also synchronize all internal contacts across all servers.
Contents |
Configuring Multi Site
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 → 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. 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] type = user host = dynamic context = incoming
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
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
X matches any digit from 0-9
Z matches any digit from 1-9
N matches any digit from 2-9
[1237-9] matches any digit or letter in the brackets
(in this example, 1,2,3,7,8,9)
. wildcard, matches one or more characters
Examples
_NXXXXXX matches a NANP 7 digit telephone number such as 555-1212
_1NXXNXXXXXX matches an area code and phone number preceeded by a one such as 1-860-555-1212
_9011. matches any string of at least five characters that starts with 9011,
but it does not match the four-character string 9011 itself.
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. Cached information will be retained until the system is rebooted or shutdown.
