 rest of the employees and meetings. Initially deployed for one location (Mountain View, California), although they also planned to deploy SIP trunks in London, England. One conferencing audio platform. Next, we look at the detailed configuration of Company P's voice network. Chapter 12: Case Studies 267 Creating Different Route Groups Initially Company P started with five CUBEs to observe the performance. Based on what it learned, it gradually added more CUBEs into the network. Basically, they stacked CUBE into its data center located in San Jose, California. It created multiple dial plans and distributed them into different CUBEs. Here is the sam- ple dial plan based on the dial pattern, where 8 is the prefix for internal dialing: Route Pattern 8-421-xxxx goes to CUBE#1 Route Pattern 8-422-xxxx goes to CUBE#2 Route Pattern 8-423-xxxx goes to CUBE#3 Route Pattern 8-424-xxxx goes to CUBE#4 Route Pattern 8-425-xxxx goes to CUBE#5 Then, it created the main route pattern 81545600 and created the route list into CUCM. This created call-load balancing, redundancy, and failover to Remote CUCM Cluster. Figure 12-4 shows the dial-plan design for Company P. MTP Configuration Media Termination Point (MTP) is required in this call flow, because: Company Q's media servers require Early Media (SIP INVITE with SDP) to interoper- ate with CUBEs. To accommodate Early Media (SIP)/Fast Start (H.323), CUCM dictates MTPs for each call, regardless of the direction. Example 12-1 shows the standard MTP configuration in IOS (into CUBE). A call using the MTP has two call legs, SO 600 sessions means 300 calls. 268 SIP Trunking CCC Cluster 81545600 Route Pattern MTV CUBE RouteList Route List Chicken SECURITY HOMELAND Called Party Transformation Called Party Transformation 81545600 Remote Destination 8+7 MTV CUBE RG Circular Gatekeeper Trunk MTV5 CUBE 1 H.323 GW MTV5 CUBE 2 H.323 GW Remote Cluster Europe CCP MTV5 CUBE 3 H.323 GW MTV5 CUBE 4 H.323 GW MTV5 CUBE X H.323 GW MTV CUBE 1 Figure 12-4 Dial Plan in CUCM Chapter 12: Case Studies 269 E