When CUCM Self-Provisioning is already enabled and each end user has a PIN, the phone must first appear in CUCM as an unassigned device.

1. The user plugs the new IP phone into the network so that it boots, requests DHCP, downloads the SEPDefault.cnf.xml file, and registers as an unassigned (dummy) device.

2. From that same phone, the user dials the Self-Provisioning IVR pilot (default 9777). After entering the extension/ID and PIN, CUCM automatically associates the device with the end user and downloads the correct configuration.

No manual device-to-user association or special key sequence is required once Self-Provisioning is configured.

A. Administrator association defeats the purpose; CUCM performs the association automatically after the IVR interaction.

C. The IVR pilot is not a hunt-pilot; using a hunt pilot will not trigger Self-Provisioning.

E. # unlocks phone settings but does not invoke Self-Provisioning or user association.

1. Cisco Unified Communications Manager 12.5 Feature Configuration Guide – “Self-Provisioning and Bulk Self-Provisioning for End Users”, Workflow Steps 1-3 (sections “End-User Self-Provisioning Process”).

2. Cisco Unified Communications Manager Administration Guide 12.x – Chapter “Configure the Self-Provisioning Feature”, section “End-user steps: Connect the phone and dial the IVR extension”.

3. Cisco Collaboration SRND (12.x), Chapter 9 “Endpoint Provisioning”, subsection “Self-Provisioning”, bullets “Plug phone into the network” and “Dial Self-Provisioning IVR (9777) to associate”.

The "Alternate Extensions" feature in Cisco Unity Connection is specifically designed to associate multiple phone numbers with a single user's voice mailbox. When an administrator configures an alternate extension for a user, any unanswered calls to that secondary number (e.g., from a mobile phone, a home office phone, or a second desk phone) are correctly routed to the user's primary voice mailbox for message deposit. This directly addresses the requirement of accessing a mailbox from a secondary device's extension.

A. Attempt Forward routing rule: This is a call routing action that forwards a call to a specified extension. It does not associate a secondary extension with a user's mailbox.

B. Mobile User: This setting is related to mobility features like Single Number Reach (SNR), which manages call forwarding to mobile devices, not linking multiple extensions to one mailbox.

D. Alternate Names: This feature allows users to be found in the directory by different names (e.g., a nickname). It is unrelated to phone numbers or device extensions.

1. Cisco Unity Connection Documentation: System Administration Guide for Cisco Unity Connection, Release 12.x, "Users" chapter, "Alternate Extensions in Cisco Unity Connection" section.

The guide states, "Alternate extensions are additional phone numbers at which a user can be reached... When a call comes in to an alternate extension and is not answered, Unity Connection is able to find the correct mailbox to record a message in based on the alternate extension number."

2. Cisco Unity Connection Documentation: User Moves, Adds, and Changes Guide for Cisco Unity Connection Release 12.x, "Setting Up User Accounts" chapter, "Phone Information for User Accounts in Cisco Unity Connection" section.

This section details the configuration fields for a user, explicitly mentioning "Alternate Extensions" as the method to add phone numbers for other devices (for example, a home office or mobile phone) that should be associated with the user's mailbox.

The show isdn status output lists “Serial x/x/x:23 is administratively down – Layer 1 DEACTIVATED.”

This message appears only when the T1/E1 controller itself is shut. With Layer 1 down, the D-channel (timeslot 24) never activates, so no setup messages are exchanged and every call fails. Entering:

controller t1

no shutdown

re-enables the physical layer; Layer 1 changes to ACTIVE, Layer 2 to MULTIPLEFRAMEESTABLISHED, and PRI call processing is restored.

A. Wrong switch-type affects Layer 2 negotiation, but Layer 1 would still be ACTIVE; the problem shown is administrative shutdown.

B. Missing bearer timeslots do not prevent the D-channel from coming up; Layer 1 would remain ACTIVE.

C. E1 (30B+1D) framing is used outside North America; circuit in New York requires a T1 card.

1. Cisco IOS Voice Troubleshooting and Monitoring Guide, “Troubleshooting ISDN PRI Layer 1 – Administratively Down”, steps 1-2 (Release 15 M&T).

2. Cisco Command Reference, show isdn status – description of “administratively down” and required no shut (IOS 15.x).

3. Odom, Guy et al., CCNP and CCIE Collaboration Core CLCOR 350-801 Official Cert Guide, 2020, Chap 6, pp. 269-270 (example output and correction with no shutdown).

During digit analysis, Cisco Unified Communications Manager first eliminates any pattern that does not match the dialed digits.

If several candidate patterns remain, CUCM applies its tie-breaker rules: it prefers the pattern with the most-specific match (longest explicit match/fewest wild-cards) and, if a tie still exists, the pattern that addresses the fewest possible endpoints (for example, a single directory number over a translation or route pattern).

Therefore a valid candidate must match the dialed string (D) and, in a tie, the pattern representing the smallest number of endpoints (C) is chosen.

A. CUCM selects the longest, not the shortest, explicit prefix; this option inverts the rule.

B. A non-matching pattern is discarded before tie-breaking and is never selected.

E. CUCM deliberately picks the pattern with the fewest—not the largest—reachable endpoints to avoid over-broad routing.

1. Cisco Unified Communications Manager Dial Plan Guide, Release 14, Chapter 3 “Digit Analysis – Best Match and Tie-Breaker Rules”, pp. 77-79.

2. Cisco Unified Communications Manager System Guide, Release 14, Section “Digit Analysis”, paragraph “If multiple patterns remain… selects the pattern that has the fewest endpoints”.

3. Cisco Live BRKCOL-2037 “CUCM Dial Plan: The Essential Guide”, 2019, slides 31-33 (Pattern Specificity and Endpoint Count).

Cisco Unity Connection can automatically create and maintain voicemail mailboxes by synchronizing its user database with Cisco Unified Communications Manager through the AXL SOAP interface. During initial Unity Connection configuration you add one or more “AXL servers”; once enabled, Unity Connection queries CUCM over AXL, imports the CUCM end-users, and immediately provisions voicemail boxes for them. SIP or SCCP integrations only provide call-routing; they do not expose the CUCM user directory. LDAP/Active-Directory synchronization is configured after installation and likewise does not occur “when the Unity Connection server is configured” by the initial wizard. Therefore, configuring an AXL server is the required action.

A. SIP integration supplies call-signaling only; it does not deliver user records for mailbox creation.

B. SCCP integration handles call-control, not directory/user synchronization.

D. LDAP/AD sync is performed post-installation in separate menus; initial server configuration cannot pull users directly from AD for automatic mailbox creation.

1. Cisco Unity Connection System Administration Guide, Release 14, “Synchronizing User Data with Cisco Unified CM via AXL,” pp. 18-1 to 18-4.

2. Cisco Unity Connection Design Guide, Release 12.x, “User Provisioning and Directory Synchronization—AXL,” Section 5.3.

3. Cisco Unity Connection Installation and Upgrade Guide, Release 12.x, Chapter 6 “Initial Configuration Wizard,” Step ‘Add AXL Server’ (page 6-12).

Cisco Expressway-E is the Internet-facing node of an Expressway‐C/E pair. When the Mobile and Remote Access (MRA) feature is enabled, Expressway-E provides secure firewall-traversal for Jabber and telepresence endpoints, exposing voice, video, IM-&-P, voicemail and directory services to users outside the enterprise. Activating MRA therefore unlocks the full, intended feature set of the Expressway-E platform. By design, Expressway-E does not allow endpoint registration, does not function as a PSTN SIP gateway, and contains no MCU/bridge resources.

A. H.323 endpoint registrations – Registration services are disabled on Expressway-E; only Expressway-C (or CUCM) can register endpoints.

C. SIP gateway for PSTN providers – PSTN connectivity is delivered by CUBE/ISR, not by Expressway-E.

D. VTC bridge – Expressway-E has no conference-bridge/MCU capability; external CMS or MCU is required.

1. Cisco Expressway Administrator Guide X14.0, “Differences between Expressway-C and Expressway-E”, Table 4, p. 18 – notes “SIP registrar and H.323 gatekeeper disabled on Expressway-E”.

2. Cisco Expressway Basic Configuration for Mobile and Remote Access X14.0, Sec. 1 “About Mobile and Remote Access”, pp. 5-6 – describes enabling MRA on Expressway-E to provide all remote collaboration services.

3. Cisco Collaboration SRND Release 12.x, Ch. 17 “Mobile and Remote Access”, pp. 17-5 to 17-7 – identifies Expressway-E as the public-side component that delivers MRA.

4. Cisco Expressway Series data sheet, DS-4018, “Key Features” – lists Mobile and Remote Access under Expressway-E capabilities; no mention of PSTN gateway, MCU, or endpoint registration.

Transrating fixes packet-size mismatches when the codec itself is identical.

Only IOS-based MTPs (software or DSP-based hardware) can negotiate and repacketize G.711 streams at different sample sizes (10/20/30/40 ms).

The built-in CUCM software MTP is limited to a fixed 20-ms packetization and therefore cannot interwork with a 30-ms endpoint.

Transcoders are irrelevant because no codec change is required.

B. CUCM software MTP supports only 20-ms packets and performs no packetization conversion; cannot interwork with 30-ms endpoint.

C. A transcoder converts between different codecs, not different packet sizes of the same codec; unnecessary here.

D. Hardware transcoder (DSP) again performs codec conversion, not packetization adjustment.

1. Cisco Collaboration SRND 12.x, “Media Termination Point,” Table “Supported Sample Sizes” – CUCM software MTP (20 ms only); IOS Enhanced MTP (10/20/30/40 ms).

2. Cisco IOS Enhanced Media Termination Point White Paper, Doc ID 116076, section “Packetization Conversion,” para 2 – “IOS software or DSP-based MTP can transrate between 10-, 20-, 30- and 40-ms packets.”

3. Cisco Unified CM Features and Services Guide 14, chapter “Media Termination Point,” sub-section “CUCM Software MTP Limitations” – “No support for packetization conversion; fixed at 20 ms.”

In Cisco Unified CM, DHCP service activation only enables the internal DHCP engine. To make the server operational, you must define at least one DHCP scope (subnet) that specifies the usable address pool, default router, option 150, and other parameters for the IP phones. This is done in Cisco UCM Administration via System > DHCP > Subnet. Until a subnet (scope) is added, the CUCM DHCP service will not hand out any leases, so adding the DHCP subnet is the required next step.

A. Cisco DHCP Monitor Service restarts automatically when activated; manual restart is not required.

B. DHCP operation is local to CUCM; no changes to external DNS servers are necessary.

C. TFTP service distributes device configuration files, unrelated to DHCP scope creation and need not be restarted for DHCP to function.

1. Cisco Unified Communications Manager Features and Services Guide, Release 14, “Configure the Cisco DHCP Server,” Steps 1–3 (pp. 281–282).

2. Cisco Unified Communications Manager Administration Guide, Release 12.5, Section “Adding a DHCP Subnet” (p. 2306).

3. Cisco Unified Serviceability Administration Guide, Release 14, “DHCP Monitor Service—Automatic Restart Behavior” (p. 119).

The exclamation-point wildcard (!) in a Cisco Unified CM route pattern represents “one or more digits of variable length.”

Pattern 9.011! therefore permits any international access code (011) followed by any length destination number, allowing a single pattern to cover all international destinations and thus minimizing the total number of route patterns required.

A. 9.011# ‘#’ is an end-of-dial marker; it does not allow additional variable digits, so a separate pattern would be needed for each length.

B. 9.011@ ‘@’ matches only NANP-compliant numbers (North American dialing), not generic international numbers, so it omits many destinations.

D. 9.011 ‘’ is treated as the literal star key, not a wildcard; no digits follow, so it cannot match variable-length numbers.

1. Cisco Unified Communications Manager Administration Guide, Release 12.5(1), “Route Pattern Wildcards and Special Characters,” Table 44: ‘!’ – “Matches one or more digits (variable length).”

2. Cisco Unified CM Features and Services Guide, Release 14, ch. Dial Plan, section “Wildcards (Special Characters),” p. 16-9: describes ‘#’, ‘@’, ‘’, and their specific behaviors; notes that ‘@’ is limited to NANP and ‘#’ marks end of dial string.

3. Cisco Press, “Deploying Cisco Unified Communications (CVOICE) v8.0 Foundation Learning Guide,” ISBN 9781587204173, ch. 5, “CUCM Dial Plan,” p. 177-178: explains that 9.011! is the recommended single pattern for international dialing because ‘!’ covers variable-length subscriber numbers.

For Mobile and Remote Access (MRA), external clients must discover the Cisco Expressway-E server to establish a secure connection. This discovery process relies on a specific DNS Service (SRV) record. The collab-edge.tls. record is configured in the public DNS to resolve to the FQDN of the Expressway-E. The collab-edge service identifier directs collaboration clients, and tls specifies that the connection must be secured using Transport Layer Security, which is mandatory for MRA.

A. cisco-uds.tcp.example.com: This SRV record is used for internal service discovery, directing clients to Cisco Unified Communications Manager (CUCM) for User Data Services (UDS), not for external MRA.

C. collab-edge.tcp.example.com: This record is incorrect because MRA mandates a secure connection. The protocol must be tls (Transport Layer Security), not the unencrypted tcp.

D. cisco-uds.tls.example.com: This record is not used for MRA. The cisco-uds service is for internal UDS discovery, and the collab-edge service is required for external MRA discovery.

1. Cisco Expressway Administrator Guide (X14.2), "DNS Records for MRA", Page 101.

The document explicitly states, "For service discovery, you must configure the collab-edge.tls. SRV record on the public DNS server. This SRV record should resolve to the FQDN of the Expressway-E that you use for Mobile and Remote Access."

2. Mobile and Remote Access Through Cisco Expressway Deployment Guide (X14.0), "DNS Configuration", Page 17.

This guide details the necessary DNS records for a successful MRA deployment, specifying: "External DNS must have an SRV record for collab-edge.tls. pointing to the Expressway-E FQDN."

3. Cisco Collaboration Edge Architecture Preferred Architecture, Design Overview, "Appendix B: DNS for Collaboration Edge", Page 61.

This design guide outlines the required DNS configuration, noting: "The external DNS server must host an SRV record, collab-edge.tls., which points to the A record of the Expressway-E server or, in a clustered environment, the A records of all Expressway-E peers."