Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Route Selection

Status
Not open for further replies.

angelo16

Technical User
May 27, 2011
15
0
0
SA
Dear Friends,

Could you please support me on this issue in Nortel Meridian Option 61C? I have two (2) outgoing routes, the DOD and Outgoing Analog trunks. I have unique access 9 for outside calls. If i access 9 from any DID extension, i should get route of DOD. However, if i access 9 from Non-DID extension, i should get route of Outgoing Analog trunk. How could i make this workable? Your suggestions are very helpful.

Thanks,
Angelo
 
Thanks Buddy!

Actually, somebody has suggested to assign different TGAR's. Could you please guide me on this?

Regards,

Angelo
 
Here's the configuration:

Outside access code = 9
TGAR in both DID and Non-DID extension = TGAR 14

1. Route 1 (Analog trunks)
TARG 01 02 03 04 05 06 07 08 09 10 11 12 13 14 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30 31
2. Route 11 (DOD)
TARG 01 02 03 04 05 13 14

Base from the above, what would be the reconfiguration?

Thanks,

Angelo
 
How many phones do you have to do? I've never seen that scenario, but if you only have to do a couple of phones, I would HOT DIAL or AutoDial the Non-DID key to the ACOD of the Analog Route.
 
We have around 100 DID extensions and 30 Non-DID extensions at the moment. Appreciate your inputs, anyway. But it is of great help to me if we can work it out through TGAR and TARG between 2 routes.

Thanks,
angelo
 
You won't be about to work it out via TGAR and TARG.

Your TGAR is 'SET' based and not 'Line' based. No matter what line you select, you will use the same TGAR.

If the TGAR matches the TARG of the route, then you can't access that route.
 
Angelo,
go into load 86 and prt the ESN block.
req prt
cust 0
feat ESN
At the end of the block see if TGAR say yes or no. If it say no then your system is not checking for TGAR. It is using NCOS for routing. i say this because the info posted shows TGAR of set and TARG of set to match.Post a copy of the RLB and prt out of each DID and non-did set.

In the RLB look for FRL in each enrty, see if it matches the NCOS of the set.
 
Hi Romar53,

I guess you are right. I worked on changing TARG and TGARs but did not work. I will check my ESN for TGAR status.

But just in case my TGAR in ESN is No, i will change it to YES right? What would be the effect in the NCOS?

Thanks,
Angelo
 
DO NOT change your TGAR to yes in the ESN block. This will cause distrubtion in your calling based on what youhave posted before.
Post the RLB and the TN print out of a DID and NON DID set.
 
Dear Romar53,

Thanks for the info. I checked the ESN block and the TGAR was No. I will capture the RLB and the TNs and have it posted tomorrow.

Regards
 
Hi Romar53,

Below the configurations of RLB and the DID extension.


REQ prt
CUST 0
FEAT rlb
RLI

RLI 1
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 0
DMI 0
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBA
IOHQ NO
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0


RLI 5
ENTR 0
LTER NO
ROUT 23
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ENTR 1
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 0
DMI 0
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0




REQ: prt
TYPE: tnb
TN 28 1 10 7
CUST 0
DATE
PAGE
DES

DES DTMF
TN 028 1 10 07
TYPE 500
CDEN 4D
CUST 0
WRLS NO
DN 59155 0 MARP
AST NO
IAPG 0
HUNT
TGAR 14
LDN NO
NCOS 0
SGRP 2
RNPG 0
LNRS 16
XLST
SCI 0
SCPW 0000
SFLT NO
CAC_MFC 0
CLS TLD DTN FBD XFA WTA THFD FND HTD ONS
LPR XRA AGRD CWD SWD MWD RMMD SMWD LPD XHD SLKD CCSA-CSI TEND LNA TVD
CFTD SFD MRD C6D CNID CLBD AUTU
ICDA CDMD EHTD MCTD
GPUD DPUD CFXD ARHD OVDD AGTD CLTD LDTD ASCD
MBXD UDI RCC HBTD IRGD IAMD DDGA NAMA MIND
NRWD NRCD NROD CRD PRSD MCRD
EXR0 SHL SMSD ABDD CFHD DNDY DNO3
CWND USRD BNRD OCBD RTDD RBDD RBHD FAXD PGND FTTC
FDSD NOVD
PLEV 02
AACS NO
MLWU_LANG 0
FTR CFW 5
DATE 8 FEB 2011
 
Angelo,
Since TAGR is set to NO in the ESN data block you are using NCOS to restrict phones.
To make the non-DID phone access the Outgoing Analog trunks, make the NCOS of the phone match the FRL of the entry that the Outgoing Analog Trunks are in.
example:
RLI xx
entr 0
route xx (outgoing analog trunks)
FRL (equals NCOS of non-did phone)
entr 1
route xx (DOD)
FRL 0 (this equals the NCOS of the DID phones)
Iset 2 (this make sure that the phone will look for other enrtys)

This assumes that all phone have an NCOS of 0 at this time.
If this you don't have the expertise to do this tpye of programming then you may want to have your vendor give you a hand.

Good luck!
 
Not that simple Romar53... I believe he is stating a phone has both a DID and non-did extension on the same phone, and he wants to select a separate route for each line type.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top