CCNA Voice: Introduction to CME Administration

CME Administration

Command Line Management

Use one of three methods to access CLI:

• Console Port
• Telnet
• SSH

telephony-service configuration command activates CME functionality on a router that supports it

Core CME config commands are performed under telephony-service configuration

show ephone registered command shows phones registered with CME and is most common verification/troubleshooting command

GUI Management

Two flavors: Integrated CME GUI and Cisco Configuration Professional

Integrated CME GUI

Files loaded into flash of router, with assigned IP and http server service turned on the router

Focused on telephony, not pretty

CCP

Can configure all major elements of routers

Wizard-based

Local install on client PC, can be used to manage any supported Cisco platform

CCP Configuration

Before managing devices a community must be configured

Community consists of devices to be managed

Devices to be managed must be configured with four things to support CCP control:

1. Reachable IP from CCP
2. Level 15 Username/password on device
3. HTTP services turned on
4. Local authentication

CCP uses Telnet/HTTP by default, can be configured to use SSH/HTTPS

When a device is discovered by CCP it populates CCP with info

Unified Communications can be configured on a router (if not already enabled) in one of four ways:

1. CME Standalone
2. Voice Gateway (PSTN to VOIP or analog to digital)
3. CME as SRST (CME acts as failover device if CUCM communication is lost)
4. None

CCP has a configuration confirmation screen that shows what commands are to be delivered to the router before being applied, in order to verify correctness prior to submitting