Has anyone seen a scenario when CCMAdmin displays the IP address of a CallManager in lists of phones where it should display the IP address of a phone?
The address is a hyperlink that takes you to a web page served by the handset. Occasionally some phones appear with the CallManager's IP address, so the link doesn't work. Resetting the phone from CCMAdmin clears the error but it seemingly happens at random.
Nope... no answer at all.
May raise a TAC case...
Was this ever resolved, we are having the same problem and when this happens, our Berbee services will not work properly b/c Berbee cannot see the IP addresses of the phones, seems to happen pretty often lately, only way to resolve is to reboot all the phones.
That still didn't do the trick, must reboot the phones in order for the IP address to display correctly. Any other suggestions to why this may happen?
Seen this a few times under 4.2(3)sr1 through sr3. Only with gen3 Java phones and newer DST firmware. Biggest problem for us is Syn-Apps SA-Announce blows chunks when it gets the wrong IP address from CallManger.
We've been resetting the phones but now its time to open a TAC case.
We've seen the same thing on CCM4.1(3)es122.1 with 7911 phones. So far we just reset the phones, but if this is more wide spread I would be interested in resolution.
Did you get anywhere with the TAC case? I am seeing this problem and am very interested in any fixes you have uncovered.
No where with TAC on this issue, I opened 2 different TAC cases with 2 different customers experiencing this problem. I restarted Tomcat and reset all phones, still happened again within about 1 to 2 weeks. Sent various logs and traces to TAC, but they couldn't find anything. One of them summed up the problem as being a 1 time cosmetic event. Very strange issue. Still happening, one of the customers has Berbee so when this occurs, Berbee doesn't work properly. If anyone else finds out any info, please pass along.
In addition to b_furgeson I opened my own TAC case.
Ours was limited to 7911 phones only. I documented the situation very thoroughly and TAC directed quite a bit of investigation and setup. Needed problem to reoccur. Waited 3 weeks and it did not reoccur and hasn't occurred since. But we did downgrade 3gen phone firmware from 8-3-2 to 8-2-2 for other reasons.
Strongly suspect SNMP MIB's on some phone firmware versions are getting out of whack and reporting incorrect information to RIS Data Collector service.
Our clusters/phones having this problem also have Syn-Apps through the phone paging.