In a distributed Media server deployment scenario without branches, calls are routed to the desired Media servers on the basis of subscriber-related routing areas.
Figure 1. Configuration representation of a distributed deployment scenario without branches
The depicted example shows the following structure:
Two Media servers are configured as redundancy to each other or working in the load balancing.
One dropping consists of up to three consecutive treatments.
Each treatment is assigned to an origin destination according to the routing area of the caller.
Several routing areas are assigned to the origin destination.
One destination is assigned to each routing area.
Several routes are connected to the destination – one per Media server.
The configuration of a distributed Media server deployment scenario without branches is divided into the following steps:
Step 1: How to add Media serversParent topic: Media Server Deployment Scenarios at Telephony Control Server
Step 2: How to configure circuits
Step 3: How to add destinations
Step 4: How to configure the redundancy / load balancing
Step 5: How to activate the audit
Step 6: How to add an origin destination
Step 7: How to assign treatments to the origin destination
Step 1: How to Add Media Servers (distributed deployment, no branches)
Step 2: How to Configure Circuits (distributed deployment, no branches)
You need to configure the circuits to be used by the Media servers. The traffic types, for which the relevant Media servers are to be used, determine, which circuits need to be configured.
Step 3: How to Add Destinations
You need to add a new destination for each routing area. In this destination you need to create a route for each announcement circuit of the Media servers that are to provide this routing area. In addition, add a destination that serves for subscribers without routing area.
Step 4: How to Configure the Redundancy /Load Balancing (distributed deployment, no branches)
You need to configure whether the different Media servers of a destination are to work as reciprocal redundancy or in load balancing.
Step 5: How to Activate the Audit (distributed deployment, no branches)
Step 6: How to Add an Origin Destination
You need to add a new origin destination. In this origin destination you need to create a route to each destination that defines a routing area. In the origin destination you also need to create a route to the destination that you have added for possible subscribers without routing area.
Step 7: How to Assign Treatments to the Origin Destination
You need to assign the preinstalled treatments of Telephony Control Server to the new destination of origin. An appropriate script is available for this purpose.