300-815 CLACC: Cisco Advanced Call Control On-Premises

Cisco’s current 300-815 exam is CLACC v2.0, Implementing Cisco Advanced Call Control On-Premises. It replaced the earlier CLACCM naming on February 3, 2026 while keeping the same exam number. Candidates arriving through an older PrepAway URL or study plan should therefore recognize 300-815 as current but use the CLACC v2.0 blueprint rather than the retired CLACCM v1.x scope.

The exam is an active concentration for CCNP Collaboration. Its focus is advanced signaling and media, session border controllers and voice gateways, Cisco Unified Communications Manager call control, supplemental features and security, mobility, and remote or business-to-business connectivity. This is the on-premises specialization in Cisco’s redesigned Collaboration portfolio.

CLACC rewards engineers who can trace a call. A dialed number or SIP URI enters a policy and routing system, matches call-control logic, crosses trunks or gateways, negotiates signaling and media, and may traverse NAT, security controls, or remote-access infrastructure. When a call fails, the candidate needs to identify which stage broke and why.

SIP troubleshooting starts with understanding a conversation, not a packet list

The v2.0 blueprint includes advanced SIP behavior such as ringback, PRACK, UPDATE, hold and resume, transfer, conferencing, session timers, retries, and refresh. These messages make sense when placed in the lifecycle of a real call: establishment, early media, modification, and termination. Memorizing method names without knowing when they appear produces weak troubleshooting.

Media adds another layer. STUN, TURN, and ICE help endpoints discover workable paths when NAT or restrictive networks complicate direct connectivity. Candidates should be able to separate signaling success from media success. A call can connect while audio or video fails because the negotiated media path, codec, firewall, NAT, or security policy is wrong.

CUBE and gateway logic translate between networks and dial plans

Cisco Unified Border Element sits at important boundaries between enterprise call control, service providers, and external SIP systems. CLACC expects candidates to work with dial peers, URI matching, E.164 pattern maps, dial-peer groups, codec preference, DTMF interoperability, signaling and media bindings, and advanced SIP profiles.

Use a deterministic troubleshooting sequence. Identify the inbound dial peer, normalize the called and calling information, determine the outbound match, verify codec and DTMF negotiation, then inspect SIP and SDP changes. VoIP trace and debugs are most useful when you already know which question the output is supposed to answer.

TLS and SRTP make secure interworking part of normal call design

CLACC v2.0 explicitly includes TLS profiles, SRTP, secure SIP trunk interoperability, certificate management, and secure endpoint registration. Encryption can fail because of trust, identity, cipher compatibility, certificate validity, or an intermediary that is not configured for secure signaling or media.

Study certificates as part of the call path. Which system presents the certificate? Which trust store validates it? Does the subject identity match what the peer expects? Is mutual TLS required? Secure calling should be tested end to end, because a call that falls back to an unexpected insecure path can be more dangerous than a call that fails visibly.

Codec selection and media resources can complicate otherwise-correct routing. A signaling path may be valid while the endpoints have no compatible codec or while a transcoder, conference bridge, or media termination point is required and unavailable. Examine the SDP offer and answer, device-region relationships, and media-resource allocation when a call connects inconsistently or fails only between particular endpoint types.

Globalized call routing requires precise number normalization

Large deployments often normalize numbers into a consistent global form, commonly +E.164, and then localize or transform them near gateways and users. CLACC expects troubleshooting of route patterns, route groups, route lists, translation patterns, transformations, local route groups, partitions, Calling Search Spaces, time-of-day routing, Forced Authorization Codes, and urgent priority behavior.

When routing fails, write down the exact calling and called values at each stage. Determine which partition contains the pattern, which CSS can see it, which transformation applies, and which route list or gateway is selected. This reduces a complicated dial plan to a sequence of explicit matches rather than a guessing exercise.

Call recording and supplemental features depend on media and feature control

The current blueprint includes network-based gateway recording, SIPREC, and built-in bridge options along with call park, pickup, hunt groups, queuing, announcements, music on hold, barge, and busy-lamp field features. These services may appear secondary to routing, but they create additional signaling and media behavior that can expose design mistakes.

Study feature interaction. A recording method may require a specific media path. A hunt group depends on line-group and distribution behavior. Barge and BLF depend on device, line, and presence state. Troubleshooting should verify the underlying call works first, then isolate the supplemental feature rather than treating every failed advanced service as a trunk problem.

UCME and SRST preserve calling when central services are unavailable

Cisco Unified Communications Manager Express and SIP SRST provide local call-control options for branches and survivability scenarios. The value is operational continuity: phones should retain useful calling capability even when WAN connectivity to centralized UCM is lost. Candidates should understand registration behavior, dial-plan differences, and what features remain available during fallback.

Test survivability by thinking through failure and recovery, not only steady-state configuration. What causes endpoints to register to SRST? Which numbers and routes exist locally? How does the site return to central call control? A design that works only while every WAN dependency is healthy is not resilient collaboration.

Call-admission and bandwidth thinking remain important even when the current blueprint emphasizes modern SIP workflows. Branches and WAN links have finite capacity, and oversubscription can degrade voice before it causes complete failure. Understand how QoS, codec choice, local survivability, and routing decisions interact so that a design continues to carry intelligible media during congestion or partial failure.

Mobility and remote access extend the enterprise call-control boundary

CLACC includes Unified Mobility, Extension Mobility, Extend & Connect, and Mobile and Remote Access. These features let identities, numbers, and devices move beyond a fixed desk phone. That flexibility introduces additional authentication, routing, certificate, DNS, and firewall dependencies.

Mobile and Remote Access through Expressway is especially important for off-network endpoints. Candidates should understand the functional roles of Expressway-C and Expressway-E, discovery and registration, traversal, certificate trust, and the distinction between a registration problem and a media-traversal problem.

DNS is a critical part of B2B and remote-access operation. SRV records, A or AAAA records, public reachability, and certificate names must agree with the architecture. A misconfigured DNS record can create a failure that appears to be SIP-related because the call never reaches the intended traversal service. Verify name resolution from the perspective of the external party, not only from an internal administrator workstation.

Expressway supports secure B2B calling across organizational boundaries

Business-to-business collaboration depends on DNS records, certificates, traversal zones, neighbor or DNS zones, transforms, search rules, and SIP trunk integration with UCM. Expressway also includes controls for TLS, mutual TLS, zone media encryption, automated intrusion detection, firewall rules, and toll-fraud prevention.

These features make B2B troubleshooting a boundary problem. Verify public DNS and certificates before assuming UCM is at fault. Confirm the search rule and zone selected for the destination. Then inspect SIP signaling and media traversal. The ability to prove which administrative domain is responsible for a failure is a core professional skill.

Change control is essential in dial plans because a small pattern or CSS modification can affect many users. Before making a production change, identify the expected match, test overlapping patterns, confirm emergency and international calling behavior, and preserve a rollback point. After the change, validate both the new route and nearby routes that could have been unintentionally shadowed by the new pattern.

Logging and packet capture are most effective when synchronized across systems. UCM traces, CUBE debugs, Expressway logs, and endpoint diagnostics should reference the same time window and call identifiers so an engineer can follow one call across administrative boundaries. If clocks differ or logs are collected from unrelated test calls, troubleshooting quickly becomes guesswork. Establish a repeatable capture method before a production incident requires it.

Security testing should also include toll-fraud scenarios. Verify that calling permissions, route patterns, Expressway policy, and border controls prevent unauthorized external users from exploiting the system to place expensive or privileged calls. Collaboration security is not limited to encrypting media; it includes protecting the dial plan and service resources from abuse.

Use synthetic test calls after maintenance to verify more than basic dial tone. Include internal calls, PSTN inbound and outbound, a remote endpoint, voicemail transfer, codec negotiation, and at least one feature such as transfer or conference. A short repeatable validation set can reveal a routing, media, or certificate regression before users encounter it during business hours.

Also verify that monitoring can detect partial failures. A trunk may remain registered while call completion drops for one destination range, or endpoints may stay registered while media quality deteriorates. Service-level tests catch these degradations earlier than simple up/down alarms.

Prepare for CLACC by connecting it to the Collaboration core and cloud track

The active 350-801 CLCOR core supplies the broader Collaboration foundation, while 300-820 CLHCT focuses on hybrid and cloud technologies. CLACC is the deep on-premises call-control concentration. The distinction is useful: a current candidate can choose the specialization that matches the environment they actually operate.

Build labs or paper traces that start with a user dialing a destination and end with signaling, media, security, and feature behavior across UCM, CUBE, gateways, and Expressway. Compare outputs before and after introducing one fault. That evidence-driven method is more effective than memorizing CLACC objectives as isolated bullets and better reflects the day-to-day work of advanced collaboration engineering across the wider Cisco certifications ecosystem.