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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't get external forwarding to work

Status
Not open for further replies.

Jreadlock

Technical User
Feb 7, 2005
34
US
Good morning/afternoon everyone.

Here's my situation:

I have a LDN (DN is 585) with a DID pointed at it and when the DID is called, it rings the attendant phone (i2004) as it should. However, after 6 rings, the EFD will not work (the EFD is forwarding to a MCR DN - 597). The DID goes through an IDC table and 585 is pointed to 689 which is a phantom 500 set. Then, 689 DCFW's to 685. CFXA is turned on, obviously. If you manually forward the phone, it works fine. I'm not sure if it affects it or not, but I have ensured that the CLS is IRD, NID, and OLD. The FNA is also set up to forward to 597 and this works fine so the problem is strictly external.

Suggestions and/or ideas?
 
585 is pointed to 689 which is a phantom 500 set"

I am not sure if it will make a diff or not, but could you out the 500 set and use a maxp 1 ncfw acdn and see if it will fly?


Mato' Was'aka
 
Your call flow is pretty confusing from your original post.

Please verify:

Is your LDN 585?
What is the DN of the attendant phone? Can you post the TN?
MCR 597? Can you post the TN of the MARP set?
If 585 is your LDN what method do you use to make it ring on the i2004?
How does 585 ever get IDC treatment to point it to 689?
Is 685 an external number?
 
First, thanks to both of you guys for posting - hopefully we can figure this dog out...

Ok, so unfortunately, I don't know why they set it up as they did but here's how ..well, maybe that's the issue: They have 585 in an IDC table pointing to 689 and yet 585 is also listed as the LDN0. Would this cause a conflict?

If not, here's what I was about to start off with:

1 - DID ending in 585 comes into the PBX
2 - 585 is translated in IDC table to 689
3 - 585 is also listed as LDN0 (although I don't know how the LDN0 is routed to the i2004 it rings on which has a DN of 685)
4 - 689 is a phantom 500 set that DCFW to 685
5 - 685 is the i2004 we use as the attendant
6 - When the receptionist isn't able to answer, the phone FNA's, Hunt's, EFD's, and EHT's, to 597
7 - 597 is a MCR DN that is set up on 5 different employees' phones

The TNB's of the 689,685, and the MARP'd phone for 597 are as follows:

DN 689
TYPE L500
TN 096 0 02 02 MARP DES TEST 17 OCT 2008

DN 685
TYPE SL1
TN 040 0 01 17 V KEY 00 H MARP DES 2004P2 (2004P2)

DN 597
TYPE SL1
TN 040 0 01 07 V KEY 05 (2004P2)

TN 040 0 00 12 V KEY 05 (2004P2)

TN 040 0 00 05 V KEY 05 (2004P2)

TN 040 0 00 21 V KEY 05 (2004P2)

TN 040 0 00 23 V KEY 05 MARP (2004P2)


DES TEST
TN 096 0 02 02 PHANTOM
TYPE 500
CDEN 4D
CUST 0
ERL 00000
WRLS NO
DN 689 0 MARP
AST NO
IAPG 0
HUNT
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
XLST
SCI 0
SFLT NO
CAC_MFC 0
CLS UNR DTN FBD XFD WTA THFD FNA HTD ONS
LPR XRD AGRD CWD SWD MWD RMMD SMWD LPD XHD SLKD CCSD LND TVD
CFTD SFA MRD C6D CNID CLBD AUTU
ICDD CDMD EHTD MCTD
GPUD DPUD CFXA ARHD OVDD AGTD CLTD LDTD ASCD SDND
MBXD CPFA CPTA UDI RCC HBTD IRGD DDGA NAMA MIND
NRWD NRCD NROD SPKD CRD PRSD MCRD
EXR0 SHL SMSD ABDD CFHD DNDY DNO3
CWND USRD BNRD OCBD RTDD RBDD RBHD FAXD CNUD CNAD PGND FTTC
FDSD NOVD CDMR MCDD T87D PKCH MPTD
RCO 0
PLEV 02
AACS NO
MLWU_LANG 0
FTR DCFW 20 685
DATE 17 OCT 2008

DES 2004P2
TN 040 0 01 17 VIRTUAL
TYPE 2004P2
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 010
CUR_ZONE 010
ERL 0
ECL 0
FDN 597
TGAR 0
LDN NO
NCOS 5
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FNA HTA TDD HFA CRPA
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTA SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDA CFXA ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD VOLA VOUD CDMR ICRD MCDD T87D KEM2 MSNV FRA PKCH
CPND_LANG ROM
RCO 0
EFD 597
HUNT 597
EHT 597
LHK 0
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG FRE
DNDR 0
KEY 00 SCR 685 0 MARP
CPND
CPND_LANG ROMAN
NAME Standard
XPLN 8
DISPLAY_FMT FIRST,LAST
01
02 ADL 20 582
03 ADL 20
04 ADL 20
05 ADL 20
06 ADL 20
07 ADL 20
08 ADL 20
09 ADL 20
10 ADL 20
11 ADL 20
12
13
14
15
16 MWK 586

17 TRN
18 AO6
19 CFW 16 597
20 RGA
21
22 RNP
23
24
25
26
27
28
29
30
31
DATE 16 OCT 2008

DES 2004P2
TN 040 0 00 23 VIRTUAL
TYPE 2004P2
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 010
CUR_ZONE 010
ERL 0
ECL 0
FDN 586
TGAR 0
LDN NO
NCOS 5
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FNA HTA TDD HFA CRPA
MWA LMPN RMMD SMWD AAD IMD XHD IRA NIA OLA VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDA CFXA ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD VOLA VOUD CDMR ICRD MCDD T87D KEM2 MSNV FRA PKCH
CPND_LANG ROM
RCO 0
HUNT 586
LHK 1
LPK 3
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG FRE
DNDR 0
KEY 00 SCR 829 0 MARP
CPND
CPND_LANG ROMAN
NAME Janick Peran
XPLN 12
DISPLAY_FMT FIRST,LAST
01 SCR 100829 0 MARP
CPND
CPND_LANG ROMAN
NAME Janick Peran
XPLN 12
DISPLAY_FMT FIRST,LAST
02 ADL 20 0012394353613
03 ADL 20
04 ADL 20
05 MCR 597 0 MARP
CPND
CPND_LANG ROMAN
NAME MAIN NUMBER - PARIS
XPLN 19
DISPLAY_FMT FIRST,LAST
06 ADL 20
07 ADL 20
08 ADL 20 00012394353613
09 ADL 20
10 ADL 20 00141239100
11 ADL 20 00147366320
12
13
14
15
16 MWK 586
17 TRN
18 AO6
19 CFW 16
20 RGA
21
22 RNP
23
24
25
26
27
28
29
30
31
DATE 26 SEP 2008

 
Thanks for all the detailed info.

This is a pretty convoluted call flow. You could streamline by changing the IDC entry for 585 to point to 685. This would eliminate the phantom DN 689 altogether.

The MARP phone for 597 has hunt and fdn set to 586, and lhk set to 1. 597 is on key 5, so will not forward or hunt off of the set.

I'm still not sure where you are trying to ultimately send this number. But I would check the other phones programmed with an appearance of 597 to see if one of them should be the MARP instead.
 
The goal was to be able to forward external calls from the 685 phone to the 597 MCR DN so it shouldn't have anything to do with the MARP at all right?

Keep in mind that if you dial 585 directly, the FDN calls 597 without a problem and if you manually forward 685 to 597, external calls work correctly. So basically, it is ONLY regular external calls that will NOT forward to 597 when 685 doesn't answer.

Is that as clear as mud? =)
 
Yes, that helps!

Try adding cls SFA to the i2004 in that case.
 
Thanks allenmac but still, no luck. Adding SFA did not work.
 
Check your RDR DATA in your CDB (Redirection Treatment)
Cheers!!
 
Did you get this figured out yet? If not, I may have the solution ... I would say it has something to do with your TGAR and NCOS not matching on every build. So, I would try 0 and 5 for your phantom instead of 1 and 0 like is currently programmed.
 
Don't forget, you will have to change the lhk on the 597 set to 5 in order for the forward and hunt settings to take effect.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top