Line not forwarding as expected 1

[Gdgtry]

I'm an IT professional that has zero knowledge of phone systems. We have a CS1000 on release 3.10.28.41 that I've inherited control of.

Currently I'm trying to get my phone to forward to my cell phone correctly. As of now, when my extension is dialed internally it forwards to my cell correctly. When my line is called externally it forwards to a different extension. I have literally zero knowledge of these systems other than what I've googled up. Here's a print out of my current lines setup:

REQ: prt
TYPE: tnb
TN 016 0 00 12
DATE
PAGE
DES

DES 7905
TN 016 0 00 12
TYPE 3904
CDEN 8D
CUST 0
KBA 1
ERL 0
FDN 7999
TGAR 0
LDN NO
NCOS 3
SGRP 0
RNPG 4
SCI 0
SSU
LNRS 16
XLST
CLS CTD FBD WTA LPR PUA MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRA NID OLA VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXA ARHA FITD CLTD ASCD
CPFA CPTA ABDD CFHA FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN
CDMR MCDD T87D PKCH
CPND_LANG ENG
RCO 0
BFTN 006 0 00 03
007 0 00 03
008 0 00 03
012 0 00 03
012 0 00 04
HUNT 7999
LHK 2
LPK 3
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 7905 1 MARP
CPND
NAME Me
XPLN 27
DISPLAY_FMT FIRST,LAST
01 SCR 6905 1 MARP
CPND
NAME Me
XPLN 27
DISPLAY_FMT FIRST,LAST
02 SCR 6805 1 MARP
CPND
NAME Me
XPLN 27
DISPLAY_FMT FIRST,LAST
03 ADL 16
04 ADL 16
05 MSB
06 ADL 16
07 ADL 16
08 ADL 16
09 ADL 16
10 ADL 16
11
12
13
14
15
16 MWK 7999
17 TRN
18 AO6
19
20 RGA
21 PRK
22 RNP
23 SSU 0000
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
32
33
34
35 ADL 16
36 ADL 16
37 ADL 16
38 ADL 16
39 ADL 16
40 ADL 16
41 ADL 16 2
42 ADL 16 1
43
44
45
46
47
48
49 ADL 16
50 ADL 16
51 ADL 16
52 ADL 16
53 ADL 16
DATE 10 NOV 2010

Any ideas?

 

[zstic78]

The way I do it is to create an ACDN in LD 23
REQ new
TYPE acd
CUST 0
ACDN (any ext not being used)
Hit return through all prompts except
MAXP 1
NCFW 91XXXXXXXXXX

then hit return through the rest until you get the REQ prompt.

Then you can call forward your phone to the acdn you just created.

I did notice there is no CFW programmed on key 19 on the phone you printed

 

[Gdgtry]

There is a CFW 16 on key 19.

I'll try the option you listed, but it sounds sort of like a work around. I'd prefer it to work correctly if possible. I know others would like to have everything forwarding correctly and I don't want to make forwarding extensions for all of them.

Another questions, can someone give me the commands to list ringing groups (I think thats the right term for a number that rings multiple phones) and their members?

 

[zstic78]

The reason I do it this way is to control what it is forwarded to. Here my customer has a lot of international employees, if we opened it up any one could forward to any number in the world and sit at home and make calls on the company dime. Yes its a bit more work but much more secure.

 

[Tman45]

Okay well the way we do it ((since you already have CFXA (call forward external allowed) - in your CLS (class of service)) is we would simply press your forward key on your phone (as you said key 19) and enter your cell phone number (add your dial out code before the number if you have one such as 9). The problem is that your TGAR may be blocking it since you have it set at 0 - typically we use 1 or 2. Doing it this way you can set it up on a per phone user basis (instead of forwarding your phone to an internal extension that anyone else could potentially hit). If you still can't get it to work then we will have to look at other configs.
Another thing is having your phone on CTD if your cell phone is a toll call it should be blocked by CTD - we use UNR for unrestricted on our admin phones. It is a good idea to leave it CTD for everyone else.

 

[Gdgtry]

I appreciate your help. Can you tell me how to view current TGAR settings? I changed my line over to TGAR 1 as a test, same result.

How quickly do these sort of changes take effect?

I won't lie, as of now I'm relying on the web interface for all these changes. I don't off hand see a CTD option. Can you elaborate on how to change it and what it does.

 

[Pir8Radio]

zstic78, couldn't you just restrict the CFW Redirection DN Length to 8 for local calls? Maybe that isnt secure? Thats how i was shown anyway..


19 CFW 8 9XXXXXXX

 

[yyrkroon]

Go to LD 15 and change the RDR data OPT from CFO to CFF

LD 15
REQ=CHG
TYPE=RDR
CUST=0
press enter till you get to OPT and type in CFF and enter. Now press the enter key till you're out of the data block and test.

If you're sending the call out over the same route as the incoming, you may also need to change a couple of other thing. We'll not go there unless this doesn't work.

 

[GHTROUT]

I concur with yyrkroon above.

http://www.ghtrout.com/rdr/cff-cfo.html

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

 

[Pir8Radio]

So what does the above actually do/accomplish?

 

[zstic78]

I guess at this point it doesn't matter, we are doing VoIP site to site to local, and using Blackberry MVS, But its the way the cust. wants it, for standard cell phone users. so that is what we do. It does not stop the user coming in on holidays and making their calls home.

 

[yyrkroon]

Changing OPT (option) within RDR (Redirection)from CFO (default - Call forward Originating) to CFF (Call Forward Forwarding) will tell the PBX to look at the NCOS of the forwarding station vs the NCOS of the trunk for xternal forwarding.

Since everything works fine if you call the extension (becuase the set NCOS is being used) and stop working if the caller is from an external source (because the trunk NCOS is being used), this tells me that the trunks were built with the default NCOS of 0 or an NCOS to low to access and external trunk.

 

[yyrkroon]

The other blockage would be if user is trying to forward a calls out the same route as the incoming. By the default, the PBX prevent this from happening but provides for the ability to over-ride this. You'll have to enable trunk to trunk xfer within the Net datablock and change the set CLS from FTTC (default setting) to FTTU, provided that FTOP is default.

 

[Tman45]

Actually that was my fault, I meant to change your NCOS setting and not the TGAR based on yyrkroon's description in his/her 2nd to last post ... sorry about that.

"this tells me that the trunks were built with the default NCOS of 0 or an NCOS to low to access and external trunk."

Follow yykroon's suggestion and you should be money - if you need more help let us know.

 

[Gdgtry]

Big thanks to yyrkroon. Calls now forward as expected.

Are there any side effects of changing that setting that I need to know about?

Are there any sites you can point me to that can give me some more detail about what various commands do? Sort of a tutorial, if you will.

 

[yyrkroon]

No side affect, it's just an option whether you want to control forwarding using the trunks or the sets.

GHTrout website is about the best site there is for beginers, lots of examples for beginers.

Nortel Resources at

http://www.GHTROUT.com

or just look a few post up and you'll see his post and the links