John_In_Dakota

Well this is what the TTY is telling me on the ERR PRI217:

PRI0217
Protocol Error: General location not supported. Output data: DCH: x
DATA: y . Where: x = D-channel number and y = General location number.
Action: Contact your technical support group if the problem persists.
Severity: Critical

__________________
Thankful for everything...at least today.

slagburn

The upper portion of that is the DCH protocol error log, can also be seen by issuing the command PLOG DCH x in LD 96. This log automatically dumps to MTC terminals when any value hits 255.

Oddly the answers to what all of that means can be found in the NTP for LD96.

10 = Count of CRC error frames.
15 = Count of messagaes missing mandatory information elements.
16 = Count of messages with undefined information elements.
18 = Count of aborted frames.

The PRI217 is probably a result of items 15 and 16.

To me it looks like there is some type of programming mismatch between your system and the far end where the far end is sending DCH messages that your system doesn't know what to do with; on rare occasions when nobody has changed nuthin sometimes the MSDL (or TMDI) will get whacky and require a reset / donwload.

Depending on how often these come you may not have to worry too much about it. I have a few systems on older releases of software that will do an auto plog about once a week or so because they don't understand every DCH message that comes from our SL100 / 5E.

darby

Sorry, didn't have the NTP with me when I posted. Thanks for the help!