Bug4108 started appearing on my terminal today. Any ideas?

[MrPederman]

Bug4108 started appearing on my terminal today by the page full. They will spit out constantly for a minute or so, then they stop for a while. I don't have a loop or route 30 so I am not sure what to do.

The definition for bug4108 is "Incoming msg not allowed for this application"

I have a cs1000M with 4.50W, 2 sig servs at 4.50.88, a 4.0 callpilot and a 5.0 SCCS. None of which are putting out any unusual logs.

Thanks in advance!



BUG4108
BUG4108 : 30 59
BUG4108 + 00AE3570 007403F9 0073E3B2 0073E1A5 00771EF5
BUG4108 + 0077145B 0195A5A5 0195A2EB 0195A1EB 01B3CBE1

BUG4108
BUG4108 : 30 59
BUG4108 + 00AE3570 007403F9 0073E3B2 0073E1A5 00771EF5
BUG4108 + 0077145B 0195A5A5 0195A2EB 0195A1EB 01B3CBE1

BUG4108
BUG4108 : 30 59
BUG4108 + 00AE3570 007403F9 0073E3B2 0073E1A5 00771EF5
BUG4108 + 0077145B 0195ABA1 0195A6B8 0195A2EB 0195A1EB
BUG4108 + 0077145B 0195ABA1 0195A6B8 0195A2EB 0195A1EB
BUG4108 + 01B3CBE1

 

[911guru]

I think you are going to have to open a Nortel ticket for this one. The numbers that are relevant are the "30" and "59" as you suspected.

The first is the Application and the Second is probably a specific command or message number. I do not know what Application 30 actually is.
I have seen these before with AML links, etc. but a different application number.

911Guru

http://pbx-e911.com

 

[PERRYPJ]

I would try an INI before I did anything

OLD ROLMEN WORKING ON NORTELS

 

[MrPederman]

I am working with my tech support, but I will probably be escalated to Nortel today. I will keep you all posted.

 

[MrPederman]

Nortel said the BUG4108 was caused by the wrong format of the Agent position ID field being sent from the 3rd party server requesting to acquire an Agent position ID.

Below is the breakdown of the BUG4108, followed by an example of a good and bad AML message.

**************************************************************************************
PBX BUG4108 breakdown from Nortel.
-Symbol File: /proj/SL1C/target/builds/csCPP2-VxWorks/mainos.txts m
Ras Decode for release: x210450w machine type: cpp
RAS ENTERED:
BUG4108
BUG4108 : 30 59 00AE3570 007403F9 0073E3B2 0073E1A5 00771EF5
BUG4108 + 0077145B 0195B5B8 0195A66F 0195A2EB 0195A1EB
BUG4108 + 0077145B 0195B5B8 0195A66F 0195A2EB 0195A1EB
BUG4108 + 01B3CBE1
Date: Mon Feb 18 11:38:50 EST 2008
Address Procedure offset
>=====================================================================================<

00AE3570: BUG_PARMS 0xa8
007403F9: PROC_CSL_I_MSG$INVALID_IP 0x21
0073E3B2: PROC_CSL_I_MSG$CSL_CCR_RCV_MSG 0x18a
0073E1A5: PROC_CSL_I_MSG 0x1f1
00771EF5: CSL_UTILITIES$CSLPROC_INPUT 0x225
0077145B: CSL_UTILITIES 0x9b
0195B5B8: WORKSHED$TIER_SCHEDULE2 0xc3c
0195A66F: WORKSHED$TIER_SCHEDULE1 0x2df
0195A2EB: WORKSHED$TIER_SCHEDULE 0x57
0195A1EB: Ltext0 0x1c3
0077145B: CSL_UTILITIES 0x9b
0195B5B8: WORKSHED$TIER_SCHEDULE2 0xc3c
0195A66F: WORKSHED$TIER_SCHEDULE1 0x2df
0195A2EB: WORKSHED$TIER_SCHEDULE 0x57
0195A1EB: Ltext0 0x1c3
01B3CBE1: sl1Main 0x2a1

In x-view the 30 and 59 seem to refer to CSL_APP_TYPE:CSL_MSGPTR and CSL_MSG_TYPE:CSL_MSGPTR respectively
In turn, the CSL_APP_TYPE:CSL_MSGPTR seems to be .CSL_CCR = 30; % Application Type for CCR
&
CSL_MSG_TYPE:CSL_MSGPTR seems to be .CSL_IACR = 59; % ICCM resource Acquire Request
-
**************************************************************************************

Next a bad and good aml request


**************************************************************************************
Example of Bad Agent ID/Position ID

-------- Output from mlsm.exe Wed Feb 20 08:36:21.984 2008 (36:21.984)
IACR Acquire an AST-POSID
03 2a 00 00 00 00 1e 3b 04 3d 00 00 header (12 bytes)
95 01 06 Subtype (Acquire an AST-POSID)
4a 06 42 4a e1 19 47 a0 Agent Position Id
e6 0c 38 7e 07 44 fe fe 00 00 1f 7b 00 00 Message Filter Bitmap
e7 04 00 00 00 00 Feature Control Bitmap

In this example the Agent ID (119470) is preceded by a code 4a 06 then the extension 42 4a (4240). In the good example the Agent ID is preceded by just 4a 03.
Assumption: Because the switch does not know to interpret the Agent ID it never responds with an IACS message.


*************************************************************************************
Example of Good Agent ID/Position ID in AML message.

-------- Output from mlsm.exe Wed Feb 27 10:30:05.437 2008 (30:05.437)
IACR Acquire an AST-POSID
03 27 00 00 00 00 1e 3b 45 ac 00 00 header (12 bytes)
95 01 06 Subtype (Acquire an AST-POSID)
4a 03 11 97 81 Agent Position Id
e6 0c 38 7e 07 44 fe fe 00 00 1f 7b 00 00 Message Filter Bitmap
e7 04 00 00 00 00 Feature Control Bitmap

In this good example the Agent ID (119781) is preceded by 4a 03 (which we see in all good messages).
Because the Switch knows how to interpret the message it responds with the IACS message below.

============================================================================
-------- Input Wed Feb 27 10:30:05.453 2008 (30:05.453)
IACS Acquire an AST-POSID
03 2a 00 00 00 00 1e 3c 45 ac 00 00 header (12 bytes)
95 01 06 Subtype (Acquire an AST-POSID)
4a 03 11 97 81 Agent Position Id
e6 0c 38 7e 07 44 fe fe 00 00 1f 7b 00 00 Message Filter Bitmap
e7 04 00 00 00 00 Feature Control Bitmap
aa 01 2c Status (Invalid AST-DN or POS-ID)