Is there a trace or log file for Attendant Console service in CCM
5.1(1) one can look at to determine why it stopped working correctly?

I had a place where the calls to the AC users stopped working and the
users were logged in and online. A restart of the AC service on all
the call managers corrected the problem. The syslog logs in RTMT did
not show anything in them and reviewing the CCM traces didn't really
show what was wrong.

Also, why did they stop listing the resolved bugs in the release
notes? I pulled up the 5.1(2) release notes to hopefully see a list of
what all was fixed and the resolved section said to use bug toolkit.
Various searches in bug toolkit revealed some possible matches but not
one that really hit on what we experienced. I really wish they go back
to listing all the bugs resolved in the release notes as the bug
toolkit doesn't show a list of all bugs fixed and not the internal
ones either, etc.

[ Post a follow-up to this message ]

Yep, "Cisco CallManager Attendant Console Server".

Mike

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Erick Bergquist
Sent: Tuesday, July 24, 2007 9:27 AM
To: ciscovoip
Subject: [cisco-voip] Attendant Console log/trace in CCM 5.1(1)

Is there a trace or log file for Attendant Console service in CCM
5.1(1) one can look at to determine why it stopped working correctly?

I had a place where the calls to the AC users stopped working and the
users were logged in and online. A restart of the AC service on all the
call managers corrected the problem. The syslog logs in RTMT did not
show anything in them and reviewing the CCM traces didn't really show
what was wrong.

Also, why did they stop listing the resolved bugs in the release notes?
I pulled up the 5.1(2) release notes to hopefully see a list of what all
was fixed and the resolved section said to use bug toolkit.
Various searches in bug toolkit revealed some possible matches but not
one that really hit on what we experienced. I really wish they go back
to listing all the bugs resolved in the release notes as the bug toolkit
doesn't show a list of all bugs fixed and not the internal ones either,
etc.
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

OT a little. But CM 5.1.2 has some kind of SNMP bug that is causing
Berbee Informacast issues.  Berbee currently has a TAC case open.

Scott

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Erick Bergquist
Sent: Tuesday, July 24, 2007 7:27 AM
To: ciscovoip
Subject: [cisco-voip] Attendant Console log/trace in CCM 5.1(1)

Is there a trace or log file for Attendant Console service in CCM
5.1(1) one can look at to determine why it stopped working correctly?

I had a place where the calls to the AC users stopped working and the
users were logged in and online. A restart of the AC service on all
the call managers corrected the problem. The syslog logs in RTMT did
not show anything in them and reviewing the CCM traces didn't really
show what was wrong.

Also, why did they stop listing the resolved bugs in the release
notes? I pulled up the 5.1(2) release notes to hopefully see a list of
what all was fixed and the resolved section said to use bug toolkit.
Various searches in bug toolkit revealed some possible matches but not
one that really hit on what we experienced. I really wish they go back
to listing all the bugs resolved in the release notes as the bug
toolkit doesn't show a list of all bugs fixed and not the internal
ones either, etc.
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]