All Barracuda Phone Systems, Firmware 2.0.x and Later.
When configuring the Barracuda Phone System, you may run into a scenario where you will need the system to communicate with one or more sites. These sites can be additional BPS Servers or simply one or more IP phones in a separate location. This configuration scenario can easily be supported by the BPS, however it requires some pre-planning and consideration in order to complete a robust configuration using this feature set.
Pre-Deployment Planning Considerations:
When configuring sites, there are a few options and scenarios which must be first considered. Let's take a look at these options one at a time.
Extension Ranges and layout/use - When using sites for inter-site routing between two Barracuda Phone Systems, it is important to make sure that extension ranges in use at different sites are unique. The Barracuda Phone System will always check to see if a local extension exists before trying a gateway, and will not route the call outbound if the extension exists locally. When arranging a number scheme, be sure to allow for future growth. As a rule of thumb, allow for at least 25% more extension numbers than you currently plan to use.
Trunk Location and Rights – With multiple sites, the concept of multi-site routing becomes a far more important consideration. Do we want all outbound routing to happen at a single location, or at multiple fail-over locations? What sites have the rights to make outbound calls, and what types? How should the site handle local calling, or emergency calling? These decisions need to be addressed fairly early in the planning process.
Emergency Routing – A critical consideration on all phone systems, this factor becomes far more important consideration when using a VoIP PBX. With traditional telephone lines, emergency calls are related to a physical location. With VoIP, though, the concept of “location” is more fluid. Enhanced 911 (or “E911”) uses a database to associate a DID phone number with a physical location. (This association is handled by the DID provider, not by the BPS.) Therefore, when a call is made to 911, the 911 call center will see the location associated with the DID number sent out as the caller ID number. In a multi-site configuration, the establishment and testing of 911 calls is critical.
Basic Site Planning
There are two primary types of configurations:
Single Phone system for multiple sites - The first type involves configuring a single BPS to route calls for multiple sites (a “hub” topology). In this configuration, we can register certain subnets as separate locations for devices registered to the Barracuda Phone System.
Multiple PBXes configured for Inter-site Dialing - The second type involves two or more independent sites that are linked together using sites (a “mesh” topology). In this scenario, each site is using its own PBX, and the sites are configured to communicate directly, using dedicated Gateways. The remote PBX may be a https://bugs.cudaops.com/browse/BNPH-11159, or it could also be a third party device.
Emergency calling and 911 location service:
Any multi-site plan should include a plan for 911 services. By default, the 911 location for calls is the address of the account holder. If you are maintaining multiple physical sites, we need a way to define the second site as a different site for 911 purposes. We will need to discuss this option with the provider to ensure that they are aware of the multiple site installation, and have accounted for it. Most providers handle this by associating a separate registration, or a single DID with the alternate site. Be sure to contact your VoIP provider and find out how they handle E911 configuration.
With this configuration, we assign a different outbound route for each site, allowing only that site to use it. We then set the outbound callerID (or registration) information to match that required by the provider.
The first step in configuring a site is defining it. There are three types of authorization accounts for the Barracuda Phone System:
Subnet or IP – All traffic from the IP address or IP subnet will be classified as coming from the site being defined. This method is required if we want to assign a separate office or area to a site for restrictions or route management. Configuration using this method requires entering an address and subnet for the remote site in CIDR format. You should use caution to limit the subnet to the required addresses.
Inbound Provider or Ports - Will treat any analog/digital port, or a provider gateway, as a site. Adding a site using this method will set a traditional telephony port on the system, or an existing provider gateway, as an internal gateway for inter-site calls. This is not generally used to connect two Barracuda Phone Systems, but rather for connecting a third party phone system.
Inbound Authorization Account - Sets up a new registration account for a remote PBX. This method creates an inbound registration account to which the remote PBX may register. This is the preferred method of connecting two Barracuda Phone Systems.
Once we have decided on a connection type, and have explored and accounted for all of our planning considerations, we can begin configuration.
Please review the following Solutions for steps required to configure the specific type of site:
Solution #00005733 - How do I configure my Barracuda Phone System to identify phones at different physical sites separately?
Solution #00005734 - How do I Configure Multiple Barracuda Phone Systems to call directly when placing internal calls?
Solution #00005735 - How do I configure my Barracuda Phone System and a third party PBX to allow internal calls between systems?
Link to this page: