Lucent Technologies Octel Unified Messenger Planning Manual
  1. Manuals
  2. Brands
  3. Lucent Technologies Manuals
  4. Telephone System
  5. Octel Unified Messenger
  6. Planning manual
Lucent Technologies Octel Unified Messenger Planning Manual

Lucent Technologies Octel Unified Messenger Planning Manual

Concepts and planning guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Octel Unified Messenger
Concepts and Planning Guide
101-1620-005

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Octel Unified Messenger and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Lucent Technologies Octel Unified Messenger

Summary of Contents for Lucent Technologies Octel Unified Messenger

  • Page 1 Octel Unified Messenger Concepts and Planning Guide 101-1620-005...
  • Page 2 E-mail: unified.messenger@octel.com This software is the property of Lucent Technologies Octel Messaging Division, formerly Octel Communications Corporation, and may not be used without a valid written license agreement. This software is protected by the copyright laws of the United States, international copyright treaties, and all other applicable national laws. The...
  • Page 3 Preface Overview This guide provides: Guidelines for planning and sizing a new installation. A description of the hardware and software components of Octel Unified Messenger. The concepts underlying Octel Unified Messenger, including voice mail domains, addressing, client and server operations, and telephony concepts.
  • Page 4 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.
  • Page 5 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: Convention Description Filenames and extensions, directory names, paths,...
  • Page 6 This page intentionally left blank.

  • Page 7: Table Of Contents

    Contents Chapter 1 Introducing Octel Unified Messenger Introduction ..............1-2 Product features .
  • Page 8 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 .
  • Page 9 Contents Addressing OctelNet messages to Octel Unified Messenger recipients ....5-7 Providing single-site interoperability ..........5-8 Automatic mailbox forwarding .
  • Page 10 This page intentionally left blank.
  • Page 11 PART 1 CONCEPTS...
  • Page 12 This page intentionally left blank.

  • Page 13: Introducing Octel Unified Messenger

    Introducing Octel Unified Messenger This chapter introduces Octel Unified Messenger and discusses the following topics: Octel Unified Messenger product features. The “unified mailbox” concept. Networked components of the Octel Unified Messenger environment. Benefits of using Octel Unified Messenger. 101-1620-005...

  • Page 14: Introduction

    Interoperability Utilizing OctelNet, Octel Unified Messenger systems interoperate with other Lucent Technologies Octel Messaging Division (OMD) voice messaging systems. This means that subscribers can exchange voice messages with users on other Octel messaging servers that support OctelNet.

  • Page 15: Product Features

    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: A single unified view of messages using the Exchange Server mailbox.

  • Page 16: The Unified 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.

  • Page 17: Telephone User Interface

    Introducing Octel Unified Messenger Telephone user interface Subscribers can access their unified mailbox from a telephone user interface to do the following: Send and receive voice messages. Play back voice messages. Listen to e-mail messages, using TTS conversion. Forward fax messages to other recipients or to a fax device for printing.

  • Page 18: Networked Components

    Octel Unified Messenger Concepts & Planning Guide Networked components Figure 1-2 shows the networked components of the Octel Unified Messenger environment. Figure 1-2. Octel Unified Messenger networked components 1 PBX 2 Telephone user interface 3 Fax (optional) 4 Octel voice server 5 Fax server (optional) 6 PC user interface 7 LAN...

  • Page 19: Voice Server

    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: Answers PBX-forwarded telephone calls. Plays personalized greetings. Records messages. Sends compressed message files to subscriber mailboxes for storage.

  • Page 20: Fax Server

    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”...

  • Page 21: Pbx

    Introducing Octel Unified Messenger Access to faxes The telephone user interface recognizes messages of the message type using the TUI 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.

  • Page 22: Lan

    Octel Unified Messenger Concepts & Planning Guide 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.

  • Page 23: Benefits Summary

    Introducing Octel Unified Messenger Benefits summary Octel Unified Messenger provides the following benefits to your organization. Subscriber convenience With Octel Unified Messenger, subscribers can: Store all messages in one place, regardless of the message type. Access voice, e-mail, and fax messages from either the telephone or PC user interface.
  • Page 24 This page intentionally left blank.
  • Page 25 PART 2 PLANNING...
  • Page 26 This page intentionally left blank.

  • Page 27: Sizing The System

    Sizing the system This chapter discusses the main points to consider when sizing the hardware for Octel Unified Messenger. It contains information about: Voice mail domain design rules. Establishing the number of voice ports required. Calculating the number of voice servers required. Hardware and software requirements.

  • Page 28: Introduction

    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.

  • Page 29: Design Rules For Voice Mail Domains

    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. Each voice server can belong to one voice mail domain only. Each voice mail subscriber can belong to one voice mail domain only.

  • Page 30: Sizing Ports

    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.
  • Page 31 Sizing the system Units of Busy hour traffic is normally expressed in units of measurement such as measurement for minutes, Erlangs, or Centum Call Seconds (CCS). busy hour traffic Note: 1 CCS = 100 call seconds. For example, there are 3,600 seconds in 1 hour.
  • Page 32 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.
  • Page 33 Sizing the system PBX integration As described in “PBX integration” on page 3-10, PBX integrations are device sizing 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.
  • Page 34 Octel Unified Messenger Concepts & Planning Guide Total estimated port To summarize, when sizing the number of total ports required for any requirements given server to provide a desired GOS, the following factors must be considered. Estimated total busy hour offered traffic generated by both internal and external callers.

  • Page 35: Calculating The Number Of Voice Servers Required

    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.

  • Page 36: Hardware And Software Requirements For Octel Unified Messenger Servers

    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 For systems using 4 to 12 ports: 200 MHz Intel Pentium. server requirements For systems using 16 to 24 ports: 400 MHz Intel Pentium. 128 MB RAM.
  • Page 37 Sizing the system Minimum tracing For systems with up to 2 voice servers: 200 MHz Intel Pentium. server requirements For systems with more than 2 voice servers: 400 MHz Intel Pentium 64 Mbytes RAM. Access to a CD-ROM drive to install the software. Microsoft Windows NT 4.0 with the latest service pack.

  • Page 38: Evaluating The Additional Load On Microsoft Exchange Servers

    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. Number of Use the following guidelines to estimate the effect of adding Octel Exchange users Unified Messenger to an existing Exchange environment: Adding Octel Unified Messenger capability to a single Exchange...
  • Page 39 Sizing the system Disk space Voice messages require 4 Kbytes per second (240 Kbytes per minute) of requirements 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.

  • Page 40: Evaluating The Additional Network Traffic

    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.
  • Page 41 Sizing the system Types of operations The Octel Unified Messenger voice servers open data streams between voice servers and: Exchange servers. Client systems. The actual Exchange server associated with each data stream depends on the operation and, in some cases, the associated mailbox: 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.

  • Page 42: Using Octel Unified Messenger Via Slow Network Connections

    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: Octel Unified Messenger voice servers. 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.

  • Page 43: Using The Telephone

    Sizing the system Using the telephone Voice messages can be played back and recorded using the telephone. Playing back voice When playing back a voice message, the message is moved from the messages Exchange server to a telephone via the voice server. The playback is not affected by the speed of the client network connection.
  • Page 44 Octel Unified Messenger Concepts & Planning Guide Recording voice When recording voice messages, the data must be copied from the voice messages 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.

  • Page 45: The Effect Of Slow Network Connections On Octel Unified Messenger Applications

    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.

  • Page 46: Octel Unified Messenger Interoperability With Third-Party Fax Servers

    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.

  • Page 47: Requirements For Third-Party Fax Server Interoperability With Octel Unified Messenger

    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: Octel Unified Messenger version 2.0 or higher must be installed. The fax server must be integrated with Microsoft Exchange as an Exchange Connector or an Exchange gateway for fax.

  • Page 48: Routing Inbound Fax Calls To The Third-Party Fax Server

    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.

  • Page 49: System Architecture

    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. 101-1620-005...

  • Page 50: Introduction

    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.
  • Page 51 System architecture Figure 3-1. Example of typical implementation of voice mail domains San Francisco Voice mail domain 1 London Voice mail domain 2 1 PBX 2 Subscribers VMD1 3 Octel Tracing Server for VMD1 4 Octel Voice Server 5 Octel Tracing Server for VMD2 6 Microsoft Exchange server 7 Subscribers VMD2 101-1620-005...

  • Page 52: Addressing Messages

    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 A subscriber can retrieve recipients’ addresses from the Exchange interface directory, in other words, from their address books.

  • Page 53: System Components

    System architecture System components The system components of Octel Unified Messenger are classified in three categories: Client components Server components 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.
  • Page 54 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.
  • Page 55 System architecture Administration System administrators can use the following applications and tools to applications 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.

  • Page 56: Server Components

    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 An Octel Unified Messenger voice server provides or supports the following functions: Call management.
  • Page 57 System architecture Tracing server A tracing server maintains connections with all voice servers in a voice mail domain, and performs the following tasks: 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.

  • Page 58: Pbx Integration

    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.
  • Page 59 System architecture Digital Meridian The Digital Meridian Integration Device (DMID) is a device that provides Integration Device 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.

  • Page 60: Audio Encoding Formats

    Octel Unified Messenger Concepts & Planning Guide Audio encoding formats Octel Unified Messenger supports the following audio encoding formats: ADPCM audio encoding format. This is a high quality audio encoding algorithm with a coding rate of 32 kilobit per second. Global System for Mobile Communications (GSM) 6.10 audio encoding format.

  • Page 61: Designing Addressing Schemes

    Designing addressing schemes This chapter introduces different forms of addressing and describes the following addressing schemes: Local mailbox number. Dial-by-Name. Numeric addresses. 101-1620-005...

  • Page 62: Introduction

    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.

  • Page 63: Local Mailbox Numbers

    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.

  • Page 64: Dial-By-Name

    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”...

  • Page 65: Numeric Addresses

    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.
  • Page 66 This page intentionally left blank.

  • Page 67: Providing Interoperability With Existing Octel Servers

    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: Designing an OctelNet addressing scheme. Addressing OctelNet messages. Providing single-site interoperability.

  • Page 68: Introduction To Octelnet

    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.

  • Page 69: Octelnet Messaging Features

    Providing interoperability with existing Octel servers OctelNet Messaging Features When sending or receiving messages via OctelNet, subscribers can: Mark messages as urgent. Request message confirmation. View envelope information. Reply to messages. Address messages by spelling a recipient’s name, using NameNet. Receive spoken name confirmation, using NameNet.

  • Page 70: Designing An Octelnet Addressing Scheme

    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.

  • Page 71: Octelnet Addressing Scheme Design Rules

    Providing interoperability with existing Octel servers OctelNet addressing scheme design rules When designing OctelNet addressing schemes, the following rules must be observed. The mailbox length must be greater than or equal to 3 digits. The additional digits must be less than or equal to the mailbox length.
  • Page 72 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. Valid OctelNet multiple addressing schemes Addressing scheme Why is this valid prefix additional mailbox...

  • Page 73: Addressing Octelnet Messages

    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.

  • Page 74: Providing Single-Site Interoperability

    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.

  • Page 75: Chapter 6 Connecting With The Pbx And Establishing Security Rules

    Connecting with the PBX and establishing security rules This chapter introduces the following: How to connect with the PBX. The Octel Unified Messenger’s security features that prevent unauthorized access. 101-1620-005...
  • Page 76 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.

  • Page 77: Establishing Security Rules

    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.
  • Page 78 Octel Unified Messenger Concepts & Planning Guide Subscriber Octel Unified Messenger subscribers maintain a password for accessing password for the their voice mail through the telephone user interface. They can do this telephone user either from Octel Unified Messenger Options on their desktop PC or interface through the telephone user interface.
  • Page 79 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.
  • Page 80 Octel Unified Messenger Concepts & Planning Guide Recipient’s name Octel Unified Messenger confirms the name of the recipient before confirmation 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.

  • Page 81: Appendix A Appendix A - Sizing For Ports

    Appendix A - Sizing for ports This appendix gives guidelines for estimating how many users can be supported with a given number of voice ports. 101-1620-005...

  • Page 82: Calculating The Number Of Supported Subscribers

    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.
  • Page 83 Appendix A - Sizing for ports Table A-2. Number of supported subscribers with eight ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1083 101-1620-005...
  • Page 84 Octel Unified Messenger Concepts & Planning Guide Table A-3. Number of supported subscribers with twelve ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1102 1417 1983 101-1620-005...
  • Page 85 Appendix A - Sizing for ports Table A-4. Number of supported subscribers with sixteen ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1051 1471 1634 2101 2942 101-1620-005...
  • Page 86 Octel Unified Messenger Concepts & Planning Guide Table A-5. Number of supported subscribers with twenty ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1317 1097 1411 1975 2194 2821 3950 101-1620-005...
  • Page 87 Appendix A - Sizing for ports Table A-6. Number of supported subscribers with twenty-four ports Average usage per Busy hour peak (% of Number of subscribers subscriber per day daily calls) (minutes) 1246 1187 1661 1384 1780 2492 2769 3560 4983 101-1620-005...
  • Page 88 Octel Unified Messenger Concepts & Planning Guide Table A-7. Number of supported subscribers with twenty-eight ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1208 1079 1510 1119 1438 2014 1678 2158 3021 3356...
  • Page 89 Appendix A - Sizing for ports Table A-8. Number of supported subscribers with thirty-two ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1017 1423 1271 1779 1318 1694 2372 1977 2542 3558 3954...
  • Page 90 Octel Unified Messenger Concepts & Planning Guide Table A-9. Number of supported subscribers with thirty-six ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1171 1640 1139 1464 2050 1519 1952 2733 2278 2929...
  • Page 91 Appendix A - Sizing for ports Table A-10. Number of supported subscribers with forty ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1032 1327 1858 1291 1659 2323 1721 2212 3097 2581 3318...
  • Page 92 Octel Unified Messenger Concepts & Planning Guide Table A-11. Number of supported subscribers with forty-four ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1156 1486 2080 1444 1857 2600 1926 2476 3467 2889...
  • Page 93 Appendix A - Sizing for ports Table A-12. Number of supported subscribers with forty-eight ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1280 1645 2303 1600 2057 2879 2133 2742 3839 3199 4113...
  • Page 94 Octel Unified Messenger Concepts & Planning Guide Table A-13. Number of supported subscribers with fifty-two ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1404 1805 2527 1755 2256 3158 2340 3008 4211 3509...
  • Page 95 Appendix A - Sizing for ports Table A-14. Number of supported subscribers with fifty-six ports Average usage per Busy hour peak (% of Number of subscriber per day daily calls) subscribers (minutes) 1529 1965 2752 1911 2457 3440 2548 3276 4586 3822 4914...
  • Page 96 Octel Unified Messenger Concepts & Planning Guide Table A-15. Number of supported subscribers with sixty ports Average usage per Busy hour peak (% of Number of subscribers subscriber per day daily calls) (minutes) 1655 2127 2978 2068 2659 3723 2758 3546 4964 4137...
  • Page 97 Appendix A - Sizing for ports Table A-16. Number of supported subscribers with sixty-four ports Average usage per Busy hour peak (% of Number of subscribers subscriber per day daily calls) (minutes) 1781 2289 3205 2226 2862 4006 2968 3815 5342 4451 5723...
  • Page 98 Octel Unified Messenger Concepts & Planning Guide Table A-17. Number of supported subscribers with sixty-eight ports Average usage per Busy hour peak (% of Number of subscribers subscriber per day daily calls) (minutes) 1907 2452 3433 2384 3065 4292 3179 4087 5722 4769...
  • Page 99 Appendix A - Sizing for ports Table A-18. Number of supported subscribers with seventy-two ports Average usage per Busy hour peak (% of Number of subscribers subscriber per day daily calls) (minutes) 2034 2615 3662 2543 3269 4577 3390 4359 6103 5086 6539...
  • Page 100 This page intentionally left blank.

  • Page 101: Appendix B Appendix B - Grade Of Service

    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). 101-1620-005...

  • Page 102: Calculating Busy Hour Traffic

    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.
  • Page 103 Appendix B - Grade of service Table B-2. Maximum busy hour traffic supported for a GOS of P.02 Ports Erlangs Minutes 1.08 65.00 3.61 216.67 6.61 396.67 9.81 588.33 13.17 790.00 16.61 996.67 20.14 1208.33 23.72 1423.33 27.33 1640.00 30.97 1115 1858.33 34.67...
  • Page 104 Octel Unified Messenger Concepts & Planning Guide Table B-3. Maximum busy hour traffic supported for a GOS of P.03 Ports Erlangs Minutes 1.25 75.00 3.97 238.33 7.14 428.33 10.50 630.00 13.97 838.33 17.56 1053.33 21.19 1271.67 24.89 1493.33 28.64 1031 1718.33 32.39 1166...
  • Page 105 Appendix B - Grade of service Table B-4. Maximum busy hour traffic supported for a GOS of P.05 Ports Erlangs Minutes 1.50 90.00 4.53 271.67 7.94 476.67 11.53 691.67 15.22 913.33 19.03 1141.67 22.86 1371.67 26.72 1603.33 30.64 1103 1838.33 34.58 1245 2075.00...
  • Page 106 This page intentionally left blank.

  • Page 107: Glossary

    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).
  • Page 108 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/36 of an Erlang.
  • Page 109 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.
  • Page 110 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.
  • Page 111 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.
  • Page 112 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.
  • Page 113 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.
  • Page 114 This page intentionally left blank.

  • Page 115: Index

    Index audio encoding formats ADPCM 3-12 access control list, definition GL-1 3-12 account security automated attendant, definition GL-1 AccuCall+, definition GL-1 additional digits, OctelNet addressing busy hour designing calculating traffic addressing schemes definition GL-1 OctelNet addressing schemes determining Dial-by-Name units of measurement local mailbox numbers messages using PC user interface...
  • Page 116 Octel Unified Messenger Concepts & Planning Guide class of service, definition GL-2 faxes accessing using the TUI client components enabling subscribers 2-21 components of Octel Unified Messenger receiving client routing to third-party fax servers 2-22 administration applications PC access telephone access Grade of service (GOS) server definition...
  • Page 117 Index message confirmation, definition GL-3 single-site interoperability automatic mailbox forwarding messages sizing ports for outgoing messages addressing OctelNet gateway sending 1-11 definition GL-4 messaging, voice server component voice server component Microsoft Exchange server OctelNet Gateway Administration calculating impact on capacity 2-12 Extension Microsoft Exchange site, definition...
  • Page 118 Octel Unified Messenger Concepts & Planning Guide planning. See sizing determining busy hour disk space requirements 2-13 please hold prompt, definition GL-5 grade of service port group, definition GL-5 number of Exchange users 2-12 Port Monitor outgoing call features definition GL-5 PBX integration using a slow network connection...
  • Page 119 Index definition GL-6 Voice player, definition GL-7 functions voice server security definition GL-7 text-to-speech functions choosing a processor 2-10 hardware and software requirements 2-10 definition GL-6 operations 2-15 language identification sizing voice server component transferring call to fax server 2-20 Token Ring 1-10 2-14...
  • Page 120 This page intentionally left blank.

Table of Contents