Hmm yes I thought it might be something to do with it - we're not using DNS at all on any of the servers, and i've renamed the hostid's to be just IP addresses.

I'm not ruling this out, but it used to work with 6.x !

Right.. it used to work with 6, but not with 7x I have found. I changed everything to IPs and it did not work for me. I opened a tac case, added in my DNS, and domain names to the pub/sub/cups and it started working.

Also, if you are trying to see yourself as presence, it does not work. If open up your client, add in your own name, this hoses the presence state completely.

Good point, i'd best remove myself! Thanks for that one...

Just sorting the DNS details now, thanks for the input!

I spent hours trying to figure out why my presence would not change. Finally I figured out or TAC, cant remember which, we removed my name from my own client and magically it started working. It's like it was looping itself for presence and never worked. So for testing, make sure you have (2) clients up and running to really test that it works. One client is not a good test.

Good luck!

What version is your CUPC? 1.2.x or 7.0.x?

Usually we see this behavior on different version of CUPC instead of CUPS.

Workflow has been changed on CUPC 7.0.x. It'll try to use the node_name+proxy_domain to connect to presence.

For more detailed information, please see:

http://htluo.blogspot.com/2009/01/how-does-cupc-deterine-presence-address.html

Michael

Ok I'm using CUPC 7.x

I've added DNS records to our AD server, and then enabled the DNS servers on the CUCM Publisher (We dont have Subs), and on the CUPS server. I then rebooted both boxes.

I can successfully enter now-d-cups or now-d-cm-pub into my browser and it resolves correctly.

Presence still isnt working however. Thanks for your post Michael, I had a read of your blog. Below is the text from the Presence server health window:

Presence.Domain=nowcomm.local

Presence.MostRecentListenPort=50027

Presenc.Primary.Address=now-d-cups

Presence.Primary.Port=5060

Presence.Primary.Protocol=TCP

Presence.username=mgerrard

Users in the contacts list originally appear as aaboo@nowcomm.local before resolving to the proper display name.

Mike.

From your CUPC computer, can you ping now-d-cups.nowcomm.local? This is the address CUPC tried to connect.

Michael

Hi Michael, yes I can no problems.

The plot thickens...

I found that under licensing, none of the units were being used! Some of the services under service parameters had "Inactive" next to them, but a quick visit to Serviceability told me that the services were activated and running (the troublshooter also says the same). i had to fully deactivate services one at a time, and reactivate them to get the services to go active properly, and to use the licenses from the pool. Definitely something screwy going on!

So..

I'm now able to see that Presence has gone "green" in the client's troubleshooter, but still no Presence information. One other slight oddity is that adding a user to the contacts list, doesn't appear until I close the program completely and re-enter it.

Mike.

This is called "Notification Issue". In English - "status didn't update until next logon".

Usually, it's firewall or VPN related. The best way to verify is to do sniffer capture on client and server side.

Michael

No firewall involved - just inter-vlan routing.

Although all the services are now green, including presence, we still get no presence information in the CUP client :(

CSS, DNS, all check out ok.

Any more ideas anyone?

The idea already given :)

"The best way to verify is to do sniffer capture on client and server side".

That's the ultimate way to tell if it's network related or not. (and easiest way)

I should be able to set this up today, and i'll post the results after i've had a look.

Have you any other suggestions though Michael? We're running inter Vlan routing (So no firewalls) and I have disabled all firewalls on my PC, including uninstalling VPN client. The thing is though that it used to work with CUPS 6.x with VPN client installed (Though my Windows firewall has always been disabled). The server has been rebuilt, but has the same IP address so routing etc to the box should be the same.

I've had the same problems here and we went back to CUPS 6.0(4).

Cisco has released CUPS 7.0(3) yesterday but there is no Readme for it now on the Cisco Site but all other new documents.

Reg.

Johann