Cisco 640-816 (Interconnecting Cisco Networking Devices Part 2) exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Cisco 640-816 Interconnecting Cisco Networking Devices Part 2 exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Cisco 640-816 certification exam dumps & Cisco 640-816 practice test questions in vce format.

Understanding the Historical Context of the 640-816 Exam

The 640-816 Exam, officially titled Implementing Cisco Unified Communications Manager, Part 2 (CIPT2), represented a significant milestone for network professionals specializing in voice technologies. It was a professional-level examination designed by Cisco to validate the advanced knowledge and skills required to implement and manage a multisite Cisco Unified Communications Manager (CUCM) solution. This exam was a cornerstone of the highly respected Cisco Certified Network Professional Voice (CCNP Voice) certification track. It focused specifically on the challenges and solutions associated with deploying a unified communications network across multiple geographical locations, which is a common scenario for large enterprises.

Successfully passing the 640-816 Exam demonstrated a candidate's proficiency in complex call routing, multisite dial plan construction, and bandwidth management. The curriculum delved into critical concepts such as centralized and distributed call processing models, call admission control, and mobility features. While the CCNP Voice certification and the 640-816 Exam have since been retired and superseded by the CCNP Collaboration track, the fundamental principles and technologies it covered remain incredibly relevant. Understanding the topics from this exam provides a solid foundation for any engineer working with modern collaboration platforms today.

The transition from CCNP Voice to CCNP Collaboration reflects the industry's evolution from traditional voice-centric systems to integrated platforms that combine voice, video, messaging, and conferencing. However, the core logic of how calls are routed, how dial plans are structured, and how remote sites are supported has not disappeared. Instead, these concepts have been built upon and expanded. Therefore, a retrospective look at the 640-816 Exam serves not just as a history lesson, but as a deep dive into the foundational pillars that support the collaboration solutions of the present and future.

The CCNP Voice Certification Path Explained

The CCNP Voice certification was a comprehensive track that required candidates to pass a series of exams, each targeting a specific area of unified communications. The 640-816 Exam was just one piece of this larger puzzle. The journey typically began with the CCNA Voice certification, which established a baseline of skills in managing a voice network. From there, professionals would advance to the CCNP Voice track, which was composed of five distinct examinations. These exams collectively covered the entire lifecycle of a unified communications deployment, from initial design and implementation to ongoing troubleshooting and management.

The five exams in the CCNP Voice track were CVOICE, CIPT1, CIPT2 (the 640-816 Exam), TUC, and CAPPS. The CVOICE exam focused on voice gateways and the public switched telephone network (PSTN), covering technologies like analog voice ports, digital T1/E1 circuits, and Quality of Service (QoS). The CIPT1 exam provided an introduction to the Cisco Unified Communications Manager, focusing on single-site deployments. It covered user account setup, endpoint registration, and basic dial plan elements. This set the stage perfectly for the more advanced topics found in the 640-816 Exam.

The 640-816 Exam (CIPT2) built directly upon the CIPT1 foundation, shifting the focus entirely to multisite deployments. Following this, the TUC exam covered troubleshooting Cisco Unified Communications systems, equipping engineers with the skills to diagnose and resolve complex issues. Finally, the CAPPS exam focused on integrating unified communications applications, such as Cisco Unity Connection for voicemail and Cisco Unified Presence for instant messaging and presence status. Together, these five exams created a well-rounded expert capable of managing a sophisticated enterprise collaboration environment from end to end.

Core Objectives of the 640-816 Exam

The primary goal of the 640-816 Exam was to assess a candidate's ability to implement a scalable and resilient multisite dial plan using Cisco Unified Communications Manager. The exam objectives were carefully crafted to reflect real-world enterprise scenarios. A major topic was the description and configuration of different multisite deployment models. This included understanding the trade-offs between a centralized call processing model, where a single CUCM cluster serves all locations, and a distributed model, where each location has its own call processing agent. This knowledge is crucial for designing a network that is both efficient and fault-tolerant.

Another core objective revolved around the implementation of features to manage bandwidth and ensure call quality over a wide area network (WAN). This involved a deep understanding of Call Admission Control (CAC), which prevents too many voice calls from congesting a WAN link and degrading the quality of all active calls. Candidates were expected to know how to configure CAC using the locations and regions mechanisms within CUCM. This included setting up Automated Alternate Routing (AAR), a feature that automatically reroutes calls over the PSTN if the required WAN bandwidth is not available.

Furthermore, the 640-816 Exam curriculum covered the creation of a highly scalable and manageable dial plan. This went far beyond simple extension-to-extension dialing. It required proficiency in using CUCM features like route patterns, route lists, route groups, partitions, and calling search spaces to control call routing and enforce toll fraud prevention policies. Advanced topics like digit manipulation, time-of-day routing, and the globalization of the dial plan using the E.164 numbering standard were also essential components. These skills are fundamental for any organization with a complex telecommunications environment.

Finally, the exam touched upon providing remote connectivity and mobility features. This included configuring Cisco Unified Mobility, also known as Single Number Reach, which allows users to have calls to their desk phone simultaneously ring on their mobile phone. It also covered the setup of Survivable Remote Site Telephony (SRST), a critical feature that allows remote offices to continue making and receiving calls even if the connection to the central CUCM cluster is lost. Mastering these objectives proved that an engineer had the expertise required for advanced CUCM administration in a large-scale enterprise.

A Primer on Cisco Unified Communications Manager (CUCM)

Cisco Unified Communications Manager, often abbreviated as CUCM or simply CallManager, is the heart of Cisco's on-premises collaboration architecture. It is an IP-based communications processing system that provides session and call control for a wide range of endpoints. These endpoints include Cisco IP phones, soft clients like Jabber, video conferencing units, and third-party SIP devices. The CUCM software runs on a dedicated server, which can be a physical appliance or a virtual machine. Its primary function is to manage the setup, routing, and termination of voice and video calls within an organization.

At its core, CUCM is a sophisticated registrar and call routing engine. When an IP phone powers on, it reaches out to the CUCM cluster to register. Once registered, the CUCM knows the phone's IP address and its directory number. When a user dials a number, the phone sends the digits to CUCM. CUCM then processes these digits against its configured dial plan to determine the destination. It might be another internal extension, a voicemail system, or an external number that needs to be sent out through a PSTN gateway. CUCM manages all the signaling required to establish the call path.

Beyond basic call control, CUCM is a feature-rich platform that serves as the integration point for many other collaboration services. It provides access to features like call forwarding, call transfer, conferencing, and music on hold. It also integrates with other applications in the Cisco collaboration portfolio, such as Cisco Unity Connection for voicemail and IM and Presence Service for instant messaging. The entire system is managed through a web-based graphical user interface, which allows administrators to configure users, devices, and the complex call routing logic tested in the 640-816 Exam.

The Importance of Underlying Network Infrastructure

A successful unified communications deployment is built upon a solid and well-designed network infrastructure. The topics covered in the 640-816 Exam assume that this foundation is already in place. Voice and video traffic are highly sensitive to network impairments like delay, jitter, and packet loss. Unlike data traffic, which can be retransmitted if packets are lost, real-time voice and video streams cannot tolerate such disruptions without a noticeable degradation in quality. Therefore, a network carrying this traffic must be engineered to provide preferential treatment to these real-time flows.

This is where Quality of Service (QoS) becomes critically important. QoS is not a single feature but a collection of network technologies that work together to manage bandwidth and prioritize traffic. Before an engineer even begins to configure the dial plan in CUCM, the underlying network of routers and switches must be configured with a robust QoS policy. This policy involves classifying traffic into different categories, marking voice and video packets with a high priority, and configuring queuing mechanisms on network interfaces to ensure that these priority packets are serviced first, especially during times of network congestion.

For a multisite deployment, the Wide Area Network (WAN) is of particular concern. The WAN links connecting remote offices to the central site often have limited bandwidth and higher latency compared to the local area network (LAN). The 640-816 Exam topics, such as Call Admission Control, are specifically designed to manage this limited resource. However, CAC is not a substitute for proper network design. The network must have sufficient bandwidth, low latency, and a consistent QoS configuration across all sites to provide a high-quality user experience for all collaboration services.

The Evolution to CCNP Collaboration

The technology landscape is in a constant state of change, and professional certifications must evolve to remain relevant. Cisco retired the CCNP Voice certification track, including the 640-816 Exam, and replaced it with the more modern CCNP Collaboration certification. This change was driven by a fundamental shift in how businesses communicate. The focus expanded from being primarily about voice to encompassing a full suite of collaboration tools. This includes high-definition video conferencing, persistent team messaging, cloud-based services, and seamless integration across multiple devices.

The CCNP Collaboration certification reflects this new reality. It is structured around a core exam and a selection of concentration exams. The core exam, "Implementing and Operating Cisco Collaboration Core Technologies" (CLCOR), covers the foundational knowledge for implementing and managing a collaboration solution. This single exam consolidates and updates many of the concepts that were previously spread across the CVOICE, CIPT1, and 640-816 Exam. It covers infrastructure design, call control, QoS, and the basics of collaboration applications, but with a modern perspective that includes cloud and hybrid deployments.

After passing the core exam, candidates choose a concentration exam that aligns with their specific job role or area of interest. These exams offer deep dives into areas such as advanced call control and dial plan design, collaboration applications, cloud and edge solutions, or automation. This new structure provides more flexibility and recognizes that the role of a collaboration engineer has become more specialized. While the names of the exams have changed, the spirit of the 640-816 Exam lives on. The complex multisite dial plan and call control skills it validated are still a central component of the new CCNP Collaboration track.

Why It Is Still Valuable to Study Retired Exam Topics

One might question the utility of studying the details of a retired exam like the 640-816 Exam. However, the underlying technologies and design principles are not only relevant but are foundational to understanding modern systems. The problems that the 640-816 Exam curriculum aimed to solve—such as how to build a scalable dial plan, how to maintain service during a network outage, and how to manage bandwidth—are timeless challenges in the world of communications. The specific commands or interface layouts may change, but the logic and best practices remain remarkably consistent.

Studying these topics provides a deeper appreciation for the architecture of current collaboration platforms. For example, understanding how partitions and calling search spaces work in CUCM is essential for any administrator, regardless of the version they are using. Similarly, the principles of Call Admission Control are still applied today, even if the mechanisms have been enhanced or supplemented with newer methods like the Resource Reservation Protocol (RSVP). Learning about the original implementation gives an engineer a more complete picture and better troubleshooting instincts when working with complex systems.

Moreover, many organizations do not immediately upgrade to the latest and greatest technology. It is common for large enterprises to be running older, yet still fully supported, versions of Cisco Unified Communications Manager. In these environments, the knowledge directly applicable to the 640-816 Exam is not just historical context; it is a practical, day-to-day requirement. An engineer who understands the evolution of these systems is better equipped to manage mixed environments, plan migrations, and appreciate the design decisions that have shaped the products they work with every day.

Revisiting the Scope of the 640-816 Exam

We established the historical context and foundational importance of the 640-816 Exam. It served as the advanced implementation test for Cisco Unified Communications Manager within the CCNP Voice track, focusing squarely on the complexities of multisite environments. This focus was not arbitrary; it reflected the reality that most large organizations are geographically dispersed. Connecting branch offices, regional headquarters, and data centers into a single, cohesive communication system presents a unique set of challenges. The 640-816 Exam was designed to ensure that network professionals had the skills to overcome these challenges effectively.

The core of this challenge lies in designing a call processing architecture that is both efficient and resilient. This involves making critical decisions about where the call processing intelligence, the CUCM cluster itself, should reside. It also requires implementing mechanisms to control the flow of voice and video traffic across expensive and often constrained Wide Area Network (WAN) links. The exam's curriculum forced candidates to think like architects, weighing the pros and cons of different models and selecting the appropriate solution based on an organization's specific business and technical requirements.

As we move forward in this part, we will explore these architectural decisions in detail. We will analyze the primary deployment models that were a cornerstone of the 640-816 Exam: the centralized call processing model and the distributed call processing model. We will also examine the essential supporting technologies, such as Survivable Remote Site Telephony (SRST) and Call Admission Control (CAC), that make these models viable in the real world. This exploration will provide a clear understanding of how to build a robust and scalable unified communications network that can span the globe.

The Centralized Call Processing Model

The centralized call processing model is one of the most common deployment architectures for multisite unified communications. In this model, a single Cisco Unified Communications Manager cluster is deployed at a central location, typically a primary data center. This central cluster is responsible for providing call control services to all endpoints across the entire organization, including those located at remote branch offices. The IP phones and other devices at the branch offices register over the WAN to the CUCM cluster at the central site. All call signaling traffic from the remote sites traverses the WAN to be processed by the central CUCM.

This architecture offers several significant advantages, with simplified management being the most prominent. With only one CUCM cluster to manage, administrators can handle all user configurations, dial plan updates, and system maintenance from a single point. This reduces administrative overhead and ensures consistency across the organization. It is also a very cost-effective model, as it avoids the expense of purchasing and maintaining separate call processing servers at each remote location. This centralization of resources often leads to a lower total cost of ownership, which is a compelling factor for many businesses.

However, the centralized model is not without its drawbacks. Its biggest vulnerability is its heavy reliance on the WAN. If the WAN connection to a remote site goes down, the IP phones at that site lose their connection to the central CUCM cluster. In this state, they are unable to make or receive calls, effectively becoming useless. This is a significant risk for any business that relies on voice communications for its daily operations. Furthermore, all call signaling for every site must traverse the WAN, which can introduce latency and potentially impact call setup times.

The Distributed Call Processing Model

In contrast to the centralized approach, the distributed call processing model involves deploying multiple CUCM clusters. In a typical distributed deployment, each major site or region has its own local CUCM cluster. The endpoints at a given site register to their local cluster, and most of the call processing is handled locally. This significantly reduces the amount of signaling traffic that needs to cross the WAN. Inter-site calls, meaning calls from a user at one site to a user at another, are routed between the clusters over the WAN using special connections known as inter-cluster trunks.

The primary advantage of the distributed model is its inherent resilience. Since each site has its own call processing capabilities, a WAN outage between two sites does not impact the ability of users to make calls within their own site or to the outside world via their local PSTN gateway. This site survivability is a critical requirement for organizations where communication is mission-critical. This model also offers improved performance for local calls, as the signaling does not need to travel across the WAN, resulting in faster call setup times. It provides a more robust and fault-tolerant solution.

The trade-off for this increased resilience is greater complexity and cost. Managing multiple, geographically dispersed CUCM clusters is inherently more complex than managing a single, centralized one. Administrators must ensure that the dial plans on all clusters are synchronized and can route calls between each other correctly. This requires careful planning and ongoing maintenance. Additionally, the hardware and software costs are higher, as a separate CUCM cluster must be purchased, licensed, and maintained for each location. This makes the distributed model a more expensive option upfront.

Survivable Remote Site Telephony (SRST)

To address the major weakness of the centralized call processing model—the loss of service during a WAN outage—Cisco developed a technology called Survivable Remote Site Telephony, or SRST. SRST provides a basic level of call processing functionality at the remote site that can be activated when the connection to the central CUCM cluster is lost. This feature is typically enabled on the Cisco router that serves as the local gateway at the remote office. The router maintains a small, cached database of the phones that are registered at its site.

When the IP phones at the remote site detect that they can no longer communicate with the central CUCM, they automatically attempt to re-register with the local SRST router. Once registered to the SRST router, the phones enter a fallback mode. In this mode, users can still make and receive calls. They can call other extensions within their own office, and they can make external calls through the local PSTN gateway connected to the router. This provides a crucial lifeline, ensuring that the business can continue to communicate during a network failure.

While SRST is a powerful feature, it is important to understand that it provides a reduced feature set compared to the full CUCM experience. Advanced features like voicemail integration, call forwarding to mobile devices, and complex conferencing are typically not available when the site is in SRST mode. The primary purpose of SRST is to provide basic dial-tone and emergency calling capabilities. When the WAN connection is restored, the IP phones automatically re-register back to the central CUCM cluster and resume their normal, full-featured operation without any manual intervention. This failover mechanism was a critical topic for the 640-816 Exam.

Enhanced SRST (E-SRST)

Over time, Cisco introduced an enhanced version of SRST, logically named Enhanced SRST or E-SRST. This version added more features and capabilities to the fallback mode, making the experience for users at a remote site much richer during a WAN outage. While basic SRST provided essential call functionality, E-SRST aimed to preserve more of the features that users had come to expect from their IP phones. This enhancement made the centralized deployment model an even more attractive option for many enterprises, as it further mitigated the risks associated with WAN dependency.

Some of the key improvements introduced with E-SRST include support for a wider range of phone features during fallback. For example, features like call hold, call transfer, and basic conferencing became available. It also allowed for the use of softkeys on the IP phones, providing a more familiar user interface. Another significant addition was the ability to have a local graphical user interface (GUI) on the router for managing the phones in SRST mode. This was a major improvement over the command-line interface (CLI) only configuration of traditional SRST.

Perhaps most importantly, E-SRST brought support for more phone types and protocols. It improved the interoperability with SIP phones, which were becoming more prevalent. These enhancements closed the gap between the full CUCM experience and the fallback mode, ensuring better business continuity. For the 640-816 Exam, understanding the distinction between SRST and E-SRST, and knowing when to deploy each, was an important aspect of designing a resilient multisite network. It demonstrated a deeper understanding of the available tools for ensuring high availability.

Understanding Call Admission Control (CAC)

In any multisite deployment that uses a WAN, bandwidth is a precious resource. Voice and video streams consume a significant amount of bandwidth, and these networks must also carry all of the organization's other data traffic. If too many simultaneous voice or video calls are placed across a WAN link, it can become congested. This congestion leads to packet loss and jitter, which severely degrades the quality of the calls, making them sound choppy and robotic. To prevent this, a mechanism is needed to limit the number of active calls on a given link. This mechanism is called Call Admission Control, or CAC.

CAC works like a gatekeeper for your WAN. Before a call is allowed to be established across a WAN link, the CUCM checks to see if there is enough available bandwidth. The administrator pre-configures the CUCM with information about how much bandwidth is reserved for voice and video calls on each WAN link. When a new call is attempted, CUCM decrements the available bandwidth. If there is enough bandwidth, the call is allowed to proceed. If there is not enough bandwidth, the call is blocked or, preferably, rerouted through an alternative path, such as the PSTN.

This process ensures that the active calls on the WAN always have the bandwidth they need to maintain high quality. It prevents the oversubscription of the link and protects the user experience. By rejecting a new call when resources are scarce, CAC preserves the quality of the calls that are already in progress. Implementing a proper CAC policy is not just a best practice; it is a mandatory component of any professionally designed multisite voice deployment. The 640-816 Exam placed a heavy emphasis on a candidate's ability to design and implement a robust CAC strategy.

Locations-Based Call Admission Control

Within Cisco Unified Communications Manager, the primary mechanism for implementing CAC is known as locations-based CAC. This method uses a logical construct called a "location" to represent a physical space, such as a remote office or a central campus. Each location is configured within CUCM, and devices like IP phones and gateways are assigned to a specific location. The key part of the configuration is defining the amount of bandwidth that is available for voice and video calls between any two locations.

For example, an administrator could create a location for the New York office and another for the London office. They would then define the bandwidth limit on the WAN link that connects these two locations. Let's say this is set to 1.5 megabits per second for video calls. When a user in New York tries to make a video call to a user in London, CUCM checks the bandwidth allocated between the New York and London locations. If sufficient bandwidth is available, the call is connected. If other calls are already consuming that bandwidth, the new call attempt will be rejected.

This is a simple yet powerful system. It allows for granular control over bandwidth usage across the entire network. An administrator can define different bandwidth limits for audio and video, ensuring that high-definition video calls do not starve out standard voice calls. The concept of a "Hub" location is also used, which typically represents the data center where the CUCM cluster resides. All remote locations would have a defined bandwidth link to this Hub location. Mastering the configuration of locations and the bandwidth between them was a fundamental skill tested by the 640-816 Exam.

Automated Alternate Routing (AAR)

Blocking a call due to insufficient WAN bandwidth is a necessary function of Call Admission Control, but it can lead to a negative user experience. From the user's perspective, they simply hear a fast-busy signal and are unable to complete their call. A much more elegant solution is to automatically reroute the call over an alternative path. This is the purpose of Automated Alternate Routing, or AAR. AAR is a feature that works in tandem with locations-based CAC to provide intelligent call routing during times of WAN congestion.

When CAC determines that there is not enough bandwidth to place a call over the IP WAN, it triggers the AAR feature. AAR then takes the originally dialed number and re-routes the call out to the Public Switched Telephone Network (PSTN). For this to work, both the originating and destination sites must have a local connection to the PSTN. The call essentially leaves the corporate IP network at the source, travels over the traditional phone network, and re-enters the corporate network at the destination. This happens transparently to the user, who is simply connected to the person they were trying to call.

Configuring AAR involves setting up specific CSSs (Calling Search Spaces) and partitions that are invoked only when a CAC bandwidth rejection occurs. The system automatically modifies the dialed digits if necessary to ensure they are in the correct format for the PSTN. While this does incur the cost of a PSTN call, it is almost always preferable to blocking the call entirely. This ensures that important business communications can still take place, even when the primary network path is congested. Understanding the interplay between CAC and AAR was a key differentiator for candidates taking the 640-816 Exam.

The Importance of a Scalable Dial Plan

We explored the high-level architecture of multisite deployments, a central theme of the 640-816 Exam. We established that choosing between centralized and distributed models, and implementing features like SRST and CAC, are critical first steps. However, the true intelligence of a unified communications system lies within its dial plan. A dial plan is the set of rules that a call processing agent, like Cisco Unified Communications Manager, uses to analyze a string of digits dialed by a user and determine where to send the call.

In a small, single-site office, a dial plan can be very simple. It might just consist of a list of internal four-digit extensions. But in a large, multisite enterprise—the environment targeted by the 640-816 Exam—the dial plan becomes exponentially more complex. It must handle routing calls between different offices, potentially in different countries. It must accommodate different dialing habits, provide a path to the public telephone network, and enforce different calling privileges for different users. Most importantly, it must be designed for scalability, allowing the organization to grow and add new locations without requiring a complete redesign of the numbering plan.

A poorly designed dial plan can be difficult to manage, hard to troubleshoot, and can lead to user frustration and toll fraud. Conversely, a well-designed, scalable dial plan is the foundation of a reliable and user-friendly communications system. It is structured, logical, and predictable. The skills required to build such a dial plan are precisely what the 640-816 Exam was designed to validate. These skills involve a deep understanding of the fundamental building blocks of call routing within CUCM, which we will explore throughout this part of the series.

Understanding Route Patterns and Route Lists

The most fundamental element of a CUCM dial plan is the route pattern. A route pattern is a string of digits, which can include wildcards, that CUCM matches against the number a user dials. For example, a route pattern of 9.1[2-9]XX[2-9]XXXXXX would match a typical ten-digit North American phone number that is prefixed with a '9' for an outside line. When a user dials a number that matches a configured route pattern, CUCM knows how to process that call. Each route pattern is associated with a destination, which tells CUCM where to send the call next.

This destination is often a route list. A route list is an ordered list of route groups. This introduces a layer of abstraction and provides redundancy. For instance, a route list named "PSTN_RL" could be created for all external calls. This route list might contain two route groups. The first route group could point to the primary PSTN gateway at the site. The second route group could point to a secondary, backup gateway. If the primary gateway is unavailable, CUCM will automatically try the next route group in the list, ensuring the call still goes through.

This combination of route patterns pointing to route lists provides a flexible and powerful way to direct calls. Administrators can create patterns that match specific types of calls—local, long-distance, international, or inter-site—and direct them to the most appropriate and cost-effective path. The use of wildcards allows a small number of patterns to cover a wide range of possible dialed numbers, simplifying management. A deep understanding of how to craft precise route patterns was a non-negotiable skill for anyone attempting the 640-816 Exam.

Route Groups and Device Pools

We mentioned that a route list contains an ordered list of route groups. A route group is simply a collection of devices that can route calls. These devices are typically trunks, which connect to other systems, or gateways, which connect to the PSTN. For example, an administrator could create a route group called "Primary_PSTN_GWs" that contains the two primary T1/E1 interfaces on the site's voice gateway. The route group tells CUCM which specific resources are available to handle a call that has been directed to it by a route list.

Within a route group, an administrator can define a distribution algorithm. This determines the order in which CUCM will select a device from the group. The most common option is "Top Down," where CUCM always tries the first device in the list and only moves to the next one if the first is busy or out of service. Another option is "Circular," where CUCM cycles through the devices in the list, distributing the call load evenly among them. This structure provides another layer of load balancing and redundancy within the dial plan.

The concept of grouping is also central to another critical CUCM configuration object: the device pool. A device pool is a template that contains a collection of common settings that can be applied to a group of devices, typically all the phones at a specific site. Settings in a device pool include the CUCM group for registration, the date/time group, and, importantly for our discussion, the Calling Search Space for outgoing calls. By assigning a phone to a device pool, an administrator can apply dozens of settings with a single configuration step, which is essential for managing a large number of endpoints.

Digit Manipulation with Translation Patterns

In a multisite environment, it is almost always necessary to manipulate the digits a user dials before sending the call to its final destination. For example, users are often trained to dial a '9' to access an outside line. However, the PSTN does not expect to see this leading '9'. The dial plan must be configured to strip this digit off before sending the call to the gateway. Conversely, a call coming in from the PSTN might need to have digits added to it to conform to the internal dialing plan. This process is known as digit manipulation.

CUCM provides several ways to perform digit manipulation, with translation patterns being one of the most powerful. A translation pattern looks and acts very much like a route pattern. It matches a string of dialed digits, but instead of routing the call, it transforms the number and then sends the modified number back into the CUCM dial plan for another analysis. This allows for complex and flexible modifications. For instance, a translation pattern could be used to convert a short, four-digit extension into a full E.164 telephone number for routing across an inter-cluster trunk.

Digit manipulation can be performed at several places in the call flow. It can be done on the translation pattern itself, on the route pattern, or even on the outgoing gateway configuration. Understanding where and when to apply these transformations is a key skill for a voice engineer. It allows for the creation of a seamless dialing experience for the user, who does not need to know about the complex routing and digit modifications happening in the background. The 640-816 Exam required candidates to be proficient in all forms of digit manipulation.

Partitions and Calling Search Spaces (CSS)

Perhaps the most important and often most confusing concepts in the CUCM dial plan are partitions and calling search spaces, commonly referred to as CSS. These two elements work together to provide call restriction and multi-tenancy. A partition is like a container that holds a set of dial plan elements, such as route patterns or directory numbers. By itself, a partition does nothing. It simply creates a logical grouping of numbers. For example, you could create a "Local_Calls_PT" partition for route patterns that allow local calling, and an "International_Calls_PT" partition for patterns that allow expensive international calls.

A calling search space (CSS) is an ordered list of partitions. The CSS is the key that unlocks the partitions. A CSS is assigned to a device, like an IP phone. When that phone attempts to make a call, CUCM will only look for matching route patterns in the partitions that are included in that phone's assigned CSS. This is how calling privileges are enforced. A phone assigned a "Local_Access_CSS" which only contains the "Local_Calls_PT" partition would be able to make local calls, but would be blocked from making international calls because the international route patterns are in a partition that is not in its CSS.

This mechanism is incredibly flexible. An administrator can create different CSSs for different groups of users—executives, sales staff, interns, and so on—each with a different level of calling privilege. It is the cornerstone of building a secure dial plan and preventing toll fraud. A significant portion of the troubleshooting effort in a CUCM environment often revolves around verifying that partitions and CSS are configured correctly. A thorough mastery of this relationship was absolutely essential for passing the 640-816 Exam.

Globalization and Localization of Dial Plans

As organizations become more global, their dial plans must evolve to handle international dialing in a simple and consistent manner. The best practice for achieving this is to globalize the dial plan using the E.164 standard. The E.164 standard defines a global telephone numbering plan, where every number is unique worldwide and is prefixed with a plus sign (+) and a country code. For example, a US number would be formatted as +1 408 555 1234. The core of a globalized dial plan is to have all directory numbers and route patterns configured in this full E.164 format.

This approach greatly simplifies inter-site and international call routing. A route pattern of +! (where ! matches one or more digits) can be used to direct all external calls to a central routing function. This function can then use the country code to determine the most cost-effective path for the call. However, users cannot be expected to dial these long E.164 numbers for every call. This is where localization comes in. Using translation patterns, the system can take a locally dialed number, like a seven-digit local call, and transform it into its full E.164 equivalent before processing it.

Conversely, when a call is presented to a user, it should be localized to a familiar format. A call coming in from the PSTN as a ten-digit number can be translated to a four-digit extension if it is an internal call. Or, the caller ID for an external call can be modified to show the local dialing format. This process of globalizing on the way in and localizing on the way out creates a powerful and scalable system that is transparent to the end user. This advanced dial plan design was a key topic in the 640-816 Exam curriculum.

Site Codes and Variable-Length Dialing

In a multisite environment with many locations, a structured numbering plan is essential. One common approach is to use site codes. In this design, each office is assigned a unique code, perhaps two or three digits long. The internal extensions at each site would then be prefixed with that site code. For example, if the London office has a site code of 22 and the New York office has a site code of 33, then extension 1001 in London would be 221001 and extension 1001 in New York would be 331001.

This creates a system where every extension in the company is a unique number of a fixed length. This makes inter-site dialing very simple. A user in London who wants to call extension 1001 in New York simply dials 331001. The CUCM dial plan can be configured with a summary route pattern that knows how to route calls based on the leading site code. This is a very clean and scalable approach. However, it does require users to dial a longer string of digits, even when calling someone in their own office.

To improve the user experience, variable-length dialing can be implemented using translation patterns. A translation pattern can be configured at each site to match the short, local extension format. For example, at the London site, a translation pattern could match the four-digit number 1001 and prepend the London site code of 22, turning it into 221001 before sending it to the rest of the dial plan. This allows users to dial short numbers for local calls and full numbers for inter-site calls, providing the best of both worlds.

Time-of-Day Routing

Businesses often have requirements to route calls differently based on the time of day or the day of the week. For example, a main customer service number might need to be routed to the primary call center during business hours, but to an after-hours answering service or a voicemail box outside of those hours. CUCM provides a mechanism to accomplish this using a combination of time periods, time schedules, and partitions.

First, an administrator defines one or more time periods, such as "Business_Hours" from 9:00 AM to 5:00 PM. These time periods are then assembled into a time schedule. For example, a "Weekday_Schedule" could be created that applies the "Business_Hours" time period to Monday through Friday. This schedule now represents the organization's standard operating hours. This schedule is then associated with a specific partition. This partition will only be considered active during the times defined in the schedule.

To implement the routing, two different route patterns would be created for the same number, for instance, the main customer service number. One route pattern, which points to the primary call center, would be placed in the time-sensitive partition (e.g., "Business_Hours_PT"). The other route pattern, which points to the after-hours service, would be placed in a different, always-on partition. By carefully ordering these partitions in the relevant Calling Search Space, CUCM will match the time-sensitive pattern during business hours and the other pattern at all other times. This powerful feature, tested in the 640-816 Exam, allows for highly automated and intelligent call handling.

Go to testing centre with ease on our mind when you use Cisco 640-816 vce exam dumps, practice test questions and answers. Cisco 640-816 Interconnecting Cisco Networking Devices Part 2 certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Cisco 640-816 exam dumps & practice test questions and answers vce from ExamCollection.