MSDL 0304 error and err 5131

[CommoGuy101]

Hello all,
I have been getting a few errors that are continually occurring.
If anyone can show me how to decipher what extension may be causing this, that would be great.

BUG5131
BUG5131 : 00000000 073CFD6D 00000000 00000000 00000000 00000000 12 07345023 073
3B3C0 00000000 0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000002 073BB6B5 00000900 00000018 00004744 00000000 0 00000000 00000000 00000
000 0 000020A5 00007724 00000008 00000000 00000000 00000000 00000000
BUG5131 + 00B53976 014A7AF2 014A54C8 013A1EFF 01393197
BUG5131 + 0138FEC2 0138C641 0138C3E7 0138C35B 01377D31
BUG5131 + 01377C69 01377BCF 01370B43 01370976 0136E058
BUG5131 + 0136C873 0136C15D 0124180E 0124B6D1 0124B61D
BUG5131 + 012492B0 0124028B 00BE1845 00BDE2CD 00BDDEB0
BUG5131 + 01CCF772 01CC8AB6 011AF40A

I am getting a MSDL0304 error as well(which I believe is a looping error)
Just not sure how I can determine what extension is making this occur.

MSDL0304 GROUP 0 MSDL 14 (1) 1976

MSDL0304 GROUP 0 MSDL 14 (1) 1990

MSDL0304 GROUP 0 MSDL 14 (1) 1999

MSDL0304 GROUP 0 MSDL 14 (1) 1944

MSDL0304 GROUP 0 MSDL 14 (1) 1999

MSDL0304 GROUP 0 MSDL 14 (1) 1996

Any help would be greatly appreciated.

Thank you,
CommoGuy101

 

[Firebird Scrambler]

I have located this error report below.

Details:
Msdl0304 messages seen on tty and the threshold counter for the respective d channel printing periodically.

The level 2 monitor facility for the d channel in question, showed streams of signalling information relating to update message waiting indication facility rejection messages. These messages related to existing Call Pilot mailboxes that no longer had a real extension configured for the lamp update to be received.

The same facility rejection messages for the same dns were repeatedly sent over and over again forcing the msdl to reset and in several instances cause the switch to initialise with berr0704's relating to the overloaded msdl device.

Fix:
Remove the mailboxes within Call Pilot for the extension numbers that no longer exist on the customers network.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[CommoGuy101]

Firebirdscrambler,
How do I determine what mailbox is sending the MWI causing the error?


CommoGuy101

 

[bhassell2000]

you should see a list of extensions in your PBX history file that Call Pilot is trying to light the lamps on but extensions dont exist

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[CommoGuy101]

Buddy,
I went to LD 22 and PRT AHST
I don't see any list of extensions causing errors that I can tell.
There are a few BUG 5131 .....MSDL 0304...
Not too sure how to decipher that to an extension:


% BUG5131 : 00000000 073CFD6D 00000000 00000000 00000000 00000000 12 073C9FCB 074
% BB6A5 00000000 0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
% 00000002 074B3B21 00000900 00008318 00004760 0000999D 0 00000000 00000000 00000
% 000 0 29165 000020A5 00008864 00000009 00000000 00000000 00000000 00000000
% BUG5131 + 00B53976 014A7AF2 014A54C8 013A1EFF 01393197
% BUG5131 + 0138CB39 0138C987 0138C8DF 01384EA6 01377C74
% BUG5131 + 01377BCF 01370B43 01370976 0136E058 0136C873
% BUG5131 + 0136C15D 0124180E 01241516 0124106A 01240D1E
% BUG5131 + 01240A13 0124019E 01CCF710 01CC8AB6 011AF40A


MSDL0304 GROUP 0 MSDL 14 (1) 1997

If this is not the info I need, what am I looking for in the history?


Thank you much,

CommoGuy101

 

[Firebird Scrambler]

BUG 5131 is defined as

Cannot initiate TRO call at originating node.

Severity: Minor

From looking at the BUG 5131 HEX output, it shows data of

Call Register: 00000002
Main PM: UNDEFINED
AUX PM:
Orig Type: NONE
Term Type: XTD_UNIT
Orig TN: Use LD 32 to Convert TN H.8318
Term TN: Use LD 32 to Convert TN H.4760
Queue: UNKNOWN
CR Fwd Link:
CR Bak Link:
Aux CR:
CR Dialed:
Digit Load: H. (DEC: 0)
Digit Unload: H. (DEC: 0)
Digits Dialed:

I have dug out Mark's old Exterminator tool which I didn't realise I still had and installed it. I read the help document and selected HEX data "00000002 074B3B21 00000900 00008318 00004760 0000999D" from the error output.

I might not have selected the correct data string, but you might want to see if the TN's found are correct on your system when using the TN converter in LD 32.

I have just used the Microsoft calculator and it has come back with

H.8318 = Decimal 33560
H.4760 = Decimal 18272

By playing around with the HEX and Exterminator tool, I was able to see different results.

Call Register: 074B3B21
Main PM: HALFDISC
AUX PM: IDLE
Orig Type: TRK_UNIT
Term Type: TRK_UNIT
Orig TN: Use LD 32 to Convert TN H.4760
Term TN: Use LD 32 to Convert TN H.999D
Queue: UNKNOWN
CR Fwd Link:
CR Bak Link:
Aux CR:
CR Dialed:
Digit Load: H. (DEC: 0)
Digit Unload: H. (DEC: 0)
Digits Dialed:

Call Register: 00000900
Main PM: UNDEFINED
AUX PM:
Orig Type: TDET_UNIT
Term Type: PWR_UNIT
Orig TN: Use LD 32 to Convert TN H.999D
Term TN: Use LD 32 to Convert TN H.
Queue: UNKNOWN
CR Fwd Link:
CR Bak Link:
Aux CR:
CR Dialed:
Digit Load: H. (DEC: 0)
Digit Unload: H. (DEC: 0)
Digits Dialed:

It might be that this tool isn't supported for the later software releases anymore.
I have added the tool in case you want to try it out.




Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin