B5800: System will randomly reboot Fatal TLB error with Auto-Attendant.

Doc ID    SOLN233462
Version:    2.0
Status:    Published
Published date:    04 Mar 2014
Created Date:    22 Jul 2013
Author:   
Michel Rodrigues dos Santos
 

Details

Issue: ALARM IP 500 V2 6.2(38) CRIT RAISED

5743118mS PRN: +++ START OF ALARM LOG DUMP +++
5743118mS PRN: ALARM: 28/06/2013 09:55:28 IP 500 V2 6.2(38) CRIT RAISED addr=000004d4 d=5 pc=f0e403c0 f512e4ac f0e46f98 f0e48428 f0e4c410 f0460f20
5743118mS PRN: +++ END OF ALARM LOG DUMP +++

B5800 release 6.2.38 mode distributed.

Problem Clarification

B5800: System will randomly reboot Fatal TLB error

Cause

Scenery to reproduce the issue.

1- Trunk R2 MFC or ISDN.
2- Auto-Attendant with option to hunt-group.
3- Hunt-group and users making login and logout extension.

How reproduce the issue.

1- All users configured on hunt group needs make logout extension.
2- Start Incoming call by trunk with call setup to Auto-Attendant.
3- After hear the Menu Option press the option to the hunt-group without extension registered (status extensions = logoff).
4- After 2 seconds the B5800 start the reboot action with alarm " 5743118mS PRN: ALARM: 28/06/2013 09:55:28 IP 500 V2 6.2(38) CRIT RAISED addr=000004d4 d=5 pc=f0e403c0 f512e4ac f0e46f98 f0e48428 f0e4c410 f0460f20".

On logs you can see the next information:

09mS H323Evt:Recv: RegistrationRequest 10.104.193.197; Endpoints registered: 8; Endpoints in registration: 0>>> User status logoff!
13mS H323Evt:Recv: RegistrationRequest 10.104.193.202; Endpoints registered: 8; Endpoints in registration: 0>>> User status logoff!
37mS CMTARGET:0.1446.0RAS.1:TimerExpired cause=CMTCNoAnswerTimeout
38mS CMTARGET:0.1446.0RAS.1:Retarget NOANSWER EXCEPTED=00000000 ValidTargets=0
38mS CMTARGET:0.1446.0RAS.1:RetargetNoAnswer on HUNTGROUP=Atende Opt5. Ring Attempt 1
38mS CMTARGET:0.1446.0RAS.1:AddHGTarget Atende Opt5 (depth=1) allowq=0 type=CMNTypeDefault
38mS CMTARGET:0.1446.0RAS.1:AddHGTargetRingRotary(Rotary) Atende Opt5 ring_attempt_count 1 index 6
38mS PRN:Begin Stack Trace
38mS PRN:pc=f0e5197c
38mS PRN:lr=f0e5196c
38mS PRN:findfunc 00000000 f0e58554 f0e599e4 f0e5e7dc f04670f4 f04674a0 f0466230 f02ed4cc f03793fc f02e7584
38mS PRN:findfunc f02e7530 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
38mS PRN:End Stack Trace
38mS PRN:ScheduleHistory NOT enabled:Task =CM File=../platform/platform.cpp Line=1195
38mS PRN:.FATAL DSI Excep address=000004d4 d=5 pc=f0e5197c 00000000 f0e58554 f0e599e4 f0e5e7dc f04670f4 IP500V2 6.2(54)

Solution

B5800 with release 6.2.54, it has a new patch 6.2.542701 - issue fixed.(In case of the B5800 has the version below that the rel.6.2.54, customer or partner need upgrade to 6.2.54+Patch2701 or waiting the next Service Pack up 6.2.54).

Patch Notes:
Core Critical Patch to resolve:
IPOFFICE-49242 - Reboot on B5800 on call to a group
Other fixes requested/incorporated for which there isn't currently a JIRA:n/a
CP type: Fix attempt
Base version CP based on: 6.2.54
CP version provided: 6.2.542701
CP Issuer:Radu Cristina
Date Issued: 12/July/2013
CP Installation Instructions:n/a
Other Instructions:n/a
Diagnostic Prints Added:n/a
SysMonitor Options to Be Enabled:n/a
Things to Test/Check:n/a


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy