CallPilot 150 Event Log

[wip]

Does anyone know how to go about reading the event log parameters given by the new Callpilot voicemail units?

Can this event log be reseted? Here is a sample of what I am seeing:

Daily statistics ..
One Call FOD 0 Two Call FOD 0 FOV 0 FAX Print 0
Incoming AMIS 0 Outgoing AMIS 0 VPorts Busy 0 Fports 0
F980 Sess O F981 Sess 58 F982 Sess 0 F983 Sess 0 F985 Sess 0
F986 Sess 10 F987 Sess 0 F988 Sess 0 F989 Sess 0
Call Ans 113 AA/CCR 7 OPN 12
Ext Trans 0 Ctx Trans 0 Broadcast Msg 0 Group list
SMTP Receive 0 SNTP Send 0 NVM Manager 0 Call Screen 0
Dsktp Logins 0 Dsktp Open Msgs 0 Text Bodies 0


This is the parts I need explained the most??!!
08:04:30 info: OrginateExtCall: mbMakeCall rc=36(0x24)
08:24:00 info: OrginateExtCall: mbMakeCall rc=36(0x24)
09:37:25 FtLog buffer overrun attempted. See Module, Funti
et code below:
09:37:25 Info
F986Start: F986 failed (one caller disconnected?)
09:37:25 rc=40(0x28
09:37:25 info: OriginateExtCall: mbMakeCall rc=36(0x24)
09:39:36 info: OriginateExtCall: mbMakeCall rc=36(0x24)
10:33:06 info: OriginateExtCall: mbMakeCall rc=36(0x24)
13:07:22 info: OriginateExtCall: mbMakeCall rc=36(0x24)
13:27:05 info: OriginateExtCall: mbMakeCall rc=36(0x24)
14:26:49 info: OriginateExtCall: mbMakeCall rc=36(0x24)
16:12:59 CallAns: No mailbox found for DN 5051 rc=1(0x1)
16:16:57 info: OriginateExtCall: mbMakeCall rc=36(0x24)
18:07:33 info: OriginateExtCall: mbMakeCall rc=36(0x24)
18:27:03 info: OriginateExtCall: mbMakeCall rc=36(0x24)


Next day
Daily Statistics ..

I have a receptionist tell me that each day that she has to reprogram the F986 key to a button on her T7316E with two Kims each day? Like it loses programming?

Does anybody know how to read the event log within the call pilot or direct me to a manual on where to start? I do not remember this in training?

WIP
Joey D.
Bgredhskr@aol.com

 

[wip]

MICS 6.1
CP 2.0

 

[senk1s]

does feature 981 stay put on the phone?

 

[wip]

Yes,

What I was able top do,

Add 8 intercom extensions to telephone and also 8 appearances for each DID Line.

It is PRI as well.

I talked to System Admin Person and he said that the programming has kept both days since I have checked.

I woould still like to know if anyone is technical enough to help me read these lines.....

08:04:30 info: OrginateExtCall: mbMakeCall rc=36(0x24)
08:24:00 info: OrginateExtCall: mbMakeCall rc=36(0x24)
09:37:25 FtLog buffer overrun attempted. See Module, Funti
et code below:
09:37:25 Info
F986Start: F986 failed (one caller disconnected?)
09:37:25 rc=40(0x28
09:37:25 info: OriginateExtCall: mbMakeCall rc=36(0x24)
09:39:36 info: OriginateExtCall: mbMakeCall rc=36(0x24)
10:33:06 info: OriginateExtCall: mbMakeCall rc=36(0x24)
13:07:22 info: OriginateExtCall: mbMakeCall rc=36(0x24)
13:27:05 info: OriginateExtCall: mbMakeCall rc=36(0x24)
14:26:49 info: OriginateExtCall: mbMakeCall rc=36(0x24)


Understand the times at which each parameter takes place, yet want to understand a little more.

Joey D
Work in Progress Here.....

 

[achuchman]

wip,

I am taking a stab in the dark here, but it seems that "OriginateExtCall: mbMakeCall rc=36(0x24)" indicates that the CP is trying to make an external call.

This could be wrong (and probably is), but, like I said, it is a stab in the dark.

Now, are you allowing out transferring or outbound notification?

If you are not, or are not intending to, I would check your class of service settings. There may be some fraud going on in your office...

Just my stab in the dark $0.02...