All Barracuda Phone Systems, Firmware 2.0.x and Later.
Two Barracuda Phone Systems can be configured to allow internal extension dialing between each other. While not difficult to configure, this does require some pre-planning.
The following options need to be considered when configuring multiple Barracuda Phone Systems to pass internal calls:
Outbound Dialing Restrictions – Will remote sites be allowed to use another sites' outbound routes (This requires special consideration for emergency routes), or be limited to internal calling only?
Topology of Multiple Sites – If you are configuring more than two Sites, will all calls route through a central “Hub Unit,” or will you link all Barracuda Phone Systems to each other in a Mesh Configuration.
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.
Note – While the Barracuda Phone System does include options for supporting multiple site installations, it is not designed to operate as a multi-tenant system, and does not include any method or option for isolating account information including Account Details, Directory Lists, and CDR data.
Please review Solution #00005725 - What is the Sites Feature, and How do I configure it on my Barracuda Phone System(s)? for general information on sites, and pre-planning requirements for installation.
Configuring Inter-site Dialing:
When configuring inter-site dialing we will need to ensure the use of common terminology to describe the connection. All configuration steps are described from the perspective of the local Barracuda Phone System. These are the terms used, and the meaning inferred, in this document:
Local System – This is the Barracuda Phone System that you are currently logged into.
Remote System – This is the Remote Barracuda Phone System as determined from the perspective of the Barracuda Phone System you are currently logged into.
Remote Extension Range – The extension ranges on the remote system.
Site Account – This is the actual provider account configured for the inter-site connection..
Configuration of the inter-site links is a four step process that is duplicated at each end of the link. Each site must have a unique configuration for each unit to which it is connecting. It is important to remember that, like phones, two Barracuda Phone Systems cannot share accounts.
With our network mapped out, and our firewall prepared, let's move on to configuring the sites:
Once you have decided which configuration type to use, we are ready to begin configuring the Sites. Please follow these steps to create your site links.
Note – Please remember that this is a one way link for outbound calls. This will need to be repeated for each direction that calls will flow. For most sites, you will want to do this from each Barracuda Phone System.
Setting up inbound accounts for Sites:
The first step in setting up sites is to create an inbound account to receive calls on the Remote System. This will allow the inbound calls from the calling site to be treated as internal calls. Please remember that this is a one-way link.
On the Remote System, Navigate to Configuration > Sites.
Click the Add Site button
Select Inbound Registration from the drop-down as the type of site to create
Enter a name which you will recognize in the Site Name field.
Click the button labeled Define Site (in 2.x) or Add (in 3.0).
Please note the settings shown for the new account so that they can be used in the following steps.
Setting up outbound accounts for Sites:
The second step in setting up sites is to create a provider account on the Local System for outbound calls to the Remote Barracuda Phone System. Please remember that this is a one way link.
COn the Local System, navigate to Providers and click on the button labeled Add a Provider.
For provider, choose Generic SIP from the drop down list for inbound registration accounts, or Generic SIP (No Registration) if the site is defined by IP Address.
Enter a name which you will recognize in the Name field.
Enter the Remote Server address in the field marked Host. This should auto-fill the same data in the field named Realm. This will, in most cases, be the external IP of the other system, though it could possibly use the internal IP over an MPLS link or VPN.
Leave the field named Port set to 5065.
Enter your Username in the field named Username. This should auto-fill the same data in the field named Authorization Username. Leave this fields blank for a site defined by IP address.
Enter your Password in the field labeled Password. Leave this fields blank for a site defined by IP address
Click the Box labeled Create.
Once the provider exists, we will need to set up an outbound route that will allow calls to pass through the gateway. Please reference Solution #00004848 for steps to create these routes.
Setting up a route for Sites / Protecting the Host Extension Blocks:
The third step in setting up sites is to create an Advanced Call Router that will forward calls to the gateway and protect the Remote System's extension range(s).
On the Calling System, navigate to Extensions > Advanced Call Routers and click on the button labeled Create New Advanced Call Router (in firmware family 2.0 you must first click Add New...)
Choose a Name you will Recognize and enter in the text box labelled Router Name.
Select Block Extension (New Block Extension in firmware 2.0) in the Extension Type field and enter the extension range used on the Remote System in the fields provided.
Check the box labelled “Do not allow (adding) extensions in this block.”
In firmware version 3.0 and higher, provide a name for the default action set (i.e. 'Send to <site name>')
Click Create to complete adding the Router.
In firmware version 3.0 and higher, edit the default action set by clicking Edit next to the Default Action Set drop down.
In the 2.x firmware family, once the Add window closes the list of routers and auto attendants will appear. Select the router you just created to open up the edit window.
In the 2.x firmware family, click the option “Delete this action” to the right of the line that says Calling sequence:”
In the section labelled “If the call is not answered...” Select the option “Send to Gateway” from the drop-down list, and select the name of the provider account which you created in step 2.
Repeat these directions for any other extension ranges on the Remote System, if they exist.
Once the site exists, we will need to set up site restrictions to allow or deny calls to pass through the gateway. Please reference Solution #00004848 for steps to create any new routes necessary.
Link to this page: