IP Office 500: PRN: .FATAL DSI Excep

[nzschooltech]

Good morning,

The above is a log entry from an IP Office 500 that immediately precedes what appears to be a "crash" instance in the IP Office phone system server. I have system email alerts turned on, and it is reported as a "power failure".

These events happen several times a week but sometimes several times a day or hour even. Below is one such sequence from the log.

This looks to me suspiciously like a system crash. However our supplier (business partner) denies that, claiming it is a phone reboot. They have no explanations or answers for this problem.

Does anyone reading this forum know what is happening and can offer us any advice, especially references to official documents that we can pass to our supplier.

68606693mS PRN: Alarm log cyclic wrap
68606693mS PRN: Begin Stack Trace
68606693mS PRN: pc=f01d0988
68606693mS PRN: lr=f01d0948
68606693mS PRN: findfunc f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c f01d1628 f01d16b4 f01cc0c8 f01cc08c 00000000
68606693mS PRN: End Stack Trace
68606693mS PRN: ScheduleHistory NOT enabled: Task = OSTrigger File = ../platform/platform.cpp Line = 910
68606693mS PRN: .FATAL DSI Excep address=029eb325 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c IP 500 5.0(8)

********** contact lost with 172.17.0.50 at 10:48:38 20/10/2009 - reselect = 18 **********
******************************************************************

********** SysMonitor v7.0 (8) **********

********** contact made with 172.17.0.50 at 10:49:15 20/10/2009 **********

********** System (172.17.0.50) has been up and running for 28secs(28996mS) **********

********** Warning: TEXT File Logging selected **********


********** Warning: TEXT Logging to File STARTED on 20/10/2009 10:49:15 **********

Here is another piece from the log file, which always gets dumped a short time after each crash:

31997mS PRN: +++ START OF ALARM LOG DUMP +++
31997mS PRN: ALARM: 12/10/2009 15:24:09 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=02a045e9 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31997mS PRN: ALARM: 12/10/2009 15:30:33 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=02a045e9 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31997mS PRN: ALARM: 12/10/2009 15:52:05 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=02a045e9 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31997mS PRN: ALARM: 14/10/2009 14:11:11 IP 500 5.0(8) <TLB Data > CRIT RAISED addr=6b047ee9 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31997mS PRN: ALARM: 15/10/2009 07:15:57 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=029f6c89 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31998mS PRN: ALARM: 15/10/2009 07:19:20 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=029f53bd d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31998mS PRN: ALARM: 15/10/2009 12:04:01 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=029f53bd d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31998mS PRN: ALARM: 20/10/2009 10:49:34 IP 500 5.0(8) <DSI Excep> CRIT RAISED addr=029eb325 d=5 pc=f01d0988 f01d093c f01d0af4 f00bd9dc f00b7c00 f01d136c
31998mS PRN: +++ END OF ALARM LOG DUMP +++

 

[CarGoSki]

The short answer is probable corruption but only Avaya will be able to tell you.

submitted for your approval >

http://tek-tips.com/viewthread.cfm?qid=1368289

 

[CarGoSki]

BTW IPO only saves 8 alarms. You may want to clear them at some point.

 

[intrigrant]

Do you have a alaw system then maybe the smartcard is the problem.
Avaya has a takeback action on a number of these cards which cause spontanous resets of the ip office.

 

[nzschooltech]

Thanks very much for the quick responses, I will try to tell you more about the system (I am a computer tech, I know this system is basically a sort of computer but its internal workings are largely mysterious to me, it's all a new learning curve)

intrigrant, how would I know if it's an A-law system? A-law is one of the VCM codecs is it? The VCM installed is VCM32/BRI4. IP phone extensions are allowed to use the "G.711 ALAW 64K" compression codec in addition to other options like "G.711 ULAW 64K"

CarGoSki, thanks, defaulting the config is something the supplier is vehemently opposed to, they appear to have lack of experience of these scenarios?

 

[CarGoSki]

Manager: Configuration Settings > System > Telephony > Companding LAW

 

[nzschooltech]

Switch set to ALAW
Line set to ALAW Line

What is a smartcard?
Where would I find any info from Avaya on a smartcard takeback?

Thanks a lot.

 

[intrigrant]

Sorry for the late response but it was time to go to sleep overhere.
In the Manager open the system settings and there is a serial dongle number that reads something like 5130445.
The locale of the system determines wether it is a A/LAW or a U/LAW system, you can check on the System > Telephony tab, it is the companding law.
The affected A-LAW cards have a 7-digit feature key number starting with 516xxxx or 517xxxx.
If you have such a card then immediate contact your vendor for help.

 

[nzschooltech]

Unfortunately not, it's a 513xxxx.

Thanks anyway.