CCIE Collaboration flashcards
CCIE Collaboration · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- CUCM cluster maximum users
- A single Cisco Unified CM cluster supports up to 20,000 users; multi-cluster deployments using Intercluster Lookup Service can scale to 40,000 or more users across clusters.
- CUCM publisher role
- The publisher holds the master database and replicates configuration to subscribers; if it is down, existing calls continue but configuration changes and new registrations fail.
- Device pool components
- A device pool defines region (codec selection), location (call admission control bandwidth), SRST reference, date/time group, and network locale for a group of devices.
- Region versus location
- Region controls which codec is used between sites; location controls how much bandwidth is allocated for calls between sites for call admission control.
- SRST purpose
- Survivable Remote Site Telephony lets IP phones register to a local router and make calls when the WAN link to the CUCM cluster is lost.
- Intercluster Lookup Service
- ILS replicates dial plan and cluster data across CUCM clusters; a hub cluster is configured and spoke clusters connect to it over TCP 7501.
- Expressway MRA ports
- Mobile and Remote Access uses TCP 7001 (TLS) for signaling between Expressway-C and Expressway-E, and UDP 50000-59999 for media traversal.
- Unity Connection cluster capacity
- A Cisco Unity Connection active/active cluster supports up to 20,000 users; each node can handle the full user load if the other node fails.
- Presence redundancy group
- A Cisco IM and Presence redundancy group pairs two nodes, one active and one standby; a cluster supports up to 40,000 users with two redundancy groups.
- Jabber service discovery SRV
- Jabber uses _cisco-uds._tcp for on-premises CUCM discovery and _collab-edge._tls for MRA via Expressway; _cisco-uds is tried first.
- Unity Connection routing rules
- Routing rules in Unity Connection match the dialed number, caller ID, or forwarding station to route calls to the correct call handler or greeting.
- Cisco Meeting Server API
- The Cisco Meeting Server API on port 443 creates spaces and coSpaces and integrates with CUCM via a SIP trunk for on-premises conferencing.
- Hybrid Call Service connector
- Cisco Webex Hybrid Call Service uses a Call Connector with Expressway-C/E and a registered CUCM to connect on-premises calls to the Webex cloud.
- SIP INVITE key headers
- A SIP INVITE includes Request-URI, Via, From, To, Call-ID, CSeq, Contact, and Max-Forwards; the SDP body lists codecs and RTP media addresses.
- SIP 183 Session Progress
- A 183 Session Progress response carries SDP to establish early media before the call is answered; PRACK can provide reliable provisional responses.
- H.323 call signaling ports
- H.323 uses TCP 1720 for Q.931 call setup and H.245 capabilities, and UDP 1719 for RAS gatekeeper registration.
- CUCM route pattern wildcards
- The @ wildcard matches any dialed number, X matches digits 0-9, # matches a single digit, and ! matches one or more digits.
- SIP OPTIONS ping
- CUCM sends SIP OPTIONS to a trunk to monitor its status; if no response arrives within the retry timer, the trunk is marked down and the route list can use the next member.
- Q.931 cause 16
- Cause 16 indicates normal call clearing; cause 17 is user busy, cause 34 is no circuit available, and cause 47 is resource unavailable.
- Digit analysis precedence
- CUCM digit analysis chooses the most specific match: longer matches win, explicit digits beat wildcards, and route patterns beat translation patterns.
- SIP trunk to route list
- A SIP trunk is a member of a route group, which is a member of a route list, which is referenced by a route pattern for call routing.
- Expressway-E certificate requirement
- Expressway-E requires a public CA-signed certificate with the client-facing domain as a SAN, static NAT to a public IP, and matching internal and external DNS.
- Secure SIP trunk
- A secure SIP trunk uses TLS on port 5061 for signaling and SRTP for media, and requires a certificate trust store and an encrypted phone security profile.
- CUCM certificate types
- CUCM uses tomcat for HTTPS, CallManager for SIP TLS, TVS for phone trust verification, CAPF for phone LSCs, and IPSec for secured signaling.
- Phone security modes
- Phones operate in Non-secure, Authenticated (TLS signaling, unencrypted media), or Encrypted (TLS signaling and SRTP media) mode; Encrypted requires a CAPF-issued LSC.
- Expressway TURN port
- Expressway uses UDP 3478 for TURN media traversal when direct media paths are not possible between MRA clients and internal endpoints.
- B2B neighbor zone
- A Business-to-Business neighbor zone on Expressway uses SIP over TLS with search rules to route calls to a third-party system.
- AXL API access
- The CUCM AXL API uses SOAP over HTTPS on port 8443 and requires an application user with the Standard AXL API Access role; the WSDL version must match CUCM.
- RTMT performance counters
- Cisco RTMT shows Perfmon counters such as Cisco CallManager registered phones and calls active, and Cisco SIP trunk status for real-time monitoring.
- CDR and CAR
- Call Detail Records are written on the CUCM publisher and can be sent to a billing server; Cisco CDR Analysis and Reporting uses the CDR database for reports.
- BAT import workflow
- Bulk Administration Tool imports CSV files for phones, users, and lines; the workflow is create the CSV, validate it, insert it, then run or schedule the job.
- DRS backup
- The Disaster Recovery System runs on the CUCM publisher and backs up the database, TFTP files, and platform configuration to a configured SFTP or FTP server.