Thank you for the quick reply.

Yes, I have checked the subscribe CSS on the phone, the CUPC client and the SIP trunk. They are all correct.

The devices are in the same Presence group, AND I have the "Allow Subscription" checked between the standard presence group and the new presence group so that should be fine.

All users are mapped to their corresponding DN's.

Some more pertinent information on my situation...

We are running CUCMBE so I cannot synch LDAP with CUCM. I do have it synched with CUPC and the user names are the same in CUCM as they appear in LDAP. The LDAP is AD.

The Presence server is running in VMware which will not allow me to apply the license obtained from Cisco, but does automatically supply two Presence Engine and two Proxy Server licenses when it detects the VMware server. I could see this being an issue, but on the other hand, even though this wouldn't be supported by TAC it is a common way to set up a lab.

I'm wondering where the CUPC client is authenticated... the login server is the CUPS server, but even though it's logged into that server the client status has never shown anything other than offline.

Call control is good... even the IMAP integration with Unity Connection is working. It seems that I have everything working with the exception of the Instant Messaging and the Presence information.

My thinking is that it's somewhere in the SIP trunk, but I have tried so many things differently and still no success. I can see subscribe and publish messages in RTMT looking at the SIP Proxy but don't know where to look for issues there.

I can't be the only one having trouble with a VMware lab can I? Someone must have faced the same challenges here....

Thanks for the help!

Scott

OK, I just loaded up CUPC 7.0 and noticed something different. When the CUPC client first comes up, the user names in my contact list are formatted like "sbarns@domain.local" and after is fully boots up (and synchs with AD?) the user names are switched to the full names which are attached to the "sbarns@domain.com" user account.

I am using MS Active Directory so I used the default synch fields in the CUP server. Maybe I have a mismatch in those fields???

I'm running CUCM7 and CUPS7 in the lab but am in offiste meetings all day. Let me check out the SIP trunks, enterprise params (around the DNS and BLFs, etc) and service parameters.

Question - Does the presence on the handset work (BLF in the directory, etc)?

I am getting device state from CUCM at the phone/AC. When I have the Attendant Console open I get the line state for each user.

Still @ meetings, however it sounds like your def on the right track.

One thing I remember that stumped me when I did a CUPS 1.0 install a while back was ensuring the Security ACLs in CUPS (inbound and outbound) were set to permit. By default CUPS has a deny for incoming and outgoing traffic.

Apart from that, DNS sounds like the most obvious issue but I'll check it out when I get back to the office.

OK, I made a couple of changes that fixed this issue. I wanted to post the resolution so others in my situation might benefit from my hours of frustration....

First, and most importantly, I changed the proxy domain field (System > Service Parameters > Presence server > Cisco UP SIP Proxy) from the suggested value of domain.local to the FQDN of my Presence server... so CUPS-6. NOT CUPS-6.domain.local... just the server name. Then after having the non-returnable IM issue, I changed that name to cups-6 and resolved all IM issues.

Second, I changed from using the SIP PUBLISH model between the CUCM 6.1 and the CUPS 6.0 and went with a standard SIP trunk. I need to go back and investigate this one because the PUBLISH model should work so I'll play with it until it does. In the mean time, I have a working system!

Graham, thanks for working with me on this. The support of the NetPro community with it's massive knowledge base is very important as we move into the fully converged IP world. It's impossible to be an expert on every subject yet sometimes our customers and/or employers expect it. After all, it's all just IT right? ;)

IT? How hard can it be?

Ha.

Good to hear you got it working.

-graham