BUG015 Message on Option 51C

[PeteI]

We relocated a console for our customer on Friday June 13th. This was a backup console for busy times of day. All seemed fine, console worked well. Monday June 16th we were called in because several extensions were inoperable.
The terminal was posting BUG 015 0 0 2 11. This was the TN for the second console. We realized that we miswired the pair on the bl/or bl/gr pairs.(power?). We removed the console altogether and disabled it in ld 32. We also disabled and enabled several extensions that were effected by this problem. Now we get a bug message "BUG015 0 0 4 7
This is the TN for the console that they use as a primary and has never been touched. Still seems like extensions are just locking up ramdomly and don't know what to do. Tried DISL 0 0 and ENLL 0 after hours last night, but didn't work. Any ideas? "Holy Can of Worms"

 

[cmawbey]

It may not be related. but here in the UK these messages are often associated with DASS trunk routes. a service update pack may be needed on the Meridian.

Colin

 

[NTOldTimer]

It is possible that the work you did should not have caused the problem you are experiencing. There are some patches that may resolve the problem but first try running a LD 1 audit. If that doesn't resolve the problem then call your vendor.