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

name tag hunt groups -cli

Status
Not open for further replies.

james1982

Technical User
Nov 14, 2003
441
GB
We have a site that relies heavily on the use of name tag hunt groups, the site in question has numerous different companies onsite - the name tag huntgroups enables us to display the name to a sole receptionist so she can answer calls in the correct manner.

I have had a problem previously where the company wanted all voicemails on companies main ddi lines to be left on a reception voicemail box (the customer is adamant this is how it used to work), I believe and according to Mitel name tag hunt groups carry cli and therefore when the call goes to voicemail it will always search for a mailbox with the same ID as the name tag huntgroup, if there isint one it will go to a generic mitel vm msg.
My question is the customer is adamant this previously used to work where the call came in via a nametag hunt group and then went to the reception voicemail, this goes against what mitel state and my findings.

The only thing I can think is about 5 months ago we upgraded to rel 8 ur 5, does anyone have a controller on rel 7 that can test the use of name tag huntgroups and whether the cli is carried or not?

3300mxe currently rel 8 ur 5, previously rel 7

Thanks
 
james1982,

You are right NameTag hunt carry/forward the CLI of that hunt group, so it would pass that information into the voicemail system.

If the customer is saying it didn't work that way in Rel7, it could of been a bug.

__________________________

There is no 'I' in 'Team'
__________________________
 
Regardless of how it worked before, you can make it work now.

What you need is 1 additional nametag group as the last hop before voicemail. The voicemail will then integrate with the last hop number and forget the previous numbers.

See the following FAQ faq1329-7197



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
KWBMitel - thats brilliant thanks.
If the mailbox corresponds to a nametag huntgroup and not a physical extension is there anyway to get the MWI lamp to light on a physical extension.
The user doesnt want MWI on key appearances she wants the actual lamp on a phone to light.

Hope this makes sense and thanks for the reply
 
Yes, read the FAQ again.

to force the call into an existing mailbox associated with the prime line of a phone the nametag group would be numbered *(Star) plus the mailbox/ext number.

e.g.
inbound number is 1111
1st Nametag is 2222
Console LDN is 3333
Phone/Mailbox for general delivery is 1234
Last nametag is *1234

For this many steps you may need to utilize forwarding but here is how I would design it.

1111 would be a speed call, actual digits = 2222
2222 Nametag group - Always route = 3333, 1st Alt = *1234
3333 Console LDN - Day = No route, Night route to *1234
1234 = Extension/Mailbox with General Delivery Greeting
*1234 = Nametag Group (May Need to be forwarded to VM, always route to VM)

To forward a hunt group you will need a phone with 3rd party call forward enabled and use the FAC for CFWD Third Party.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
KwbMitel : I have been working on this but am struggling to get it working, my senario is as follows.
Current Setup:-
inbound number 3260
3260 Name tag hunt group with always reroute day to 3100
3100 - IP console
1st alternative - 1111 (voicemail) - here the admin box system greeting is to play that states all the lines are busy press 1 to leave a msg

Mailbox 1 is assocaited with IP extn 3102, if the user presses 1 I need the call to go to this mailbox, leave a msg and light the MWI.
This fails when the call goes to vm I simply get a default greeting as there is no mailbox associated with 3260.

What I have tried:-
inbound number 3260
name tag huntgroup 3260 with always reroute day to 3100
1st alternative nametag hunt group *3102, 2nd alt 1111 voicemail

The above failed - i simply got the default system voicemail greeting
Ive also rerouted *3102 always to vm, when calling *3102 I dont get IP extn 3102 mailbox, again I get a default system vm msg.

Unsure if this is because 3102's mailbox has an ID of 1 and not 3102.

I dont believe the setup is possible, I think the need for the admin greeting stating press 1 to leave a msg is causing the complication.

Can KWBMitel or anyone else adivse.

Thanks

 
Yes you have correctly identified the issue.

Question, If you get this working, will you still require the Dial 1 to leave a message option?

My suggestion is to get rid of Mailbox 1 and instead create mailbox 3102 associated with Ext 3102.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top