Cannot pickup a call

[taverny]

we have the merlin legend , it's been few times now that after hours when we transfer our call to a messaging system, the call gets stuck into the system. if trying to call our number we get a busy signal , and if we try to pickup the phone call that is stuck , we are unable to pick it up;the only way to solve the problem is to shutdown merlin and restart it. and then everything is fine.
Is there a way to check the log file of the errors happening to the system thru winspm?

Thanks.

 

[TravelingTom]

What kind of lines are you using? You could be getting hacked if you have loop start lines without positive disconnect and you do not have your ARS tables set right, particularly on older Legends. Check Maintenance- system - error logs - transient to see if your pools are busy at these times. Check to make sure your outcalling is programmed correctly.

 

[taverny]

Hi Tom,

We use a PRI. I went to transient, but nothing is showing , same for permanent. I went into "the last 30" and it shows
INVALID SLOT INTERRUPT
SLOT00 PORT00

LAST 04/24/04 07:30
CODE 0010

and actually that was the last time , that the problem occured.
how can I check if the outcalling is done correctly?

 

[taverny]

I just did a printout of the error log , and actually there is more errors:
ERROR LOG


Last 30 System Errors:

Message ss/pp Cnt First Last Code
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 00/00 00:00:00 0010
CARD INSERTED/REMOVED 06/00 - - 04/24 07:30:18 000B
POWER UP COLD START 08/00 - - 04/24 07:30:19 0016
POWER UP COLD START 00/00 - - 04/24 07:30:48 000A
PRI D-CHNL INOPERATIVE 09/00 - - 04/24 07:31:00 7003
PRI D-CHNL INOPERATIVE 09/00 - - 04/24 07:31:09 7003
PRI D-CHNL INOPERATIVE 09/00 - - 04/24 07:31:15 7003
NO I-VMS PORT IN SERV 00/00 - - 04/24 07:32:29 0C01
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010
INVALID SLOT INTERRUPT 00/00 - - 04/24 07:30:18 0010

Permanent Errors:

Message ss/pp Cnt First Last Code

Transient Errors:

Message ss/pp Cnt First Last Code

 

[TravelingTom]

Invalid slot interrupt code 0010 is The Legend cannot determine which module is causing the problem but the action is to troubleshoot the modules and then the processor. This could be from the power down and up that you did to reset the the system. How are you transferring the call out of the system? Forwarding the calls from an extension you must have a # at the end of the dial stream or the call will just sit there.

 

[taverny]

Hi
to transfer the call we do a forwarding, actually the receptionist does the forwarding. It's possible that she forgets to press the # at the end. how could I troubleshoot the module?

 

[TravelingTom]

If the receptionist transfers the call she doesn't need the #. The # disconnects the TTR and tells the CO that the dialing is finished. You can go to mainitenance - slot - busy out - demand test- restore. Otherwise you can replace suspect card if you have spare ones. It seems that you problem is sporadic and maybe by doing the powerdown and restart the problem is gone. Power hits and glitches sometimes create problems when the system does not fully come down and restart.

 

[taverny]

I have tried to troubleshoot the problem and finally called my vendor . we endup switching the ds1 card. it seems to be working properly now .
Thanks for your help.