CO trunk not defined

[coniglio]

this is completely confusing me. I have a CO trunk that I suspected was my voicemail telephone number. When I tried calling out on this trunk in LD 36 I got a TRK008 alarm (trunk is not defined). However, when I call the voicemail number and trace this same trunk in LD 80 I see myself hitting it and my call is answered by the voicemail (I'm calling externally, by the way). The trunk itself auto-terminates to a voicemail DN. How can I be hitting this trunk if it's not defined? Just curious...thanks in advance.

 

[johnpoole]

ld 20 prt tnb, 20 0 0 0, it may be a in bound only, so ld 36 can't let you call out

john poole
bellsouth business
columbia,sc

 

[coniglio]

how can I tell? I printed the TN but there's nothing there to indicate whether it's in or out or both. When I printed the RDB in LD 21 the ICOG says IAO (in and out).

 

[johnpoole]

so it is a two way trunk, is it auto=yes in the route, if so it has a inbound target on the trunk, change that target to your phone and test it in bound, i would have used a butt set on the frame to test that cot for dt, usually ground start..

john poole
bellsouth business
columbia,sc

 

[coniglio]

it's a remote site. and it autoterminates to our voicemail DN. My concern is that the trunk says it's undefined, but when i call the telephone number and trac I see myself on this TN. Also, the TN is going into LOCKOUT after one call hits it. Everything seems to be working fine, but I just found it to be strange that it's undefined and also going in and out of lockout. Perhaps there's no need to be concerned.

 

[johnpoole]

change fdec and ndec to eht in the route on both ends and supn to no on both ends, that will do a cleaner release and avoid the lockout, you can set a forced disconnect on it out at say 5 minutes but it is a force so use with care. as far as being undefined that makes no sense at all.

john poole
bellsouth business
columbia,sc

 

[coniglio]

I don't think it makes sense either, but here is what I'm getting...

TYPE TLST
TKTP COT
ROUT 3
DES VMAIL
TN 002 0 00 00 MBER 1 VMAIL

.trak 2 0
LOCKOUT TN 002 0 00 00

It shows in Lockout. When I call the phone number and then trace, however, I get the below:

.trak 2 0


ACTIVE TN 002 0 00 00
ORIG 002 0 00 00 COT RMBR 3 1
TERM NONE
DIAL DN NONE
MAIN_PM READY
TALKSLOT NONE
QUEU 2S
CALL ID 0 90

How does it automatically come out of lockout? I also keep getting this alarm:
TRK156 2 0 0 0

I probably shouldn't even think about this, because the dial-in voicemail number is working, but I just don't understand how. If I'm missing something here please let me know. Thank you.

 

[johnpoole]

the switch missed a disco timer from the far end, the err happens when the timer expires, thats when you get a forced release of the lockout. a failsafe to keep them all from locking up forever

john poole
bellsouth business
columbia,sc

 

[coniglio]

so should I do anything or just leave this alone? The trunk was LOP in PBX and loop at Verizon, but this phone number kept ringing BUSY so my vendor suggested changing it to GRD, which I did, and the number isn't busy anymore, but Verizon still has it as loop. I have some time today for a change and would love to clean this up but I don't know if I should even try to at this point. I await your recommendation. Thank you.

 

[johnpoole]

ground is much cleaner with release and glare. it needs to be ground at both ends, and check the manual, their USED to be a switch setting for that as well, i haven't used a analog trunk in forever. thank goodness

john poole
bellsouth business
columbia,sc

 

[coniglio]

okay, I will ask Verizon to change their end to Ground as well and hopefully everything will be fine then. Thanks. PS: I'll look for that setting as well.