TRK106 on WATS trunks

[PEMpal]

Opt 61C, Rel 25.15.
I have four WATS trunks (remember them?!)
For the past two weeks, every night around 2200-2300, I get a handful of TRK106 messages on the four WATS TN's. At first I thought it might be an errant fax machine or modem trying to re-dial. I unplugged one of the suspect fax machines two nights ago to see if messages stopped. They didn't. Last night I set up a Trace (LD 80) on the first two WATs TNs, hoping I would get info on the ORIG TN. Here's what I got:
>logo
TTY #06 LOGGED OUT JRC 08:25 23/8/2005
SESSION DURATION: 00:03

>
logi jrc
PASS?
TTY #06 LOGGED IN JRC 22:06 24/8/2005
>ld 80
TRA000
.entc 16 0 6 2 0200
.entc 4 0 0 3 0200
gotr
.22:09:14 24/08/2005
IDLE TN 016 0 06 02
.22:09:14 24/08/2005
IDLE TN 004 0 00 03
.
AUD000
DTC001
22:25:14 24/08/2005
ACTIVE TN 004 0 00 03
ORIG 004 0 00 03 WATS RMBR 2 2
TERM NONE
DIAL DN NONE
MAIN_PM READY
TALKSLOT NONE
EES_DATA:
NONE
QUEU 2S
CALL ID 0 1940

.22:25:26 24/08/2005
ACTIVE TN 004 0 00 03
ORIG 004 0 00 03 WATS RMBR 2 2
TERM NONE
DIAL DN NONE
MAIN_PM HALFDISC
TALKSLOT NONE
EES_DATA:
NONE
QUEU NONE
CALL ID 0 1940

.22:26:00 24/08/2005
TIM101 22:26 24/8/2005 CPU 1

LOCKOUT TN 004 0 00 03


.
TRK106 4 0 0 3

TRK106 4 0 1 3

Unfortunately, this didn't help me. Can anyone there see anything in this capture that gives a clue? ANy other ways I can investigate? I'm going to set up another trace tonight on all four TN's. It's interesting that all four TN's work fine all day long, handling lots of traffic. It's just SOMETHING at night between 2200 and 2300.

 

[PERRYPJ]

ARE YOUR WATS TRKS LOOP START

OLD ROLMEN WORKING ON NORTELS

 

[PEMpal]

Ground start

TN 004 0 00 03
TYPE WAT
CDEN 8D
CUST 0
XTRK XUT
TIMP 600
BIMP 3COM
TRK ANLG
NCOS 0
RTMB 2 2
NITE
SIGL GRD
SUPN NO
AST NO
IAPG 0
CLS UNR DTN CND WTA LPR APN THFD
P10 NTC
TKID
DATE NO DATE

 

[PERRYPJ]

SET SUPY TO YES

OLD ROLMEN WORKING ON NORTELS

 

[johnpoole]

supn to yes, can help.. in the rdb set ndec and fdec to eth

john poole
bellsouth business
columbia,sc

 

[mluckie1]

Do you have a console? Where is it programmed to go to in the Nit_data block? Looks like an inbound call, the ORIG is the wats line. It appears as if the call doesn't know where to go. After awhile times out and then the TRK error is generated. Could also change auto to yes and send the call to a specified ATDN. There is a AOCS, all other calls, that should be DIS DIS, disconnect disconnect, just cann't remember what the gateopener is for that. it is in the CDB, I think.

 

[mluckie1]

Is in LD 15. gate opener is MPO, FMOP YES, return to AOCS DIS DIS return, keep hitting return until REQ. You can prt this and NIT in ld 21. If there is no console AOCS should be dis dis, default is DIS ATN, the first is for internal calls the second is for exteranl calls. The TRK106 is a WATS-release failure then TN.

 

[PEMpal]

All interesting ideas. Thank you.
However, this Opt 61 with these same four WATS has run just fine for THIRTEEN years, even through three software upgrades and one forktruck upgrade in 2001! Why would it SUDDENLY need re-programing???? THAT doesn't make sense.

 

[johnpoole]

because the central office upgraded and changed options with out telling you. happen all the time, you get new and improved dialtone, that don;t work

john poole
bellsouth business
columbia,sc

 

[mluckie1]

Or someone got the number on their CLID and figures it's the number to call for whatever reason. Also when you upgrade some features begin to work the way they were originaly designed to.

 

[PEMpal]

Just as a reminder, these four WATS trunks work just fine all day long, handling hundreds of calls. The TRK106 error ONLY shows up between 10 and 11 pm, EVERY night.
I changed SUPY from NO to YES a few nights ago, but it didn't help. NDEC and FDEC are already ETH.
There is an M2250 console and AOCS is DIS ATN.
NIT_DATA sends console to voice services in MM, where a night menu plays
WHY ONLY BETWEEN 10 and 11 PM?
Any suggestions for other call trace? I already did LD 80 on three of the four trunks, with results posted here earlier.

 

[mluckie1]

Does your nite service go to a menu service? Try and set the NITE on the Members to a FAX machine. Somehow there is an incoming call that goes to the menu service and then is disconnected by the mail system. the call sits thereuntil it times out. If you change the NITE on the member and send it to a FAX or Voicemailbox it may leave a FAX or voice message. Left to follow the system default this may continue indefinely. I would try the fax first.

 

[PEMpal]

I changed NITE on all four members to a fax machine that is on the PBX. Nothing happened at the fax machine and I still got TRK 106.

 

[PERRYPJ]

WHAT ARE THE WATS USED FOR, ARE THEY REAL WATS LINES FROM THE CENTRAL OFFICE

OLD ROLMEN WORKING ON NORTELS

 

[mluckie1]

Try and send to a mailbox, maybe they will stay on long enough to leave a message.

 

[PEMpal]

PERRYPJ - Yes, they are real WATS from the CO. They handle hundreds of outbound calls all day long. The messages only appear between 10 and 11 pm, EVERY NIGHT, seven days a week. There are only 2 to 5 messages, then it stops.

mluckie1 - Why do you think NITE is involved in this? I don't think these are real calls. I think there's a glitch somewhere. I have ruled out a UTC problem becasue the same error is generated for 16-0-6-2, 4-0-0-3, 16-0-3-3, and 4-0-1-3; four separate cards on two separate shelves (4 and 16).

 

[johnpoole]

between 10 and 11. what time is your midn? that rls failure could be releasing a perm hold that was active during working hours. try trac on all the trunks around 9, see if any of them are locked out. they release, you get the error. they don't give a error when the trunks hangs

john poole
bellsouth business
columbia,sc

 

[PERRYPJ]

IF THESE ARE COPPER TRKS IT COULD BE THE CO TESTING THE LINES. I SEE A OFF HOOK CONDITION WHEN THEY TEST MY HOME PHONE. ALSO IF THERE IS NO PROBLEM CAUSED BY THIS I WOULDN'T WORRY ABOUT IT

OLD ROLMEN WORKING ON NORTELS

 

[PEMpal]

johnpoole - MIDN is at 0200 every day.
perrypj - I never ignore an error that suddenly starts appearing after many years of NOT. Something has changed and I WILL FIND OUT WHAT IT IS.
Thanks.
JimC

 

[mluckie1]

PEMpal,

If you change the nite on that TN it may redirect the call to someplace that it can be answered. The trace looks like an inbound call that the system really doesn't know what to do with.