Amp’s CCIE Quest

Chapter 1: Cisco Unified Communications Manager Architecture

Chapter 1 is just an overview of Cisco Unified Communications Manager (CUCM).

The purpose of the Unified Communications network is to integrate voice, video, and data over a single network infrastructure.

Like everything else in the networking world, CUCM is built and based upon a set of standard layers.

• Infrastructure Layer: This is where your physical devices live at. Routers, Switches, and voice gateways. The infrastructure layer carries data, voice, and video between all network devices and applications. This is the layer that also supplies high availability, management, QoS, and network security.

• Call Control Layer: The CUCM and CUCM Express live at this layer. This layer provides for call processing, device control, and administration of the dial plan and features. Call processing is physically independent from the infrastructure layer. That means the CUCM does not have to be in the same physical location for a device.

• Applications Layer: Applications are integrated through IP which allows the applications to reside anywhere in the network. Applications are independent from call-control functions and the physical infrastructure. Some examples of applications include but are not limited to voice mail, meetingplace, ER, and unified presence.

• Endpoints Layer: This where the applications are brought to the end user. The end device can be a Cisco IP Phone, a software based phone on a PC, or a video terminal or communications client.

This chapter discussed the functions, signaling and media paths, hardware specifications, licensing, and the cluster of the CUCM.

Functions:

• Call processing: Basically the complete process of originating, routing, and terminating calls.
• Signaling and device control: CUCM sets up all the signaling connections between call endpoints. (Signaling is also known as call setup and teardown.)
• Dial plan administration: User created list that CUCM uses to perform call routing.
• Phone feature administration: Features and services such as hold, transfer, forward, conference, etc…
• Directory services: Database information such as user information is handled here. CUCM uses LDAP for its local database.
• Programming interface to external applications: Cisco IP SoftPhones, IP Communicator, IVR, etc…
• Backup and Restore Tools: This is where CUCM provides a Disaster Recovery System (DRS) to backup and restore the CUCM configuration database.

Signaling and Media Path:

CUCM uses Session Initiation Protocol (SIP) or Skinny (SCCP) to communicate with Cisco IP Phones for setup/teardown and features.

Once a call has been setup, Cisco IP Phones communicate directly with each other across the IP network using Real-Time Transport Protocol (RTP) to carry the audio.

• SCCP phones send their digits to the CUCM digit by digit.
• SIP phones send their digits to the CUCM in one message. This is also known as enbloc signaling.

CUCM Cluster:

A CUCM cluster is a pool of CUCM servers. There can be up to 20 servers in the cluster. Only 1 can be the publisher with up to 8 subscribers. Only 4 of the subscribers can perform active call processing. The remaining 11 servers in the cluster can be used for TFTP and media resources like music-on-hold (MOH), transcoding, and conferencing.

A CUCM cluster can either be in a hub-and-spoke (one publisher/many subscribers) topology or in a mesh topology (every node updates every other node).

*Device settings are stored in the IBM IDS database.*

Hardware:

Nothing much to say here other than Cisco will ONLY support Cisco-approved hardware, the Cisco 7800 Series Media Convergence Servers. The servers come in two flavors, -H and -I. -H for HP and -I for IBM.

• 2-Ghz processor
• 2 GB RAM
• 72-GB hard disk

CUCM Database

The CUCM database is divided into two types, static and dynamic.

• Static configuration data is created as part of the configuration of the CUCM cluster. The publisher gets read/write access to that data, whereas the subscribers only get read access.
• A portion of the DB is treated as dynamic, allowing read/write access to all servers in the cluster. The dynamic information that can be manipulated is also known as user facing features (UFF).
  • Call Forward All (CFA)
  • Message Waiting Indication (MWI)
  • Privacy, Enable/Disable
  • Do Not Disturb, Enable/Disable (DND)
  • Extension Mobility Login (EM)
  • Hunt Group Login Status
  • Monitor (future use)
  • Device Mobility
  • CTI CAPF Status (Computer Telephony Integration, Certificate Authority Proxy Function)

Implementing Cisco Unified Communications Manager Part 1 (642-446) - June 12 - July 31

Cisco Unified Communications Manager (formerly known as Cisco Unified CallManager) is a really cool IP-based communications system that integrates voice, video, data, and mobility products and applications. In simple terms a one stop shop for your enterprise communication needs.

There are 19 chapters in the Authorized Self-Study Guide so it is my plan over the next month and a half to knock out this book and ace the test. According to Cisco’s CCVP page for the 642-446 exam this test will consist of a gang load installing, configuring, and of course troubleshooting the CUCM cluster.

So here is my plan or goal:

June 12 - June 19

Chapter 1: Cisco Unified Communications Manager Architecture

Chapter 2: Deployment Models

Chapter 3: Installation and Upgrade

Chapter 4: Administration

I will write up a complete chapter summary at the end of each chapter. I am still not to sure which CCIE track I am going to pursue now. I work for a service provider, we do a ton of routing and switching, and we are now bringing in a plethora of IPT customers. Oh the choices…

Cisco Voice Over IP 5.0: To Be Determined

Course 1: Introduction to VoIP
=========
Lesson 1: Introducing VoIP Network Technologies
Lesson 2: Introducing VoIP Network Architectures
Lesson 3: Building Scalable Dial Plans
Lesson 4: Calculating Bandwidth Requirements
Lesson 5: Allocating Bandwidth for Voice and Data Traffic
Lesson 6: Considering Security Implications of VoIP Networks

Course 2: Configuring Voice Networks
=========
Lesson 1: Configuring Voice Networks
Lesson 2: Adjusting Voice Interface Settings
Lesson 3: Configuring Dial Peers
Lesson 4: Configuring Voice Port Network connections

Course 3: VoIP Signaling and Call Control
=========
Lesson 1: Introducing Signaling and Call Control
Lesson 2: Introducing H.323
Lesson 3: Deploying and Configuring H.323
Lesson 4: Configuring SIP
Lesson 5: Configuring MGCP
Lesson 6: Comparing Call Control Modes

Course 4: Improving and Maintaing Voice Quality
=========
Lesson 1: Designing for Optimal Voice Quality
Lesson 2: Implementing CAC

Ok I know it has been many many months since the last time I posted something here on the blog. So where do I begin? Oh yeah, how about the beginning. Well when I started this blog I was gung ho about pursuing the CCIE SP when I was volunteered to pursue a new direction. The powers that be on my job decided that I should be the go-to-guy for our IPT solution on the Midnight Shift. With performance objectives dictating whether or not I get my bonus, keep my job, and get in line for a promotion I gladly welcomed the new direction and set out to obtain the CCVP. Well in the midst of that I started going through some very traumatic personal issues on the home front. I ended up losing over 20lbs due to all the stress, hurt, and aggravation. Don’t get me wrong I wanted to lose weight, I WAS 5′10″ and 230lbs with 28% body fat, I just didn’t want to lose weight that way. So fast forward a few months, I am still 5′10″ (hoping to reach at least 6′0″ one day) and now down to 205lbs and about 20% body fat. Still fighting through the issues at home and now trying to find the same passion for the CCVP that I have for the CCIP and CCIE SP. I have taken two of the CCVP tests so far, QoS and CVOICE. I am preparing for the CIPT1 test at this time. Once I fulfill my obligation of getting the CCVP I will more than likely pursue the 350-030 exam for the CCIE Voice. My approach will be very similar to what Ethan Banks over at www.cciecandidate.com used when he was preparing for the CCIE. I saw that a methodical, detailed approach will work much better than just hodgepodging my way through it. As a matter of fact I decided last night at work that I will utilize the E. Banks method while I am pursuing my CCVP. Even though the name of this blog is CCIE Quest, for the time being I will use it to chronicle my CCVP Quest. Well until next time…Keep banging…

I must apologize again for my tardiness in giving you all an update about the head injury I suffered a couple of weeks ago. First let me say thanks to my friend Thequest2 for calling me to check on me. Anyway, after a CAT Scan and a MRI the doctors can not conclusively say what it was that was causing me to suffer. So on the one hand it is great that they found nothing and on the other hand it sucks that nothing was found because there is no logical explanation as to what was wrong.

So  I am as healthy as can be, and very thankful to Christ that nothing is harming me….

There is another blog that I have been reading that is actually a joy for me to read. It is from Steve Cook over @ http://www.lifeonaire.com. Check him out whenever you get a chance…

Well I know I have been away for about a week or so but I had to work hard to TRY and make my deadline for sitting for the written. I thought that it would be in my best interest to not post daily about what I was reading and studying and to save that for the lab studies. I was going to take the written this coming Friday but I am going to have to push the date back 2 weeks so instead of September 14 I plan on taking the written on September 28, 2007.

Sorry for not posting any useful updates in a while but I promise once I get past this written and actually start working on the lab it will get better…

I wanted to also send a shout out to Layer 1 Transport for adding me to his blogroll. Please show some love to them over @ http://layer1transport.blogspot.com/

I finished the 1st chapter of the BGP Design and Implementation book (Advanced BGP Introduction) and I must say that so far this book seems to be well written. Now I don’t want to jump the gun and say that it is written as well as a Doyle book, it is definitely not as bad as the BSCI book that was written by two young ladies that I will leave nameless, (I am a respectful guy). It was very hard for me to follow that particular book; so far I don’t think I will have that problem with this book.

The 1st chapter covered BGP characteristics such as:

• Reliability - BGP is considered reliable because it uses TCP as is transport service.
• Stability - BGP is considered stable because of features like Route Dampening. Unstable routes are penalized and subject to being suppressed.
• Scalability - BGP is scalable due to the number of peer sessions and the number of routes that it can support. Considering that the internet has well over 100,000 routes can show you just how scalable BGP is. Also two features such as Route Reflection and Confederation also show why BGP is scalable. I will discuss Route Reflection and Confederation later on.
• Flexibility - BGP is considered flexible because of the number of path attributes that can be used to define policies. (more on path attributes later).

This 1st chapter also had a brief section discussing the difference between BGP (an EGP) and the IGP’s in use today. Nothing really major to report there, an IGP isn’t as suitable as BGP (an EGP) for interdomain routing.

I am starting on chapter 2 tonight, Understanding BGP Building Blocks…

Before I leave, I wanted to send a shout out to Carl over @ http://www.sunpenguin.net for sending me some well wishes with this injury I told you guys about last night, anyway Thanks Carl…

Ok I know I have been away for a few days but there is a really good reason why. I hit my head while carrying a metal tent and since then I have been battling sharp head pains. I had a CAT Scan which did not show what the cause of the pain is. I had to argue with my doctor and her nurse to let them know that this pain is not something that I made up in my head. (no pun intended). So after persuading them that something is wrong, other than a sinus infection, I am scheduled to have an MRI done on my head this Friday. I am not thrilled about having an MRI, mainly because I don’t like to feel enclosed or trapped, I am not claustrophobic at all but not being in control of my environment is something that I do not like.

Anyway, I received my book from Ciscopress.com, BGP Design and Implementation I plan on devouring this book before I sit for my written. Being that I have to take the written shortly I may have to back away from the good-ole-blog until I start prepping for the Lab. That’s when I will be able to get into more detail anyway.