Manuel D’UtilisationTable des matièresPreface11Introduction15Introducing Avaya Modular Messaging17Benefits of Avaya Modular Messaging19Scalability19Mobility19Familiar telephone user experience20Multiple language support20Ease of administration22Switch integration23Industry standards23Concepts25Modular Messaging versions27Avaya Modular Messaging versions28Modular Messaging-MSS28Modular Messaging-Exchange and Modular Messaging-Domino30Comparing characteristics of Modular Messaging versions32Modular Messaging server components35Messaging application server36MAS services and functionality36Modular Messaging software components37Distributing server components and services41Message store43Functions of a message store43Avaya Message Storage Server43Microsoft Exchange server44IBM Lotus Domino server44Directory server45Modular Messaging interfaces47Telephone user interfaces48The caller interface48The subscriber interface52Multilingual support58Graphical user interfaces60Client Add-in for Microsoft Outlook62Subscriber Options67Desktop deployment of Client Add-in for Microsoft Outlook and Subscriber Options68Avaya Modular Messaging Web Client69Standards-based clients with Modular Messaging-MSS71IBM Lotus Notes with IBM Lotus DUC72Unified Communication Center Speech Access73Administrative and management interfaces74Message Storage Server administration74Messaging application server administration75Reporting capabilities76Voice mail domain79Modular Messaging features81Key features and capabilities82Modular Messaging-MSS85Modular Messaging-Exchange and Modular Messaging-Domino88Text-to-speech conversion capability89Multilingual text-to-speech89SNMP with Modular Messaging91SNMP system queries91Logs and notifications92MAS alarms and logs92MSS alarms and logs93SNMP alarm notification95Licensing97Audio encoding formats98GSM 6.1098G.71198Binary size and MIME transfer size99Offline messaging101Offline Call Answer102Offline access to Call Answer messages103When a Microsoft Exchange message store goes offline104When an IBM Lotus Domino message store goes offline105Messaging with e-mail clients in offline mode105N+1 server configuration107Added redundancy with N+1 server configuration107Distributing ports in an N+1 server configuration108Communities and sending restrictions109System lists111Modular Messaging-MSS Enhanced-List Application111Modular Messaging-MSS Broadcast112Modular Messaging-Exchange and Modular Messaging-Domino system lists113Personal Distribution Lists114PDL members114PDL labels and identifiers115Working with PDLs116Addressing messages to PDLs118Other concepts related to PDL addressing121Message Privacy122Creating private messages122Accessing private messages123Creating private Call Answer messages124The Privacy Enforcement Level privacy parameter125Restricting client access to mailboxes127Standard RFC822 Privacy Header128Summary of the privacy parameters129Subscriber data migrations and system upgrades131Addressing and networking133Addressing134Primary mailbox address134Local mailbox numbers136Numeric Address137Additional forms of addressing from the TUI138Additional forms of addressing from the PC user interface142Multiple mailboxes and alias extensions144Multiple extensions per mailbox144Multiple mailboxes per extension145Networking146Modular Messaging-MSS and the Message Networking Server147Message Networking server among multiple Modular Messaging- MSS systems148Modular Messaging and fax servers151Modular Messaging-MSS native fax server152Providing interoperability with third-party fax servers155An overview of third-party fax servers155Requirements for fax server interoperability with Avaya Modular Messaging156Enabling subscribers for fax157Routing inbound fax calls to the third-party fax server158Working with fax messages159Fax messaging from the TUI159Fax messaging from the PC user interfaces162Telephony concepts165Voice ports166Switch integration167Switch integration options167Integration features169Telephony protocols172Signaling174Hunt groups175Types of hunt groups175Support for message and call notification177Message notification178Call Me178Notify Me - Automatic180Overview of Message Waiting Indicator (MWI)182Call notification185Caller-requested Notify Me185Find Me186Intercom paging189Call screening from the Automated Attendant189Combining features190Planning193Designing voice mail domains195General rules for voice mail domains196Rules for MSS messaging environments199Rules for Microsoft Exchange messaging environments200Rules for IBM Lotus Domino messaging environments201Considering the proximity of the switch to e-mail message stores202System capacities203Voice mail domain capacities204Avaya Message Storage Server capacities206Messaging application server capacities207MAS port capacities (Modular Messaging-MSS)208MAS port capacities (Exchange and Domino)210Port Sizing211Port sizing using Modular Messaging offers212Port usage patterns212Modular Messaging-MSS offers213Modular Messaging Aria TUI offers215Modular Messaging AUDIX TUI offers218Offers for Modular Messaging with Exchange and Domino message stores220Identifying which Modular Messaging offer a customer needs228Estimating the additional e-mail readers required228Port sizing without using Modular Messaging offers231Concepts a planner must know231Estimating port requirements232Calculating the number of messaging application servers required236Evaluating the additional load on the network and e-mail servers237Other planning considerations241Planning for redundancy242Messaging application server redundancy242Message Store Server redundancy243Messaging application server load balancing245Distribution of server components245Recommendations for the Tracing Server247Recommendations for the Offline Call Answer Store249Hunt algorithm252Calculating the message storage capacity253Storage space available on the MAS253Storage space available on the MSS254Calculating the storage space on e-mail servers254Storage planning256Fax port and storage planning257Message retention estimate258Calculating the number of desktop users per voice mail domain260IMAP4 client limits260POP3 client limits261Port requirement planning262Grade of service265Customer environment271Site requirements for Avaya servers273Environmental requirements273Weight and space considerations273Customer-provided cabinet requirements274Power requirements274Modular Messaging and the Microsoft Windows domain infrastructure275Modular Messaging and the Windows domain275Subscriber and administrator authentication275Considerations when implementing Modular Messaging-MSS277Considerations when implementing Modular Messaging with e-mail servers280Minimum hardware requirements and supported software (MSS version)282MAS specifications with Modular Messaging-MSS282Client Add-in for Microsoft Outlook requirements283Subscriber Options requirements284Modular Messaging Web Client requirements285Tracing Server requirements287Tracing Server or Offline Call Answer store requirements288Mailbox Manager Minimum Requirements for Single User Implementation290Administration Client requirements291Browser requirements for the MSS administration interface291Compatibility with Avaya Integrated Management292Minimum hardware requirements and supported software (Exchange and Domino)293Messaging application server requirements293Tracing Server requirements296Tracing Server or Offline Call Answer store requirements298Administration Client requirements299Caller Applications Editor requirements300Client Add-in for Microsoft Outlook requirements301Subscriber Options requirements302Subscriber Administration Extension requirements304Peer Exchange Server requirements305Peer Domino Server requirements306Other considerations307Considerations with Message Networking server309Glossary313Index323Taille: 2,4 MoPages: 328Language: EnglishOuvrir le manuel
