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

MWI from remote cluster element

Status
Not open for further replies.

KurpeusLondon

Technical User
Apr 14, 2010
119
GB
Hi guys,

How do I get MWI to work from an extension located on controller B when the mailbox is on controller A ?

To explain

I've a cluster of two 3300 running MCD 4.1. I'm using embedded voicemail on both controllers for some kind of resilience.


On controller A, a mailbox - 4301 - (for ACD use) is created without prime line. I've a nametag huntgroup *4301 that is CFWA to voicemail.

If the ACD agent is located on controller A, a MWI key with 4301 works fine. If the agent is located on controller B, I can't program a MWI key because of the DN does not exist. As expected I don't have the DN in the Remote telephone directory number form which btw is shared with SDS (Read Only).

Any thoughts?

Thanks,

 
Assuming EMEM

It will only work if the device is listed on both systems

If you name the 4301 key it should sync

**********************************************
What's most important is that you realise ... There is no spoon.
 
Hi KwbMitel, thanks for your response

I'm not sure I'm following, do you mean on the second controller I need to create a key line appearance 4301 and name it using the telephone directory ?
 
in a cluster if you assign a name to the extension number then it will be carried across the cluster by SDS and will appear in the RDN form. I think that is what he means.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Yes name the key onthe system where it already exists

**********************************************
What's most important is that you realise ... There is no spoon.
 
If I name the key on the system where the voicemail exists I can indeed configure the MWI key on the remote system. However, the key does not do anything.


To resume what I did,

I've a nametag huntgroup *4308 CFwA to voicemail
I created a voicemail 4308 user extension 4308
I added a single line 4308 on a PKM48 phantom 5220 IP set
I created a entry for 4308 in the Telephone directory

On the remote controller, I have an ACD Agent for which I configured a MWI button for 4308. However no lights :(

If I do a locate number 4308 on the remote controller I get a
"The number refers to a Non Prime Broadcast Group".

and oh the *4308 is access when users dial out of a queue.

I'm probably missing something.
 
If I use the FAC on any controllers, the key light up so it must configured fine.

Why is the embedded VM not activating the MWI then ?
 
in cluster programming do you have the feature info programmed?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Yes - Feature code in Cluster Programming is required

**********************************************
What's most important is that you realise ... There is no spoon.
 
Yes a Feature DN is programmed on both cluster members

Am I supposed to have these feature DN programmed in the ARS dialed digits form ?

 
no Ars needed.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Just to make sure we are talking about the same feature programming. In the Cluster Programming form there is an optional programming slot for a Feature DN. The feature DN programmed in this form must be unique to each system in much the same way as the Cluster ID. The programming must match on every system.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Would it be this?

Multiple Message Waiting Indications
Description:
Line keys on multiline telephones can be programmed as message waiting indicators which are associated with the mailboxes of other stations. The indicator flashes when a message is waiting in the associated mailbox. This allows users to look at a multiline telephone and recognize which mailboxes have messages. When the flashing key is pressed, it calls the associated mailbox using the prime line. If the prime line is busy, the user can select a free line. If the voice mail system is centralized, the call may occur across an MSDN network or cluster.

Conditions and Feature Interactions

All voice mail indications for a given directory number (DN) must be on the directory number's local telephone system.



I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Loopylou - We should have caught that before. Yes, now that you bring it up, I remember trying to do this and having issues. The lamp can be set on the remote system but only if the DN is local to that system.

@ KurpeusLondon - Sorry, we're not perfect here. With embedded mail you're out of luck. You could try to use email notifications as a method of letting people know there is a message.

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

Thanks for you responses and no worries you're always good help anyway :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top