Group Hunt Limitation

[entebo]

Hi all,

I have a question. I have 2 DNs defined in a Group Hunt PLDN. DNs are 2000 and 2001 and PLDN is 1500. I also used Call Forward All Calls feature for 2001 and forwared to another DN 2050.

When I call PLDN 1500, the first DN 2000 rings, and after defined unanswered rings, it should be supposed to go to 2001 and directly forwared to 2050. However, DN 2000 keeps ringing, which means it hunts by itself.

Is this design intent, is there a workaround to overcome this issue?

 

[bajangsa]

How is your hunt group programmed?

You can program the group, so a CFW phoneset in the group is logged out of the group.
Alternatively can the hunt group be programmed, so the CFW on the phoneset only takes the DN calls, the hunt group calls will still ring on the phoneset.

I dont remember the prompt, but if you program the hunt group via TM, can you in the General settings toggle "Call Forward All Calls" to achieve one or the other.

Also check FNA on the phonesets if you want the calls to go to the next one in the hunt group.

 

[entebo]

I put TNB of 2001 and output of GHT. As you see on Key 16, I forwared the DN 2001 to DN 2051. So, all the calles terminating on DN 2001 should be forwarded to 2051 automatically. When a hunt call terminates on 2000, it does not continue with 2001 because of CFW feature is used.

I dont use TM. I think this is design intent. Do you advise any workaround?

DES 1120
TN 252 0 00 04 VIRTUAL
TYPE 1120
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 000
CUR_ZONE 000
ERL 0
ECL 0
FDN 2051
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SFLT NO
CAC_MFC 0
CLS CTD FBD WTA LPR MTD FNA HTD TDD HFD CRPA
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLA VCE DRG1
POD DSX VMD SLKD CCSA-CSI SWD LND CNDA
CFTD SFA MRD DDV CNIA CDCA MSID DAPA BFED RCBD
ICDA CDMD LLCN MCTD CLBD AUTR
GPUA DPUA DNDD CFXA ARHD CLTD ASCD
CPFA CPTA ABDD CFHA FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USMD USRD ULAD CCBD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD VOLA VOUD CDMR ICRD MCDD T87D KEM3 MSNV FRA PKCH
AUTH 1
2
3
4
5
6
CPND_LANG ENG
RCO 0
HUNT
LPK 0
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 2001 0 MARP
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16 2051
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 13 APR 2009


MEM AVAIL: (U/P): 98966414 USED U P: 5259269 44138 TOT: 104269821
DISK SPACE NEEDED: 35 KBYTES
REQ prt

TYPE ffc

CUST 0

CODE pldn


CUST 00
FFCT NO
PLDN 1500
USE GPHT
LSNO 1
HTYP LIN
CFWI NO
MQUE ALL

 

[entebo]

I forgot to put GHT output:

REQ: prt

TYPE: ght

LSNO


GHLN 0001
GHT

PLDN
DNSZ 4
STOR 0 2000
STOR 1 2001
STOR 2
STOR 3
STOR 4

 

[PareshTC]

As the call keeps ringin at 2000 and doesnt follow the hunt group to 2001 in the first place, you will need to look at extn 2000 config and not 2001. Try and do a trace fo the call while its ringing at 2000.

Also paste the config for x2000

 

[entebo]

I think it is normal that DN 2000 keeps ringing because it is the only DN left in the Group Hunt List. The other DN 2001 in the Group Hunt List is using CFW feature to another extension.

When I try to get Call Trace from 2001, I receive nothing, becuase Hunting is now sending the call to DN 2001.

I just want to make sure if this is design intent and if there could be any workaround?

Output of DN 2000:

>ld 20


PT0000
REQ: prt

TYPE: 1120

TN 252 0 0 4

DATE

PAGE

DES

MODEL_NAME

EMULATED

KEM_RANGE


DES 1120
TN 252 0 00 04 VIRTUAL
TYPE 1120
CDEN 8D
CTYP XDLC
CUST 0
NUID
NHTN
CFG_ZONE 000
CUR_ZONE 000
ERL 0
ECL 0
FDN 2051
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SFLT NO
CAC_MFC 0
CLS CTD FBD WTA LPR MTD FNA HTD TDD HFD CRPA
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLA VCE DRG1
POD DSX VMD SLKD CCSA-CSI SWD LND CNDA
CFTD SFA MRD DDV CNIA CDCA MSID DAPA BFED RCBD
ICDA CDMD LLCN MCTD CLBD AUTR
GPUA DPUA DNDD CFXA ARHD CLTD ASCD
CPFA CPTA ABDD CFHA FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USMD USRD ULAD CCBD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN
FDSD NOVD VOLA VOUD CDMR ICRD MCDD T87D KEM3 MSNV FRA PKCH
AUTH 1
2
3
4
5
6
CPND_LANG ENG
RCO 0
HUNT 2051
LHK 0
LPK 0
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 2001 0 MARP
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16 2000
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 13 APR 2009


and also output of RDR data in CDB:

REQ PRT
TYPE: rdr

TYPE RDR_DATA
CUST


TYPE RDR_DATA
CUST 00
OPT CFO CFRD DSTD PVCA CWRD MCX
FNAD HNT
FNAT HNT
FNAL HNT
CFTA NO
CCFWDN
CFN0 2
CFN1 3
CFN2 3
DFN0 3
DFN1 3
DFN2 3
DNDH NO
TRCL 0
DFNR 3
CRT0 00 00 00 00
CRT1 00 00 00 00
CRT2 00 00 00 00
CRT3 00 00 00 00
DAY0
DAY1
DAY2
DAY3
HOLIDAY0
HOLIDAY1
HOLIDAY2
HOLIDAY3

 

[bajangsa]

I still think you should look at the hunt group. Here is a quote from Nortels documentation Document Number: 553-3001-306

Call Forward All Calls
When Group Hunt attempts to terminate on a DN, which has Call Forward All Calls active, it will continue with the next DN in the group if the attempted DN is busy, or if the DN is idle and the response to the Call Forward Ignore (CFWI) prompt in LD57 is NO.
If the attempted DN is idle and the response to the CFWI prompt in LD 57 is YES, then the system terminates Group Hunt and ring stations associated with the DN.

 

[entebo]

Yes, I also noticed that, but thought that maybe there is a workaround. Well, I think I should accept that this is design intent.