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

MiVoice 8.0 NameTag Hunt Groups

Status
Not open for further replies.

steveycarr

Technical User
Apr 23, 2003
132
GB
Guys,

MiVoice 8.0 SP3 PR2

Think I might be going mad but for years now I've been using Name Tag Hunt Groups to override Voicemail and Hunt Group re-routing integration rules. For example a Name Tag HG #150 call re-routed to Voicemail should when called drop straight into the Mailbox of X150 assuming X150 has a Mailbox set up with a Greeting. With the Software 8.0 SP3 PR2 I can't seem to get this working, although it works on 8.0 SP3 PR1 and on 7.2 Software.

Has anyone else experienced this or has there been some change I've missed.

Any Ideas would be much appreciated.

Steve



!ExtraDunce
 
name tag should be *150 for embedded vmail not #

If I never did anything I'd never done before , I'd never do anything.....

 
@BillZ66, I believe Both * and # work as leading digits but I've personally never tested #.

Of Course, something may have changed as well without me noticing.

@steveycarr. Nametag groups are not the best way to do this as once you use a nametag, it is maintained throughout the call. If the Destination MB is a Menu node then it is especially bad.

It is more work, but you should use the ACD method to break the integration.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Gents,

Thanks for your replies, as suggested both * and # do work.... and I've tried it now on both releases of 8.0 Software so that blew my theory out of the window.

As mentioned I've used this loads of times before because I can call reroute the Main I/C number away from an Embedded AA or HG simply into a Night Mailbox and add an MWI key to any phone I need to.

However on this switch I'm struggling. I'll need to have a closer look again in case I've missed something. I've not had much experience with ACD as most of my switches are in the small to medium market.

Many Thanks for your input.

Steve





!ExtraDunce
 
Thanks Stevey and Kwb , learnt something new .. never know that # worked as well

just tried it on our system and it Works on 8.0 SP3 PR1 14.0.3.22
miVb has had a few bugs lately so it wouldn't surprise me if its just that load

do you have a name on the name tag? found this in one of the release notes for an older version (clutching at straws)

MN00555164 - VM integration via a name tag hunt group does not work if the name tag hunt group has a tel. dir entry
SYMPTOMS (REPORTED IN SW LOAD - 13.0.1.28)
Setup: Nametag hunt group is rerouted always to VM. DN for name tag hunt group has a tel. dir. entry with a name.
Calling the nametag hunt group works OK; it integrates with the proper greeting
The problem is a blind transfer to the name tag hunt group. The caller goes to the incorrect greeting.

WORKAROUND= Remove the name from the name tag hunt group



If I never did anything I'd never done before , I'd never do anything.....

 
Guys

Once again thank you for your input tried removing the name but it's still not working. I may have to try the ACD solution. Can anyone point me the right direction as I've no exposure to ACD on Mitel only on Cs1k and ISDX.

Basically all I have is a embedded AA and I want to call reroute incoming calls to a generic mailbox when system is in Night Service.

Steve

!ExtraDunce
 
we normally create a skill group with no members set to queue with no agents
then create an acd path - apply that skill group as its primary
set interflow 1 second to nametage hunt group *mailbox ( rerouted to voicermail)

send calls to acd path , it should then interflow to name tag and end up in voicemail as required

If I never did anything I'd never done before , I'd never do anything.....

 
Guys,

Used the above ACD method and thankfully my issue has been resolved. Still cant understand how a tried and tested message which I've been using for years wont work but its not worth losing any sleep over. Once again many thanks.

Steve

!ExtraDunce
 
Probably an issue with COS1 on that system not having something enabled.
Important to remember now that Mitel has added COS to RG's and ACD paths it actually does something :)
 
yes it does

we recently took over a customer and upgraded them
unbeknown to us the previous configurator had set a destination on 1st alternative pattern 1
after upgrade the ring groups and hunt groups were all following it

If I never did anything I'd never done before , I'd never do anything.....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top