Voicemail Resiliency on 3300

[AndrewTech]

Despite putting network server information in, I can't seem to get voicemail to work on my backup system. I have the ports turned on, no port numbers setup. I figure i'm going to have to setup the port range numbers on the 2nd switch manually, is there anything else i need to get my mailboxes and my auto attendant to failover?

Both MCD are on 14.0.3.22

 

[kwbMitel]

Networking is not designed for resiliency. It is to allow users to send messages from their local MB to a MB on a remote system.

Resiliency is not really viable with Embedded VM
Mailboxes need to be setup manually on each system by Admin and require separate licensing
Mailboxes need to be maintained individually by the users
The Hunt Groups need to be setup individually (As the ports within them are going to be different)
AA greeting need to be maintained manually

Basically, everything needs to be duplicated manually and it costs twice as much for licensing.

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.

 

[kwbMitel]

EMBEDDED VOICE MAIL

The embedded voice mail in each MiVoice Business system is set up as a hunt group with up
to 750 mailboxes and up to 30 ports. The number of ports you have determines the number of
users who can access the embedded voice mail on an ICP at the same time.
[ul]
[li]Each voice mail port must be configured as part of a voice mail hunt group. The pilot number of this hunt group is programmed as a (non-resilient) RDN in the Remote Directory Numbers form of all 3300 ICP Release 4.0 or later system in the resilient cluster, other than the ICP that is hosting the voice mail. The CEID of the ICP hosting the voice mail is programmed in that ICPs Remote Directory Numbers form. There is no CEID for the secondary ICP.[/li][/ul]


[ul][li]If programming non-centralized embedded voice mail, two embedded voice mailboxes must be assigned for the user of a resilient device: one on the primary ICP and one on the secondary ICP. Each mailbox must be individually configured (password, greeting, name) by the user. The user must set up pastiches and greetings on both the primary and secondary ICPs.[/li][/ul]


[ul][li]Call rerouting must be programmed to the local voice mail on a resilient device’s primary and secondary ICP so that the user does not need to do anything to make the mailbox active in the case of Fail-over.[/li][/ul]

[ul][li]For users to be notified of messages waiting on either of their controllers, you must amalgamate the callback message queues on the primary and secondary controllers.[/li]
[/ul]

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.