CUCM 6.1 - Attendant Console Slow 3

[snootalope]

We've got three users that all run the attendant console. Since upgrading to 6.1.1 from 4.1.3, the console is painfully slow when they attempt to click between speed dial tabs, or do just about anything. The console window turns to a grey box for about 5-7 seconds and then snaps out of it. Once it snaps out of it, it works just fine, doesn't miss a beat. But, if they go work in their email, or web, or anything other than the console and come back to it, it freezes for another 5-7seconds and then is fine again.
This is becoming extremely frustrating for our users here and TAC provided no help at all. The machines they're running are loaded with memory and have new processor's, so I really don't think its a lack of resource issue.

Anyone else experiencing this issue?

Also, this message keeps getting generated in the real-time monitor:

LowAttendantConsoleServerHeartbeatRate

Attendant Console Server heartbeat rate below 24 beats per minute. Current heartbeat rate is 0 beats per minute.

 

[whykap]

Did you upgrade AC on the PC's to version that comes with 6.1?
I would think you did but I figured I ask.

 

[snootalope]

yep, upgraded them to the latest.

 

[achadbourne]

I'll be damned. We are having the exact same problem as you. We upgraded a few months ago from version 4.2 to 6.1 and now our Attendant Console is ahving the exact same symptons. Been working with TAC for over a month and still no resolution on this problem.

Is your TAC still open?

 

[snootalope]

No.. our case has been closed now for a while. They did all the webex sessions they could and determined the console is "just fine" and that was the end of it.

Still having the same exact issues today that we were when I posted this back in March.

 

[achadbourne]

Ah, we have done about 5 webex sessions and finally yesterday an engineer indicated there was a problem with the AC version and the Callmamanger version we are running. Currentl we are using 6.1.1 2000-1, we are upgrading to 3115 Wednesday as this is supposed to fix the problem, since a new AC version was released in 3115. Here is the bug number CSCsq85761 Cisco provided me if you want to investigate further. Also a direct link to the Cisco page,

http://tools.cisco.com/Support/BugT...ls.do?method=fetchBugDetails&bugId=CSCsq85761

Upgrading might fix your problem as well, I will know more Wednesday and post my findings.

 

[achadbourne]

Looks like the 3115 patch fixed our AC problem.

 

[darinz]

Could you let me know if you upgraded to 6.1.1 3115 OR 6.1.2 3115 to correct this issue?

 

[snootalope]

We applied an ES to get to 6.1.1.3117-3, and that fixed our slow AC issue. But now, when our users in the AC use their quick dial list to transfer a call inside the AC, the call hangs for about 4 seconds after they click transfer before it's finally released and transferred. yea, they're dropping call simply because of the lag it takes to release the call.

We've got yet another TAC case open for this issue now.. Plus a case for CDR automatic generation emails going to basic users, and another case for trying to add new phones that weren't here during our upgrade will not register with the CUCM's.

ugh.....wasn't expecting so many issues with the upgrade from 4.1x to 6.x

 

[sweetonphones]

Has cisco given you a resolution yet? If so what was it and how does it work now?

 

[pndscm]

I have a customer with almost 100 AC users on CCM 6.1.2 and are not having any problems at all. I'd upgrade to at least CCM 6.1.2 and see if that fixes your issues.

 

[snootalope]

nope.. no resolution yet. they're wanting sniffer traces from like every possible place on our network. I'm thinking an upgrade might be well worth it.

 

[whykap]

6.1.1 had a lot of bugs as pndscm already mentioned. Upgrade to latest 6.1.2 and reinstall AC.
You can do the upgrade during the day and switch over after hrs.

 

[snootalope]

What about 6.1.3? I see that's available as of the 15th. I'm downloading now....any of you using it?

 

[pndscm]

I haven't tried it yet. I usually let others suffer through any problems before I try new stuff unless I am already having problems.
At least 6.1.3 should have the patch that fixes the 240 day lockup problem that is in a lot of early versions.

 

[iptuser]

re 240 days . We were advised of this issue and did a SHOW STATUS on the CLI which showed the call manager service was up for 280+ days which showed the number being incorrect or it did not effect us. I also checked the CTI manager and that was 40+ days so I`m a bit confused on what the 240 day problem is/ was- We are upgrading to 6.1.3 in the new year though

 

[snootalope]

I'm upgrading to 6.1.3 tonight....I'll report back probably next week if this worked or not.

 

[lx1]

Have you found any fix for the call transfer delay?

 

[snootalope]

Yes, we found a fix. It was not upgrading though.

After doing some more network sniffing, we noticed there were a few ICMP unreachables showing up.. I wasn't really looking for these so never paid attention to them before. I went in and added the servers to the local lmhosts and hosts file.

Delay was gone right away and hasn't came back.. I made this change about two weeks ago now and still working like a champ.

I REALLY hope this helps anyone else having this issue, I messed with this problem for months and months...

 

[vodocrk]

Which servers did you add to the local lmhosts and host files in order to resolve the problem (i.e. what was the source of the ICMP unreachables)?

I'm assuming it was the UCM servers, but were the name entries any different than what you already had entered on your DNS servers?