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!

Voicemail Migration to Cisco Unity 1

Status
Not open for further replies.

ukricardo

MIS
Mar 31, 2011
1
GB
Hiya,

We're migrating our Octel Voice Mail to Cisco Unity Connection - the whys etc behind this are a whole different debate....

However...

Is it possible to re-programme the 'Message Key' to dial the new Cisco Unity VM number rather than access the current Octel voice mail system?

Alternatively, can this function be removed from the phones completely and a new 'Speed Dial' provided instead?

MWI works across the two systems but it's just accessing it from a user perspective...

System Details are:
Mitel SX2000
Controller 3300
Phones: 4150 4025

Thanks for your help.

Ricardo
 
Not to the best of my knowledge.

You're probably going to miss your Octel, especially if you have any good-sized caller's menus on it and make use of type 35 conditional transfer mailboxes. Unity is a decent box, offering some newer integration features (i.e., with LDAP) that you couldn't do with the Octel and from an enduser perspective your user's will be satisfied, but for any applications requiring time of day/night switching with menu tree options under both scenarios, you'll be scratching your head. It takes 3 "system call handlers" to do the work of a single type 35 and Unity does not offer anything similar to a type 34.

Anyway, to answer your question, not to my knowledge. Perhaps someone else knows a trick.

Original MUG/NAMU Charter Member
 
Well unless I am mistaken you should be able to do it although I don't know the Cisco Unity VM. How does the Cisco or will the Cisco connect to the Mitel gear?

Normally the message key is just reacting to a message waiting indication from the voicemail. For example on a Nupoint voicemail you can tell the Nupoint the message waiting on and off code and setup the ports to the Nupoint with the COV voicemail port option in the COS for the ports.When a message is received in the Nupoint it simply issues a message waiting on code against the extension and the telephone lights the message waiting key. In addition a callback is placed on the phone. You go off hook and push the message key and it invokes the callback to the source of the callback i.e the Nupoint. My guess is you setup the Cisco correctly and the message key should work as you acutally can setup multiple voicemails on the Mitel at one time ( I have had the embedded, a Nupoint and an ESNA all going at once.. don't ask ). The message key should go to what voicemail sets the message waiting indication.

Am I missing something here? Its possible haven't had my first coffee of the day yet. Still half asleep.

The single biggest problem with communications is the illusion that it has taken place.
 
How are you integrating? Using ONS DTMF or a PIMG?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top