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

Group Voicemail MWI 1

Status
Not open for further replies.

mitelmmaniac

Technical User
Feb 9, 2009
83
GB
Hi,

I have about 80 group voicemail boxes (multiple extns going to 1 mailbox) across 14 3300mxe controllers on NuPoint. I have forwarded the extns to a path, which then has an interflow number of a dummy key which is cfwd always to v/m. A dummy agent group with queue callers to path when no agents logged in. this sends all extns that are pointed at this path to the same mailbox, perfect. The 3300's are clustered. so all dummy numbers are named to be able to forward to them as they are all located on 1 controller (same as NuPoint).

The problem i have is trying to put a MWI key on one phone per group... When trying to add the mailbox number (same as forwarded dummy number)as a mwi key it tells me the directory number is in use elsewhere (remote Dir). is there any way you can think around this?

sorry its so long..tried to get as much info in.

Thanks
MM

Desk Jockey Lunacy
 
Option A - Make the first routing point a keyline DN that is always forwarded to the setup you have already built. This way you can accociate the MWI with the Keyline without otherwise changing the setup.

Option B - Nupoint can broadcast MWI status from 1 MB to Another. FCOS option bit 122 (i think). Have 1 MB take the message and another set the lamp.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Thanks for the reply KWB.

To be honest I can't remember why I had to give the dummy numbers names. The extensions get forwarded to the path which obviously has to be named and then the path has the dummy number as an interflow, but its on the same 3300, so now I can't think why I would need to name the dummy numbers??

Desk Jockey Lunacy
 
I know why i did it. If i try and create a MWI Key with the mailbox number (same as interflow dummy) it says it doesnt exist as it can see it.

The dummy numbers are keylines spread over 2 dummy phones.

Extn ---> Call Re-route 1st Alt ---> Path (no agents logged in)--->goes to interflow----> interflow is a dummy key on dummy extn----> Call Re-route always to voicemail.

mailbox matches dummy number. Does this make sense?

Desk Jockey Lunacy
 
KWB,
How do i configure option b.. Done the fcos bit.

thanks

Desk Jockey Lunacy
 
With the information you first provided I was assuming that the MB was associated with the Path. MWI keys cannot be associated with Paths and thus your problem.

Now that I know the MB is associated with a keyline.

I am assuming that your issue is that the keylines are on a separate system than the MWI key you are trying to program.

Without completely rebuilding your setup, I can only offer bandaid solutions.

1 - Create a Dummy extension on system 2 where the MWI is required. DN does not matter other than it can not match any other existing. You must name it to have the extension # propogated to all systems

2 - (Guessing this might work) Add the new dn as an alternate extension in the original mailbox.

3 - Use broadcast MWI - lets see if option 2 works before I go into detail here.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Thanks again for replying..

I've suggested they use email as a notification.. They can create a group with a few admin people in and we can email that.. Saves complete reprogramming.

Thanks buddy

Desk Jockey Lunacy
 
Works for me.

If you want, I could tell you how I would have set it up.

Assuming I can use as many mailboxes as I want that is.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
If you don't mind I would be very gratefull. Quite frustrating not being able to resolve it.

Yep as many as you like they are only using 150.

Desk Jockey Lunacy
 
Simplest solution for group mailboxes where qty of mailboxes is not a factor.

Every phone has a mailbox and every phone is routed to VM on not answer.

Every mailbox that needs to be steered to a group MB has the FCOS - Rotational. I would modify the FCOS to deny access.

For Every Rotational Mailbox - Personal Distribution list 1 would have 1 member and that member would be the Group Mailbox.

The group mailbox would be associated with a keyline on the system where the MWI key is required.

Group MWI keys would be programmed on the stations that route to the Group MB.

Call Flow -
Station rings
Station routes to VM
VM = Rotational MB - No Greeting - route to Dist List 1 Member (Group MB)
Group MB answers, plays greeting and takes message
Group MB send MWI
Keyline associated with Group MB
MWI keys associated with key line start to flash
User presses MWI key
User logs into Goup MB abd retrieves message
Group MB turns off MWI

This is but 1 solution to your problem. There are others, but this is the least creative, least steps.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Thanks very much for that buddy. Makes perfect sense.
Favour owed

Desk Jockey Lunacy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top