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!

Transfer to busy dn doesn't hunt to an idle dn on set? 2

Status
Not open for further replies.

cypher0

Programmer
Mar 7, 2011
20
0
0
US
Is it expected that a transfer to a busy dn would -not- hunt to an open, idle dn on the set, even if lhk is set appropriately?

Is this also expected behavior from the console?

We have a console attendant who is saying that when trying to transfer some external calls to an internal user, there are certain users who she often finds that when she goes to transfer the call, it stays on the console and doesn't transfer.

The users she is experiencing this with are often on the phone for extended periods of time. My assumption is that a transfer is direct and rollover hunting won't work that way... is that true? Can it be made to hunt to an idle dn if we want it to?

Thanks,

-C
 
Is it expected that a transfer to a busy dn would -not- hunt to an open, idle dn on the set, even if lhk is set appropriately?

If the HUNT and LHK is set properly and the number you're calling is busy, it will HUNT to a the LHK then to VM or whatever the HUNT target is. (note: pay attention to the MARP, plus LHK will not hunt over other feature keys)

Same goes for the console, except on the console you can have a busy verify key to check the target.

You'll have to check the programming on the set of the called person and verify hunt and lhk is set properly.
 
So you're saying that a transfer either from a console or from another phone would hunt the same way a normal dialed call would?

Here is one of the sets that our console attendant has reported this issue on:

DES 200711
TN 020 0 07 11
TYPE 3905
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
FDN 7000
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
CLS CTD FBD WTA LPR MTD FND HTD ADD CRPD STSD
MWA LMPN RMMO SMWA AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXD ARHD 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 PRED MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 7000
LHK 1
PLEV 02
PUID
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
RMTN
KEY 00 SCR 2033 0 MARP
CPND
NAME Joe Jeppson
XPLN 27
DISPLAY_FMT FIRST,LAST
01 SCR 2233 0 MARP
CPND
NAME Joe Jeppson
XPLN 27
DISPLAY_FMT FIRST,LAST
02 ADL 16
03 ADL 16
04 ADL 16
05 ADL 16
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 4
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 18 MAR 2011

It looks right to me, but I'm still pretty new with this system. The attendant says she is transferring to 2033 (his key 0). 7000 goes to Call Pilot.

Thanks,

-C
 
Just as rajbabu12 states, without HTA and/or FNA, that set is not hunting or forwarding anywhere.
 
*sheepish grin* Seems obvious after the fact, of course. :) Thanks, appreciate the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top