Barry Hesk: Cisco Unified Communications Manager training deck 1


Published on

CUCM overview training

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Barry Hesk: Cisco Unified Communications Manager training deck 1

  1. 1. CiscoUnified Communications Manager Training Author – Barry Hesk 26-28/02/2013
  2. 2. ScheduleIntroductionCUCM BasicsAdvanced Configurations and Topics 26-28/02/2013
  3. 3. Introduction“Instructor”- Barry HeskDemo Environment 2 x CUCM 8.5 Servers 1 x Cisco Unity Connection (Voicemail)Focus on the “world according to Customer x” 26-28/02/2013
  4. 4. Platform and ArchitectureCUCM 5.x and higher – delivered on dedicated Linux basedOperating System (RHEL)OS and application bundled into single imageOwned, supported and maintained by CiscoNo supported direct root / shell accessCUCM 4.x and lower – Windows 2000 / 2003 serverplatform. Separate OS and Application (although use ofWindows update was prohibited)CUCM 4.x and lower – SQL database engine.CUCM 5.x and higher – INFORMIX database engine. 26-28/02/2013
  5. 5. Publisher / SubscriberMaster server is called the “Publisher” and is the database “owner”.One Publisher per CUCM cluster.Up to eight call processing “Subscriber” servers can be installed within a CUCMcluster which replicate the database from the Publisher.Any to any DB replication required between all servers in the cluster. List ofTCP/UDP ports available.Publisher is the most important device in the cluster. All configuration changesare made by the Publisher to the DB, and are replicated to Subscribers (even ifthey are made via a Sub GUI).If Publisher is down – or inaccessible – then no major changes can be made tothe DB.Some limited changes are still permitted (Call Forward, Extension Mobility login,toggle DND and a few others).Cannot promote Subscriber to a Publisher.Publisher failure needs to be fixed ASAP! 26-28/02/2013
  6. 6. CUCM ClustersA group of more than CUCM servers.One Publisher per clusterClusters can be interconnected by Inter Cluster Trunks(ICTs).Any to Any call flows required even across ICTs(configurable) 26-28/02/2013
  7. 7. Hardware PlatformsTraditionally CUCM deployed on Cisco MCS servers (rebadged IBM/HP) or specificIBM/HP serversCisco UCS hardware is now Cisco’s preferred platform (the reason they fell out withHP)Rebadged IBM MCS servers are still available.CUCM 8.x provide full support for VMware (4.x and higher) Intel Processors only OVA files available to simplify provisioning.Server platform defines number of handsets that can be registered on a servers 7816 – 500 7825 – 1,000 7835 – 2,500 7845 – 7,500 VMware – size dependant on OVA file used up to a maximum of 10,000 26-28/02/2013
  8. 8. Installation ProcessSingle bootable image (ISO). Cannot be downloadedfrom Cisco’s web site. For new Subscriber – must have network connectivity (including firewall access) to Publisher, plus cluster security password. Each Subscriber consumes a server license on the Publisher Subscriber licenses are (now) FOC. Firewall rules very important! 26-28/02/2013
  9. 9. Upgrade ProcessSingle ISO image which can be downloaded from Cisco’s website. Full reimage of each server. Active / Inactive partitions Upgrade always updates Inactive Partition “switch version” command swaps partitions and reboots Publisher server must be done first. Subscribers can be done after Publisher complete Many upgrades can be done “online” – “switch version” is disruptive. Current upgrades to version 8.6/9.0 mean that servers are down for the duration (upgrade to RHEL core) 26-28/02/2013
  10. 10. Phone FirmwarePhone Firmware New phone firmware can be downloaded from Cisco’s website. Installed onto all servers in the cluster. Must restart TFTP service on each cluster member. By default all phones of the same type will upgrade next time they reset 26-28/02/2013
  11. 11. Backup / RestoreUses Cisco’s utilities (Disaster Recover System)Publisher backs up Publisher and Subscribers to remoteSFTP serverDRS system can restore Publisher and Subscribers,individually or togetherFull system replacement (cannot restore parts of thesystem).Cannot view contents of the backup.Used to replace failed servers within a cluster.Vital to have a valid backup of the Publisher 26-28/02/2013
  12. 12. External AppsCUCM provides call control onlyVoicemail provided by Cisco Unity – runs on Windows platform, now EoS (Unified Messaging) Cisco Unity Connection – runs on same OS CUCM (UM now supported) Cisco Unity Express – runs on module within Cisco ISR.Presence Cisco Unified Presence Server (CUPS) Provides IM, Presence and desk phone control Runs same underling OS as CUCM/CUCNone of these apps can be co-resident with each other (VMware)Cisco Business Edition 5000 provides co-resident CUCM and CUC; howeverthis product is now EoS. 26-28/02/2013
  13. 13. Voice ProtocolsTrunk Side ProtocolsUsed for “server” to “server” signallingSIP – TCP/UDP 5060 Derived from XML. Commonly used to connect to ITSPs for external calls.H.323 – TCP/1720 Simple protocol; tried and trusted and used by default in GKN.MGCP – TCP 2427 Not used in GKN; bugs + functional issues (no support for fractional T1/E1). Issues with fax / modems 26-28/02/2013
  14. 14. Voice ProtocolsClient / Device Side ProtocolsUsed for “client” to “server” signallingSCCP (Skinny) –TCP/2000 Cisco proprietary protocol Default on all Cisco 79XX handsets Most feature rich option (and less bugs)SIP – TCP/UDP 5060 Industry standard protocol SIP firmware images available for most Cisco handsets Some newer handsets are SIP only (89XX/99XX) Jabber / CUPC clients are SIP onlyRealTime Transport Protocol (RTP) Used to transport audio between devices RTP session required in both direction (2 flows per call) Audio in CUCM environment flows end point to endpoint: CUCM only does signalling! RTP uses random UDP port number. RTP is unencrypted. Can be captured and replayed through Wireshark and other tools. 26-28/02/2013
  15. 15. Video and CUCMCUCM natively supports point to point video betweenenabled endpointsIncludes cross cluster.Possible to do video across external gateways (e.g.Lync / other H.323 or SIP system) 26-28/02/2013
  16. 16. Cisco IP Handsets69XX, 79XX, 89XX, 99XX Wide range of wired / wireless phones Video camera options Cannot use entry level SPA phones with CUCM 7915/16 side cars require power supplies!ATA / VGXXX Analog gateways for modem / faxes ATA 187 newer model which has lots of software issues. Can also use Cisco 2900 ISR with FXS ports.CUCM generally supports all phones in new releases (i.e. it does not drop support for old EoSphones).SPA5xx phones use SPCP protocol not SCCP; SPCP is only supported on UC500 seriesplatformsSoftware Phones Cisco IP Communicator Cisco CSF (software based phone that Jabber for Windows / CUPC use) 26-28/02/2013 Jabber for Android / Jabber for iPhone / Blackberry MVS
  17. 17. Cisco IP HandsetsPhone Boot Sequence (useful for troubleshooting) For PoE, phone detects and requests power. None PoE requires power supply Phone communicates to switch via CDP CDP MUST be enabled on the switch Switch returns “voice VLAN” setting to the phone. Switch boots in voice VLAN and requests IP address via DHCP. DHCP server returns IP address of CUCM Server(s) by option 150. Phone contacts CUCM Server(s) and requests phone configuration file. Phone config file contains Phone firmware (with automatic upgrade / downgrade) CUCM server(s) to register with Extension number settings etc Phone’s switch port is placed in “access” VLAN. If “auto qos” is enabled on the switch port, QoS is automatically configured. Interface FastEthernet0/0 Switchport mode access Switchport access vlan 100 26-28/02/2013 Switchport voice vlan 200 Auto qos voip cisco-phone
  18. 18. GatewaysCUCM has no connectivity other than Ethernet/IPNeeds external gateways to connect to PSTNCisco 2800/2900/3800/3900 series gateways “ISRs”CUCM communicates with gateways through H.323 or SIP trunk protocolGateway will be equipped with ISDN cards supporting both T1 (US) and E1 (restof the civilised world)ISDN interface configured with number of channels (which cannot be changedon the fly) called “timeslots”Gateway also contains DSPs – one DSP channel required per external PSTN call.Gateways also can contain analog (FXS/FXO) ports. One DSP channel requiredper active call. FXS – provides connection to analog device (phone / modem / fax machine) FXO – provides connection to PSTN Exchange line 26-28/02/2013Communications Manager Express embeds phone system and gateway intosingle platform