Besides the Media servers of the
branches you also always need to configure at least one central, branch-independent Media server. This Media server is used for subscribers who are not configured at branches. It also serves as redundancy for the branch Media servers.
Apart from the Media Server the Telephony Control Server system is already fully installed and configured.
The Media server used is already fully installed and connected to Telephony Control Server via a network connection.
An individual routing area without office code has been created for each branch.
One endpoint, normally assigned to an endpoint profile, exists for each SIP gateway and SIP proxy server system that supplies a branch.
The endpoint profile for each SIP gateway and SIP proxy server system is assigned to the associated routing area via the Routing Area
You have executed the associated previous configuration steps.
Adequate administrative permissions
The following elements are already pre-configured by default:
Three default destinations – one for the announcement line, one for the conference line and one for the monitoring line
Three origin destinations – one for the announcement line, one for the conference line and one for the monitoring line
One origin route that refers to the associated destination in every origin destination.
Furthermore, you need to configure a route towards the relevant line of the central Media Server in every pre-configured destination.
Parent topic: Initial Configuration of a Distributed Deployment Scenario with Branches
- On the Telephony Control Server navigation tab click on the navigation menu option Global Translation and Routing.
- In the navigation tree, click on Destinations and Routes -> Destinations.
The work area displays a list of the destinations that are configured in the global numbering plan of Telephony Control Server.
- Click on the name of the default destination DefDestAnn.
The dialog with the settings of the relevant destination opens.
- Switch to the Routes tab.
- Create a route that refers to the announcement line of the central Media Server:
- Click on Add.
The dialog with the settings of a route opens.
- Enter under ID an arbitrary number – e. g. 1.
You need to assign an individual ID to each route.
If various Media servers are later to act as reciprocal redundancy, the ID controls which Media server Telephony Control Server uses as primary system and which Media server works first as redundancy. Telephony Control Server uses the Media server as primary system that is reached via the route with the smallest ID.
- Select under MGCP Media Service the announcement line of the first Media Server.
The line names have the format:
<name of the Media Server>.ann/\$
- Click on OK to preliminarily copy the settings.
- Click on Save to copy the entries to the system's database.
- Create a route that refers to the conference line of the central Media Server in the DefDestCnf default destination in the same way.
- Create a route that refers to the monitoring line of the central Media Server in the DefDestCal default destination in the same way.
Step 1: How to Add Media Servers (distributed deployment, with branches)
Step 2: How to Configure Circuits (distributed deployment, with branches)
Step 4: How to Assign Media Servers to a Branch
Step 5: How to Configure the Redundancy /Load Balancing
Step 6: How to Activate the Audit
Step 7: How to Assign Treatments to their Origin Destination