Unity Connection Lab Scenario

Here is a lab scenario that a buddy of mine threw out there for me to attempt.  He suggested this concept on the phone and I decided to write it out for the benefits of my readers out there (all two of you, just kidding).  Remembering that the CCIE is an expert-level exam, I felt this was a good test of going beyond basic functionality when it comes to Unity Connection.

Scenario:

Setup voicemail such that users can access voicemail using the messages button.  They should also be able to leave messages with other users in their office and remote offices running CUCM.

However, the users should not have the ability to call the voicemail ports or the MWI on/off numbers from their phones.  They should also not be able to forward their phones to voicemail using the CFwdAll softkey.

Solution:

For the phone lines, assign them the name of whatever voicemail profile you configured as default.  If using the system-generate profile called “Default,” you can leave this field set to <None>.

Configure the Call Forward All, Call Forward Busy, and Call Forward Unregistered fields to “Voicemail,” defining the CSS-Internal partition that only contains internal directory numbers.  The voicemail pilot of 5600 is not in the internal partition.  Therefore, they will not be able to use the CFwdAll softkey to forward to that pilot.

For the device CSS, you can set that to whatever you wish.  The important thing to note is that your device does not require a CSS with the voicemail partition.  The voicemail profile will take of that need for you.

For the voicemail-related components in CUCM (excluding the hunt pilot), throw them all in a partition separate from PT-Internal.

For the hunt pilot, configure the directory number in the internal partition.  Otherwise, the message button on the phone will never work.  Without a correctly defined hunt pilot, callers will be able to leave messages but never check them.

The CSS-Voicemail CSS must contain the PT-Internal partition in order for the MWI on/off feature to work.  Essentially, we are giving Unity a way to contact the IP phones, but restricting the IP phones from being able to access the PT-Voicemail partition apart from the voicemail profile.

Configuration Notes:

CSS-Internal    Contains: PT-Internal
CSS-Voicemail    Contains: PT-Voicemail, PT-Internal

CiscoUM1-VI1    CSS-Voicemail    5601    PT-Voicemail
CiscoUM1-VI2    CSS-Voicemail    5602    PT-Voicemail
MWI On            CSS-Voicemail    8000    PT-Voicemail
MWI Off            CSS-Voicemail     8001    PT-Voicemail
VM Pilot        CSS-Voicemail    5600
VM Profile        5600/CSS-Voicemail

Hunt Pilot        5600/PT-Internal        Points to HL-Voicemail
Hunt List        HL-Voicemail            Points to CiscoUM1 (Line Group)
Line Group        5601/PT-Voicemail and 5602/PT-Voicemail

4 Responses to “Unity Connection Lab Scenario”

  1. Kim Duplex April 6, 2010 at 2:56 am #

    First let me say Thank You for posting. I know this CCIE journey is a huge endeavor and your willingness to share is not going unnoticed. I've been lurking on your blog because I have found it very helpful to read others experiences (especially on balancing family and studying). I passed the written two weeks ago, scheduled the lab for 10/15 and started a notebook. Thank you again for insight and inspiration!

  2. VJ April 6, 2010 at 3:51 am #

    Amazing material! Thank You very much for sharing it.

  3. me April 6, 2010 at 4:16 am #

    Great compilation, thanks for this!

  4. Asa Hoehne May 4, 2010 at 9:15 pm #

    you know your stuff, thank you bud, excellent read.