Attendant Console logon/logoff info?

[vocollect]

I was wondering if there is any way to find the logon/logoff information on the attendant console. Something to the effect that you can get from IPCC Express on the log in/log out of agents.

I'm getting complaints that calls that should be answered by the attendant console are being dropped directly into voice mail.... which leads me to believe that either the attendant console is not working or that the receptionist is not logging in or not aware that she's loged out.

Thanks

Debbie Olah

Telecommunciations Administrator

[MICHAEL BASTINCK]

I was planning to ask the same question so if somebody knows the answer ?

[brian-henry]

The only way that I know is to use the NT Performance monitor to see when an Attendant is logged in or not.

You could most likely create an SNMP threshold that says if it is less than 1 then send an SNMP trap.

That is the only thing that I can think of right off hand.

I am sure the RTMT The Real Time Monitoring Tool will give you the same info but I am not sure if it will alert you, you will just have to keep an eye on it.

[jricomunoz]

Hi,

the attendant console has a folder named "logs". In this folder you have the files "ac.out.log" or ac_j.out.log" . Maybe this files can help you to see the login time .

Greats

José Rico

[vocollect]

I looked in the acclient.txt in the \\receptionist\c$\Program Files\Cisco\Call Manager Attendant Console\logs folder.

Does this look like the Attendant console went offline at 8:54 am and then back online at 8:56? Can you tell if this was on purpose or if the Attendant console is losing it's online status and recovering on its own? My receptionist swears that she didn't go offline.

Here is a portion of what I found...

numEntries: 1, pktLength: 28

1277 02/03 08:49:18.622 DEBUG Processing queued packet. numEntries: 1

1278 02/03 08:49:18.622 DEBUG DN: 2427 Status: Idle

1279 02/03 08:52:01.577 DEBUG Packet queued. Received from: 10.0.8.22, numEntries: 1, pktLength: 28

1280 02/03 08:52:01.655 DEBUG Processing queued packet. numEntries: 1

1281 02/03 08:52:01.655 DEBUG DN: 2490 Status: Ringing

1282 02/03 08:52:03.331 DEBUG Packet queued. Received from: 10.0.8.22, numEntries: 1, pktLength: 28

1283 02/03 08:52:03.660 DEBUG Processing queued packet. numEntries: 1

1284 02/03 08:52:03.660 DEBUG DN: 2490 Status: Idle

1285 02/03 08:54:37.184 DEBUG ACMainFrame.invoke: Invoked command

1286 02/03 08:54:37.184 DEBUG Command ID: COMMAND_FILE_OFFLINE

1287 02/03 08:54:37.184 INFO Going offline

1288 02/03 08:54:37.184 INFO ACClientCommunication offline

1289 02/03 08:55:46.483 DEBUG ACClientCallObserver.callChangedEvent(): DontCareEv(101) for call[(P1-ac) GCID=(2,74988)->ACTIVE].

1290 02/03 08:55:46.483 DEBUG ACClientCallObserver.callChangedEvent():

1383 02/03 08:56:55.610 DEBUG Processing queued packet. numEntries: 1

1384 02/03 08:56:55.610 DEBUG DN: 2490 Status: Active

1385 02/03 08:56:55.688 DEBUG Packet queued. Received from: 10.0.8.22, numEntries: 1, pktLength: 28

1386 02/03 08:56:56.111 DEBUG Processing queued packet. numEntries: 1

1387 02/03 08:56:56.111 DEBUG DN: 2490 Status: Active

1388 02/03 08:56:59.505 DEBUG ACMainFrame.invoke: Invoked command

1389 02/03 08:56:59.505 DEBUG Command ID: COMMAND_FILE_ONLINE

1390 02/03 08:56:59.505 INFO Going online

1391 02/03 08:56:59.505 INFO ACClientCommunication online

Debbie

[vocollect]

PS: Why are these log files accumulating? These files seem to exist for the last year... Is there a setting somewhere to reduce that to 2 months or so?

[vocollect]

I could really use some insight on the log information given above.

Is there any way to tell if when the attendant console went off line at 8:54:37 did it lose it's connection or was there a button push from the client software that told it to go off line?

[jerake]

Yep, it looks like the AC did go offline, although the logs will never say if it was a button push or a connection issue.

Been going through a simlilar situation, except one of my attendants is losing their Call Control randomly. The logs are only telling me that Call Control went down, but not why...frustrating beyond belief.

TMH