DN (not TN) hunting on Meridian 1 (option 11e)
Charlie Root
Hello.
We've got an Option 11e and want to do hunting between DNs (directory numbers).
The problem is that all of the hunting options we've been able to find are
specified on a TN (station set) basis. This works fine for things like
voice mail, but doesn't seem to allow for seperate groups of DNs on a phone
that will hunt.
Specifically what we'd like to do is assign a couple of single call ringing
DNs that would be shared across a group of phones. When a call comes into
the base number (for that group, not any particular phone), the call would
ring on the first available DN in that hunt group. The hunt group needs to
be completely unrelated to the short hunt sequence of the phone. Think of
it like you would if you had a group of CO lines with hunting that had a
shared appearance on a bunch of 1A2 key telephones.
We think that a feature called "Group Hunt" (defined in LD 18) may solve
our problem. However, we haven't been able to find *anything* about the
group hunt list in the Nortel documentation. Also, we can't figure out what
the Pilot DN in a group hunt list is or how to set it.
Any help would be greatly appreciated.
Thanks.
Cheers,
Brian
Mark Fletcher
Charlie Root wrote:
>
> Hello.
>
> We've got an Option 11e and want to do hunting between DNs (directory numbers).
> The problem is that all of the hunting options we've been able to find are
> specified on a TN (station set) basis. This works fine for things like
> voice mail, but doesn't seem to allow for seperate groups of DNs on a phone
> that will hunt.
Brian-
Seems what you might be looking for is an MCR key, and not an SCR key.
This DN would not be affected by the hunt feature as lonk as the LHK
(Last Hunt Key) was set to a key number lower than that of the MCR.
An MCR DN will ring simultaneously on all of the sets programmed with an
MCR appearance.
Hope that this helps or solves your problem.
--
========================================================
Mark Fletcher Bell Atlantic Meridian Systems
Adv. System Technician Parsippany, New Jersey
--------------------------------------------------------
*** All opinions expressed are mine, etc........... ***
Brian Cuthie
In article <31BB91...@planet.net>,
Mark Fletcher <mfl...@planet.net> wrote:
>Charlie Root wrote:
>>
>> Hello.
>>
>> We've got an Option 11e and want to do hunting between DNs (directory numbers).
>> The problem is that all of the hunting options we've been able to find are
>> specified on a TN (station set) basis. This works fine for things like
>> voice mail, but doesn't seem to allow for seperate groups of DNs on a phone
>> that will hunt.
>
>Brian-
>
>Seems what you might be looking for is an MCR key, and not an SCR key.
>This DN would not be affected by the hunt feature as lonk as the LHK
>(Last Hunt Key) was set to a key number lower than that of the MCR.
>
>An MCR DN will ring simultaneously on all of the sets programmed with an
>MCR appearance.
>
Mark,
Thanks for the suggestion. However, the problem with MCR is that if I'm the
only guy in the office it becomes difficult to answer a second call to the
same number. This is why I would rather use SCR and have the call hunt up
to another key. Short hunting doesn't work, though, because these DNs will
be shared by phones that otherwise have unrelated DNs in their short hunt
list. Once a call hunts up to the shared call appearances, everyone who
shares that appearance will have their phone ring; even though the call
was really for a number unrelated to the shared DNs.
BTW: Do you know how the GHT list in LD 18 is used? I can't find it
documented anywhere (other than in the LD 18 references, which is nearly
useless). It looks vaguely like it might do what I want since it's the
only thing I've seen that's hunt related that uses a list of DNs. I've
been able to define the list, but I have no idea how you set the
"Pilot DN" entry for the list. Or, for that matter, what the GHT feature
really does.
Cheers,
Brian
Guido_Zijlstra
ro...@homer.systemix.com (Charlie Root) wrote:
>We think that a feature called "Group Hunt" (defined in LD 18) may solve
>our problem. However, we haven't been able to find *anything* about the
>group hunt list in the Nortel documentation. Also, we can't figure out what
>the Pilot DN in a group hunt list is or how to set it.
OK, This is how it works.
The Pilot DN (PLDN) is the group number. This is the number you dial. It is
setup in LD 57, the FFC's. This is how you make a group which is accessed
by dialing 1234 and hunts DNs 2222, 3333 and 4444..
First in LD 18 make the list :
LD 18 REQ NEW ; Offcourse
TYPE GHT ; A group-hunt list
LSNO 1001 ; A list-number.(Shares # with SCL lists)
CUST 0 ; Probably
DNSZ 4 ; The length of your extensions
SIZE 4 ; The number of DNs in the list
STOR 0 2222 ; The DNs themselfs.
STOR 1 3333
STOR 2 4444
Then we need to define the PLDN (Group Number)
LD 57 REQ CHG ; Can't new
TYPE FFC ; That's what it is
CUST 0 ; Probably
FFCT ; Just return
CODE PLDN ; What we want
PLDN 1234 ; The group Number
USE GPHT ; Use this for group hunt
LSNO 1001 ; The list number we made in LD18
HTYP RRB ; How do we like to hunt
CFWI YES ; Skip set ins CFWAC
MQUE ALL ; Queue all calls
PLDN ; Just return
CODE ; Just return
Now, when you call DN1234, DNs 2222,3333 and 4444 should be tried in turn.
Prompt USE : can be PLDN (as shown) or SCLU. The latter giving dial-access
to speedcall lists. This enables you to use multiple speedcall lists be
dialing a prefix.
Prompt HTYP : can by LIN or RRB. LIN = Lineair, allways start hunting a
stor 0 and then down the list. RRB = Round-Robin, start hunting first at
stor 0, then at stor 1 for the next call, then at stor 2 for the third call
etc.
Prompt CFWI : can be yes or no. YES : Skip sets the have CFWAC activated.
NO, DO ring sets that have CFWAC actived.
Prompt MQUE : can be 0,1 or ALL. 0 : Do not queue calls. 1 : Queue 1 call.
ALL : queue all calls. With X11R20 and up, there is another one that lets
you queue a number of calls equal to the number of dn's in the list, but
the mnemonic escapes me.
There or two other FFC's (and for digital sets a key) to enable users to
put themselfs into or outoff the grouphunt list.
JUST A BIT OF WARNING.
We have extensive experience with group hunting and have found that when a
set has one or more of it's dn's in a grouphunt list you SHOULD NOT CHANGE
THE SET. First remove the dn's from the list(s) and the change the set.
Also do NOT REMOVE SETS/DN's which have the grouphunt deactivate
key/feature active.
Both of these things can cause datacorruption in the form that the group
and/or set doesn't work anymore. If you observe the rule that all dn's
should be activated and taken out of the list before changing all should be
ok.
I hope this helps, if you need more info, give me a shout.
Tnx,
Guido
G. Zijlstra, Sometimes i wonder if i'm on the right planet.
e-mail : g...@euronet.nl
CumpuServe : 100340,3525
fido : 2:500.8.1826
Mark Fletcher
Brian Cuthie wrote:
> This is why I would rather use SCR and have the call hunt up
> to another key. Short hunting doesn't work, though, because these DNs will
> be shared by phones that otherwise have unrelated DNs in their short hunt
> list. Once a call hunts up to the shared call appearances, everyone who
> shares that appearance will have their phone ring; even though the call
> was really for a number unrelated to the shared DNs.
OK Brian, now I understand what you are trying to do! Off the top of my
head, here's a "quick fix" they may be a better one....
Set up a "Virtual phone" Software only.
Key 0 SCR 5000 (The Pilot Number)
Key 1 SCR 5001
Key 2 SCR 5003 etc.....
Have the set LHK to the last key in the Virtual Group of DN's.
Do appearances of the line keys on the other sets in the REAL group.
With the virtual set being the MARP, the hunting patter will follow THAT
set, but the ringing will also follow on the other REAL sets not
affected by any hunting set up on them. You may get a wierd interaction
if someone call forwards their phone or something, but I don't think so
off the top of my head. Follow me? It might just do what you want.
> BTW: Do you know how the GHT list in LD 18 is used? I can't find it
> documented anywhere (other than in the LD 18 references, which is nearly
> useless).
Group call is not for you. What group call does is ring all of the DN's
in the group if any of them are dialed (No Pilot for the group). Other
parties in the group can pick up and join the call in progress. Kinda
like a hardwired intercom emulation. Definately not what your looking
for.
Hope this helps!
Ernie Holling
Brian
What release is your Opt 11 on??
Ernie
In article <4pg7po$g...@homer.systemix.com>, Brian Cuthie (br...@homer.systemix.com) writes:
>In article <31BB91...@planet.net>,
>Mark Fletcher <mfl...@planet.net> wrote:
>>Charlie Root wrote:
>>>
>>> Hello.
>>>
>>> We've got an Option 11e and want to do hunting between DNs (directory numbers).
>>> The problem is that all of the hunting options we've been able to find are
>>> specified on a TN (station set) basis. This works fine for things like
>>> voice mail, but doesn't seem to allow for seperate groups of DNs on a phone
>>> that will hunt.
>>
>>Brian-
>>
>>Seems what you might be looking for is an MCR key, and not an SCR key.
>>This DN would not be affected by the hunt feature as lonk as the LHK
>>(Last Hunt Key) was set to a key number lower than that of the MCR.
>>
>>An MCR DN will ring simultaneously on all of the sets programmed with an
>>MCR appearance.
>>
>
>Mark,
>
>Thanks for the suggestion. However, the problem with MCR is that if I'm the
>only guy in the office it becomes difficult to answer a second call to the
>same number. This is why I would rather use SCR and have the call hunt up
>to another key. Short hunting doesn't work, though, because these DNs will
>be shared by phones that otherwise have unrelated DNs in their short hunt
>list. Once a call hunts up to the shared call appearances, everyone who
>shares that appearance will have their phone ring; even though the call
>was really for a number unrelated to the shared DNs.
>
>BTW: Do you know how the GHT list in LD 18 is used? I can't find it
>documented anywhere (other than in the LD 18 references, which is nearly