Cisco Presence Integration with CCM 7x in 20 minutes

Posted: June 8, 2009 in CCIE VOICE-LAB
Tags:

hehe… Not in 10 minutes but its in 20 minutes 🙂

It has been a long time since my previous posting on this blog. I have been busy doing all sorts of bits and pieces!!

It seems that people are finding issues with integrating Cisco Call manager with Cisco Presence server. I have to agree to it because there is very limited documentation available for the public on the net. So I thought to spare some time and post it for the benefit of all.

I’m assuming you have already installed and configured Cisco Call manager 7x. Two phones are already registered to it.

Also assuming that you have done the basic installation of the Cisco presence server. As you know Installing Cisco presence is like installing Yahoo messenger in your windows XP.

The next .. next.. next and finish strategy :). It’s just the same as you add Call manager subscriber to a Publisher (in 5/6/7x), same secret, the same Pub Ip address will be asked during the installation.

Here are the summary steps of integrating Cisco call manager 7x with Cisco presence 7x.

Step#1: Enable presence globally on Cisco Call manager

By default presence subscription is disable on CCM.

System>Service parameter>Cisco Call Manager>

Search for “Inter-presence” key word and set “Allow Subscription”

Step#2: Create SIP trunk Security Profile in CCM

Special setting is required for SIP trunk which runs from CCM to Presence.

Copy “non Secure SIP Trunk Profile” to “Presence non-secure SIP trunk Proifle”

Modify below parameters:

  1. Device security mode: Non-Secure

  2. Incoming Transport type: TCP+UDP

  3. Outgoing Transport Type: TCP

  4. Incoming Port 5060 (untick Enable digest authentication)

  5. Enable application Level Authentication UNTICK

  6. Accept Presence Subscription TICK

  7. Accept Out-of-Dialogue REFER TICK

  8. Accept Unsoliciliated Notification TICK

  9. Accept Replace header TICK

  10. Transforms security status UNTICK

Save it

Step#3: Add a SIP trunk now from CCM to Presence

Device>TRUNK>SIP-trunk>

Protocol = SIP

Fill in below parameters:

  1. Device Name : PRESENCE-TRUNK

  2. Description : blah blah

  3. Device Pool : DP_HQ

  4. Common Dev conf : None

  5. Call classification : On-Net

  6. Media resource Grp : MRG_HQ

  7. Location : HQ_LOC

  8. AAR GROUP : HQ_AARG (if not using AAR leave empty)

  9. Packet Capture mode : None

  10. Packet Capture duration: 0

  11. MTP required : TICK

  12. Retry Video call as audio : TICK

  13. SIP information – Desitnation Add: 142.2.64.51

DST is a SRV : UNTICK

  1. Destination port : 5060

  2. SIP PROFILE : Presence non-secure SIP trunk Proifle

Save above.

Step#3: Make your IP Phone presence capable

  1. Register a phone 2001 name it HQ-Phone1

  2. Create end user “test” and associate HQ-Phone1/2001 with the “test” user

  3. Make sure test user is a part of “Standard CCM End User” and “standard CTI enable”

  4. Make sure Primary extension “2001” is selected when you create the above “test” user

Step#3: Add an application user for IPPM and MOC CTI ports

This will be used by Presence server to initiate IP Phone services:

A) Go to > User Management>Application User>

  1. User ID : IPPM

  2. pass : blah

  3. Presence Grp : Standard

  4. Groups : Standard CCM End User

Save it

Repeat above “A” steps for moc_user as well. moc_user will be used by the MOC CTI user in Presence. All users who want presence using Microsoft MOC client will be associated with this user.

Make sure all “accept” tick boxes are TICKED on moc_user.

B) Go to > SYSTEM>Application Server> Add NEW

Add Presence server IP address here, i.e. 142.2.64.51

Save this as well. Damn, too many things to save 🙂

Step#4: Create IP Phone service URL

Go to> Device>Device Settings> IP Phone Service

  1. Service Name : IP PhoneMSG

  2. ASCII Service Name : IP PhoneMSG

  3. Service Description : Blah

  4. Service URL : http://142.2.64.11:8081/ippm/default?name#Device blah

  5. Service Category : XML Service

  6. Service Type : Standard IP Phone Service

  7. Blank

  8. Blank

  9. Enable : TICK

It’s standard Phone URL we create and subscribe in CCM. Nothing new!!

Make sure you copy the correct URL from the DOC CD.

Save above as well.

****Then subscribe above service to HQ phone1/2001*****

Step#5: Enable presence Licensing for each user

Go to> System>License>Capability Assignment>

Then Find the end user you want to assign the presence license.

Tick the user and hit <Bulk Assignment>

A new pop up window to pop-up. Tick both checkboxes in that and save.

  1. Enable CUP – TICK
  2. Enable CUPC – TICK

Step#6: Add CUPC client in CCM for HQ 2001 phone

The trick here is, this is a dummy phone which will control provide HQ Phone1/2001’s presence information to Presence server. Add this dummy presence client and add a HQ2001 DN to it.

Go to> Device>Phone> add NEW

Phone Type : Unified Personal Communicator then hit <NEXT>

  1. Device Name : XXXCISCO

  2. Device Pool : DP_HQ

  3. Phone Button Templ : Personal Communicator SIP blah

  4. CSS : Blah select all common things

  5. Owner user ID : test ← a must

  6. Leave everything else default

  7. Device security profile : Unified Personal Communicator Standard

  8. SIP profile : Standard SIP profile

  9. Digest User : test ← a must ** read more about this

    Save everything above 🙂 so far so good , well done 🙂

    Now add a DN to this above device: (same as HQ phone1 shared one)

  10. Directory Number : 2001

  11. Everything else… default or your customizeble >> Save above

Once above dummy device is added, associate this device with “test” user we created previously. Now you remember we have 2 device associated with this user: A) 2001 phone and B) XXXCISCO

Also Make Physical phone DN2001 has “test” user associated with it. This is the last option in line 2001’s setting before “save” button. If this has not been done and you run presence diagnostic it will keep telling you that “No line appearance existed in CCM blah blah”

That is all we needed to do with Call Manager. Now Jump on the Presence BOX.

Step#7: Presence box general configuration:

After installing basic presence, you’ll see presence post install, setup screen in your web browser by typing a presence Server IP address on your browser and supplying credentials to the login screen.

(hehe, I call it doscreen, sitting like a dog waiting for your fingers to feed it like dog wait for food :))

So you’ll see “Post Install Setup” screen with below options:

  1. CUCM Publisher IP address : 142.2.64.11 (default, not changeable)

  2. AXL User : Administrator

            1. (I’m too lazy to create a new one, for production server, you must create a new AXL user for security reason.)

  3. Axl password : blah blah..

  4. Confirm password : blah blah <then hit the “NEXT”>

  5. Security password : blah blah (whatever you supplied during installation)

  6. Then hit the “CONFIRM” (Ignore the warning)

    Finally you will get 3 options:

    A) Home B) Status C) TOPOLOGY

  7. Click on “HOME” you’ll see you are in a new home 🙂 i.e. Presence main admin page.

Step#8: Upload License and Activate presence Services

  1. First upload the license if you haven’t done that so far.

  2. GO to > Cisco Unified Servicebility>>Tools>Activate services
    Activate all services, it will take 2-3 minutes.

Step#9: Configure Presence

Jump straight on Presence Admin page>>Diagnostic>System Troubleshootor

Pay attention to RED crossed balls and yellow exclamation! Signs and fix them one by one.

  1. Under Presence Engine: Click on FIX under “no communication presence” this will take you to add presence gateway:

    Add NEW>

    Presence Gateway type : CUCM
    Description : blah

    Presence Gateway : 142.2.64.11 ← CCM IP

    Double check the settings under below menus:

  2. SYSTEM> CCM Publisher : Check all parameter under this

  3. SYSTEM> Application Listioner>Default class SIP TCP Listioner (make sure its what you have defined in the SIP trunk on CCM – transport method TCP or UDP, both should have the same protocol/port) we are using:
    Protocol = TCP
    PORT = 5060

  4. SYSTEM> Security>INCOMING ACL
    Add NEW> description=blah/all address pattern=all

Step#10: Tune the Presence Engine’s Service parameter (same as we do with CCM)

SYSTEM>> Service Parameter>Select active CUPS Server> Select Presence Engine

  1. Search “Proxy Domain” and set it to : 142.2.64.51 (or domain name)

  2. Search “Transport Preferred Order” and set it to : TCP/UDP/TLS

Step#10: I Configure IP-Phone Messenger on Presence server

Application>IP Phone> Setting

  1. IPPM Application Status : ON

  2. Application user Name : IPPMSG (created in step 3A)

  3. Application Password : blah…

  4. Confirm password : Blah

  5. Max Instant message : 25 default

  6. Subscription timeout : 3400 default

  7. Publish timeout : 3600 default

    Hit “SAVE”

Step#11: Select a SIP trunk between Presence to CCM

Tell presence which SIP trunk should be used for pumping calls to CCM.

Presence>>Setting>

  1. CUP CVP Support : UNTICK

  2. MAX Contact List Size : 200

  3. Enable instant messaging : TICK

  4. Enable SIP Publish on CUCM TICK

  5. CUCM SIP Publish Trunk : <Select_Your_Trunk><– A MUST

Don’t forget to save after above. Above SIP trunk will be automatically listed in above “5”. This we is the one we created on CCM.

Step#12: Set TFTP address for IP COMMUNICATOR Clients

Application>Unified IP Personal Communicator>Settings

  1. Proxy Listenor : Default Cisco SIP proxy TCP Listenor

  2. Primary TFTP : 142.2.64.11 (CCM pub tftp)

  3. Backup TFTP : 142.2.64.12 (sub tftp) or whatever

LDAP – if you are using LDAP put LDAP parameters there. Else disable it.

Step#13: For MOC client define CTI Gateway

Application>>CUCM CTI Gateway>Settings

  1. Application Status : ON

  2. Application Username : moc_user (make sure its created on CCM as app usr)

  3. Application Password : blah

  4. Confirmed Password : blah

  5. CUCM Address : 142.2.64.11 (CCM address)

Now time to run the Presence troubleshooter again. This will tell you what’s remaining and how to fix it. Once those are done, activate the presence and other services and bingo.. You are ready to rock!! On hang on, oh no!! Still remaining:

  1. Rremote call control (RCC) – for MOC integration (Click2Call, RCC)

  2. Creating users and testing presence

  3. Voicemail integration with Presence

I’m sleepy now, will continue to remain part next day!!

————————————————————————————————————————————

How to integrate Cisco Presence with Call manager

————————————————————————————————————————————

Push Bhatkoti

Advertisements
Comments
  1. Vishal Kp says:

    Have you died or got your ass busted by some one ?Perhaps,your “next day” has not arrived yet.Keep sleeping and take a bamboo in your back!

    • pushkarbhatkoti says:

      hey hey hey Vishal,
      I am not dead yet, I was lucky enough someone took me to the hospital and now I am alive 🙂
      It seems that you have been having a hard day- keep your mental cool mate.

      really don’t have time to do much posting these days. but stay tuned, in a few weeks i will be doing some posting for sharing!!

      cheers

  2. anil says:

    You are AWESOME !!!

    Thanks,
    Anil

  3. Vaijanath Sonvane says:

    Hi…

    This is Vaijanath. I am setting up the CUCM ver 7.x and CUPS ver. 7.x. I have done the same settings as mentioned above but when I am trying to Configure the “Proxy Domain” as CUPS IP address in Service Parameter I am getting the below error:

    ” Proxy Domain: Provide a Valid domain (for example: cisco.com)”

    Also as mentioned in Step 13 where is the “Application>>CUCM CTI Gateway>Settings ” option. I am not getting the this option.

    Please help me out….Wating for your positive reply…as well as your remaining document……

    Thanks in advance…..

    Vaijanath Sonvane

  4. Ahmed says:

    Hi

    Truly great help!

    Regards

  5. Angel says:

    Hi!

    I’m trying to do this, but CUPS 7.x doesn’t have MOC Assignment capabilities like Presence 6.x

    Also some menus are a bit different.

    Regards.

  6. kelash kumar says:

    HI

    It’s very good, please rest of part still remaining can you add me. I need some help in unity if you help me I appreciate.

    Thanks
    Kelsh kumar

  7. Alphawest says:

    Reply to Vaj

    You need to enter your Domain

    such as cisco.com
    or lab.com

    From your Domman Controller you need to be able to ping both CM or Presence server.

  8. Jamin says:

    Well after reading your post you make Cisco Presence install seem easy and I guess it should be. However for myself I keep running into installation errors. I have a HP G3 (Intel Processor) with 4 GB of RAM and 128 GB of hard drive space. I am running VMware and have created a new virtual machine using Linux Red Hat 4 (32 bit), 3072 of Memory and 80 GB of hard drive space. I am using the Cisco Presence ISO image loaded into VMware. It boots up and seems to load according to plan. As I get towards the end I get “an fatal installation error occurred. I’ve tried different servers, different configurations and I still get the same issue. I went into Call Manager and completed steps 1,2,and 3. I’m currently re-installing now but have a feeling it will fail once again. It was my understanding that in order to install Presence all you had to have was network connectivity to your Publisher? I’m new to your site but appreciate what you are doing. I’ll definitely be checking out some of the other posts. If you have any insights into this issue I would appreciate your help.

  9. Arjun says:

    Hi Pushkar,

    Ur writeup was of graet help and plssssssssss could you complete the remaining stuff i.e

    1.MOC integration

    2.Creating users and testing presence

    3.Voicemail integration with Presence

  10. Gisele says:

    I visited many web sites however the audio quality for audio songs present at this website is actually wonderful.

Leave a Reply , I will reply ASAP

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s