After several readers have visited my blog and downloaded Cisco Unified Presence Server Deployment Video Cook Book , I have decided to provide all other blog readers with an opportunity to preview the contents of book. To give further insight into it , i have also included several FREE video tutorials.

You can download LITE version of ebook here for FREE.(Right click to save).

Cisco Unified Presence Server Video Cook Book ToC (Lite)

So, what are you waiting for ? Download the FREE version of ebook & Enjoy Studying ! . If you like the product and want the FULL version , you can get it here:

Cisco Unified Presence Server Video Cook Book FULL Version.

Remember , Cisco Unified Presence  Server Deployment Video Cook Book (FULL Version) includes 35+ Detailed Step-By-Step Video Tutorials focusing on Cisco Unified Presence Server 7 , as well as Microsoft Office Communicator Server 2007 , Cisco Unified Communication Manager 7 and Cisco Unity Connection 7 integration . Not only this , but you will be able to avail  UNLIMITED FULL 1 YEAR FREE UPDATES with new and additional content.

For Downloading the FULL product , click here :

Cisco Unified Presence Server Video Cook Book FULL Version.

SIP phones and trunks use SIP messages for presence information; SCCP phones use presence primitives in SCCP messages.SIP/SCCP phones can subscribe to Busy Lamp Field (BLF) speed-dial notification as well as BLF for directory call lists for missed calls, placed calls, and received calls.

Here are the steps you need to setup BASIC presence feature in CUCME:

• Enabling Presence for Internal Lines:

cucme(config)#sip-ua
cucme(config-sip-ua)#presence enable
cucme(config)#presence
cucme(config-presence)#max-subscription 100
cucme(config-presence)#presence call-list

• SCCP : Enabling a Directory Number to be Watched :

cucme(config)#ephone-dn 2
cucme(config-ephone-dn)#allow watch

• SIP : Enabling a Directory Number to be Watched :

cucme(config)#voice register dn 2
cucme(config-ephone-dn)#allow watch

• SCCP : Enabling BLF Monitoring for Speed-Dials and Call Lists :

cucme(config)#ephone 2
cucme(config-ephone)#blf-speed-dial 1 3001 label “Receptionist”

Enable “Phone Based Monitoring” using following syntax:

cucme(config)#ephone 2
cucme(config-ephone)#blf-speed-dial 1  3001 label “Receptionist” device

• SIP: Enabling BLF Monitoring for Speed-Dials and Call Lists:

cucme(config)#voice register pool 2
cucme(config-ephone)#blf-speed-dial 1 3001 label “Receptionist”

There are couple of ways BLF status can be seen in CUCM:

BLF Speed Dial :

BLF SD is two-fold feature.First,you can press SD button to call another Speed Dial extension and also, you can see “phone presence” status of SD user’s extension.

BLF Call Lists  :

Using BLF Call Lists Feature,which is actually configured at Enterprise Parameter Level, you can monitor “phone presence” status via Missed Calls / Received Calls / Placed Calls. Also,you can see status of Corporate Directory Users.

CUPS (Cisco Unified Presence Server) offers lot more than just “phone presence” status. CUPS offers following three (3) types of Presence Status:

• Phone Presence
• Calendar Presence
• Reachability Presence

In addition to Instant Messaging capability,CUPS can be integrated with Microsoft Exchange Server,Microsoft Office Communication Server (MOCS) 2007, as well as Microsoft Office Communicator (MOC).CUPS also integrates well into Meeting Place Server for Web Conferencing capability.

Now,let me explain each of Presence type for you:

Phone Presence:

As i explained earlier,this is also available in CUCM.While CUPS is integrated with CUCM, it can display Phone Presence status i.e “On the phone”,”Off the phone”,”Do not disturb” etc . to Cisco Unified Presence Communicator (CUPC) client users.

Calendar Presence:

By integrating CUPS with Microsoft Exchange Server, CUPC would be able to display a contact’s status as “In a Meeting”,if user’s schedule is set to busy during that time period.This way ,users can be aware of their contact’s meeting schedules .

Reachability Presence:

Since CUPS is mainly an Instant Messenger (IM) application, Users can set their status as “Online”,”Available”,”Away”,”Idle” etc. Furthermore,users can set custom status for their contacts to see e.g “Out of Office”,”Out for lunch break” etc.

Each of these 3 features is an Independent feature .Forexample, assume that a User has set his/her CUPC Reachability presence status to “Away”.At same time,his Calendar Presence (Exchange) status is set to “Busy” and yet he is also on the phone right now i.e Phone presence status is “On the Phone”. In such circumstance, there is a non-configurable priority for each type of Presence i.e

Phone Presence –> Calendar Presence –> Reachability Presence

So,in short Phone Presence will override all other statuses if other than normal. e.g In case of above example, CUPC will display the user’s status as “On the Phone”.If user puts phone on hook , CUPC would display status as “In a Meeting” (based on Busy schedule in Exchange Calendar).When meeting is over,CUPC will display status as “Away”.Its important to understand each of these presence types in order to better troubleshoot Presence Server.

Cisco is pushing this product forwards mainly for two reasons :

• Before CuCiMoC was launched,the only possible way to integrate Cisco Unified Communication Manager (CUCM) to Microsoft Office Communication Server (MOCS 2007) for call control was via CUPS.CUPS is acronym for Cisco Unified Presence Server and adds another Server  to administrative overhead .Considering High Availability requirements,it would require atleast a 2nd CUPS node and a pair of Load Balancers. CUPS integrated with Microsoft OCS using Remote Call Control (RCC) functionality.For most enterprises already running Microsoft OCS/LCS ,it ended up as a unnecessary burden and high deployment cost mainly due to licensing requirements and administrative overhead.

• Cisco’s primary focus is to control End-to-End Voice path.By introducing Microsoft OCS into the picture,Cisco’s strategy for voice went into jeopardy.Cisco would rather allow Customers to utilize Microsoft OCS for Instant Messaging and Presence while holding control of Voice Path.As per Cisco’s initiative,it would help it maintain QoS requirements for End-to-End Unified Communication.

Thus , by introducing CuCiMoC into the picture will allow MOC client to integrate directly with Cisco Unified Communications Manager for Voice Control.CuCiMoC actually utilizes what’s called Cisco Unified Client Services Framework (CSF) which also acts as a Softphone.Thus,you can either control a Physical Cisco IP Phone (CIPC or 79xx Hardware phone) Or use CuCiMoC softphone capability without need for physical phone. Besides, CUPS integration with Microsoft OCS was accomplished via direct SIP connection which is relatively complex to configure and doesn’t scale well for advanced feature support.

CuCiMoC is a client-side plug-in which integrates into Microsoft Office Communicator by adding a conversation pane to the window.Essentially,its implemented as a tab that is added to the Microsoft Office Communicator window.

I will continue this discussion in future blog posts. Meanwhile, If you want to explore CuCiMoC on your own,see this link for a quick Video Overview.

http://www.cisco.com/cdc_content_elements/flash/voice/uc_10317/index.html