Tracking System Resets.

[jontout]

Hi Folks.
Over the past few months we're getting a reset somewhere in our telephone system that I'm finding almost impossible to track down.
We have an IP406 that at random times, at least once a day - but not every day, appears to reset itself. This manifests as active phone calls dropping out and any phones that are logged in being logged out as they're reset. Other than that there appears to be no traceability that the system has been reset.

We're using IP Office V5.0 (580), Delta Server 5.0.31,
VoiceMail Pro V2.1(25).

Has anyone else had a similar problem?

Here's a brief sample from the System Monitor log.

0161793c 016184e0 0163f5dc 016050c8
3009mS PRN: ALARM: 25/03/2008 11:21:43 IP 406 2.1(77) <TLB Data Error> CRIT RAISED addr=0000009c d=5 pc=01625d38 01625d18 0161793c 016184e0 0163f5dc 016050c8
3010mS PRN: ALARM: 25/03/2008 12:22:42 IP 406 2.1(77) <TLB Data Error> CRIT RAISED addr=0000009c d=5 pc=01625d38 01625d18 0161793c 016184e0 0163f5dc 016050c8
3010mS PRN: ALARM: 28/03/2008 15:57:50 IP 406 2.1(77) <TLB Data Error> CRIT RAISED addr=0000009c d=5 pc=01625d38 01625d18 0161793c 016184e0 0163f5dc 016050c8
3010mS PRN: ALARM: 28/03/2008 16:26:30 IP 406 2.1(77) <TLB Data Error> CRIT RAISED addr=0000009c d=5 pc=01625d38 01625d18 0161793c 016184e0 0163f5dc 016050c8


Cheers,

Jon

 

[tlpeter]

The alarm code is always the same
Get your business partner involved
Let them send the trace with the config to avaya


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[gknight1]

it appears you are running different versions of IPO and VMPro, that would be a place to start.

 

[Escorthosis]

You are already using the manager from 3.0.580DT and the IP406 is still on 2.1.77?


Upgrade your IP and all it's expansion modules to 3.0.580 and your VMPro server to the 2.1.26 (latest version of 2.1 that still goes with 3.0DT software).

In the meantime I would read my config in a 4.1. manager to see if there are any errors detected.
Then amend them using your normal 3.0.580DT manager program.

 

[jontout]

We've had our engineers making software upgrades & mods to various config files, but nobody seems to be any closer as to why the system resets. We're going to have to start looking at the hardware...

Thanks for the advice, I think Avaya will need to be the next people we contact.

 

[jontout]

Here's an update for those interested parties...

It seems that the system monitor may have been kicking out some 'spurious' messages. We may have had a fault with a previous piece of hardware causing actual resets but later line drops didn't manifest in a similar way.
On further inspection of the log files I managed to track down a scenario that calls coming into our call centre, hitting a certain hunt-group were prone to cutting off and dropping the lines of each user in the particular hunt group. Turns out that we didn't have an overflow message in VoiceMail which would (appear to) drop the calls.
I've recorded a messages for each hunt group and after a sanity check in the call center where we flooded the lines, no calls dropped and haven't for over a week.
I'm not 100% sure as to why VoiceMail would have caused these issues - and therefore if we've even fixed them - but the solution applied seems to have had some affect, so I'm happy.

Cheers,

Jon

 

[tlpeter]

Now delete those alarms

Open monitor -> status -> alarms
Click on clear alarm log and you'r done


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!