At least one Media server has already been configured for the existing Media server deployment scenario. Add the new Media servers. Proceed as described in the relevant steps for the reconfiguration of a distributed Media server deployment scenario with branches.
The Telephony Control Server system is already installed and configured with an existing Media server deployment scenario.
All Media servers used are 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. If routing areas are already available for the existing Media server deployment scenario, you can adjust them according to your requirements.
Existing routing areas are later also valid for the migrated deployment scenario. These routing areas can therefore simply be used e. g. for members who are not assigned to any 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
Adequate administrative permissions
Parent topic: Migration of an existing Deployment Scenario to a Scenario with Branches
Step 2: How to Modify / Configure Lines
Step 3: How to Modify / Add Routes to the Central Media Server (migrated deployment)
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 (migrated deployment)
Step 7: How to Change the Destination for Announcement Treatments