Octel Unified Messenger Concepts and Planning Guide 101-1620-005
Your comments on this document are welcome. They can assist us in improving our products. Please address comments to: Unified Messenger Documentation Team Lucent Technologies, Octel Messaging Division 1001 Murphy Ranch Road Milpitas, CA 95035-7912 USA +1 408-321-2000 http://www.octel.com/um E-mail: unified.messenger@octel.
Preface Overview This guide provides: n Guidelines for planning and sizing a new installation. n A description of the hardware and software components of Octel Unified Messenger. n The concepts underlying Octel Unified Messenger, including voice mail domains, addressing, client and server operations, and telephony concepts. Audience This guide is intended for use by anyone recommending, purchasing, or installing Octel Unified Messenger.
Octel Unified Messenger Concepts & Planning Guide Octel Unified Messenger documentation See the following documentation for more information about Octel Unified Messenger: Installation Guide, 101-1621-005 Provides information on the installation process. Available on the Octel Unified Messenger CD-ROM. Administrator’s Guide, 101-1618-005 Provides information on administering the Octel Unified Messenger system. Available on the Octel Unified Messenger CD-ROM.
Preface Unified Messenger Online Support For Octel Unified Messenger support, contact your Octel Unified Messenger support representative. For important, up-to-date information on Octel Unified Messenger, see the Readme file available on the Octel Unified Messenger CD-ROM. Conventions The following conventions are used in this guide: 101-1620-005 Convention Description ALL CAPITALS Filenames and extensions, directory names, paths, and acronyms.
This page intentionally left blank.
Contents Chapter 1 Introducing Octel Unified Messenger Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 The unified mailbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Octel Unified Messenger Concepts & Planning Guide Hardware and software requirements for Octel Unified Messenger servers . . . . . . . . . . . . . . . 2-10 Evaluating the additional load on Microsoft Exchange servers . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Evaluating the additional network traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Using Octel Unified Messenger via slow network connections. . . . . . . . . . . . . . . . . . . . . . . . .
Contents Addressing OctelNet messages to Octel Unified Messenger recipients . . . . . . . . . . . . . . . . .5-7 Providing single-site interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8 Automatic mailbox forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8 Chapter 6 Connecting with the PBX and establishing security rules Connecting with the PBX . . . . . . . . . . . . . . . . . . . . . .
This page intentionally left blank.
PART 1 CONCEPTS
This page intentionally left blank.
1 Introducing Octel Unified Messenger This chapter introduces Octel Unified Messenger and discusses the following topics: 101-1620-005 n Octel Unified Messenger product features. n The “unified mailbox” concept. n Networked components of the Octel Unified Messenger environment. n Benefits of using Octel Unified Messenger.
Octel Unified Messenger Concepts & Planning Guide Introduction Today e-mail, voice mail, and fax are established as strategic, enabling technologies at companies large and small. As a result, people are receiving both a larger volume and more types of messages than ever before. However, each kind of message typically requires its own access medium (telephone, personal computer, or fax device) and support structure (capital equipment, management tools, and service procedures).
Introducing Octel Unified Messenger Product features OMD uses the next-generation client/server messaging system Microsoft Exchange Server to deliver a truly unified messaging architecture that meets the mission-critical demands of even the largest organization. Specific features of Octel Unified Messenger include: 101-1620-005 n A single unified view of messages using the Exchange Server mailbox. n Telephone access to the Exchange Server mailbox.
Octel Unified Messenger Concepts & Planning Guide The unified mailbox For each Octel Unified Messenger subscriber, all voice mail, telephone answering, e-mail, fax, and data messages (including documents and forms) are stored in the unified mailbox. Messages can be viewed, listened to, stored, or retrieved using either telephone, PC, or fax. Figure 1-1 shows the concept of the unified mailbox. Figure 1-1.
Introducing Octel Unified Messenger Telephone user interface Subscribers can access their unified mailbox from a telephone user interface to do the following: n Send and receive voice messages. n Play back voice messages. n Listen to e-mail messages, using TTS conversion. n Forward fax messages to other recipients or to a fax device for printing. n Store, delete, reply to, or forward e-mail, voice, or fax messages. n Print e-mail messages on a fax device.
Octel Unified Messenger Concepts & Planning Guide Networked components Figure 1-2 shows the networked components of the Octel Unified Messenger environment. Figure 1-2.
Introducing Octel Unified Messenger Voice server The voice server is a Windows NT-based system that is the integral link between the LAN and the telephone network. It performs the following functions: Multilingual text-to-speech n Answers PBX-forwarded telephone calls. n Plays personalized greetings. n Records messages. n Sends compressed message files to subscriber mailboxes for storage. n Retrieves stored messages for playback through the telephone or through multimedia.
Octel Unified Messenger Concepts & Planning Guide can generate reports summarizing voice mail activity using the Octel Unified Messenger Reporting Tool application. Fax server The fax server is a third-party component to which the voice server delegates all functionality related to sending and receiving faxes. For more information on third-party fax server compatibility with Octel Unified Messenger, see “Octel Unified Messenger interoperability with third-party fax servers” on page 2-20.
Introducing Octel Unified Messenger Access to faxes using the TUI The telephone user interface recognizes messages of the message type IPM.NOTE.FAX. If a fax server does not support this message type, Octel Unified Messenger does not classify messages as faxes but only as e-mail messages with TIFF attachments. Subscribers can send fax messages to other recipients or to a fax device for printing. They can also send e-mail messages to a fax device for printing.
Octel Unified Messenger Concepts & Planning Guide LAN The LAN provides a high-speed (minimum 10 Megabit per second switched) connection between servers and client systems. Octel Unified Messenger supports Ethernet and token ring based LAN topologies. Octel Unified Messenger takes advantage of the file streaming capabilities of Windows NT to transfer voice files across the network. This minimizes network traffic congestion and provides speedy message playback and navigation.
Introducing Octel Unified Messenger Benefits summary Octel Unified Messenger provides the following benefits to your organization. Subscriber convenience With Octel Unified Messenger, subscribers can: n Store all messages in one place, regardless of the message type. n Access voice, e-mail, and fax messages from either the telephone or PC user interface. n Reply to messages in one medium (for example, voice) with another medium (for example, e-mail).
This page intentionally left blank.
PART 2 PLANNING
This page intentionally left blank.
2 Sizing the system This chapter discusses the main points to consider when sizing the hardware for Octel Unified Messenger. It contains information about: 101-1620-005 n Voice mail domain design rules. n Establishing the number of voice ports required. n Calculating the number of voice servers required. n Hardware and software requirements. n Evaluating the additional load on the Microsoft Exchange server. n Evaluating the additional network traffic.
Octel Unified Messenger Concepts & Planning Guide Introduction Sizing the hardware for Octel Unified Messenger involves the following steps: 1. Designing the voice mail domain structure for the organization. 2. Calculating the number of voice ports required. 3. Calculating the number of OMD voice servers needed. 4. Designing fax server and voice server communication. 5. Evaluating the additional load on Microsoft Exchange. 6. Evaluating the additional network traffic that must be handled.
Sizing the system 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. 101-1620-005 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.
Octel Unified Messenger Concepts & Planning Guide Sizing ports Accurate port sizing is critical to the successful implementation of any voice processing application. A careful analysis of system traffic patterns must be made. Specifically, the volume of calls generated by internal subscribers and external callers to the system during the busiest hour of the day must be determined.
Sizing the system Units of measurement for busy hour traffic Busy hour traffic is normally expressed in units of measurement such as minutes, Erlangs, or Centum Call Seconds (CCS). Note: 1 CCS = 100 call seconds. For example, there are 3,600 seconds in 1 hour. To determine the number of CCS in 1 hour, divide 3,600 by 100 to get 36 CCS. Minutes, Erlangs, and CCS are different ways of expressing busy hour traffic.
Octel Unified Messenger Concepts & Planning Guide To convert this total into call minutes, divide by 60: 67,500/60 = 1,125 call minutes. To convert this total into Erlangs, divide by 3600: 67,500/3600 = 18.75 Erlangs. To convert this total into CCS, divide by 100: 67,500/100 = 675 CCS. To predict busy hour traffic accurately, you must collect reliable traffic data that reflects the calling patterns specific installation or application.
Sizing the system PBX integration device sizing Sizing outgoing call features: Intercom Paging and OctelNet As described in “PBX integration” on page 3-10, PBX integrations are accomplished by different methods depending on the PBX type and the capabilities of the PBX. Although all PBX Integration Devices (PIDs) perform the same basic functions, they all accomplish it in a slightly different manner.
Octel Unified Messenger Concepts & Planning Guide Total estimated port requirements To summarize, when sizing the number of total ports required for any given server to provide a desired GOS, the following factors must be considered. n Estimated total busy hour offered traffic generated by both internal and external callers. n Estimated total busy hour offered traffic generated by all applications, including those that place outgoing calls.
Sizing the system Calculating the number of voice servers required Having established the total number of voice ports, it is possible to calculate the minimum number of voice servers needed. The minimum number of servers is equal to the total number of ports needed, divided by the number of ports to be installed on each of the servers. An Octel Unified Messenger voice server can support up to 24 voice ports.
Octel Unified Messenger Concepts & Planning Guide Hardware and software requirements for Octel Unified Messenger servers Octel Unified Messenger servers require the following configuration: Minimum voice server requirements n For systems using 4 to 12 ports: 200 MHz Intel Pentium. For systems using 16 to 24 ports: 400 MHz Intel Pentium. n 128 MB RAM. n Access to a CD-ROM drive to install the software. n Microsoft Windows NT 4.0 with the latest service pack.
Sizing the system Minimum tracing server requirements n For systems with up to 2 voice servers: 200 MHz Intel Pentium. For systems with more than 2 voice servers: 400 MHz Intel Pentium 101-1620-005 n 64 Mbytes RAM. n Access to a CD-ROM drive to install the software. n Microsoft Windows NT 4.0 with the latest service pack. n Microsoft Exchange Client software. n 2 Gbyte free disk space.
Octel Unified Messenger Concepts & Planning Guide Evaluating the additional load on Microsoft Exchange servers Implementing Octel Unified Messenger affects the activity of the Exchange servers and the disk space usage.
Sizing the system Disk space requirements Voice messages require 4 Kbytes per second (240 Kbytes per minute) of space for storage. Subscriber mailboxes A subscriber who receives five voice messages per day, with an average message length of 60 seconds, requires 1.2 Mbyte of storage space to keep all messages stored on the Exchange server or on another machine if the subscriber stores the messages in Personal Folders. However, most people have no need to store all of the messages they receive.
Octel Unified Messenger Concepts & Planning Guide Evaluating the additional network traffic Implementing Octel Unified Messenger results in the flow of voice data over the organization’s data network. This section provides the information required to calculate the additional network traffic generated by an Octel Unified Messenger system. This calculation is based on several factors, including: Worst-case network load n The number of voice servers in the voice mail domain (S).
Sizing the system Types of operations The Octel Unified Messenger voice servers open data streams between voice servers and: n Exchange servers. n Client systems. The actual Exchange server associated with each data stream depends on the operation and, in some cases, the associated mailbox: n The operation of telephone answering results in the establishment of a data stream between the voice server and the voice server’s peer e-mail server.
Octel Unified Messenger Concepts & Planning Guide Using Octel Unified Messenger via slow network connections Octel Unified Messenger applications move voice messages between Octel Unified Messenger client systems and: n Octel Unified Messenger voice servers. n Octel Unified Messenger client systems and Exchange servers. How the data flows between systems is dependent on whether a subscriber uses multimedia or the telephone and whether voice messages are recorded or played back.
Sizing the system Using the telephone Voice messages can be played back and recorded using the telephone. Playing back voice messages When playing back a voice message, the message is moved from the Exchange server to a telephone via the voice server. The playback is not affected by the speed of the client network connection. However, if playback controls are used, for example, fast forward or rewind, these are routed through the network connection.
Octel Unified Messenger Concepts & Planning Guide Recording voice messages When recording voice messages, the data must be copied from the voice server to the client PC via slow network connections. It is stored on the client PC until the recording is stopped. Once recording is stopped, the message is copied to the Exchange server mailbox. Therefore it is very important to have adequate network bandwidth.
Sizing the system The effect of slow network connections on Octel Unified Messenger applications This section lists all Octel Unified Messenger applications and how each is affected by slow network connections. Octel Unified Messenger Voice Form If Octel Unified Messenger Voice Form is used with multimedia, a slow network connection is sufficient. If the Octel Unified Messenger Voice Form is used with a telephone to play back voice messages only, a slow network connection is sufficient.
Octel Unified Messenger Concepts & Planning Guide Octel Unified Messenger interoperability with third-party fax servers This section describes how third-party fax servers interoperate with Octel Unified Messenger. It is recommended that the third-party fax server resides on a separate Windows NT server. The fax hardware is connected to a fax hunt group on the PBX. Figure 2-3.
Sizing the system Requirements for third-party fax server interoperability with Octel Unified Messenger The following are the requirements for third-party fax server interoperability with Octel Unified Messenger: n Octel Unified Messenger version 2.0 or higher must be installed. n The fax server must be integrated with Microsoft Exchange as an Exchange Connector or an Exchange gateway for fax. n The fax server must use a FAX address type that is specified to Octel Unified Messenger.
Octel Unified Messenger Concepts & Planning Guide Routing inbound fax calls to the third-party fax server Like voice calls, fax calls placed to a subscriber’s extension are redirected to the Octel Unified Messenger voice server when these calls encounter a ring-no-answer or busy condition. Whenever the voice server receives a call and detects that it is a fax, it places the call on courtesy hold and initiates a call to the fax server hunt group.
3 System architecture This chapter introduces the Octel Unified Messenger system architecture and describes some of its key concepts, such as the voice mail domain (VMD) and addressing mechanisms. This chapter also contains a list of the main system components, including client, server, and telephony.
Octel Unified Messenger Concepts & Planning Guide Introduction This section introduces the concept of a voice mail domain, as well as the various methods that subscribers can use to address voice messages. Voice mail domain An Octel Unified Messenger voice mail domain is a group of OMD voice servers that share the same set of properties, for example, PBX settings. Any changes made to a voice mail domain’s properties are updated and replicated automatically to all voice servers in the domain.
System architecture Figure 3-1.
Octel Unified Messenger Concepts & Planning Guide Addressing messages When sending voice messages, subscribers enter recipients’ addresses differently depending on whether they use the PC user interface or the telephone user interface. From the PC user interface From the telephone user interface A subscriber can retrieve recipients’ addresses from the Exchange directory, in other words, from their address books.
System architecture System components The system components of Octel Unified Messenger are classified in three categories: n Client components n Server components n Telephony components Client components The client applications enable subscribers and administrators to access Octel Unified Messenger from the telephone or from their desktop PCs. Telephone access Outside callers interact with Octel Unified Messenger through the telephone to leave voice messages or faxes.
Octel Unified Messenger Concepts & Planning Guide PC access From a desktop PC, subscribers and administrators can use the following Octel Unified Messenger applications. Octel Unified Messenger Options The Octel Unified Messenger Options application enables subscribers to modify their mailbox settings at any time from their PC user interface. Note: The Octel Unified Messenger Options can also be accessed from the telephone user interface.
System architecture Administration applications System administrators can use the following applications and tools to manage Octel Unified Messenger. Voice Mail System Configuration This application displays property pages for configuring and maintaining the voice mail system. Properties that are shared across voices servers in a voice mail domain can be configured centrally. Any changes made to a voice mail domain’s properties are then replicated to all voice servers in the domain.
Octel Unified Messenger Concepts & Planning Guide Server components Octel Unified Messenger adds two types of servers, the voice server and the tracing server, to the Microsoft Exchange Server environment. Voice server 3-8 An Octel Unified Messenger voice server provides or supports the following functions: n Call management. This function provides an interface between the voice cards and the Octel Unified Messenger telephony applications. n Messaging.
System architecture Tracing server 101-1620-005 A tracing server maintains connections with all voice servers in a voice mail domain, and performs the following tasks: n Collects the events that are of interest to an administrator for diagnostic purposes, for example, a Call Waiting state generated by the telephone user interface. n Writes the events to the operation history database.
Octel Unified Messenger Concepts & Planning Guide PBX integration Callers who are forwarded to a voice server can leave a message for the called party without additional intervention. This is made possible through the integration of the PBX or Centrex with the Octel Unified Messenger voice server. With an integrated voice server, callers are greeted by the personal greeting of the called party, inviting them to leave a message.
System architecture Digital Meridian Integration Device The Digital Meridian Integration Device (DMID) is a device that provides integration with Northern Telecom switches, such as the Meridian SL-1. The DMID is located between the PBX and the voice server and appears as one or two digital telephones to the PBX, depending on the number of analog ports required. It is connected to the voice server via an RS-232 link. Analog line circuits for the voice path appear on the digital set of the DMID.
Octel Unified Messenger Concepts & Planning Guide Audio encoding formats Octel Unified Messenger supports the following audio encoding formats: n ADPCM audio encoding format. This is a high quality audio encoding algorithm with a coding rate of 32 kilobit per second. n Global System for Mobile Communications (GSM) 6.10 audio encoding format. This audio encoding format has a coding rate of approximately 13 kilobit per second.
4 Designing addressing schemes This chapter introduces different forms of addressing and describes the following addressing schemes: 101-1620-005 n Local mailbox number. n Dial-by-Name. n Numeric addresses.
Octel Unified Messenger Concepts & Planning Guide Introduction Octel Unified Messenger subscribers can use different forms of addressing: From the PC user interface Subscribers use the Microsoft Exchange directory for addressing messages. An address is always unique within the Exchange directory. An address entered at any location is automatically available at all locations within the organization. From the telephone user interface Octel Unified Messenger supports four custom forms of addressing.
Designing addressing schemes Local mailbox numbers Local mailbox numbers are used to address any Octel Unified Messenger subscriber in a voice mail domain from the telephone user interface. Traditional voice mail systems typically use this form of addressing. Within a voice mail domain, all local mailbox numbers must have the same number of digits. Each local mailbox number must be unique within the domain. Many organizations use telephone extension numbers as local mailbox numbers.
Octel Unified Messenger Concepts & Planning Guide Dial-by-Name Dial-by-Name is a method of addressing messages by spelling the recipient’s name using the keys on the telephone keypad. To support Dial-by-Name addressing, Octel Unified Messenger maintains an internal database of all recipients in the Exchange directory. This database is indexed by the DTMF codes corresponding to their spelled names in “last name, first name” order.
Designing addressing schemes Numeric addresses A numeric address enables subscribers to address any Octel Unified Messenger recipient in an organization. Every Octel Unified Messenger recipient must be assigned a unique numeric address. The numeric address allows a subscriber to send a message to any recipient from the telephone user interface without having to know the recipient’s location.
This page intentionally left blank.
5 Providing interoperability with existing Octel servers This chapter describes how existing Octel servers can communicate with Octel Unified Messenger. It introduces OctelNet, OMD’s solution for voice networking between Octel servers. It includes information on: 101-1620-005 n Designing an OctelNet addressing scheme. n Addressing OctelNet messages. n Providing single-site interoperability.
Octel Unified Messenger Concepts & Planning Guide Introduction to OctelNet™ OctelNet is a networking application that allows users on one OMD system to exchange messages with users on other OMD systems. For example, organizations already using OMD’s Octel system can provide interoperability with Octel Unified Messenger through OctelNet. This allows them to link all employees in one cost-effective messaging network that is easy to use and manage.
Providing interoperability with existing Octel servers OctelNet Messaging Features When sending or receiving messages via OctelNet, subscribers can: NameNet™ n Mark messages as urgent. n Request message confirmation. n View envelope information. n Reply to messages. n Address messages by spelling a recipient’s name, using NameNet. n Receive spoken name confirmation, using NameNet.
Octel Unified Messenger Concepts & Planning Guide Designing an OctelNet addressing scheme For messages to be sent via the OctelNet gateway, the administrator must set up an OctelNet addressing scheme. If required, multiple addressing schemes can be set up for a single OctelNet node. This allows OctelNet messages to be addressed in different ways to the same destination system. Setting up an OctelNet addressing scheme An OctelNet addressing scheme consists of: n A prefix. n Additional digits.
Providing interoperability with existing Octel servers OctelNet addressing scheme design rules When designing OctelNet addressing schemes, the following rules must be observed. n The mailbox length must be greater than or equal to 3 digits. n The additional digits must be less than or equal to the mailbox length. n The number of digits in the prefix plus the additional digits must be greater than or equal to the mailbox length.
Octel Unified Messenger Concepts & Planning Guide Sample addressing schemes Table 5-1 shows examples of valid OctelNet address schemes. Table 5-2 shows examples of invalid OctelNet multiple addressing schemes. Table 5-1.
Providing interoperability with existing Octel servers Addressing OctelNet messages OctelNet addresses provide a means of sending voice messages to recipients on a voice messaging server that supports OctelNet networking, such as any OMD Octel Message Server. Addressing OctelNet messages from Octel Unified Messenger Two methods can be used for addressing messages to OctelNet recipients: Administered OctelNet addressing n Administered OctelNet addressing. n Casual OctelNet addressing.
Octel Unified Messenger Concepts & Planning Guide Providing single-site interoperability Although OctelNet is generally used to link multiple sites, it can also be used to exchange messages between Octel Unified Messenger subscribers and Octel message server users at the same site. When an Octel Unified Messenger system and an Octel server share the same PBX, OctelNet networking can be configured to operate like a single voice server by using automatic mailbox forwarding.
6 Connecting with the PBX and establishing security rules This chapter introduces the following: 101-1620-005 n How to connect with the PBX. n The Octel Unified Messenger’s security features that prevent unauthorized access.
Octel Unified Messenger Concepts & Planning Guide Connecting with the PBX Using the Voice Mail System Configuration application, an administrator can specify the parameters necessary to enable PBX integration to the voice server. See the Octel Unified Messenger documentation for the specific information required for the major PBX types. These notes are available from the Octel support representative.
Connecting with the PBX and establishing security rules Establishing security rules Octel Unified Messenger offers several features that reduce the risk of fraudulent long distance charges, unintended disclosure of confidential information, and decreased performance of the voice servers. Access to voice mail domain administration Administrators create and maintain voice mail domains, and configure the voice servers in these domains.
Octel Unified Messenger Concepts & Planning Guide Subscriber password for the telephone user interface Octel Unified Messenger subscribers maintain a password for accessing their voice mail through the telephone user interface. They can do this either from Octel Unified Messenger Options on their desktop PC or through the telephone user interface. The administrator enables a subscriber account for voice messaging and determines the initial password for telephone access.
Connecting with the PBX and establishing security rules The administrator can also enable password expiration that forces subscribers to change passwords at predetermined time intervals. Changing passwords periodically reduces the chances of an unauthorized user gaining access to a subscriber’s mailbox. Table 6-1.
Octel Unified Messenger Concepts & Planning Guide Recipient’s name confirmation Octel Unified Messenger confirms the name of the recipient before sending a voice message from one subscriber to another. This feature makes it possible for sender of voice messages to ensure that their messages are delivered to the intended destination.
A Appendix A - Sizing for ports This appendix gives guidelines for estimating how many users can be supported with a given number of voice ports.
Octel Unified Messenger Concepts & Planning Guide Calculating the number of supported subscribers Table A-1 through Table A-18 can be used as guidelines for estimating how many users can be supported with a given number of ports, based on average daily port usage per subscriber. These tables also provide for traffic patterns of 10%, 14%, or 18% Busy Hour traffic. Table A-1.
Appendix A - Sizing for ports Table A-2.
Octel Unified Messenger Concepts & Planning Guide Table A-3.
Appendix A - Sizing for ports Table A-4.
Octel Unified Messenger Concepts & Planning Guide Table A-5.
Appendix A - Sizing for ports Table A-6.
Octel Unified Messenger Concepts & Planning Guide Table A-7.
Appendix A - Sizing for ports Table A-8.
Octel Unified Messenger Concepts & Planning Guide Table A-9.
Appendix A - Sizing for ports Table A-10.
Octel Unified Messenger Concepts & Planning Guide Table A-11.
Appendix A - Sizing for ports Table A-12.
Octel Unified Messenger Concepts & Planning Guide Table A-13.
Appendix A - Sizing for ports Table A-14.
Octel Unified Messenger Concepts & Planning Guide Table A-15.
Appendix A - Sizing for ports Table A-16.
Octel Unified Messenger Concepts & Planning Guide Table A-17.
Appendix A - Sizing for ports Table A-18.
This page intentionally left blank.
B Appendix B - Grade of service This appendix illustrates the maximum amount of busy hour traffic supported by a given number of ports for each grade of service (GOS).
Octel Unified Messenger Concepts & Planning Guide Calculating busy hour traffic Table B-1 through Table B-4 show the maximum amount of busy hour traffic supported by a given number of ports for each grade of service. Note: Erlangs, CCS, and minutes are three different measures of traffic. 60 minutes = 1 Erlang = 36 CCS. Table B-1. B-2 Maximum busy hour traffic supported for a GOS of P.01 Ports Erlangs CCS Minutes 4 0.86 31 51.7 8 3.11 112 186.7 12 5.86 211 351.7 16 8.86 319 531.
Appendix B - Grade of service Table B-2. 101-1620-005 Maximum busy hour traffic supported for a GOS of P.02 Ports Erlangs CCS Minutes 4 1.08 39 65.00 8 3.61 130 216.67 12 6.61 238 396.67 16 9.81 353 588.33 20 13.17 474 790.00 24 16.61 598 996.67 28 20.14 725 1208.33 32 23.72 854 1423.33 36 27.33 984 1640.00 40 30.97 1115 1858.33 44 34.67 1248 2080.00 48 38.39 1382 2303.33 52 42.11 1516 2526.67 56 45.86 1651 2751.67 60 49.64 1787 2978.
Octel Unified Messenger Concepts & Planning Guide Table B-3. B-4 Maximum busy hour traffic supported for a GOS of P.03 Ports Erlangs CCS Minutes 4 1.25 45 75.00 8 3.97 143 238.33 12 7.14 257 428.33 16 10.50 378 630.00 20 13.97 503 838.33 24 17.56 632 1053.33 28 21.19 763 1271.67 32 24.89 896 1493.33 36 28.64 1031 1718.33 40 32.39 1166 1943.33 44 36.19 1303 2171.67 48 40.00 1440 2400.00 52 43.83 1578 2630.00 56 47.69 1717 2861.67 60 51.
Appendix B - Grade of service Table B-4. 101-1620-005 Maximum busy hour traffic supported for a GOS of P.05 Ports Erlangs CCS Minutes 4 1.50 54 90.00 8 4.53 163 271.67 12 7.94 286 476.67 16 11.53 415 691.67 20 15.22 548 913.33 24 19.03 685 1141.67 28 22.86 823 1371.67 32 26.72 962 1603.33 36 30.64 1103 1838.33 40 34.58 1245 2075.00 44 38.56 1388 2313.33 48 42.53 1531 2551.67 52 46.53 1675 2791.67 56 50.53 1819 3031.67 60 54.56 1964 3273.
This page intentionally left blank.
Glossary access control list A list of people in a voice mail domain who have access to Octel Unified Messenger applications and tools. AccuCall+ A Rhetorex utility for Windows NT and Windows 95 that allows you to build and edit tone tables. Adaptive Differential Pulse Code Modulation (ADPCM) A speech encoding method that produces a digital signal with a lower bit rate than standard pulse code modulation (PCM).
Octel Unified Messenger Concepts & Planning Guide Centum Call Second (CCS) A unit of measurement for call time. The formula for a CCS is the number of calls per hour multiplied by their average duration in seconds, all multiplied by 100. A CCS is 1/36th of an Erlang. Class of Service (COS) A category used to determine a subscriber’s access to system options and features. The administrator assigns a class of service to each subscriber. DID See Direct Inward Dialing.
Glossary hunt group A group of telephone lines where the incoming calls are distributed according to a priority scheme. in-band signaling A method of connecting the voice server to the PBX as if it were a series of single-line telephones or a series of trunks in a hunt group. The term “in-band” is used because all of the call identification information is passed from the PBX to the voice server using DTMF signals on the same line as the voice connection.
Octel Unified Messenger Concepts & Planning Guide OctelNet gateway An OctelNet gateway enables Octel Unified Messenger subscribers to exchange voice messages with any other OctelNet-enabled voice mail system, either at the same site or at remote sites. OctelNet Gateway Administration Extension An administration tool that adds administration capabilities for an OctelNet gateway to Microsoft Exchange Server Administrator.
Glossary PBX integration A method that establishes communication between the PBX and the voice mail system. The PBX supplies information such as who is calling on internal calls, and the extension that the caller is trying to reach. PC client applications A group of applications that enable subscribers and administrators to access Octel Unified Messenger from their desktop PCs.
Octel Unified Messenger Concepts & Planning Guide subscriber A Microsoft Exchange user whose profile is enabled for voice messaging. A subscriber can use both the telephone user interface and the graphical user interface of Octel Unified Messenger. switch See PBX. telephone user interface (TUI) An interface through which callers and subscribers can access the Octel Unified Messenger system via the telephone.
Glossary voice mail domain A group of Octel Unified Messenger voice servers that share a common set of properties. All subscribers who are provided with telephone answering by these voice servers are said to “belong” to the same voice mail domain. voice mail enabling When a new user profile is created in Microsoft Exchange, it does not include any voice mail information.
This page intentionally left blank.
Index A access control list, definition account security GL-1 6-3 AccuCall+, definition automated attendant, definition GL-1 additional digits, OctelNet audio encoding formats ADPCM 3-12 GSM 3-12 5-4 B addressing designing addressing schemes 4-2 OctelNet addressing schemes 5-4 Dial-by-Name 4-4 local mailbox numbers 4-3 messages using PC user interface 3-4 telephone user interface 3-4 numeric addresses 4-5 OctelNet addresses 5-7 busy hour calculating traffic 2-5 definition GL-1 determining 2-4 un
Octel Unified Messenger Concepts & Planning Guide class of service, definition client components faxes accessing using the TUI 1-9 enabling subscribers 2-21 receiving 1-8 routing to third-party fax servers GL-2 3-5 components of Octel Unified Messenger client administration applications 3-7 PC access 3-6 telephone access 3-5 server tracing server 3-9 voice server 3-8 counters, statistics and performance G Grade of service (GOS) definition GL-2 GSM 3-12 definition D Dial-by-Name 4-4, 5-3 definition GL
Index message confirmation, definition messages addressing 3-4 sending 1-11 messaging, voice server component 3-8 Microsoft Exchange server 1-6 calculating impact on capacity 2-12 Microsoft Exchange site, definition monitoring, system usage reports multimedia, definition GL-3 6-6 NameNet OctelNet Gateway Administration Extension 3-7 definition GL-4 2-5, GL-4 2-14 1-6 Operation History Viewer 3-7 definition GL-4 using a slow network connection operator, definition optional greeting, definition O
Octel Unified Messenger Concepts & Planning Guide determining busy hour 2-4 disk space requirements 2-13 grade of service 2-6 number of Exchange users 2-12 outgoing call features 2-7 PBX integration 2-7 ports 2-4 voice mail domain 2-3 voice servers 2-9 worst case network load 2-14 planning.
Index Voice player, definition definition GL-6 functions 1-5 security 6-4 voice server 1-7 definition GL-7 functions 3-8 hardware and software requirements operations 2-15 sizing 2-9 transferring call to fax server 2-20 text-to-speech choosing a processor 2-10 definition GL-6 language identification 1-7 voice server component 3-8 Token Ring 1-10, 2-14 VoiceBridge II, PBX integration tracing server 1-8 definition GL-6 functions 3-9 requirements 2-11 2-10 3-11 W WAV file, definition GL-7 wide area
This page intentionally left blank.
