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 basic installation of Cisco presence server. As you know Installing Cisco presence is like installing Yahoo messenger in your windows XP.
By default presence subscription is disable on CCM.
System>Service parameter>Cisco Call Manager>
search for “Inter-presence” key word and set “Allow Subscription”
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
Protocol = SIP
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: 126.96.36.199
DST is a SRV : UNTICK
1. Destination port : 5060
2. SIP PROFILE : Presence non-secure SIP trunk Proifle
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
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
Repeat above “A” steps for moc_user as well. moc_user will be used by MOC CTI user in Presence. All user who want presence using Microsoft MOC client will be associated to 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 188.8.131.52
save this as well. Damn too many things to save
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://184.108.40.206:8081/ippm/default?name#Device blah
5. Service Category : XML Service
6. Service Type : Standard IP Phone Service
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*****
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 with pop-up. Tick both check-boxes in that and save.
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 appreance existed in CCM blah blah”
That s all we needed to do on Call Manager. Now Jump on the Presence BOX.
After installing basic presence, you’ll see presence post install setup screen on your web browser by typing presence Server IP address on your browser and supplying credentials to the login screen.
(hehe, I call it doggie screen, 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 : 220.127.116.11 (default, not changeble)
2. AXL User : Administrator
(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. preseence main admin page.
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.
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 commnication presence” this will take you to add presence gateway:
Presence Gateway type : CUCM
description : blah
Presence Gateway : 18.104.22.168 ← 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
SYSTEM>> Service Parameter>Select active CUPS Server> Select Presence Engine
1. Search “Proxy Domain” and set it to : 22.214.171.124 (or domain name)
2. Search “Transport Preferred Order” and set it to : TCP/UDP/TLS
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
Tell presence which SIP trunk should be used for pumping calls to CCM.
1. CUP CVP Support : UNTICK
2. MAX Contact List Size : 200
3. Enable Instalt messeging : 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.
Application>Unified IP Personal Communicator>Settings
1. Proxy Listenor : Default Cisco SIP proxy TCP Listenor
2. Primary TFTP : 126.96.36.199 (CCM pub tftp)
3. Backup TFTP : 188.8.131.52 (sub tftp) or whatever
LDAP – if you are using LDAP put LDAP parameters there. Else disable it.
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 : 184.108.40.206 (CCM address)
Now time to run the Presence troubleshooter again. This will tell you whats remaining and how to fix it. Once those are done, activate the presence and other services and bingo.. you are ready to rocck!! on hang on, oh no!! Still remaining:
1. MOC integration
2. Creating users and testing presence
3. Voicemail integration with Presence