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

DID to 2 different AA menus 1

Status
Not open for further replies.

wacker43

Technical User
Jun 5, 2007
61
US
I am trying to send a DID number to an IP console during Day mode, main menu 8000 during night1 and main menu mode 8005 at night2. I have tried setting my DID up as a phantom, and using reroute for my services, and made 8000, and 8005 voice hunt groups and changed COS to cfna to my VM and I get a reorder. I have tried to ACD to VM and use Unavailable to my VM hunt group and I get the canned AA. I am using embedded VM. Any suggestions? Thanks
 
Make a huntgroup (without members) and set the always alternative for day night1 and night 2 to where you want




ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Make a hunt group for 8000 and 8005 and then send them to VM hunt group using call reroute? or 2 different hunt groups?
 
When I try to send it to 8000 or 8005 on always alternative, it says dn is not assigned.... ?
 
There is a How To Doc on the FAQ page.

This doc was generated directly from a Mitel bulletin.

faq1329-6743

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
To get the menu node working correctly so you can "route to it" just create 2 nametag hunt groups 1 X 8000 and 1 X 8005 and reroute all to VMS.

Then you can either use kwbmitel FAQ or:

Present the ddi to another dummy hunt group. Set day to the console key night 1 to 8000 and night 2 to 8005. BUT MAKE SURE YOU@VE SET UP 8000 and 8005 AS NAMETAG HUNT GROUPS FIRST.

It must be nametag groups as the strip the original dialed digits and replace with it's own, so when it hits VMS it doesn't use the original dialled digits
 
There have been some inconsistancies with Nametag Hunt Group routing not always doing what it's told. More specifically when routing immediately as opposed to routing on ring no answer or busy.

I don't know the specific scenario's when it fails but the Mitel method using ACD groups has never failed in my experience.

Here is an example of Nametag not working as expected
thread1329-1414636

Here is another
thread1329-1366664





*******************************************************
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