Routing question

[Ski123]

Having an issue whith a RLI. I have an SPN of 1408 programmed to go out RLI 4. Enrty 0 for RLI 4 is rout 0 entry 1 is rout 1. The issue is that enrty 0 never gets used all the calls go directly to enrty 1 (rout 1). I have checked the trunks for rout 0 and they are all inservice and idle (this is a DID/DOD route). I do see incomming calls to this trunk group but no outbound calls ever hit it. As a test I set up a new RLI and put rout 0 as the only choice. I then programmed SPN 1408 to use the new RLI and now the my test calls go directly to the attendant console. Any ideas why rout 0 isn't working? The NCOS on my test phone is 6 which has an FRL of 6. Route 0 is set up as IAO in the data block.


RLI 4
ENTR 0
LTER NO
ROUT 0
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 1
DMI 0
FCI 0
SBOC NRR
IDBB DBA
IOHQ NO
OHQ NO
CBQ NO

ENTR 1
LTER NO
ROUT 1
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 1
DMI 0
FCI 0
SBOC NRR
IDBB DBA
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 1
OVLL 0


TYPE spn

SPN 1408

SPN 1408
RLI 4
SDRR NONE
ITEI NONE

 

[KCFLHRC]

Does NCOS 6 equal FRL of a 6 in the ESN data block? LD 87, also check your MFRL on the entry.

 

[KCFLHRC]

There are also Trunk Group Busy Keys on the Attendant console on the far left side, make sure the operator didn't accidentally press the key for Route 0 and busy it out.

 

[Splic3d]

Make sure TGAR/TARG are not involved. You can set the system to look at the TGAR with LD 86 even though your using BARS/NARS.

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[GHTROUT]

Eliminate the route as the problem: Dial the Route Access Code to see if you can actually dial out.

~~
Gene at GHTROUT.com

 

[Ski123]

We tried dialing the acod for the route. I was expecting either a dial tone or a busy signal but the operator answered the call. I had them look at the attendant console and they said no keys are lit up. Below is how the console is set up. I also tried doing a trace on each of the conole keys and they show Idle.



TN 004 0 09 00
TYPE 2250
CDEN 8D
CTYP XDLC
CUST 0
SGRP 0
SETN 004 0 09 01
ANUM 01
IADN
ALPD NO
SSU 0001
ICDR ICDD
ABAN ABDD
CPND CNDA
EBLF BLFD
AADN
DNDI DNDA
DAPC DAPA
LANG 00
KEY 00 BVR
KEY 01 BIN
KEY 02
KEY 03 SSC 0001
KEY 04 EES
KEY 05 PAG 88
KEY 06 ADL 4401
KEY 07 ADL 5588
KEY 08 ADL
KEY 09 ADL
KEY 10
KEY 11
KEY 12
KEY 13
KEY 14
KEY 15
KEY 16
KEY 17
KEY 18
KEY 19
DATE 8 MAY 2002

 

[Splic3d]

Post the RDB

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[KCFLHRC]

I would look at the console myself. Far left side keys, make sure none are lit up. When the call hits the console there may a key lighting up or something on the display that may point you in the right direction. Like maybe the call coming in on the Intercept key.

 

[Ski123]

TYPE RDB
CUST 00
ROUT 0
DES BELL
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 2
SBN NO
PNI 00001
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 8905
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 1
NDNO 1 *
DEXT NO
DNAM NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 8192
NRD 10112
DDL 70
ODT 8192
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096


PAGE 002


IENB 5
VSS 0
VGD 6
DRNG NO
CDR YES
INC NO
LAST NO
QREC NO
OAL YES
AIA NO
OAN NO
OPD YES
CDRX NO
NATL YES
VRAT NO
MUS YES
MRT 9
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
TDET NO
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

 

[Splic3d]

The only thing I see is you may try changing the route NCOS to 0. The RLI's should already be doing the restrictionNCOS levels. Not sure that will be the problem, but its worth checking.

http://www.i3techgroup.com

If its not working, get a bigger hammer!

Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

 

[Ski123]

Is there a specific Key on the 2250 attendant console that could be causing the outgoing calls to go to the console instaed of going out the DID/DOD trunk group. All the T'1 are in service and idle. Incomming calls work fine but any attempt to send an outgoing call to this trunk group ends up going to the attendant console.

 

[GHTROUT]

Quick fix if memory serves me - make the TGAR of your phone = 15, then dial the Route Access code and place the call. I think 15 is a magic TGAR and is not affected my Attendant TGB keys. It has been a while.

As for "where the buttons are on the console" - you do need to check a console in person. Look at the far left column (next to the edge of the M2250). If any button is solid, press it.

Now press Shift and do the same. Make sure when you walk away, no buttons on the left column are on steady.

Lastly, go to LD15 and REQ CHG, TYPE FTR, then return to OPT and type "XTG" --this will disable future use of the Trunk Group Busy keys.



~~
Gene at GHTROUT.com

 

[DFKSydney]

Bit late responding but:

If you do not already have a solution... I notice that your FRLs all use NCOS 0 (as indicated above). Try changing the RDB with entries: FRL 0 7, FRL 1 7, etc etc. Basically you open the route to all calls, and use the extns NCOS for barring.

Another thing to look at is the trunk members programming. Usually in the CLS they are set to UNR (unrestricted).