CH 2 Unified Communications REVIEW Flashcards
Four types of Cisco Unified Communications
- Cisco Unified Communications Manager Express (CME)
- Cisco Unity Express (CUE)
- Cisco Unified Communications Manager
- Cisco unity Connection
Cisco Unified Communications Manager Express (CME)
- Embeds in router (2800)
- Terminates T1 ports and other ports for VoIP phones (FXO, FXS)
- FXO - foreign exchange office - analog interface type that connects to a CO or PBX system; FXO ports receive dial tine from the attached device.
- FXS - foreign exchange station - analog interface type that connects to a legacy analog device; FXS ports provide dial tone to the attached device.
- Supports up to 450 phones
- Need product authorization key (PAK) to unlock.
CME Features
- Call processing, Device control - handles signaling to endpoints, call routing and termination.
- Configd via CLI or GUI (CCP)
- Local Directory - can house a local database of users you can use for authentication in the IP Telephony Network.
- Computer Telephony Integration support - Integrated with MS Office contacts with Cisco Unified CallConnector. Use Cisco Unified CallConnector to make calls directly from your MS Outlook contact list.
- Trunks to other VoIP systems, such as CUCM cluster of servers. Use CUM for a small 40-user office and have it connect directly over your data network to the corporate HQ supported by a full CUCM cluster of service.
- Direct Integration with CUE - can work with CUE to get voice mail.
CME Interaction with Cisco IP Phones
- CME controls virtually every action performed at the Cisco IP phones.
- As the user begins to dial digits, each digit is sent to the CME router via SSCP or SIP.
- Once the user completely dials the phone number of the other Cisco IP phone, CME connects the IP phones directly and steps out of the communication stream.
- The two IP phones now communicate directly using the RTP, which handles the actual audio stream between the devices.
The Cisco IP phone to the CME router using either the SSCP or the SIP protocols.
- SSCP –Skinny Client Control Protocol – signaling protocols that allow the CME to communicate with and control an IP phone.
- SIP –Session Initiation Protocol – signaling protocols that allow the CME to communicate with and control an IP phone.
CME Benefits
The fact that CME steps out of the middle of the RTP stream and allows the IP phones to communicate directly is fantastic because of two primary reasons:
- It eliminates the CME router as a point of failure. After CME establishes the RTP stream between the IP phones, CME can crash, reboot and the conversation between the two endpoints continues unhindered.
- The CME router does not become a bottleneck for the RTP stream. If the links to the CME router became saturated or the router ran out of resources, RTP packets can drop, causing the call quality to degrade.
CME Call Flow for calls to the PSTN
- User of the Cisco IP phone picks up the phone to place a call, all the communication is handled by SSCP or SIP.
- After the user finishes dialing the phone number of the PSTN phone, the CME router realizes (due to its dial-plan) that the all needs to exit out a PSTN-connected interface.
- CME now assumes the role of voice gateway and signals to the PSTN to establish the call on behalf of the Cisco IP phone. (the CME router is attached to the PSTN using a digital T1/E1 or analog FXO trunk.)
- Many VoIP now connect to the PSTN using Internet Telephony Service Provider (ITSP) rather than a traditional TSP using a SIP trunk rather than an analog or digital circuit.
- Once the audio for the call connects, the CME router assumes the role of converting between VoIP audio and PSTN audio.
- Use of DSP at this point.
- The CME router has now established two different legs of the call:
- one to the PSTN
- the other to the Cisco IP Phone
- the CME stands in the middle, independently handling signaling from both sides in two different formats.
Note: Unlike the first example, the CME router is now a critical piece of the ongoing RTP audio flow. If it were to fail in the middle of the call, the audio for the call would also fail.
Cisco Unity Express (CUE)
- CUE is a voicemail system – Gives us voicemail.
- CME does not have CU by itself.
- You can install into your CME router in one of two form factors:
- CUE AIM
- CUE NM
Note: ISM and SM are upgrades from the previous AIM and NM.
- Internal Service Module (ISM) – installs internal to the CME router and uses solely flash memory for storage.
- Service Module (SM) – installs externally to the router and uses a hard disk for storage. Because of this, it can hold ten times as much voicemail as the ISM form factor.
CUE Modules Chart
- CUE AIM
- 6 ports included
- 6 ports max
- 65 max mailboxes
- 14 hours of storage.
- CUE NM
- 8 ports included
- 24 ports max
- 275 mailboxes
- 300 hours of storage
- ISM
- 2 ports included
- 10 ports max
- 100 max mailboxes
- 60 hours of storage
- SM
- 4 ports included
- 32 ports max
- 300 max mailboxes
- 600 hours of storage
CUE Features
- Voicemail
- Auto attendant – dial by name, extension, etc.
- Interactive voice response (IVR) – more features than auto attendant with menu driven options.
- Fax - Native T.37 fax processing, to receive and process faxes as TEFF email attachments.
- Backup voice mail with Unity connection - Survivable Remote Site Voicemail (SRSV)
- Standards-based: All signaling between the CME router and CUE module use the SIP protoco.
Cisco Unified Communications Manager (CUCM)
- Current version 8.X
- Runs as a Linux appliance on certified hardware platforms and acts as the powerful call-processing component of the Cisco Unified Communications solution. Think of CUCM as the “director” behind any large org’s Cisco IPT solution.
- It provides the core device control, call routing, permissions, features, and connectivity to outside applications.
CUCM Features
- Appliance based – which means the OS is harden (secure) and inaccessible.
- Supports audio and video
- Redundant server cluster – supports redundant servers configured in a cluster relationship.
- Replicates static (directory numbers and route plans) and real-time (dynamic data such as active calls) database
- Up to 30,000 phones (unsecure mode) and 27,000 (secured mode)
- VMWare – this brings all the high availability and scalability benefits of virtualization to your CUCM deployment.
- Disaster Recovery with SFTP – built-in feature, this service allows you to backup the CUCM database to a network device or over Secure FTP (SFTP)
- Can integrate into a directory structure (Microsoft Active Directory) – CUCM has the capability to be its own directory server to hold user accounts or it can integrate into an existing corporate directory structure like MS AD and pull user account info from there.
CUCM Database Replication & Interacting with Cisco IP Phones
- CUCM works in a cluster relationship.
- CUCM server clusters function as multiple, individual servers with their own, unique config working for the common good of the IP phones.
- In CUCM server cluster, there are 8 servers.
- The CUCM cluster relationship includes two types of communication.
- CUCM Database Relationship
- CUCM Runtime Data
CUCM Database Relationship
The CUCM IBM Informix database includes all the “static” data of the cluster (directory numbers, route plan, calling permissions) This data replicates to ALL the servers in the cluster.
CUCM Runtime Data
The runtime data encompasses anything that happens in “real-time” in the CUCM cluster. Example, when a device registers with a CUCM server, it communicates to all the other servers that it now “owns” that IP phone.