CCNP Collaboration common mistakes
CCNP Collaboration · Understand the traps and how to avoid them.
Designs a CUCM cluster by assigning one region codec everywhere and never configuring location bandwidth or CAC.
The candidate conflates regions (codec policy between sites) with locations (call admission bandwidth), so the design looks correct on paper but fails when WAN links are oversubscribed.
What to do instead
Separate the two constructs explicitly: use regions to choose codecs and locations to enforce bandwidth. Calculate per-call bandwidth including IP/UDP/RTP overhead, apply location CAC, and validate with a call-admission test between locations.
Treats route patterns and translation patterns as interchangeable and cannot predict which pattern wins during digit analysis.
Memorizing wildcards without practicing best-match rules, partition/CSS behavior, and urgent priority leads to wrong selections in tie cases.
What to do instead
Build a small dial plan with partitions, CSS, route groups, and route lists. Use Dialed Number Analyzer to test longest-match, urgent-priority, and translation-pattern tie cases, then document the precedence rules from observed results.
Assumes 180 Ringing always means no early media and 183 Session Progress always means early media is present.
The candidate maps provisional SIP responses to media behavior without checking SDP, Require: 100rel, and PRACK negotiation in the actual call flow.
What to do instead
Trace a SIP ladder for each case: inspect whether the 183 contains SDP, whether 100rel is required, and whether PRACK is sent. Correlate those fields with SIP profile settings and endpoint behavior.
Deploys Expressway-E for Mobile and Remote Access with self-signed certificates or certificates missing required SAN entries, then expects endpoints to register.
The candidate focuses on traversal zone and DNS configuration but overlooks certificate trust, SAN completeness, and the chain of trust required by endpoints and CUCM.
What to do instead
Use CA-signed certificates, include the required public and internal names in the SANs, install the full chain, and verify _collab-edge._tls SRV resolution plus endpoint trust before testing registration.
Confuses UCCX script/trigger behavior with CUCM CTI route point configuration when designing a contact center call flow.
Collaboration Applications is studied in isolation, so the candidate cannot map a CUCM route point to a CTI port/trigger and then to the UCCX script.
What to do instead
Draw the end-to-end flow: CUCM route pattern to CTI route point, CTI port/trigger to UCCX script, queue and agent selection. Lab each hop and verify with UCCX script traces and CUCM call logs.
Configures DHCP option 150 for every endpoint and expects SIP phones to register through TFTP.
The candidate assumes one DHCP option fits all endpoint types and does not distinguish SCCP from SIP provisioning behavior.
What to do instead
Know which option each endpoint family uses: option 150 for SCCP TFTP, and option 66/67 for SIP provisioning. Verify TFTP reachability, phone firmware load, and certificate trust after changing DHCP scope options.
Assigns MTP, transcoder, and conference bridge resources to an MRG without checking MRGL assignment on devices and trunks.
Media resource selection depends on MRG/MRGL order and device-level assignment, not just resource registration, so calls fail only when a supplementary service invokes the resource.
What to do instead
Build MRGs by site and function, attach MRGLs to devices and trunks in the intended order, and test hold, transfer, conferencing, and codec mismatch scenarios that force MTP or transcoder use.
Calculates location bandwidth using only the codec payload bit rate, such as 64 kbps for G.711.
The candidate ignores IP/UDP/RTP overhead, Layer 2 overhead, and the additional bandwidth consumed by MTP or transcoders, so CAC allows more calls than the link can carry.
What to do instead
Use Cisco bandwidth values per codec including overhead, add media-resource overhead where applicable, and verify location call counts against the actual WAN capacity.
Overlooks that Extension Mobility applies a device profile CSS and that line CSS can override or supplement device CSS expectations.
The candidate studies CSS only on physical devices and misses how device profiles, line CSS, and partition ordering interact after login.
What to do instead
Trace digit analysis after an Extension Mobility login: confirm the device profile CSS, line CSS, and partition order. Test with Dialed Number Analyzer using the logged-in user and device profile context.
Treats Mobile and Remote Access and VPN client access as the same deployment and misconfigures UDS or CUCM certificate trust.
The candidate does not distinguish Expressway-based MRA from VPN, so DNS, UDS, and certificate requirements for endpoint onboarding are applied incorrectly.
What to do instead
Compare the two flows explicitly: MRA requires _collab-edge._tls SRV, Expressway traversal, UDS, and trusted certificates; VPN requires client tunnel and internal reachability. Test onboarding with a real endpoint and inspect Expressway and CUCM logs.