Single extension going over COT 2

[bshubinsky]

We seem to have a single user that is apparently going over our copper line for external dialing. Does anyone know how to check this within the switch and how to make sure they go over our DS3 like everything else?

We are on a CS1000 Rls 6.0 and the phone is an M3904.

 

[bigindian65]

how does their set NCOS/TGAR compare to others?

Mato' Was'aka

 

[bshubinsky]

The TGAR is actually set differently. Everyone has 2 whereas the user is set to 1.

How do I print the TGAR out to see the difference in restrictions?

 

[bigindian65]

just match it to the norm. Set it to 2 and it has to follow others if ncos is same. TARG/TGAR are, for most part, match = deny.

Mato' Was'aka

 

[bshubinsky]

I would but they are an executive - I guess I'll just run it by her and see if it's OK with her. I figure I'll have her test it and if it doesn't fix it I'll set it back to what it was.

 

[bigindian65]

• TGAR is assigned to a phone. Each phone has one TGAR.
• TARG is assigned to the trunk route. Each route can have multiple TARG entries.
• When a phone's TGAR = a route's TARG, access is restricted. Example: When a phone with a TGAR of "1" tries to dial the trunk route access code of a route that has a TARG of "1", the calls is blocked.
• Phones with TGAR 0 are not restricted by TGAR/TARG.


Mato' Was'aka

 

[bshubinsky]

Ok - so, apparently it doesn't happen all the time. It appears to be random. She was set to TGAR 1 because that is the TGAR we have set to allow paging.

Other users are set to TGAR 1 and don't experience the same issue so I don't think it's a problem with that.

Any other suggestions?

 

[DocVic]

So, if her dialing over copper isn't costing any additional money, don't fix it. If it is, change it, then tell her you just found a problem, and are now saving her a boatload of money. The Big guy has explained all this in detail and wouldn't lie to you, unless you owe him money.

Think ahead of the curve, unless there is ice on that road, then stop and plan your strategy. In this case, Bigindian has given you the roadmap. Use it.

DocVic
Dedicated to Nortel Products till the end.
Need help?

http://www.TSS-CO.com

 

[bigindian65]

perhaps, it is unique to an NPA or NXX they are dialing, which is using an RLI point to the COT route.

Mato' Was'aka

 

[bhassell2000]

If she dials the same external number from a differetn phone does it route out the same way?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[bshubinsky]

OK, I lied. It is the TGAR setting. Can someone explain to me (kind of a self-taught noob at this) how to check those settings and change it?

I can't just leave it (as much as I want to) since the CIO himself is requesting the caller ID to match.

 

[bigindian65]

ld 11
chg
type <-set type
cust 0
TN
easy chg yes
item tgar 2 <---put in tgar 2 if that is what you want.
enter out..

Mato' Was'aka

 

[bshubinsky]

Sorry, I didn't mean change the TGAR on the set. TGAR 1 is the one that allows her to use the paging system; I want to edit the TGAR itself to route through the DS3 rather than the COT.

 

[GHTROUT]

Are you certain this person doesn't just have a Private Line?? I do not think it's all this TGAR stuff.

Print the TN of this person

--
Nortel Resources at GHTROUT.com | Connect with me on LinkedIn
--

 

[bshubinsky]

I'm fairly positive it is a TGAR issue - I tried it on another TGAR 1 phone and had the same experience. Either way, here's the TN:

REQ: prt
TYPE: tnb
TN 004 0 08 01
DATE
PAGE
DES

DES TC19
TN 004 0 08 01
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN 3507
TGAR 1
LDN NO
NCOS 5
SGRP 0
RNPG 0
SCI 0
SSU
XLST
CLS CTD FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD DOS XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDA CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHD CNTD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
OUSD OBPD CDMR PRED MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 3507
LHK 2
PLEV 02
PUID
FCAR NO
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
PRI 05
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 ACD 8900 0 8902
SPV
01 SCR 4011 0 MARP
CPND
NAME User Name
XPLN 18
DISPLAY_FMT FIRST,LAST
02 SCR 4111 0 MARP
CPND
NAME USer Name
XPLN 18
DISPLAY_FMT FIRST,LAST
03 NRD
04 OBV
05 DIG 1 22 R
06 DWC 8100
07 DWC 3503
08 DWC 3504
09 ADL 16
10 ADL 16
11 ADL 16
12
13
14
15
16
17 TRN
18 AO6
19 CFW 4 3507
20 RGA
21
22
23
24
25
26 CPN
27 CLT
28 RLT
29
30
31
DATE 22 DEC 2010

 

[GHTROUT]

What happens if you make this person TGAR 0

That essentialy turns off all Trunk Group Access Restrictions for the user.

If they still hit the copper, then your BARS is where the problem is.

You probably have TGAR=YES in your LD86 ESN data. There is rarely a reason for that.

--
Nortel Resources at GHTROUT.com | Connect with me on LinkedIn
--

 

[bshubinsky]

I set the TGAR to 0 on one of the test phones and it came up the right way (not copper, showing main line). Since it's not a BARS issue, where would it lie?

 

[bshubinsky]

Can't seem to figure out how to edit a post. I did a PRT of the ESN in LD86 and it is indeed set to TGAR = YES.

 

[GHTROUT]

Not a way to edit a posted post.

If things are working, then now is not a good time to change ESN - it is too close to holidays where people will be gone.

If TGAR 0 fixed this user, then leave it - they are an executivie you say, so they have an interest in not screwing things up for you.

The issue is a TGAR issue. Here is a primer on TGAR:

http://www.ghtrout.com/ghtrout/files/TGAR_and_TARG_Help.html

The top row is the Trunk Routes and the left column is the phones. You will want to print all ytour routes out and find out which one is set to "match" the users TGAR - when there is a match of TARG and TGAR, access is denied.



--
Nortel Resources at GHTROUT.com | Connect with me on LinkedIn
--

 

[bshubinsky]

Thanks for the help everyone, got it all figured out.