Design rules for voice mail domains, Design rules for voice mail domains -3 – Lucent Technologies Octel Unified Messenger Concepts and Planning Guide 101-1620-005 User Manual

Page 29

Advertising
background image

Sizing the system

101-1620-005

2-3

Design rules for voice mail domains

Designing voice mail domains (VMDs) is very similar to designing
domains in Microsoft NT.

When designing Octel Unified Messenger voice mail domains, the
following rules must be observed.

n

Each voice server can belong to one voice mail domain only.

n

Each voice mail subscriber can belong to one voice mail domain
only.

n

Each voice server has a single peer Exchange server.

n

Different voice servers in a voice mail domain can have different
peer Exchange servers, provided that those Exchange servers are
in the same Exchange site.

n

An Exchange server can be a peer server for more than one voice
server.

n

An Exchange server can be a peer server for voice servers from
different voice mail domains. However, the voice mail domains
must be located in the same Exchange site as the Exchange
server.

n

A Microsoft Exchange site can contain more than one voice mail
domain.

n

In a voice mail domain, there can be one tracing server only.

n

Voice mail domains cannot spread across multiple Exchange
sites.

n

There is only one PBX integration link per voice server. This
means that if your PBXs are integrated, you need one voice server
per PBX.

n

There can be several PBX types in one voice mail domain.
However, each PBX must be linked to its own voice server and
the voice mail domain properties must match every PBX type.

Advertising