Multi-site
Multi-site is an advanced Allworx feature. This document assumes working knowledge of the Allworx system. For more detail on this topic see the “Allworx Advanced Multi-site Guide”
Allworx Advanced Multi-Site provided seamless integration between Allworx servers that are owned by one customer, but are installed in different locations. With some exceptions, the network will behave like a single, enterprise-wide system.
Note: Listed per software version 7.3x, also see Advanced Multi-Site for 7.4x for latest features
Features common across all sites:
Partially integrated feature:
To create a Controller site, a Primary Key is needed in the Allworx server. Branch sites can have either Branch keys or Primary keys. Branch Keys are limited to 10 handset mappings from a remote site. If a site requires more than 10 handset mappings, a Primary key will need to me installed at the remote location.
Configuration Requirements:
The following are the steps for setting up the Multi-site network. These steps should only be performed after the individual sites have been configured and proper operation has be verified on each server.
A. Configure each site router(s)
B. Configure the internal Dial Plan on all servers
C. Enable the Advanced Multi-site on the Control Server
D. Enable Advanced Multi-site on the Branch Server(s)
E. Accept the Branch(s) requests to join the network
F. Test the communications between each site
G. Verify the exchange of site data
H. Check for and resolve any conflicts
I. Add Handsets and Call Appearances for remote users (optional)
J. Map Handsets (optional)
K. Define call routes for multiple sites (optional)
L. Configure handsets for multiple site (optional)
M. Configure Auto Attendants for multiple sites (optional)
N. Configure outside line routing (optional)
O. Configure Paging Zones (optional)
P. Configure Parking Orbits (optional)
Q. Test all site to site operations
Enable Advanced Multi-site on the controller
1. Install the Advanced Multi-site Primary key
2. Go to Network / Multi-site
3. In the Configuration section, click the “modify” link
4. Click the Controller Site radio button
5. Enter a descriptive Site name. The name will be displayed on the Admin page of all sites as the home location of extensions, users, and handsets configured on this site.
6. Click “Update”
If an alternate SMTP port is to be used, change the SMTP Voicemail Port settings on the controller under “Server” / “E-mail”.
Enable Advanced Multi-site on the Branches
1. Install the Advanced Multi-site Primary or Branch feature key
If an alternate SMTP port is to be used, change the SMTP Voicemail Port settings on the controller under “Server” / “E-mail”.
2. Go to Network / Multi-site
3. In the configuration section, click the “modify” link
4. Click the Branch Site radio button
5. Enter the public IP address or the domain name of the Allworx server at the Controller site
6. Enter a descriptive Site name. The name will be displayed on the Admin page of all sites as the home location of extensions, users, and handsets configured on this site.
7. Click “Update”
Note: If the Internal Dial Plan or Extension Length in a Branch site is different from those settings on the Controller site, the Branch site will not be permitted to join the network.
In the Site List section, a message will be displayed:
“[Controller Site IP Address] contacted. Pending acceptance from admin at site.”
This indicates that the Branch site has sent the request to the Controller to join the Multi-site network. You will need to login to the Controller site admin page and accept the request to allow the Branch site to join the Multi-site network.
Note: You may have to refresh the browser a few times on the Branch site, after accepting the request.
Accepting the Branch requests
1. Go to Network / Multi-site
2. In the site list section, all Brach sites should be listed in the Pending Sites table
3. For each pending site, click the “Accept” button.
4. After the sites are accepted, they will be moved from the Pending Sites table to the Active Sites table. Notice the status that is displayed in the Inbound Link and Outbound Link columns. It might take a few minutes for all servers to report an “Active” status. You may have to refresh the browser a few times. It can take up to 10 minutes to exchange all the information between the sites.
Test communications on each site
Utilities are provided on the Multi-site page to test that all required communications between sites are configured properly. These tests can only be performed on sites that have already joined the network.
1. Go to Netowrk / Multi-site
2. If handsets from other sites are to be mapped on the site you are logged into, map at least one of the handsets form each site, now. See: Advanced Multi-Site Guide
3. Locate the active sites table in the site list section. Choose the test link for the first site.
4. Click all of the test buttons that appear.
5. Verify that all tests have passed. (Could take as long as 2 minutes)
6. If any tests fail, the most likely cause will be the configuration of network devices between the sites. Check the fire wall settings, port assignments, static routes, and port forwarding between the sites you are logged into and the remote site you are testing.
Verify the exchange of all site data
1. Go to Phone System / Extensions
2. Verify that extensions from all sites are listed.
3. Go to Business / User
4. Verify that users from all sites are listed.
Check for and resolve conflicts
There are two main conflicts you need to check for, extension number conflicts and same username conflicts.
1. Go to Network / Multi-site
2. Scroll down to the Conflicts section. Any conflicts will be displayed in a table.
3. Entries in the Username and User Extension Conflicts table could indicate either a User Extension Conflict or a Username Conflict.
4. Resolve User Extension Conflicts by changing one of the users Extension numbe
5. Resolve Username Conflicts by deleting one of the users and reading them with a different name. Note: The call route for that Extension will be removed and will need to be recreated.
6. Refresh the tables by clicking the “Refresh: link that appears at the top of the page. Verify that all conflicts have been resolved on all servers.
For more detail on Multi-site setup and information on optional configurations see the Allworx Advanced Multi-Site Guide
Allworx, Multi-Site, multisite, multi site, setup, configure
Multi-site is an advanced Allworx feature. This document assumes working knowledge of the Allworx system. For more detail on this topic see the “Allworx Advanced Multi-site Guide”
Allworx Advanced Multi-Site provided seamless integration between Allworx servers that are owned by one customer, but are installed in different locations. With some exceptions, the network will behave like a single, enterprise-wide system.
Note: Listed per software version 7.3x, also see Advanced Multi-Site for 7.4x for latest features
Features common across all sites:
- Extensions
- Users
- Voicemail
Partially integrated feature:
- Handsets
- Auto Attendants
- Outside lines
- Paging Zone
- Parking Orbits
- Call Queues
- Call Monitors
- Conference Bridges
- Dialing Rules
- Message Aliases
- Multi-site Primary Key
- Multi-site Branch Key
To create a Controller site, a Primary Key is needed in the Allworx server. Branch sites can have either Branch keys or Primary keys. Branch Keys are limited to 10 handset mappings from a remote site. If a site requires more than 10 handset mappings, a Primary key will need to me installed at the remote location.
Configuration Requirements:
- All servers in the multi-site network must utilize the same Internal Dial Plan including both the number of extension digits (3-digit vs. 4-digit) and the choice of numerical ranges for extensions (e.g. 1xx/2xx vs. 3xx/4xx) must be the same for all sites.
- All extension in the Multi-site must be different. The system will prevent the same extension from being added to two different sites. If sites have extension configured prior to the integration into the network, steps should be taken to avoid conflicts that will occur if the same extension is used at more than one site. E.G. Site A (1000 – 1050), Site B (1051 – 1100), Site C (1101 – 1150), Site D ( 1151 – 1199)
- User names must be unique across the Multi-site network. The system will prevent new users with the same username from being added at two different sites. This conflict refers to the user’s login name ( E.G. JWSmith).
The following are the steps for setting up the Multi-site network. These steps should only be performed after the individual sites have been configured and proper operation has be verified on each server.
A. Configure each site router(s)
B. Configure the internal Dial Plan on all servers
C. Enable the Advanced Multi-site on the Control Server
D. Enable Advanced Multi-site on the Branch Server(s)
E. Accept the Branch(s) requests to join the network
F. Test the communications between each site
G. Verify the exchange of site data
H. Check for and resolve any conflicts
I. Add Handsets and Call Appearances for remote users (optional)
J. Map Handsets (optional)
K. Define call routes for multiple sites (optional)
L. Configure handsets for multiple site (optional)
M. Configure Auto Attendants for multiple sites (optional)
N. Configure outside line routing (optional)
O. Configure Paging Zones (optional)
P. Configure Parking Orbits (optional)
Q. Test all site to site operations
Enable Advanced Multi-site on the controller
1. Install the Advanced Multi-site Primary key
- From the Admin Page, navigate to Maintenance / Feature Keys
- Retrieve the servers feature keys over the Internet by clicking on the install button
- Verify that Multi-site Primary is shown in the Currently Installed Feature list.
- If it is not on the list, you must obtain a Multi-site Primary key
2. Go to Network / Multi-site
3. In the Configuration section, click the “modify” link
4. Click the Controller Site radio button
5. Enter a descriptive Site name. The name will be displayed on the Admin page of all sites as the home location of extensions, users, and handsets configured on this site.
6. Click “Update”
If an alternate SMTP port is to be used, change the SMTP Voicemail Port settings on the controller under “Server” / “E-mail”.
Enable Advanced Multi-site on the Branches
1. Install the Advanced Multi-site Primary or Branch feature key
- From the Admin Page, navigate to Maintenance / Feature Keys
- Retrieve the servers feature keys over the Internet by clicking on the install button
- Verify that Multi-site Primary / Branch is shown in the Currently Installed Feature list.
- If it is not on the list, you must obtain a Multi-site Primary / branch key
If an alternate SMTP port is to be used, change the SMTP Voicemail Port settings on the controller under “Server” / “E-mail”.
2. Go to Network / Multi-site
3. In the configuration section, click the “modify” link
4. Click the Branch Site radio button
5. Enter the public IP address or the domain name of the Allworx server at the Controller site
6. Enter a descriptive Site name. The name will be displayed on the Admin page of all sites as the home location of extensions, users, and handsets configured on this site.
7. Click “Update”
Note: If the Internal Dial Plan or Extension Length in a Branch site is different from those settings on the Controller site, the Branch site will not be permitted to join the network.
In the Site List section, a message will be displayed:
“[Controller Site IP Address] contacted. Pending acceptance from admin at site.”
This indicates that the Branch site has sent the request to the Controller to join the Multi-site network. You will need to login to the Controller site admin page and accept the request to allow the Branch site to join the Multi-site network.
Note: You may have to refresh the browser a few times on the Branch site, after accepting the request.
Accepting the Branch requests
1. Go to Network / Multi-site
2. In the site list section, all Brach sites should be listed in the Pending Sites table
3. For each pending site, click the “Accept” button.
4. After the sites are accepted, they will be moved from the Pending Sites table to the Active Sites table. Notice the status that is displayed in the Inbound Link and Outbound Link columns. It might take a few minutes for all servers to report an “Active” status. You may have to refresh the browser a few times. It can take up to 10 minutes to exchange all the information between the sites.
Test communications on each site
Utilities are provided on the Multi-site page to test that all required communications between sites are configured properly. These tests can only be performed on sites that have already joined the network.
1. Go to Netowrk / Multi-site
2. If handsets from other sites are to be mapped on the site you are logged into, map at least one of the handsets form each site, now. See: Advanced Multi-Site Guide
3. Locate the active sites table in the site list section. Choose the test link for the first site.
4. Click all of the test buttons that appear.
5. Verify that all tests have passed. (Could take as long as 2 minutes)
6. If any tests fail, the most likely cause will be the configuration of network devices between the sites. Check the fire wall settings, port assignments, static routes, and port forwarding between the sites you are logged into and the remote site you are testing.
Verify the exchange of all site data
1. Go to Phone System / Extensions
2. Verify that extensions from all sites are listed.
3. Go to Business / User
4. Verify that users from all sites are listed.
Check for and resolve conflicts
There are two main conflicts you need to check for, extension number conflicts and same username conflicts.
1. Go to Network / Multi-site
2. Scroll down to the Conflicts section. Any conflicts will be displayed in a table.
3. Entries in the Username and User Extension Conflicts table could indicate either a User Extension Conflict or a Username Conflict.
4. Resolve User Extension Conflicts by changing one of the users Extension numbe
5. Resolve Username Conflicts by deleting one of the users and reading them with a different name. Note: The call route for that Extension will be removed and will need to be recreated.
6. Refresh the tables by clicking the “Refresh: link that appears at the top of the page. Verify that all conflicts have been resolved on all servers.
For more detail on Multi-site setup and information on optional configurations see the Allworx Advanced Multi-Site Guide
Allworx, Multi-Site, multisite, multi site, setup, configure