Message Waiting Indicator and General Question about Ports 1

[TecknowJoe]

I am an avaya transplant, so be patient.... I have been impressed and pleased with the mitel product to date. Not a phone guy by nature, but certainly know my way around. Here is a question I have that I would like an answer to:

Currently, our main company DID# is setup as a speedcall to a HG (xxxx), which has 6 members (lines 1-6). The call rerouting for the hunt group points to the VM ports associated w/ the General MB for the main line. I want to add a MWI for the general MB, however, I know we can not since the general mailbox # is the hunt group number (I know we can not have MWI for groups).

what can we do to get MWI for the general mailbox? My thought is the following: remove huntgroup xxx and speed call mainDID#; add huntgroup (mainDID#) w/ the 6 members mentioned above (lines 1-6); modify the call rerouting assignment for mainDID# (now the HG) to match previous HG (xxxx) setup; add a phantom key so we can add MWI for the general mailbox

If that is not accurate, what am I missing? and why?

Port Questions: How/Where do you go in 3300 or NuPoint to determine which ports/extensions are assigned for VM. I mean, I see in the 3300 where everything is programmed, but how does NuPoint know how these #'s are associated?? I seem to have a disconnect on this one....

Also phantom extensions: I know how to create the buttons, but am confused as to where how you setup the phantom extension/board/card?? concept just hasn't clicked with me

 

[kwbMitel]

Currently, our main company DID# is setup as a speedcall to a HG (xxxx), which has 6 members (lines 1-6). The call rerouting for the hunt group points to the VM ports associated w/ the General MB for the main line. I want to add a MWI for the general MB, however, I know we can not since the general mailbox # is the hunt group number (I know we can not have MWI for groups).

Actually, you can have a MWI for a huntgroup. The system will turn on the lamp for either the first member of the huntgroup OR the first phone programmed with the appearance of the first member of the HG. This can be very confusing and should be avoided if at all possible.

what can we do to get MWI for the general mailbox? My thought is the following: remove huntgroup xxx and speed call mainDID#; add huntgroup (mainDID#) w/ the 6 members mentioned above (lines 1-6); modify the call rerouting assignment for mainDID# (now the HG) to match previous HG (xxxx) setup; add a phantom key so we can add MWI for the general mailbox

If I am following your description above, then I believe it will work.
Existing = SD=>HG=>VM=>MWI issue
Proposed = SD=>PHTM=>HG=>VM=>MWI for PHTM

If the proposed is different than your intent, try this, it will work.

Additionally, with a Nupoint, there are options to broadcast MWI status to multiple different ext's. Personally, I like to keep it simple though.

Port Questions: How/Where do you go in 3300 or NuPoint to determine which ports/extensions are assigned for VM. I mean, I see in the 3300 where everything is programmed, but how does NuPoint know how these #'s are associated?? I seem to have a disconnect on this one....

In the Nupoint in the Offline configuration under line groups you will find the lines defined by Nupoint Port and Mapped Extension e.g. 1:0:0 = 1001, 1:0:1 = 1002, 1:0:2 = 1003.

Also phantom extensions: I know how to create the buttons, but am confused as to where how you setup the phantom extension/board/card?? concept just hasn't clicked with me

the Mitel does not require a physical port for a phantom extension. Creating a key on a phone is sufficient for most applications. I typically create a 5224IP set with a dual PKM which allows me up to 120 programmable DN's.










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

 

[TecknowJoe]

Thanks for such a quick response! And this is where my apologies come in as this is the last I feel I need to grasp.

"Existing = SD=>HG=>VM=>MWI issue" / "Proposed = SD=>PHTM=>HG=>VM=>MWI for PHTM".... Existing is correct. My proposed was looking more like HG=>VM=>MWI; There would be no need for a speed dial; the phantom was so that I could program MWI. However, the more i look at this, I sit here and say, do I really need the PHTM phone built? I guess I do for the MWI to work, yes?

As far as the NuPoint ports, I will check it out but I think that clarifies alot for me!

and quickly about phantom: I know it doesn't require physical port and that a button is sufficient. My fear w/ the button method is accidental delete. So if I decide to create a 5224 (in this case) where am I assigning the device? phantom cabinet w/ the phantom # associated w/ the mailbox # (that was removed in the proposed method above?

ok, that should do it. thanks again

 

[kwbMitel]

"Existing = SD=>HG=>VM=>MWI issue" / "Proposed = SD=>PHTM=>HG=>VM=>MWI for PHTM".... Existing is correct. My proposed was looking more like HG=>VM=>MWI; There would be no need for a speed dial; the phantom was so that I could program MWI. However, the more i look at this, I sit here and say, do I really need the PHTM phone built? I guess I do for the MWI to work, yes?

Taking the SD out of the equation gains nothing and reduces flexibility. Introducing the PHTM as the first DN establishes the DN to be used for message waiting. Using the huntgroup as the MWI DN is not recommended (by me) and can be very confusing.

and quickly about phantom: I know it doesn't require physical port and that a button is sufficient. My fear w/ the button method is accidental delete. So if I decide to create a 5224 (in this case) where am I assigning the device? phantom cabinet w/ the phantom # associated w/ the mailbox # (that was removed in the proposed method above?

Accidental deletion is a valid concern. My rule of thumb is to create the 5224 with a very recognisable / unusual DN such as 1*****1 (7 digits long yes). I name the extension - .Phantoms - DO NOT DELETE (period at beginning avoids phonebook searches) this leaves me with 119 programmable keys. I also keep exported copies of the set and keys "Just In Case".

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

 

[TecknowJoe]

ok, so if I interpreted your recommendation right: you suggest keeping the SD in place. May i ask what flexibility is lost? In the end, we program the SD (MAIN#DID) => PHNTM (General MB#) => HG => VM => MWI

and if I understand how everything is processed: we would then need to establish a call reroute statement for PHNTM# to always route to the HG# under call rerouting??...

btw: I did find the offline config and everything made sense. thank you so much!

 

[kwbMitel]

When the call is "Translated" via the SD table, the DN that it terminates to can be easily changed as the need arises. (As is the case here)

If the hunt group matched the DID, you would need to delete everything associated with the DN before rebuilding. This way, you can add the phantom, route the phantom to the hunt group. Point the SD at the phantom and see what happens. If it doesn't work, point the SD back where it was and figure out the problem. Much more flexible for testing and implementation.

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

 

[TecknowJoe]

My apologies for taking more of your time, but I am a bit confused. Let me use actual #'s so it can be clearer maybe?

Existing Setup (by consultant who wont give answers):
System Speed Call #: 3943 -> 3500 (Main Line# is 3943 - will never change
Hunt Group #: 3500 (internal# for operator - 5330 phone)
- Hunt Group Members: 3501-3506 (line appr on operator phone)
Hunt Group #: 3000 has 3 ports for company general mailbox (1,2,3)
Call Reroute 3500: RERoutes to HG 3000
General Mailbox # in Nupoint is: 3500

Proposed Setup (2 options):
Options 1
Remove System speed call 3943 to hg3500
Add new HG 3943 w/ members 3501-3506
Modify call reroute for 3943 to always route to 3000
Add phntm phone/key 3500 so MWI functions properly

Option 2
Change HG3500 to 3X00
Add Phntm phone/key 3500
Change SD 3943 to point to 3500
Change call reroute of 3500 to point to HG3000

 

[kwbMitel]

Options 1
Remove System speed call 3943 to hg3500 OK
Add new HG 3943 w/ members 3501-3506 OK
Modify call reroute for 3943 to always route to 3000 OK
Add phntm phone/key 3500 so MWI functions properly FAIL

Two issues at last step.
1) might be a typo, 3500 instead of 3943. I believe 3500 was removed at first step and replaced with 3943 at second step.
2) You cannot associate a MWI with a hunt group. What I said earlier is that the VM will set the lamp against the HG master (3943) and turn on the lamp of the phone that has the first programmed appearance of the first member of the huntgroup (in this case the 5330 as long as its extension was programmed first) If more than 1 station has appearances of the first member of the huntgroup then at the time of the next upgrade, the lowest extension number will be programmed first (and may not be the one you want)


Option 2
Change HG3500 to 3X00 OK, requires delete and re-create
Add Phntm phone/key 3500 OK
Change SD 3943 to point to 3500 Not necessary, no change
[highlight]ADD[/highlight] - Set Call Reroute of PHTM 3500 to huntgroup 3X00 on always condition
[highlight]Modify[/highlight] - SetChange call reroute of 3500 on 1st alternative to point to HG3000



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

 

[TecknowJoe]

Options 1
Remove System speed call 3943 to hg3500 OK
Add new HG 3943 w/ members 3501-3506 OK
Modify call reroute for 3943 to always route to 3000 OK
Add phntm phone/key 3500 so MWI functions properly FAIL

Two issues at last step.
1) might be a typo, 3500 instead of 3943. I believe 3500 was removed at first step and replaced with 3943 at second step.
2) You cannot associate a MWI with a hunt group. What I said earlier is that the VM will set the lamp against the HG master (3943) and turn on the lamp of the phone that has the first programmed appearance of the first member of the huntgroup (in this case the 5330 as long as its extension was programmed first) If more than 1 station has appearances of the first member of the huntgroup then at the time of the next upgrade, the lowest extension number will be programmed first (and may not be the one you want)

1. No typo. I wanted to create the 3500 key so that it would associate w/ the 3500 MB. In step 1, I created a new HG (3943), pointing to HG3000 that points to the GMB ports
2. By doing step 1, the MWI would be associate w/ a phantom key, not a HG. This is why i am confused: in this step I am not associating MWI w/ a HG. I am associating it w/ the phantom key (its just not in the flow of the call path)

Option 2
Change HG3500 to 3X00 OK, requires delete and re-create
Add Phntm phone/key 3500 OK
Change SD 3943 to point to 3500 Not necessary, no change
ADD - Set Call Reroute of PHTM 3500 to huntgroup 3X00 on always condition
Modify - SetChange call reroute of 3500 on 1st alternative to point to HG3000

I definitely understand and see this. thank you! Multiple thumbs up once I figure out how to do that for you

 

[kwbMitel]

With option 1 and no typo. The call would not end up in mailbox 3500 as nothing in the call string ever touches 3500. You could theoretically get the 3943 group to route to the 3500 MB but again, this would gain nothing and you would be left with the same MWI issues you had before changing.

Option2 is definitely the way to go.

As for thanks, check below my signature.

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