Bug 6071

[gforce9]

A customer has a MIRAN (MC-8) they were using for music (on hold, Symposium,...; TN 9-6 RTMB 10-1). They bought an external music source (like MUZAK)from another vendor and I built a trunk on an XUT, outted trunk 9 6 (MIRAN), rebuilt new trk 6 2 (XUT) as same RTMB. The music works, but I am getting repeating BUG 6071's (presumably, everytime the trunk is accessed). I looked in Symposium and the scripts point to route 10. Any ideas why the BUG's?

 

[bigindian65]

seems like it would be some pointing to an empty ran and getting re-order tone. Old stuff gone and not referenced?

Mato' Was'aka

 

[gforce9]

I just don't know if the pointer issue is somewhere in Symposium I haven't found, in the queue, or somewhere else. The good news is callers are hearing the new music......just with BUG codes.........

 

[bigindian65]

No clues after bug? No x y type info?

Mato' Was'aka

 

[gforce9]

Sorry....
Bug6071 Invalid CR pointer 0x607. CR range is (0x319896, 0x345d13)

 

[Triton101]

Post the route and Trunk so we can see programming.

 

[gforce9]

REQ: PRT

TYPE: RDB

CUST 0

ROUT 10


TYPE RDB
CUST 00
DMOD
ROUT 10
DES MUSIC
TKTP MUS
NPID_TBL_NUM 0
VTRK NO
NODE
ICOG OGT
SRCH LIN
STEP
BDCT NO
ACOD 8010
TARG
CLEN 1
OABS
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
SST 5 0
NEDC ETH
FEDC ETH
HOLD 02 02 40
SEIZ 02 02
RGFL 02 02
CDR NO
MUS NO
TTBL 0
OHTD NO
ALRM NO
SGRP 0
ARDN NO
AACR NO

REQ: ****
OVL000
>LD 20


PT0000
REQ: PRT

TYPE: MUS

TN 6 2

DATE

PAGE


DES MUS
TN 006 0 00 02
TYPE MUS
CUST 0
XTRK EXUT
TIMP 600
BIMP 600
AUTO_BIMP NO
RTMB 10 1
CFLP 29
DATE 16 APR 2008

 

[KZ9Y]

Watching this thread. I have a 61c with BUG 6071 0x100 CR range 0x365b411, 0x36e5bfa. Vendor opened a ticket w/ Nortel - no fix yet.

jva

>****

 

[gforce9]

The wierd thing is that the only thing I changed was to out TN 9-6 (MIRAN) and rebuild TN 6-2 as music trunk (XUT).

 

[Triton101]

Do a test, by accessing the MUSIC trunk via ACCESS code. Then hang up, see if you get the same thing (BUG message).

If not, then it might be something to do with Symposium possibly.

 

[johnpoole]

Pointer to Call Register is not on a valid range... i could see that, i would make a single change in the params, maybe bump a buffer number up, then do an ini.. the change will force the params to reload, that should clear the new/old call register problem..

most of the time a nortel eng will request that change and ini prior to looking for a problem.. that file is only reload on ini IF the check sum does not match

john poole
bellsouth business
columbia,sc

 

[phonz1]

Has all programming on the Miran card been removed?? Have ALL routes with music on them been changed to the new??

 

[Triton101]

The person is RE-USING the existing route, he just removed the trunk from the MIRAN and added a XUT trunk from a regular trunk card.

 

[gforce9]

OK....I finally got back to this place. An INI cleared it (bogus pointer as JP suggested?). I'm not generally the 'rebooting' type, but it worked.....Thanks, fellas!