Intel IP Media Server User Manual
IP Media Server for Host Media
Processing
Demo Guide
July 2005
05-2389-003
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
This IP Media Server for Host Media Processing Demo Guide as well as the software described in it is furnished under license and may only be used
or copied in accordance with the terms of the license. The information in this manual is furnished for informational use only, is subject to change
without notice, and should not be construed as a commitment by Intel Corporation. Intel Corporation assumes no responsibility or liability for any
errors or inaccuracies that may appear in this document or any software that may be provided in association with this document.
Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any
means without express written consent of Intel Corporation.
Copyright © 2003, Intel Corporation
BunnyPeople, Celeron, Chips, Dialogic, EtherExpress, ETOX, FlashFile, i386, i486, i960, iCOMP, InstantIP, Intel, Intel Centrino, Intel Centrino logo,
Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure,
Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Xeon, Intel XScale, IPLink, Itanium, MCS, MMX, MMX logo, Optimizer logo, OverDrive,
Paragon, PDCharm, Pentium, Pentium II Xeon, Pentium III Xeon, Perfor mance at Your Command, skoool, Sound Mark, The Computer Inside., The
Journey Inside, VTune, and Xircom are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other
countries.
* Other names and brands may be claimed as the property of others.
Publication Date: July 2005
Document Number: 05-2389-003
Intel Converged Communications, Inc.
1515 Route 10
Parsippany, NJ 07054
For Technical Support, visit the Intel Telecom Support Resources website at:
http://developer.intel.com/design/telecom/support
For Products and Services Information, visit the Intel Telecom Products website at:
http://www.intel.com/design/network/products/telecom
For Sales Offices and other contact information, visit the Where to Buy Intel Telecom Products page at:
http://www.intel.com/buy/networking/telecom.htm
IP Media Server for HMP Demo Guide – July 2005
Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Demo Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 Preparing to Run the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 Editing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.1 Configuration File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.2 Editing the IPMediaServer.cfg Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Compiling and Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Running the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1 Starting the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Demo Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3 Using the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.1 Keyboard Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.2 Using the Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4 Stopping the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5Demo Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Files Used by the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Demo Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.2 PDL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2 Programming Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2.1 Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.2 EventRouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.2.3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.4 Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3 Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.5 Event Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.1 Event Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.2 Handling Keyboard Input Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.3 Handling SRL Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.4 Handling Application Exit Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.5.5 TSUsrEvent Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.6 Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
IP Media Server for HMP Demo Guide – July 2005 3
Contents
Figures
1 Demo Voice Menu Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 IP Media Server Demo Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3 EventRouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4 IP Media Server Demo Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5 System Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6 Typical Scenario: Call Offered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7 Typical Scenario: Play Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
8 Typical Scenario: Fax Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9 Typical Scenario: Establish Fax Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10 Typical Scenario: Fax Session Established . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
11 Typical Scenario: Fax Sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12 Typical Scenario: Fax Session Closed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
13 Typical Scenario: Fax Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
4 IP Media Server for HMP Demo Guide – July 2005
Contents
Tables
1 Command Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2 Runtime Keyboard Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3 Files in IPMediaServer Folder Used by the IP Media Server Demo . . . . . . . . . . . . . . . . . . . . . 25
4 Files in Modules Folder Used by the IP Media Server Demo . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5 PDL Files Used by the IP Media Server Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6 Application Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7 IP Module Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8 Voice Module Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9 Fax Module Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
IP Media Server for HMP Demo Guide – July 2005 5
Contents
6 IP Media Server for HMP Demo Guide – July 2005
Revision History
This revision history summarizes the changes made in each published version of this document.
Document No. Publication Date Description of Revisions
05-2389-003 July 2005 Added updated Linux information.
05-2389-002 April 2005 Globally changed file paths to use installation directory environment variable, and to
reflect latest Windows directory hierarchy
Globally removed Linux-specific information and references to pre-1.3 HMP releases
Demo Description chapter : Added note about channel density and numbering
restrictions
Demo Voice Menu Flowchart figure : Multiple minor updates for clarity
05-2389-001 September 2004 Initial version under this title and part number as an HMP-specific document. Much of
the information contained in this document was previously published in the IP Media
Server (Global Call) Demo Guide for Windows Operating Systems, document
number 05-2065-001. The following changes were made in preparing this document:
Software Requirements section: Added HMP 1.2 Linux and HMP 1.1 Windows FP1
releases with description of differences
Configuration File Location section: Added location info for Linux
Editing the IPMediaServer.cfg Configuration File section: Updated descriptions of
QoS attributes to match IPML API Reference. Updated sample configuration file
listing.
Compiling and Linking section: Added compile info for Linux
Starting the Demo section : Added file location info for Linux
Using the Media Server section: Added CSP Barge-in to Main Menu listing.
Corrected description of CSP Prompt.
Demo Voice Menu Flowchart figure : Corrected description of CSP Prompt. Clarified
descriptions of fax prompts.
Demo Source Code Files section: Added Linux directory info. Added Linux makefiles
to file lists.
PDL Files section: Added file location info for Linux. Added Linux makefile to file list.
Application Classes table: Changed module order (now IP last) in description of init
method
Initialization section: Changed module initialization order (now IP last)
System Initialization figure: Changed module initialization order (now IP last)
Handling Application Exit Events section: Deleted Ctrl+C
TSUsrEvent Structure section: Updated field descriptions
IP Media Server for HMP Demo Guide — July 2005 7
Revision History
8 IP Media Server for HMP Demo Guide — July 2005
About This Publication
This section describes the purpose of the guide, the intended audience, and provides references to
other documents that may be useful to the user.
• Purpose
• Intended Audience
• How to Use This Publication
• Related Information
Purpose
This guide provides information on the IP Media Server for HMP demo that is available with the
Intel NetStructure
its requirements, and provides details on how it works.
This guide specifically documents the IP Media Server for HMP demo as it is implemented and
supplied in the Host Media Processing Software 1.3 for Windows*, Host Media Processing
Software 1.5 for Linux* and later releases.
Note that the IP Media Server demo that is supplied with Intel
software has significantly different functionality than the Host Media Processing implementation,
and is therefore described in a separate Demo Guide document.
®
Host Media Processing Software product. The guide describes the demo, lists
®
Dialogic® System Release 6.x
Intended Audience
This guide is intended for application developers who will be developing a media server
application using the Global Call API. Developers should be familiar with the C++ programming
language and either the Windows or Linux programming environments.
This information is intended for:
• Distributors
• Toolkit Developers
• Independent Software Vendors (ISVs)
• Value Added Resellers (VARs)
• Original Equipment Manufacturers (OEMs)
IP Media Server for HMP Demo Guide — July 2005 9
About This Publication
How to Use This Publication
Refer to this publication after you have installed the hardware and the system software.
This publication assumes that you are familiar with the Windows or Linux operating system and
the C++ programming language.
The information in this guide is organized as follows:
• Chapter 1, “Demo Description” introduces you to the demo and its features
• Chapter 2, “System Requirements” outlines the hardware and software required to run the
demo
• Chapter 3, “Preparing to Run the Demo” describes the preparations required before running
the demo
• Chapter 4, “Running the Demo” describes how to run the demo
• Chapter 5, “Demo Details” provides details on how the demo works
Related Information
See the following for more information:
• Intel NetStructure Host Media Processing Software Release Guide
• Global Call IP for Host Media Processing Technology Guide
• Global Call API Library Reference
• Voice API Programming Guide
• Voice API Library Reference
• Standard Runtime Library API Programming Guide
• Standard Runtime Library API Library Reference
• Fax Software Reference
• http://developer.intel.com/design/telecom/support/ (for technical support)
• http://www.intel.com/design/network/products/telecom (for product information)
10 IP Media Server for HMP Demo Guide — July 2005
1.Demo Description
This chapter describes the basic features of the IP Media Server for HMP demo.
The IP Media Server for HMP demo is an object-oriented host-based application that demonstrates
using the Global Call API to build an IP media server, providing voice and fax services via IP
technology. The demo source code can be used as sample code for those who want to begin
developing an application from a working application.
Note: The IP Media Server for HMP demo is limited to a maximum of four simultaneous channels.
Additionally, the channel numbers used must be below 120; the demo will fail to run if you attempt
to use a channel number higher than 120.
The IP Media Server for HMP demo supports the following features:
• Voice service
• Fax service
• CSP barge in
• Configuration file
• Command line options
Note: The IP Media Server for HMP demo does not function as a gateway. Therefore, it can only answer
calls from the IP network. Gateway functionality can be added by writing additional software code
within the IP module that will allow it to make outgoing calls to the IP network, and connecting a
gateway to interface with the PSTN.
1
The IP Media Server for HMPIP Media Server (Global Call) demo is a cross-OS demo, designed to
run under both the Windows and Linux environments. Most of the differences in the environments
are handled directly by the programming interface and are transparent to the user. Other
differences, due to inherent differences in the operating systems, are handled by the Platform
Dependency Library (PDL). For more information about the PDL refer to the source code in the
pdl_win or pdl_linux directories directory.
IP Media Server for HMP Demo Guide — July 2005 11
Demo Description
12 IP Media Server for HMP Demo Guide — July 2005
2.System Requirements
This chapter discusses the system requirements for running the IP Media Server for HMP demo. It
contains the following topics:
• Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
• Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1 Hardware Requirements
To run the IP Media Server for HMP demo, you need:
®
• Intel
• CD-ROM drive
• VGA display
• Pointing device (e.g., mouse)
• 100Base-T network interface card (NIC)
Pentium® III processor (minimum requirement). For detailed processor clock speed and
memory requirements, refer to the Release Guide (or Release Notes) for the HMP version you
are using.
Note: A 1000Base-T NIC will yield better performance.
2
Memory Requirements
For production purposes, a minimum of 512 MB of memory is required. For development and
demo purposes using a low-end configuration, 256 MB of memory may be sufficient.
IP Endpoints
The following H.323 IP devices were tested for interoperability with HMP:
• Microsoft* NetMeeting* (Version 3.0 or later)
• Polycom* SoundPoint* IP 500
• Intel NetStructure
• Intel Optimizers Internet Phone
The following SIP IP devices were tested for interoperability with HMP:
• Polycom SoundPoint IP 500
• Intel NetStructure PBX-IP Media Gateway
®
PBX-IP Media Gateway
IP Media Server for HMP Demo Guide — July 2005 13
System Requirements
2.2 Software Requirements
To run the IP Media Server for HMP demo as documented in this guide, you need one of the
following software releases:
• Intel NetStructure Host Media Processing Software 1.3 for Windows (or later)
• Intel NetStructure Host Media Processing Software 1.5 for Linux (or later)
For operating system requirements, see the release documentation (Release Guide or Release
Notes) that accompanies your specific HMP release.
14 IP Media Server for HMP Demo Guide — July 2005
3.Preparing to Run the Demo
This chapter discusses the preparations necessary to run the IP Media Server for HMP demo. It
provides information about the following topics:
• Editing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
• Compiling and Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 Editing Configuration Files
This section discusses how to configure the demo for your system. It contains the following topics:
• Configuration File Location
• Editing the IPMediaServer.cfg Configuration File
3.1.1 Configuration File Location
Before running the IP Media Server for HMP demo, modify the IPMediaServer.cfg file to reflect
your system environment. Use a text editor and open the file from the following location:
3
Windows
$(INTEL_DIALOGIC_DIR)\Demos\IPMediaServer\Release
Linux
$(INTEL_DIALOGIC_DIR)/demos/IPMediaServer/Release
3.1.2 Editing the IPMediaServer.cfg Configuration File
Below is an example of the IPMediaServer.cfg file. Update the following information:
ipProtocolName
The IP protocol for opening IP line devices. Possible vlues are:
• H323
• SIP
• both
DTMFmode
Specifies how DTMF tones are transmitted. Possible values are:
• OutofBand – usually used with low bandwith coders, such as GSM
Note: OutofBand is used for H.323 only.
IP Media Server for HMP Demo Guide — July 2005 15
Preparing to Run the Demo
• InBand – usually used with G.711 coders
• RFC2833
Capability
Describes the transmit and receive coders. See the Global Call IP Technology Guide for
specific information about coder support. The parameters are as follows:
• TxType – the transmit voice coder
Note: By default, the fax demo is turned off. This feature may be enabled when tested with
T.38 capable IP endpoints. To do this, “uncomment” the line
in this section by removing the # from the start of the line, or add the line if not
present.
• TxFramesPerPkt – the number of frames per packet for the selected Tx coder
• TxVAD – specifies if VAD is active for the selected Tx coder
• RxType – the receive voice coder
• RxFramesPerPkt – the number of frames per packet for the selected Rx coder
Note: The G.711 coder defines frames per packet using the packet size in milliseconds, i.e.
10, 20, or 30 milliseconds. Refer to the Sample Configuration File, below, for the
correct syntax for all the parameters.
• RxVAD – specifies if VAD is active for the selected Rx coder
Quality of Service
The application can set threshold values to monitor the quality of service during calls. A fault
occurs when the result of a measurement of a QoS parameter crosses a predefined threshold. A
success occurs when the result of a measurement of a QoS parameter dis not cross a predefined
threshold. The QoS parameters are measured during time intervals, starting when a call is
established. The following parameters are supported:
• MediaAlarmLostPackets – monitors the number of lost IP packets during a call
• MediaAlarmJitter – monitors the jitter (as defined in RFC 1889) during IP transmission
TxType = t38UDPFax
QoS Attributes
The threshold for each QoS parameter is measured with the following six attributes:
• Threshold – defines when a QoS parameter is in a fault condition. A fault occurs when the
result of a measurement of a QoS parameter crossed the Threshold value.
• DebounceOn – the time during which faults are measured (in msec., must be multiple of
Interval)
• DebounceOff – the time during which successes are measured (in msec., must be multiple
of Interval)
• Interval – the amount of time between two QoS parameter measurements (in multiples of
100 msec)
• Percent_Fail – used to detect failure condition, together with DebounceOn (expressed as
a percentage of failures)
• Percent_Success – used to detect failure recovery, together with DebounceOff (expressed
as a percentage of successes)
The default values are as follows:
QoS Type Threshold DebounceOn DebounceOff Interval
Lost packets 20 10000 10000 1000 60 40
Jitter 60 20000 60000 5000 60 40
Percent_
Fail
Percent_
Success
16 IP Media Server for HMP Demo Guide — July 2005
Preparing to Run the Demo
Sample Configuration File
################################################################################################
# IP Protocol :
# The IP Protocol used for opening the IP Line devices, values: H323, SIP, both
#
# DTMFmode
# possible options:
# OutOfBand, inband, rfc2833
#
# Capability posiblities:
# g711Alaw
# g711Mulaw
# gsm
# gsmEFR
# g723_5_3k
# g723_6_3k
# g729a
# g729ab
# t38UDPFax
#
# Note: if you want to run the demo with coder g729 use:
# g729a for running with VAD disable
# and 729ab for running with VAD enable
#
# Caution:
# If capability is g711Alaw /Mulaw ==> FramesPerPkt = 10,20,30.
# G711 frame per packet defines the packet size in
# milliseconds
# If capability is g723_5_3k / 6_3k ==> FramesPerPkt = 1, 2, 3 .
# FrameSize isn't needed, default= 30ms.
# If capability is gsm ==> FramesPerPkt = 1, 2, 3 .
# FrameSize isn't needed, default= 20ms.
# If capability is gsmEFR ==> FramesPerPkt = 1, 2, 3 .
# FrameSize isn't needed, default= 20ms.
# If capability is g729a ==> FramesPerPkt = 3, 4 .
# FrameSize isn't needed, default= 10ms.
# VAD disable, the VAD parameter is ignored
# If capability is g729ab ==>FramesPerPkt = 3, 4 .
# FrameSize isn't needed, default= 10ms.
# VAD enable, the VAD parameter is ignored
#
################################################################################################
ipProtocolName = H323
DTMFmode = inBand
Channel = 1-120
{
Capability
{
# TxType = g711Alaw
# TxFramesPerPkt = 30
# TxVAD = 0
# RxType = g711Alaw
# RxFramesPerPkt = 30
# RxVAD = 0
TxType = g711Mulaw
TxFramesPerPkt = 20
TxVAD = 0
RxType = g711Mulaw
RxFramesPerPkt = 20
RxVAD = 0
# TxType = t38UDPFax
}
IP Media Server for HMP Demo Guide — July 2005 17
Loading...