Functional Considerations
New Features Available In IPedge Software Release R1.5
8 of 16
There is no license charge for the mailboxes that are replicated in the other nodes.
Figure 2 - DCN With Centralized Messaging
Figure 2 shows how DCN may work within a centralized voice mail configuration. Should IPedge Node 11
(DCN node 1) fail, Node 13 may use the replicated mailboxes on Node 12.
Functional Considerations
Although DCN provides a robust voice mail survivability solution, there are some functional considerations
that need to be understood and communicated to customer users.
•
If a telephone has a Message Waiting Indicator (MWI) illuminated, and the system that supports that
telephone fails the MWI will not be reinstated until another new message is received. The telephone
survives over to another system that is in the cluster and has its mailbox intact, but the Message
Waiting light will not light until a new message is received.
•
The voice mail hunt group pilot number should be the same on the different nodes. If the voice mail
hunt group pilot number is different on the different nodes incorrect voice mail forwarding after a node
failure will occur. For example, station 201 on IPedge Node 11 (DCN Node 1) is set to system call
forward to voicemail hunt group pilot 300. The DNs on IPedge Node 12 (DCN Node 2) are set to
system call forward to voicemail hunt group pilot 400. If IPedge Node 11 fails and station 201 re-
registers with IPedge Node 12, station 201 will not properly forward to voicemail when a call is
presented to it.
Note
The Messaging application must be running on every IPedge system that will run DCN.
DCN Node 1
DCN Node 2
DCN Node 3
DCN Node 4
IPedge Node 11 (Primary)
IPedge Node 12 (Member)
IPedge Node 13 (Member)
IPedge Node 14 (Member)
