Bug Errors?

[Deweyhumbolt]

I get a BUG440 like once an hour and twice a day I'll get a BUG6215, BUG4030 or a BUG115. Is this a problem? What can I do to investigate?

Thanks.

 

[bigindian65]

Looks like you are getting a lot of CDR bugs as CDR runs

BUG6215 x
The CDRTTA_ANS was not set up for a CDR record with a CDRTTA_ARR stamp.
The TTA information cannot be printed for this call. Where: x = TOD2SEC
. Procedures DO_TTA_RINGING and
DO_TTA_QUEUEING in module CDR.

Severity: Minor




BUG4030
"An Analog Line Card (NT8D03) supported PBX set (500/2500 type) went
off-hook but the mainpm in the associated Call Register was improper.
The mainpm was not RINGING, ESTABLISHED,
CAMPON, CWAITING, SPECIAL, RAN_WAITING, nor was it CDR. Software will
idle the call."

Severity: Minor




BUG0115
"TERMINAL does not match DN or TN in Call Register. TERMINAL (packed
format), *(CRPTR) Procedure LIN500 / DNKEY / FORCEDISCONNECT /
DISCONNECT"

Severity: Minor

 

[Deweyhumbolt]

So these are all related to call detail recording? It's not like these are going to sneak up on me and down the switch?

 

[bigindian65]

Truthfully, no bug or error should be ignored, never know what ticks away toward a bigger problem or ini. I would guess CDR has mis-info, or too much, too little

fyi- bug, sch, err

at the > without being in a load

>err bugXXX, or err or sch

will give you the info I posted.

if your in a ld hit ! to kick to the > prompt

 

[Deweyhumbolt]

Much appreciated!

 

[Deweyhumbolt]

One of the FAQ's claims you can decipher the TNs causing the problems in my BUG codes by using the CONV cmd in LD 32. It's not working for me. What's the hitch.

Thanks.

 

[bigindian65]

If it is a super loop you can. What is the full error beside the bug code?

 

[Deweyhumbolt]

BUG440: 00CA6D16 00001002 00008018 00002F08 00000000 19 00000001 00000001 00000000 0 2143