Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Executive Summary Designing a telephony and/or multimedia system with a software model allows for flexible system designs to match specific customer requirements. Dialogic HMP Software is an excellent platform to build your solution to the customers specific requirements. Knowing how to configure a Dialogic HMP Software runtime license enables you to choose the exact functionality that benefits your customers using Dialogic Host Media Processing Software Release 3.0 for Windows, including the of the Dialogic HMP Interface Boards that provide PSTN connectivity for building converged TDM and IP solutions.
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Application Note Table of Contents Configuring Media and Interface Resources... 2 Types of Resources... 2 Media Resources... 2 IP Network Interface Resources... 2 Resources... 2 Summary of Available Resources... 3 Rules for Combining Resources... 3 Combining Resources to Create Basic IP Media Sessions... 4 Multimedia with IVR Session Example... 4 Voice Mail Session Example... 4 Speech-Enabled IVR Session Example... 4 T.38 Fax Session Example... 4 Combining Resources to Create Sessions for a Call Center... 4 Session Using G.729 Example... 4 Session Using Example... 4 IVR/Auto-Attendant Session Using Example... 4 Combining Resources to Create Sessions for a Server... 5 Provisioning Examples... 6 Unified Messaging Server Example... 7 Center Example... 8 Hybrid Call Center Example... 8 Summary of Dialogic HMP Software 3.0 Resources... 10 For More Information... 10 1
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Configuring Media and Interface Resources Dialogic Host Media Processing Software Release 3.0 for Windows has a flexible software license model for resource provisioning rather than the fixed quantities model that is delivered in hardware boards. Choosing a customized package of resources for each license based on the types of resources available and the rules for combining them is a relatively straightforward task. Note: Information in this document is valid for Dialogic HMP Software 3.0. This information is subject to change in future releases of the software. Types of Resources The two general classes of resources available in Dialogic HMP Software 3.0 are Media and Interface. Media Resources Media resources are used for voice and video applications, such as video mail, video portal, voice mail, or Interactive Voice Response (IVR). The five types of Media resources are as follows: Voice for functions such as play/record, tones, call progress, etc. Continuous Speech Processing (CSP) as an add-on to voice resources and required for speech enablement. See the Rules for Combining Resources section for more information. Fax Termination A Multimedia resource for play/record of H.263 video and audio streams Access to Media resources is available through the Dialogic R4 API and Dialogic MM API. IP Network Interface Resources Interface resources are grouped in two categories: IP Media Streaming IP Media Streaming Resources IP Media Streaming resources provide the functionality required to stream media between Dialogic HMP Software 3.0 and IP clients using the Real-time Transport Protocol (). Two types of licensable resources are offered with Dialogic HMP Software: Basic Acts as a pipe to establish an connection between Dialogic HMP Software 3.0 and one remote IP endpoint. Each Voice over IP (VoIP) call into the server running Dialogic HMP Software 3.0 requires one resource. This resource provides streaming using the ITU-T voice coder. Enhanced Enables customers to implement the G.723.1, G.729a, and G.729ab coders for streaming over. A Basic resource is required for each Enhanced to become operational. See the Rules for Combining Resources section for more information. Resources The resources are required to access IP Call functionality provided through the H.323 and SIP protocol stacks from RADVISION, which are included with Dialogic HMP Software. Access to resources is available through the Dialogic Global Call API. Both H.323 and SIP are included in a single resource. The use of the Global Call API is optional, and is enabled when resources are licensed with Dialogic HMP Software. Alternatively, customers can choose to use their own call control stacks. resources can be used in two modes: first party call control and third party call control. When used in first-party mode, the resources are directly tied to a corresponding number of connections each call that is controlled by Dialogic HMP Software 3.0 is routed through the media server. (For example, 60 connections will require 60 resources.) Dialogic also s third party call control, giving developers the ability to set up SIP sessions without media, thus enabling a back-back user agent (B2BUA) type application. The media stream goes directly from one SIP endpoint to another. This allows for many more endpoints to be controlled by Dialogic HMP Software 3.0 than media streams passing through the media server itself (see Figure 1). Third-party mode is only available for SIP call control. When resources are used in firstparty mode, they must be used on IP connections. For example, on a system with 60 licensed Basic resources, 60 resources are required. When licensed in third-party mode, the number of IP 2
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Application Note First-Party Call HMP Media Server Third-Party Call HMP Media Server Figure 1. Models Call resources must be equal to (and can be greater than) the number of sessions. Note: A server must operate either in first- or third-party mode when using. Summary of Available Resources In summary, eight types of resources are available with Dialogic HMP Software 3.0: Media Voice Speech Fax Termination Multimedia IP Network Interface IP Media Streaming Basic Enhanced Rules for Combining Resources Some resources cannot be used alone, and must be combined with other resources. The following table lists the resources and identifies if a resource is required for using it. Resource Requires the Resource(s) Speech Voice Enhanced Basic Multimedia Basic Voice, conferencing, or fax used in an IP-only Basic environment and used with an external endpoint (without Dialogic HMP Interface Boards) Note: Voice resources and Conferencing resources used to record a conference would not require a Basic resource. 3
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Combining Resources to Create Basic IP Media Sessions Dialogic HMP Software 3.0 resources are combined to enable various sessions in an application, just as they would if telephony boards were in use. The following are examples of sessions (examples are for IP-based media servers): Multimedia with IVR Voice mail Speech-enabled IVR T.38 fax Multimedia with IVR Session Example A single multimedia (audio/video) session using H.263 as the video coder and as the audio coder along with SIP-based call control using the Global Call API requires: A Multimedia resource for play/record of H.263 video and audio streams A Voice resource to provide media resources for DTMF detection A Basic resource An resource for SIP call control using the Global Call API Voice Mail Session Example A single voice mail session using G.729 and the H.323 call control stack requires: A Voice resource to provide media resources for play/ record and DTMF detection A Basic resource An Enhanced resource for G.729 An resource for Global Call API of H.323 and SIP Speech-Enabled IVR Session Example A single speech-enabled IVR session using and the SIP call control stack requires: A Voice resource to provide media resources for play/ record A Speech resource for speech enablement via CSP A Basic resource An resource for Global Call API T.38 Fax Session Example A single fax session using the Global Call API requires: A Fax resource A Basic resource An resource for Global Call API Note: Fax sessions never require Enhanced resources. Combining Resources to Create Sessions for a Call Center For a call center, two kinds of sessions are basic: sessions in which a customer calls an agent or an agent calls another agent, and IVR or auto-attendant sessions. Global Call API is used in the following examples. Session Using G.729 Example A single voice call session using G.729 requires: A Voice resource to provide a Media resource for the call A Basic resource An Enhanced resource for G.729 An resource for Global Call API Session Using Example A single voice call session using requires: A Voice resource to provide Media resources for the call A Basic resource An resource for Global Call API IVR/Auto-Attendant Session Using Example A single IVR/auto-attendant session using requires: A Voice resource to provide Media resources for the call to the IVR/auto attendant A Basic resource An resource for Global Call API Since the IVR/auto attendant is not speech-enabled, only a Voice resource is required. 4
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Application Note Dialogic HMP Software Media Processing Resources Voice Enhanced Basic Enhanced Basic Basic IP Network Interface Resources Session G.729 Session Session G.723 Figure 2. Resources for a Server Combining Resources to Create Sessions for a Server A conference server usually requires one type of session, but provision for different coders may be needed. In addition, a conference is often recorded. The ability to record a conference requires a single Voice resource and one additional resource. The following is a list of resources needed for a threesession conference, assuming three endpoints: one using, one using G.723, and one using G.729. The conference also must be recorded. A Voice resource to provide a Media resource for recording the conference Four Conferencing resources, one for each of the three conference participants, plus one to connect the Voice resource to the conference so that it can be recorded Three Basic resources, one for each conferee Two Enhanced resources for G.723 and G.729 Three resources for Global Call API Figure 2 shows how these resources are grouped. 5
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Dialogic HMP Software Media Processing Resources Speech Voice Voice T.38 Fax Enhanced Basic Basic Basic IP Network Interface Resources T.38 Fax Gateway Voice Mail Session G.729 Speech-Enabled IVR Session T.38 Fax Session Figure 3. Resources for a Unified Messaging Server The number of Enhanced resources governs the number of sessions that will allow the use of lowbit-rate coders and lower bandwidth usage. The number of Enhanced resources must be equal to or less than the number of Basic resources. The number of resources must equal the number of Basic resources if Global Call API is required. Provisioning Examples The common types of solutions in which Dialogic HMP Software 3.0 is used include unified messaging servers and IP call centers. Hypothetical examples for provisioning such solutions are provided. 6
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Application Note Media Processing Resources Dialogic Host Media Processing Software Voice Enhanced Basic Basic Basic IP Network Interface Resources Session G.729 Session IVR/AA Session Figure 4. Resources for an Center Unified Messaging Server Example Table 1 provides the requirements for a unified messaging server and the required Dialogic HMP Software 3.0 resources. Scenario Requirements Resource Required A unified messaging server with 120 sessions, 120 Basic resources with 60 Enhanced resources 60 of which use low bit rate coders Use of the Dialogic Global Call API 120 resources A maximum of 30 users of voice applications, 30 Voice resources and 10 Speech resources such as IVR and voice mail, 10 of which are speech enabled 30 conference participants 30 resources 5 fax sessions 5 Fax resources Table 1. Unified Messaging Server Requirements Figure 3 shows how these resources are grouped. 7
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Center Example Table 2 provides the requirements for an IP call center and the required Dialogic HMP Software 3.0 resources. Scenario Requirements Resource Required An IP call center with 40 agents and 80 trunk lines 120 Basic resources with 60 Enhanced resources for incoming calls, requiring 120 sessions, 60 of which will allow the use of low-bit-rate coders Use of the Dialogic Global Call API 120 resources A maximum of 80 voice ports to enable playing of 80 Voice resources and 30 Speech resources prompts or recording messages, with 30 possible speech-enabled sessions 30 conferencing sessions for coaching and monitoring 30 resources A maximum of 20 conference ports for agent 20 resources coaching and monitoring Table 2. Center Requirements Figure 4 shows how these resources are grouped. Hybrid Call Center Example Table 3 provides the requirements for a hybrid call center and the required Dialogic HMP Software 3.0 resources. Scenario Requirements Resource Required A hybrid PBX ing two E-1 lines for TDM 30 Basic resources traffic and 30 IP stations Requires a dual-span digital network interface board 30 resources to the TDM traffic Use of the Dialogic Global Call API A maximum of 60 voice ports to enable playing of 60 Voice resources prompts or recording messages 5 fax ports available for V.17/T.38 Fax Termination 5 Fax resources or Gateway functionality A maximum of 20 conference ports for agent 20 resources coaching and monitoring Table 3. Hybrid Call Center Requirements Figure 5 shows how these resources are grouped. 8
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Application Note Media Processing Resources Voice Fax IP Network Interface Resources TDM Interface Dual Span E-1 Digital Network Interface Board Coach Agent Customer PSTN External Caller PSTN Fax Figure 5. Resources for Hybrid Call Center 9
Configuring Dialogic Host Media Processing Software Release 3.0 for Windows Software Licenses Summary of Dialogic HMP Software 3.0 Resources Table 4 provides a summary of the information required for configuring licenses for Dialogic HMP Software 3.0. Dialogic HMP Software 3.0 has different licensing limitations based on which release is in use; these limitations are also detailed in Table 4. Resource Type Dialogic HMP Software 3.0 Limits Notes Basic 750 maximum Sum of the number of sessions allowed or lines plus trunks allowed; is the default coder used Enhanced 200 maximum; less than or equal Allows use of low bit rate coder; must be equal to to Basic or less than the number of Basic resources Equal to number of Basic Requires one resource for each Basic for first party call control resource if Dialogic Global Call API is required Equal to, or greater than for third Delivered stack party call control, 5000 maximum (H.323 and SIP) must be used Voice 750 maximum Equals the number of play/record sessions Speech 240 maximum Equals the number of Voice sessions that can be speech-enabled Must be equal to or less than the number of Voice resources 580 maximum To record a conference, include a Voice resource and an additional resource Fax 120 maximum T.38 fax sessions for all releases V.17 fax sessions for HMP Software 2.0 and 3.0 only Multimedia 120 maximum H.263 Table 4. Summary of Dialogic HMP Software 3.0 For More Information General information, proof points, and case studies about the products described in this application note http://www.dialogic.com/manuals/hmp30win/default.htm 10
To learn more about Dialogic products, go to www.dialogic.com. Dialogic Corporation 9800 Cavendish Blvd., 5th floor Montreal, Quebec CANADA H4M 2V9 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH PRODUCTS OF DIALOGIC CORPORATION OR ITS SUBSIDIARIES ( DIALOGIC ). NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Dialogic may make changes to specifications, product descriptions, and plans at any time, without notice. Dialogic is a registered trademark of Dialogic Corporation. Dialogic s trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized use of Dialogic s trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic s trademarks requires proper acknowledgement. Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of actual companies and products mentioned herein are the trademarks of their respective owners. Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement their concepts or applications, which licenses may vary from country to country. Copyright 2008 Dialogic Corporation All rights reserved. 03/08 10721-02 www.dialogic.com