Option 81C Post-dial delay

[Tomiga1]

I stumbled across something while troubleshooting a post-dial delay problem. This has been ongoing for a few months. Outbound calls take anywhere from 5-20+ seconds for ringback?
The circuits are set to linear hunt though I really don't know how to tell if the channels are being chosen in the correct order.
Anyway, today I read something on TekTips that made me try dialing the number by first inserting the ACOD.
It only made a difference though if I used the area code too......even for local numbers.
Ringback began immediately.....for local and long distance.
Any comments/suggestions how to fix?

Thanks for all!

 

[libram11]

the manual solution is to dial a # after the number.

 

[Tomiga1]

Thanks libram.....tried that early on and dialing NXX-XXXX + # had no effect on time in my case.
The only resolution so far to improve the ringback was to dial the ACOD + NPA + NXX.....etc.
Ringback is two seconds.

 

[GHTROUT]

You are in the USA? Are these calls going over a PRI?

Here is one test: Change on of your NXXs to an SPN. (Out the NXX and build it back as an SPN to the same RLI). Set the FLEN to 7 (assuming you dial 9+seven digits)

If that fixes it, tell your carrier about the delay - the problem is on their end.

One timer that might come into play is the "NIT" Timer. The NIT should be 8 is most cases.

>ld 21
PT1000

REQ: prt
TYPE: tim
TYPE TIM_DATA
CUST 0

TYPE TIM_DATA
CUST 00
FLSH 45
PHDT 30
DIND 30
DIDT 14
LDTT 6
BOTO 14
DBRC 60
RTIM 0 0 0
ATIM 0
AQTT 0
ADLD 0
NFNA 0
HWTT 300
NIT 8 <--- This should be 8
FOPT 0

REQ:


Find more at GHTROUT.com

 

[Tomiga1]

GHTROUT, yes U.S, no we have copper?T1s.....no caller id.

Yes, standard outbound calls are dialed 9 + seven digits.

I'll check on the NIT. Just curious how this could have all of a sudden (months ago) happened. We did upgrade end of last year to latest version. I wouldn't have noticed the time delay after the upgrade so I don't know exactly when it occurred.

Thanks!

 

[libram11]

I'm confused, are you going out on copper or t-1? Youre 7 digit dialing locally? Is there only a delay in 7 digits or 10? Or is the delay different with the acod and 7 or 10?

 

[Tomiga1]

Sorry, terminology may be incorrect but we have T1's, not PRI.

The delay occurs with both 7 and 10 digit dialing. The ACOD alone did not have any effect. I MUST use the ACOD and area code for both local and long distance to get instant ringback.

 

[oldtelman]

Could be a trunking start issue using dly(delay) instead of imm(immediate) to start dialling immediately.

 

[libram11]

Ok so t-1 outbound, let me ask a couple more questions. have you checked your nars to make sure there isnt erroneous data in there for other routes? can you post a copy of a tnb of one trunk and the rdb of the route?

 

[Tomiga1]

Oldtelman/libram, not familiar/qualified to check nars/bars data. I'm posting rdb, but not sure how to prt tnb of trunk, LD 60?

REQ: prt
TYPE: rdb
CUST 0
ROUT 10

TYPE RDB
CUST 00
ROUT 10
DES
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP DTI
ISDN NO
DSEL 3VCE
PTYP DCO
CNDP UKWN
AUTO NO
DNIS YES
NDGT 4
DDLY NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 5910
CPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 0 *
NDNO 0
DNAM YES
TIMR ICF 384
OGF 384
EOD 8192
DSI 34944
NRD 10112
DDL 70
ODT 2048
RGV 640
FLH 510
GRD 896
SFB 3

IENB 5
VSS 0
VGD 6
SST 5 0
NEDC ETH
FEDC ETH
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG YES


PAGE 002

NDRI 00
CDR YES
INC YES
LAST YES
QREC NO
OAL YES
AIA YES
OAN YES
OPD YES
CDRX NO
NATL YES
VRAT NO
MUS YES
MRT 27
MR NO
MANO NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TTBL 0
ATAN NO
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
ARDN NO
CTBL 0
AACR NO

 

[Tomiga1]

Another piece of the puzzle.....the ACOD I'm using (5910) is actually the second ENTR for the RLB. The first ENTR uses ACOD 5902 and when I try dialing that, I get a fast busy. Here is route 2.
TYPE RDB
CUST 00
ROUT 2
DES COT/POWERFAILURE
TKTP COT
NPID_TBL_NUM 0
PRIV NO
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP DTI
ISDN NO
DSEL VOD
PTYP DCO
CNDP UKWN
AUTO NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 5902
CPP NO
TARG
CLEN 1
BILN NO
OABS
TIMR ICF 384
OGF 384
EOD 8192
DSI 34944
NRD 10112
DDL 70
OOD 1
ODT 2048
RGV 640
FLH 510
GRD 896
SFB 3
CRD 512

IENB 5
TFD 0
LEXT 100
VGD 6
SST 3 0
NEDC ETH
FEDC ETH
CPDC NO
SPCT IMM
HOLD 02 02 40
SEIZ 02 02
RGFL 02 02
RVSD 08 31
ILLR 02 02
DRNG YES
NDRI 00
CDR YES
INC YES
LAST YES
QREC NO


PAGE 002

OAL YES
AIA YES
OAN YES
OPD YES
CDRX NO
NATL YES
MUS YES
MRT 27
MR NO
RACD NO
MANO NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TTBL 0
ATAN NO
OHTD NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
ARDN NO
CTBL 0
AACR NO

 

[GHTROUT]

You have some or many bad trunks. Go to LD21 and REQ LTM to list the trunks in all routes.

You can also do this on Route 2

>LD 36
.LOVF 0 2

As for the delay, it is the system trying to find a good trunk.

Find more at GHTROUT.com

 

[Tomiga1]

Does the LTM in LD21 indicate the order in which trunks are selected? It doesn't appear to match what I am seeing in LD60>stat. It seems like the lower channels should be busy.

TYPE TLST
TKTP COT
ROUT 2
DES COT/POWERFAILURE
TN 051 01 MBER 1
TN 051 02 MBER 2
TN 051 03 MBER 3
TN 051 04 MBER 4
TN 051 05 MBER 5
TN 051 06 MBER 6
TN 051 07 MBER 7
TN 051 08 MBER 8
TN 051 09 MBER 9
TN 051 10 MBER 10
TN 051 11 MBER 11
TN 051 12 MBER 12
TN 051 13 MBER 13
TN 051 14 MBER 14
TN 051 15 MBER 15
TN 051 16 MBER 16
TN 051 17 MBER 17
TN 051 18 MBER 18
TN 051 19 MBER 19
TN 051 20 MBER 20
TN 051 21 MBER 21
TN 051 22 MBER 22
TN 051 23 MBER 23
TN 051 24 MBER 24

DTI TRK LOOP 51 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - IDLE CO VOD CH 02 - IDLE CO VOD
CH 03 - IDLE CO VOD CH 04 - IDLE CO VOD
CH 05 - IDLE CO VOD CH 06 - IDLE CO VOD
CH 07 - IDLE CO VOD CH 08 - IDLE CO VOD
CH 09 - BUSY CO VOD CH 10 - IDLE CO VOD
CH 11 - IDLE CO VOD CH 12 - IDLE CO VOD
CH 13 - BUSY CO VOD CH 14 - IDLE CO VOD
CH 15 - IDLE CO VOD CH 16 - BUSY CO VOD
CH 17 - BUSY CO VOD CH 18 - BUSY CO VOD
CH 19 - BUSY CO VOD CH 20 - IDLE CO VOD
CH 21 - BUSY CO VOD CH 22 - BUSY CO VOD
CH 23 - BUSY CO VOD CH 24 - BUSY CO VOD

 

[GHTROUT]

LOL, the DES on Route 2 says "COT/POWERFAILURE" - Clearly, they will not work in a power fail - they are digital trunks

Outgoing (from you to the world) calls always take the higher member number in the case of linear trunk selection.



Find more at GHTROUT.com

 

[Tomiga1]

GHTROUT, yes that is correct, these are power fail channels. Please explain why they wouldn't work. We have not had reason to use in the 6-7 years that I've been onsite, but I would imagine my predecessor would have verified functionality.

Thanks!

 

[GHTROUT]

For Power Failure, you want a phone line that does not require power. The only lines that do not require power are analog trunks or POTS, or Centrex lines, which are powered by the phone company Central Office.

The lines you have are powered inside your building.






Find more at GHTROUT.com

 

[Tomiga1]

GHTROUT, thanks again for the words. It certainly seems logical, even to this newbie. Note that we do have a Gordon Kapes unit/device in line if that makes a difference.

 

[GHTROUT]

That Kapes unit is probably for some analog lines that exist, or used to exist.

Find more at GHTROUT.com

 

[Tomiga1]

GHTROUT, why would I get ringback quicker by inserting the area code after ACOD? And by dialing the ACOD, does that sieze the first available trunk because if it does then dialing 5902 shouldn't give me an intermittent fast-busy, right?

 

[rpneal44]

Go into LD 86 and in the RLB entry for Rt 2 respond to TOD with "X0". If you are getting a FB when you dial the ACOD for Rt 2, they are not working and your BARS are searching through every one of them looking for a trunk before it goes on to the next entry. TOD X0 will shut off that entry and the search will skip that entry.

Phil, the Phriendly Phone Man