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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Hunting on Option 11
- Thread starter DonnaMP
- Start date
This feature allows a call which encounters a busy extension to automatically Hunt (forward) to a predefined DN. If the extension that is hunted to is also busy the system will look at the Hunt DN of that second set and Hunt (forward) again to that DN. This continues until an idle DN is found. The Hunt DN is set on a per extension basis and cannot be changed or disabled by the extension user.
For systems that have Meridian Mail equipped, the extension user can have their calls hunt on busy to Meridian Mail in the same way as hunting to another extension. This is achieved by specifying the access DN for Mail instead of an extension number. Hunting to Meridian Mail will however preclude the use of some features like Ring Again.
The maximum number of hunt steps is as follows :-
For Option 11, 51, 61 systems 18 steps
For Option 71 & 81 systems 30 steps
Hunting Chains
By linking the Hunt DNs together in this fashion various types of hunting chain can be achieved :-
Linear
Linear Hunting starts at the called DN and continues through to the last DN in the chain, therefore a call to 3421 will hunt to 5682 and 4791 only.
Circular
For Circular Hunting the last DN in the chain is given the first DN in the chain as its hunt number. When a call encounters a busy extension the system will step along the chain until it returns to the original number dialled.
Secretarial
Secretarial Hunting uses a specific DN, as the last DN in two or more hunt chains.
Feature Implementation
The feature is assigned to both analogue and digital sets by allowing the feature in the Class of Service and also defining the Hunt directory number.
Example
In this example Hunting has been assigned to an analogue TN 9 3 with the calls to be forwarded to DN 2432.
LD 10
Load Program 10.
REQ CHG Change
TYPE 500
TN 9 3
ECHG YES Easy Change allowed
ITEM HUNT 2432 Hunt to extension 2432 when busy
ITEM CLS HTA Allow Hunting
ITEM Carriage return back to REQ prompt
REQ END Exit program10
LD 11
Load Program 11.
REQ CHG Change
TYPE 2616 Telephone type
TN 7 4
ECHG YES Easy Change allowed
ITEM HUNT 2432 Hunt to extension 2432 when busy
ITEM CLS HTA Allow Hunting
ITEM Carriage return back to REQ prompt
REQ END Exit program10
For systems that have Meridian Mail equipped, the extension user can have their calls hunt on busy to Meridian Mail in the same way as hunting to another extension. This is achieved by specifying the access DN for Mail instead of an extension number. Hunting to Meridian Mail will however preclude the use of some features like Ring Again.
The maximum number of hunt steps is as follows :-
For Option 11, 51, 61 systems 18 steps
For Option 71 & 81 systems 30 steps
Hunting Chains
By linking the Hunt DNs together in this fashion various types of hunting chain can be achieved :-
Linear
Linear Hunting starts at the called DN and continues through to the last DN in the chain, therefore a call to 3421 will hunt to 5682 and 4791 only.
Circular
For Circular Hunting the last DN in the chain is given the first DN in the chain as its hunt number. When a call encounters a busy extension the system will step along the chain until it returns to the original number dialled.
Secretarial
Secretarial Hunting uses a specific DN, as the last DN in two or more hunt chains.
Feature Implementation
The feature is assigned to both analogue and digital sets by allowing the feature in the Class of Service and also defining the Hunt directory number.
Example
In this example Hunting has been assigned to an analogue TN 9 3 with the calls to be forwarded to DN 2432.
LD 10
Load Program 10.
REQ CHG Change
TYPE 500
TN 9 3
ECHG YES Easy Change allowed
ITEM HUNT 2432 Hunt to extension 2432 when busy
ITEM CLS HTA Allow Hunting
ITEM Carriage return back to REQ prompt
REQ END Exit program10
LD 11
Load Program 11.
REQ CHG Change
TYPE 2616 Telephone type
TN 7 4
ECHG YES Easy Change allowed
ITEM HUNT 2432 Hunt to extension 2432 when busy
ITEM CLS HTA Allow Hunting
ITEM Carriage return back to REQ prompt
REQ END Exit program10
- Thread starter
- #4
DES 5
TN 005 0 00 00
TYPE 3904
CDEN 8D
CUST 0
KBA 1
ERL 0
FDN 2699
TGAR 1
LDN NO
NCOS 4
SGRP 0
RNPG 1
SCI 0
SSU
LNRS 16
XLST
CLS UNR FBD WTA LPR PUA MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRA NID OLD VCE DRG1
POD DSX VMD SLKD CCSD SWD LNA CNDA
CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHA FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC MCBN
CDMR MCDD T87D PKCH
CPND_LANG ENG
RCO 0
HUNT 2699
LHK 1
LPK 1
PLEV 02
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 2614 0 MARP
CPND
NAME bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
XPLN 27
DISPLAY_FMT FIRST,LAST
01 SCR 6614 D MARP
Wow, that's detailed.
The LD 21 RDR_DATA is where system-wide redirection settings are made
LD 21
REQ PRT
TYPE RDR
There are not that many to study - post if needed
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
The LD 21 RDR_DATA is where system-wide redirection settings are made
LD 21
REQ PRT
TYPE RDR
There are not that many to study - post if needed
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
- Thread starter
- #6
REQ PRT
TYPE: rdr
TYPE RDR_DATA
CUST 0
TYPE RDR_DATA
CUST 00
OPT CFF CFRD PVCD CWRD MCI
FNAD FDN
FNAT FDN
FNAL FDN
CFTA NO
CCFWDN
CFN0 4
CFN1 4
CFN2 4
DFN0 4
DFN1 4
DFN2 4
DNDH NO
MDID YES
NDID YES
MWFB YES
TRCL 0
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
If the problem is "system-wide" then I can't see why.
Another thing to check is do you have "Do Not Disturb" activated? I doubt that is it though...
If the problem is just this TN, first I'd verify it isn't CFW'd. If not, I'd OUT and rebuild it, that could be a solution. Everything looks perfect to me.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
Another thing to check is do you have "Do Not Disturb" activated? I doubt that is it though...
If the problem is just this TN, first I'd verify it isn't CFW'd. If not, I'd OUT and rebuild it, that could be a solution. Everything looks perfect to me.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
You should also call 2699 directly to make sure THAT isn't the problem 
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
I spoke to DonnaMP and this is an odd one. There are a couple things at play. It's a distant office she is working remotely, so testing isn't easy with the end users. There is also some chance the Telco has a "paths" issue because there is some Telco RCF involved. An unavoidable configuration at this time...due to unique business changes.
One number (a main listed tel in the same DID range) on one TN does seem to "Hunt". So the step she is taking now is to OUT a non-working and rebuild to see if that changes anything. Then of course, re-try the test with an end-user to see if the problem is internal *and* external.
DonnaMP knows her way around the system, so whatever it is, it's not an easy one.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
One number (a main listed tel in the same DID range) on one TN does seem to "Hunt". So the step she is taking now is to OUT a non-working and rebuild to see if that changes anything. Then of course, re-try the test with an end-user to see if the problem is internal *and* external.
DonnaMP knows her way around the system, so whatever it is, it's not an easy one.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
FBA/FBD is not what it sounds like.
FBA says "DID calls should go the the Attendant Console upon Busy" Even though HTA takes precedence, it is still a feature with rooms from 30 years ago.
So: It is DID calls only; It can only send calls to an Attendant; Hunt takes precedence over FBA. If the HUNT is Busy, then the Attendant has no idea why they are getting calls for this user, so all they do is send them back/camp them on. Nothing was gained.
I can't think of any good applications for FBA. All TNs should generally have FBD.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
FBA says "DID calls should go the the Attendant Console upon Busy" Even though HTA takes precedence, it is still a feature with rooms from 30 years ago.
So: It is DID calls only; It can only send calls to an Attendant; Hunt takes precedence over FBA. If the HUNT is Busy, then the Attendant has no idea why they are getting calls for this user, so all they do is send them back/camp them on. Nothing was gained.
I can't think of any good applications for FBA. All TNs should generally have FBD.
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
rooms from 30 years ago" - That should be "roots" from 30 years ago
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
- Status
Similar threads
- Locked
- Question
