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!

FNA of an SCR number appearing on two sets

Status
Not open for further replies.

BikeTours

Technical User
Dec 28, 2004
63
0
0
CA
I have two users who were using 2616 sets and who were recently relocated. In the move they were given new 3904 sets and describe that some of their capabilities were lost.

The move was done by a colleague who did not save the original configuration. I can only surmise how they should be configured. The problem is impacting a shared department number 8300.

The users indicate that prior to the move an inbound call to 8300 would first land on the set who's primary number is 6008. If that employee did not pick up after three rings the call would route to the set with primary line appearance 6018. Again if that set did not pick up the call went to voicemail. You will notice in the TNB output below both Hunt and FDN was to our CallPilot voice messaging number.

without prior knowledge I have assumed the following.
1) to have the calls ring into 8300 as described above they must have FNA active.
2) 8300 must be optioned as SCR on both phones.
3) I have assumed the following: that 6008 gets the call first because it is the MARP for that number or simply because numerically 6008 is lower than 6018.

When I looked at the configurations set 6018 had lost the line appearance of 8300. I have added back in and have asked the users to test and see if it works as currently configured.

If it does can anyone describe the interactions between this line appearance and the FNA or other CLS feature that made this particular ring pattern work?

If it doesn't can anyone describe what I am missing? For example does the LHK [Line Hunt Key] come into play, and should I have HUNT on 6008 pointing toward 6018... something like that?

>ld 20

PT0000
REQ: prt
TYPE: tnb
TN 020 1 00 09
DATE
PAGE
DES

DES 3904
TN 020 1 00 09
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN 6666
TGAR 1
LDN NO
NCOS 6
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
CLS CTD FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPA STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNIA CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXA ARHD FITD 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
CDMR MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 6666
LHK 1
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 MCR 6018 0 MARP
CPND
NAME Mary
XPLN 17
DISPLAY_FMT FIRST,LAST
01 MCR 6018 0
CPND
NAME Mary
XPLN 17
DISPLAY_FMT FIRST,LAST
02 SCR 8300 0
CPND
NAME ACT
XPLN 5
DISPLAY_FMT FIRST,LAST
03 ADL 16
04 ADL 16
05 ADL 16
06 ADL 16
07 ADL 16
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12
13
14
15
16 MWK 6666
17 TRN
18 AO6
19 CFW 11
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 1 OCT 2009


NACT


DES 3904
TN 008 0 14 06
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN 6666
TGAR 1
LDN NO
NCOS 6
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
CLS CTD FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPA STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNIA CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXA ARHD FITD 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
CDMR MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 6666
LHK 1
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 6008 0 MARP
CPND
NAME CAROL
XPLN 13
DISPLAY_FMT LAST,FIRST
01 SCR 8300 0 MARP
CPND
NAME ADT
XPLN 5
DISPLAY_FMT FIRST,LAST
02 ADL 16
03 ADL 16
04 ADL 16
05 ADL 16
06 ADL 16
07 ADL 16
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12
13
14
15
16 MWK 6666
17 TRN
18 AO6
19 CFW 11
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 1 OCT 2009



 
Let's start by understanding MARP:

In your release, for FDN to work, the DN needs to be within the KEY number value of LHK. This isn't always apparent.

For example, to get KEY 4 to "FDN" you may need to have LHK be 4 or greater. Like I said, this isn't always apparent and not well documented.

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top