Cinphony giving errors in Test Log and causing MICS to reboot

[newtel1]

MICS 6.1 XC with Cinphony 3.6 giving 995 codes in test log, have checked that code is created when entering ACD whether through Voice Mail or straight into ACD. Everyday phone system is rebooting due to volume of codes. Any ideas why the ACD is causing issue.

 

[gforce9]

Evt 995 isn't in the code book I have, but I know I've seen a bunch of 995's on Norstars w/o ACD. That is going to be interesting problem to figure out. Is it a co-resident NAM (mail + ACD) or a separate NAM for each?

 

[newtel1]

It is 2 seperate Application Modules and here is what 995 is tells you nothing.


995: G_LOSS_PLAN_ERROR
Cause:
The Global Loss Plan Engine encountered an error.
First Parameter=Loss Plan Error code. Remaining
parameters are dependant on the error code.
Enviroment:
This can occur in any product which supports market
profiles.
Human Action:
The customer should report the problem, including all
of the information that accompanied the event in the
log. Designers should see unit glb_lss_defs for inter-
pretation of the error codes and other parameters.

 

[curlycord]

PRI? change the clocking card to see if helps.


=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[newtel1]

No not PRI just CLID

 

[chiden]

I don't know if this helps at all. Don't remember if we were getting code errors. We had situation where set relocation was set to ON. This caused us all kind of problems when system reset. ACD would sometimes take DN of NAM. We turned relocation OFF and haven't had problem.

 

[newtel1]

No set relocation is off the system resets because of the number of errors that the MICS is getting from the ACD

 

[curlycord]

Maybe HD failure


=----(((((((((()----=
curlycord

http://www.curlycord.com