Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Update

Transcription

1 Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Update

2 System Release 6.0 for cpci on Linux Operating Systems: Release Update 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, life sustaining, critical control or safety systems, or nuclear facility applications. Intel may make changes to specifications and product descriptions at any time, without notice. This document 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 the express written consent of Intel Corporation. Copyright , Intel Corporation. Dialogic, Intel, Intel logo, and Intel NetStructure 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: August, 2006 Document Number: Intel 1515 Route 10 Parsippany NJ For Technical Support, visit the Intel Telecom Support Resources website at: For Products and Services Information, visit the Intel Telecom and Compute Products website at: For Sales Offices and other contact information, visit the Buy Telecom Products page at: 2

3 Table of Contents Table of Contents Table of Contents...3 Document Revision History...6 About This Information...9 Purpose...9 Intended Audience...9 How to Use This Information...9 Related Information...9 Post-Release Developments...11 Service Update for System Release 6.0 for CompactPCI on Linux...11 Installing the Service Update...12 Uninstalling the System Release...13 Time Stamp for Tone-On/Off Events on DM/V2400A...13 Feature Description...13 Structure...13 Scenario...13 Code Example...13 Documentation...14 Dynamically Changing the Transmit Time Slot on IP Media Devices...14 Feature Description...14 New PARMCH_TX_TIMESLOT Parameter...17 Restrictions and Limitations...17 Documentation...17 Hot Swap Support on Additional Compute Platform...18 dx_stopch( ) EV_NOSTOP Mode Support for DM3 Boards...18 Feature Description...18 Documentation...18 GSM-AMR-NB Coder Support for Intel NetStructure IPT Boards...18 Feature Description...19 Release Documentation...20 Fixed Problems...20 Compatibility Issues...30 System Software...30 CT69000 Graphics Adapter...30 Evaluation Version...30 Administration Software...30 Installation - Backward Compatibility...30 Hardware Products...31 Intel NetStructure IPT Boards...31 Development Software...31 Programming Using External References...31 Voice...34 Diagnostic and Utilities Software...34 Restrictions and Limitations...35 System Software...35 Applications...35 Demos...35 Device Mapper...36 Installation and Configuration...36 SCSI Driver (Adaptec)...36 System Startup...36 Administration Software...36 Redundant System Slot (RSS)...36 Using the Hot Swap Kit on ZT Hardware Products

4 System Release 6.0 for cpci on Linux Operating Systems: Release Update DM/F Fax...37 DM/IP Boards...38 DM/V Boards...38 DMN160TEC...39 Intel NetStructure HDSI...39 IPT Boards...39 Chassis Support...43 Development Software...43 Continuous Speech Processing...43 Global Call...43 Host-Based H.323 Protocol Stack...46 IP Media API...47 Modular Station Interface (MSI)...47 Voice...47 Diagnostic and Utilities Software...47 DM3STDERR...47 Tools and Utilities...48 Known Problems...49 Documentation Updates...53 System Release Documentation...53 SR 6.0 cpci for Linux Release Guide...53 Administrative Software Documentation...53 Intel NetStructure on DM3 Architecture for CompactPCI on Linux Configuration Guide...53 Development Software Documentation...54 Continuous Speech Processing API Library Reference...55 Continuous Speech Processing API Programming Guide...55 Fax Software Reference...55 Global Call Analog Technology User's Guide...55 Global Call API for Linux and Windows Library Reference...56 Global Call API for Linux Programming Guide...57 Global Call E-1/T-1 Technology User s Guide...58 Global Call IP Technology User's Guide...60 Global Call ISDN Technology User s Guide...79 IP Media Library API for Linux and Windows Library Reference...85 IP Media Library API for Linux and Windows Programming Guide...86 MSI/SC Software Reference...86 Standard Runtime Library (SRL) API for Linux Library Reference...90 Standard Runtime Library (SRL) API for Linux Programming Guide...90 Voice API for Linux Library Reference...91 Voice API for Linux Programming Guide...92 Operating Software Documentation

5 Document Revision History Unlike other documents associated with the Intel Dialogic System Release 6.0 for CompactPCI* on Linux* Operating Systems, the Release Update is a document that is subject to updates during the lifetime of the release. Therefore, this section has been added to provide a quick reference for changes occurring since the last release of this document. Version Date Description of Changes 021 8/25/06 In the Documentation Updates section: Added IPY (PTR# 36210) under Intel NetStructure on DM3 Architecture for CompactPCI on Linux Configuration Guide. Added IPY (PTR# 27337) under Fax Software Reference. Added IPY (PTR# 36646) under Global Call IP Technology User's Guide. Added IPY (PTR# 35666) and IPY (PTR# 34546) under Voice API for Linux Programming Guide /23/06 Updated for Service Update 52. In the Post-Release Developments section, added Time Stamp for Tone-On/Off Events on DM/V2400A /20/06 Updated for Service Update 49. In the Fixed Problems section, added PTR# In the Documentation Updates section: Added PTR# under Global Call E-1/T-1 Technology User s Guide. Added documentation update to the Global Call IP Technology User's Guide about the IP_H221NONSTANDARD data structure /17/06 Updated for Service Update 47. In the Fixed Problems section, added PTR# /15/06 Updated for Service Update 46. In the Post-Release Developments section, added Dynamically Changing the Transmit Time Slot on IP Media Devices /30/05 Updated for Service Update 44. In the Post-Release Developments section, added Hot Swap Support on Additional Compute Platform. In the Fixed Problems section, added PTR# 33530, /22/05 Updated for Service Update 42. In the Fixed Problems section, added PTR# 34492, 34858, 35101, 35617, In the Documentation Updates section, added PTR# under Global Call E-1/T-1 Technology User s Guide /4/05 Added PTR# in the Known Problems section under "IPT Boards". Added PTR# in the Documentation Updates section under Fax Software Reference. Added PTR# and PTR# in the Documentation Updates section under Global Call API for Linux and Windows Library Reference. Added PTR# in the Documentation Updates section under Global Call IP Technology User's Guide. Added PTR# in the Documentation Updates section under IP Media Library

6 System Release 6.0 for cpci on Linux Operating Systems: Release Update API for Linux and Windows Library Reference and Global Call IP Technology User's Guide. Added PTR# in the Documentation Updates section under Standard Runtime Library (SRL) API for Linux Library Reference. Added PTR# in the Documentation Updates section under Standard Runtime Library (SRL) API for Linux Programming Guide. Added PTR# in the Documentation Updates section under Voice API for Linux Library Reference /14/05 Updated for Service Update 37. Added a new section, Post-Release Developments, to discuss the Service Update and provide installation information. In the Post-Release Developments section: Added dx_stopch( ) EV_NOSTOP Mode Support for DM3 Boards. Added GSM-AMR-NB Coder Support for Intel NetStructure IPT Boards. In the Fixed Problems section, added 22694, 24828, 24895, 26167, 26173, 26358, 26837, 27255, 27335, 27357, 27382, 27645, 27741, 27994, 28022, 28028, 28030, 28060, 28282, 28340, 28357, 28470, 28561, 28634, 28678, 28707, 28737, 28807, 28964, 29009, 29167, 29188, 29189, 29428, 29735, 29853, 30300, 30173, 30334, 30357, 30418, 30482, 30515, 30585, 30608, 30630, 30744, 30756, 30767, 30788, 30789, 30818, 30901, 30902, 30921, 30935, 30938, 31094, 31331, 31389, 31392, 31456, 31465, 31598, 31641, 31658, 31750, 31751, 31769, 31955, 31963, 32078, 32122, 32201, 32223, 32233, 32364, 32471, 32540, 32608, 32717, 32809, 32902, 32975, 33011, 33039, 33116, 34678, 34944, 35507, 35797, 35839, 50058, /17/05 Added PTR# in the Documentation Updates section under Voice API for Linux Library Reference. Added PTR# in the Documentation Updates section under Global Call ISDN Technology User s Guide. Added PTR# in the Documentation Updates section under Global Call IP Technology User's Guide. Added PTR# 32413, PTR# 32705, and PTR# in the Documentation Updates section under IP Media Library API for Linux and Windows Library Reference. Added PTR# in the Known Problems section under DMV, DMV/A, IPLink and VFN Fax Boards with Network Interfaces. Added PTR# in the Known Problems section under "Global Call IP Call Control" /8/05 Added PTR# in the Documentation Updates section under Global Call IP Technology User's Guide /16/05 In the Documentation Updates section: Added PTR# under IP Media Library API for Linux and Windows Library Reference. Added PTR# under Continuous Speech Processing API Library Reference. Added PTR# and PTR# 32607/21073 under Continuous Speech Processing API Programming Guide. Added PTR# under Voice API for Linux Library Reference and Voice API for Linux Programming Guide. Added PTR# and PTR# under Voice API for Linux Library Reference. Added PTR# 32544, PTR# 32501,and PTR# under Global Call API for Linux and Windows Library Reference. Added PTR# under Global Call API for Linux Programming Guide /7/04 Added PTR# 30759/30761 in the Documentation Updates section under Global Call 6

7 Document Revision History IP Technology User's Guide. Added PTR# 31812/32282 in the Documentation Updates section under the Intel NetStructure on DM3 Architecture for CompactPCI on Linux Configuration Guide /25/04 Added PTR# in the Restrictions and Limitations section under DM/IP Boards. Added PTR# in the Restrictions and Limitations section under Host-Based H.323 Protocol Stack. Added PTR# 31211/31213 in the Documentation Updates section under Global Call IP Technology User's Guide /17/03 Added PTR# in the Documentation Updates section under the Voice API for Linux Library Reference. Documented PTR# in the Restrictions and Limitations section under DM/V Boards. Added PTR# in the Documentation Updates section under the Global Call API for Linux Programming Guide. Added PTR# in the Documentation Updates section under the Global Call API for Linux and Windows Library Reference. Added PTR# in the Documentation Updates section under the Intel NetStructure on DM3 Architecture for CompactPCI on Linux Configuration Guide /28/03 Added a documentation update for the SR 6.0 cpci for Linux Release Guide. In Section 2.2, Basic Software Requirements, the following information should be included: This release is supported on single processor systems only (no SMP support) /22/03 Added a note to the Compatibility Issues section regarding the Evaluation Version of this software /21/03 In the Documentation Updates section. added PTR# to reflect changes in the Standard Runtime Library (SRL) API for Linux Programming Guide in Section 8.2, "Implementing the Asynchronous Model with Event Handlers". Corrections and clarifications have been made to the Programming Using External References section. For example, the section on Running Continuous Speech Processing Using an External Reference Signal (ec_listen( )) had erroneous information which has been corrected. Additionally, a new graphic is now included that depicts the use of an external reference signal. A few more updates have been included for the Global Call IP Technology User's Guide /02/02 Documented a limitation regarding the use of older versions of DM/V boards in the Restrictions and Limitations section under DM/V Boards. Several changes were made to the Restrictions and Limitations section regarding IPT Boards /29/02 In Section 2.2 of the Release Guide, it states that the gcc version is but the correct version is In order to clarify what is meant by chassis support in this release: It means that the Intel Dialogic software and the chassis were tested together and they passed the testing criteria. Only the ZT 5082, 5083, 5084 and 5087 support the Hot Swap feature in this release. In addition, in order to enable the ZT 5087 to do hot swap, you need to follow the instructions provided under Using the Hot Swap Kit on ZT 5087 in the Restrictions and Limitations section of this document. dm3diag has been replaced by diagbrd and several new utilities are introduced: startbrd, stopbrd, pbl, and removebrd. These are all documented in the Administration Guide or the Diagnostics Guide. The following changes were made in the Restrictions and Limitations section regarding Installation and Configuration: 7

8 System Release 6.0 for cpci on Linux Operating Systems: Release Update REMOVED: "If you are using Intel NetStructure boards, the compat-libstdc++ package is also required and is selected by choosing the "Select Individual Packages" option during Package Selection and accessing the System Environment- >Libraries folder. (Other packages may be installed if you like, but these are necessary)." CHANGE FROM: ", but during install is copied to /usr/dialogic/bin." CHANGE TO: "but is not installed on the system. If you wish to have the ability to uninstall the release without requiring the original distribution media, copy this file into /usr/dialogic/bin. To uninstall the release, change into the root directory and run /usr/dialogic/bin/dlguninstall.sh." 001 9/30/02 Initial version of the document is released as part of the production release of the system software. 8

9 About This Information About This Information This section contains information about the following topics: Purpose Intended Audience How to Use This Information Related Information Purpose This Release Update addresses issues associated with System Release 6.0 cpci for Linux. In addition to summarizing issues that were known as of the release s general availability, this Release Update will continue to be updated to serve as the primary mechanism for communicating new issues that arise after the release date. The fixed problems from previous releases can be found in the Fixed Problem History List., a separately available document available from the Intel Telecom Support Resources website at: Intended Audience This release update is intended for the following types of customers: Distributors System Integrators Toolkit Developers Independent Software Vendors (ISVs) Value Added Resellers (VARs) Original Equipment Manufacturers (OEMs) How to Use This Information This release update is designed so that information can be found quickly. Major sections include: Post-Release Developments - This section describes significant changes to the system release subsequent to the general availability release date. For example, any new features provided in Service Updates are described here. Fixed Problems - This section lists problems that have been fixed in this release. Compatibility Issues - This section addresses issues involving compatibility with other software. Restrictions and Limitations - This section discusses restrictions and/or limitations of the products provided in this system release. Known Problems - These are problems with the software that could not be fixed prior to shipment. Documentation Updates - These are changes to the documentation that could not be made prior to shipment. Related Information See the following for additional information: If you are new to Intel Dialogic products or some of the latest technology and don't want to search through volumes of documentation looking for the information you need, use Learn About to get started quickly. It can be found at: 9

10 System Release 6.0 for cpci on Linux Operating Systems: Release Update For Intel Networking and Communications technical support for developers, visit the Telecom Support Services website at: For Intel Networking and Communications product information, visit the website at: For information about the products and features supported in this system release, see the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Guide ( ) that is included as part of the documentation bookshelf for the release. Note: This will be the last system release where the Fixed Problems History List, the Fixed Problems section or Known Problems section will be provided. In the future, this information will be replaced by a new PTR Lookup Tool capability. This web-enabled tool is located at: When you select this link, you will automatically be asked to either LOGIN or JOIN. If you have any questions about this new tool or wish to provide feedback regarding this tool, please feel free to contact us at the Telecom Support Services website at: 10

11 Post-Release Developments Post-Release Developments This section describes significant changes to the system release subsequent to the general availability release date. Service Update for System Release 6.0 for CompactPCI on Linux Time Stamp for Tone-On/Off Events on DM/V2400A Dynamically Changing the Transmit Time Slot on IP Media Devices Hot Swap Support on Additional Compute Platform dx_stopch( ) EV_NOSTOP Mode Support for DM3 Boards GSM-AMR-NB Coder Support for Intel NetStructure IPT Boards Service Update for System Release 6.0 for CompactPCI on Linux A Service Update for System Release 6.0 for CompactPCI on Linux is now available. Service Updates provide fixes to known problems, and may also introduce new functionality. New versions of the Service Update will be released periodically. This Release Update will document the features in the Service Updates. The installation of this Service Update uses a process known as slipstreaming. This allows you to install the latest system release software under the following scenarios: If you already have the base system release installed, installing this Service Update gives you the latest versions of the Red Hat Package Manager (RPM) files that were installed previously (when you installed System Release 6.0 for CompactPCI on Linux). Installing the Service Update also deletes any obsolete RPMs. If you do not already have the base system release installed, installing this Service Update provides the full install menu for System Release 6.0 for CompactPCI on Linux. This allows you to install the complete system release, including the latest updates in this Service Update. It is not necessary to perform a separate install for the base system release and for the Service Update. If you already installed this Service Update, installing it again gives you the full install menu for System Release 6.0 for CompactPCI on Linux. This allows you to install additional packages that you didn t select when you first installed the base system release. Note: Builds that use the slipstream install process are referred to as Feature Releases and Service Updates. Some earlier builds for System Release 6.0 for CompactPCI on Linux were referred to as Feature Packs (FP1) and Service Packs (SP1). If you have one of these earlier FP1 or SP1 builds installed, you will get an error message the first time you use the new install process. For further information and the workaround for this error, see the section below about Installing this Service Update if an FP1 or SP1 Build Is Installed. The buildinfo file in the $INTEL_DIALOGIC_CFG directory shows the base release plus any Service Packs, Feature Packs, Service Updates, and Feature Updates that are on your system. For example: System Release Build Date = None System Release Build Number = -1 System Release Major Number = 6 System Release Minor Number = 0 System Release SubMinor Number = -1 Service Pack Number = -1 Service Pack Build Number = -1 Service Pack Build Date = None Feature Pack Number = -1 Feature Pack Build Number = -1 Feature Pack Build Date = None Service Update Number = 1 Service Update Build Number = 9 Service Update Build Date = 04/03/

12 System Release 6.0 for cpci on Linux Operating Systems: Release Update Feature Release Number = -1 Feature Release Build Number = -1 Feature Release Build Date = None Installing the Service Update This section discusses the installation procedure for the following scenarios: Installing the Latest Updates Installing the Complete System Release Reinstalling this Service Update (to Select Additional Packages) Installing this Service Update if an FP1 or SP1 Build Is Installed Note: In all scenarios except the last one, start the install script (install.sh) from the top level directory. The install script will determine the software that is already present, and the install will then be run from either the full or update directory, as appropriate. For the last scenario (if an earlier FP1 or SP1 build is installed), starting the install script from the top level directory will result in an error message. In that case, you have to run install.sh from the update directory as discussed below. The system requirements for this Service Update are the same as for the base system release. Refer to the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Guide for specific hardware and software requirements. Installing the Latest Updates If you already installed System Release 6.0 for CompactPCI on Linux and only want the updates from this Service Update, running install.sh gives you the latest versions of the RPMs that you already have on your system. It is not necessary to specify the packages that you need. Installing the Complete System Release Note: Before installing the complete system release, make sure that all of the prerequisites discussed in the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Software Installation Guide have been met. If you have not already installed System Release 6.0 for CompactPCI on Linux, running install.sh gives you the full install menu, which allows you to select the packages to install. The selections are: Software for the Intel NetStructure DMV/DMN/DMT Software for the Intel NetStructure DMIP Software for the Intel NetStructure DMF Software for the Intel NetStructure HDSI Software for the Intel NetStructure High Density DMN (DMN160TEC) Software for the Intel NetStructure IPT SNMP Agent Software Documentation The base system release plus the latest updates from this Service Update will be installed for the selected packages. For further information about the packages and for detailed instructions for installing the system release, see the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Software Installation Guide. Reinstalling this Service Update (to Select Additional Packages) If you already installed this Service Update, running install.sh a second time gives you the full install menu for System Release 6.0 for CompactPCI on Linux, which allows you to install packages that you didn t select the first time you installed the base system release. The complete list of packages is given above, in the Installing the Complete System Release section. For further information about the packages and for detailed instructions for installing the system release, see the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Software Installation Guide. Installing this Service Update if an FP1 or SP1 Build Is Installed Before initiating the slipstream install process for System Release 6.0 for CompactPCI on Linux, some builds referred to as Feature Packs (FP1) and Service Packs (SP1) were available. When the slipstream install process detects one of these builds, it operates as though the installed FP1 or SP1 build is a later build, even though it is actually an earlier build, because it is assumed that Feature Releases come before a Feature Pack, and Service Updates come before a Service Pack, in the release hierarchy. 12

13 Post-Release Developments The new install process does not allow upgrading from a later release to an earlier release, so the install will fail with an error message similar to the following: You already have a later service pack release on your system. CURRENT=System Release 6.0 cpci Service Pack 1 for Linux NEW=System Release 6.0 cpci Service Update 1 Build 1 for Linux Aborting install due to newer release already on the system. If this occurs, run the install.sh contained in the update directory rather than in the top level directory. This gives you the latest versions of the RPMs that you already have on your system, and installs a buildinfo file that is compliant with the new release model. Any subsequent updates will no longer experience this problem. Uninstalling the System Release Running the uninstall script (dlguninstall.sh) uninstalls the complete system release. It is not possible to uninstall only the Service Update and revert to a previous version of the software. You can return to a previous version of the software by installing the particular Service Update that you want. For further information about uninstalling the system release, see the Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Software Installation Guide. Time Stamp for Tone-On/Off Events on DM/V2400A With the Service Update, a new time stamp has been added to the existing DE_TONEON and DE_TONEOFF events. A new TN_TIMESTAMP structure has been added to the device header file dxxxlib.h. This time stamp is used to associate, or group, certain tones in order to detect a particular country tone made up of two or more defined tone templates. Feature Description To test the various tones from various countries, the Tone-On/Off Call Status Transition (CST) event data have been modified to add a time stamp structure to the end of the TN_INFO structure. The CST event data are obtained by calling sr_getdatalen( ) and sr_getevtdatap( ). A new structure, TN_TIMESTAMP, is in the device header file, dxxxlib.h. If the event is for Tone-On, then the time stamp represents the tone-on time, and if the event is for Tone- Off, then it represents the tone-off time. The Tone-On/Tone-Off messages are extended to add the start time and the stop time, respectively. These time stamps are used by the customer application to calculate the Tone-On/Tone-Off duration (cadence). Structure TN_TIMESTAMP is as follows: // Tone ON/OFF time stamp typedef struct { unsigned long tn_timestamp; /* Time stamp for tone on/off event. The time stamp is in milliseconds from when the firmware was downloaded on the board. There is no co-relation to the system time. It wraps around every ~149 hours. */ } TN_TIMESTAMP; Scenario When a Tone-On CST event is received, the application gets the CST event data with the sr_getdatalen( ) and sr_getevtdatap( ) functions, as usual. The application then applies the TN_TIMESTAMP structure to the event data and obtains the time stamp of the tone-on event or tone-off event. The TN_TIMESTAMP structure is appended to the end of the TN_INFO structure. The CST event data comprises the DX_CST, TN_INFO, and TN_TIMESTAMP structures. Code Example The following is an example for Tone-On. Tone-Off is done the same way. DX_CST *datap; TN_INFO *tonep; TN_TIMESTAMP *tsp; long timestamp; // time stamp in ms units 13

14 System Release 6.0 for cpci on Linux Operating Systems: Release Update switch(sr_getevttype(ehandle)) { case TDX_CST: datap = (DX_CST *) sr_getevtdatap(ehandle); if (datap->cst_event == DE_TONEON) { tonep = (TN_INFO*)(datap+1); // tone structure starts at end of CST structure tsp = (TN_TIMESTAMP*)(tonep+1); // time stamp structure starts at end of TN_INFO structure. timestamp = tsp->tn_timestamp; // get the time stamp } break;.. Documentation The online bookshelf provided with System Release 6.0 CompactPCI for Linux contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about the Standard Runtime Library and Voice API, see the following documents: Standard Runtime Library API for Linux and Windows Operating Systems Library Reference Standard Runtime Library API for Linux Programming Guide Voice API for Linux Programming Guide Voice API for Linux Library Reference Note: The online bookshelf has not been updated for this feature, so the manuals above do not contain information relating to this feature. Dynamically Changing the Transmit Time Slot on IP Media Devices With the Service Update, the ability to dynamically change the transmit time slot on IP Media (ipmbxcx) devices is provided. The feature is supported on Intel NetStructure IPT boards only. Feature Description The transmit time slot for IP Media devices is allocated by the time slot allocation model that runs at board initialization time. In previous releases, this allocation could not be changed at runtime. Starting with this Service Update, the transmit time slots on the IP Media devices associated with IPT boards can be dynamically changed at runtime using the ipm_setparm( ) IP Media Library (IPML) function. The companion ipm_getparm( ) function can be used to retrieve the transmit time slot to which the IP Media device is currently allocated. The newly assigned transmit time slot allocation remains in effect until the device is closed or another request to change the transmit time slot allocation is issued. Caution: Assigning transmit time slots incorrectly can have a destructive effect on the IPT board when two or more devices are transmitting on the same time slot. This is particularly true when the devices are not physically resident on the same board. It is the responsibility of the application to ensure that the transmit time slot of each IP Media device is allocated to a time slot that has no other device transmit time slots allocated to it. A number of use case scenarios that describe the usefulness of this feature are described in the following subsections. The system configuration for use cases 1 and 2 is described first. System Configuration for Use Cases 1 and 2 The figure below shows the system configuration for use cases 1 and 2. 14

15 Post-Release Developments China Request New York Request Request Japan Request Germany Customer Application Resource Manager IP Network AMR Messaging Telephony Server / 3G GSM Gateway IP Network AMR Intel NetStructure IPT Board (IP resources, AMR <=> PCM) Intel NetStructure DM/V2400A Resource Board (media resources, G.711 <=> PCM) Third Party Multi-Protocol Board (SS7, Frame Relay, ISDN, CAS) Third Party IP Resource Board PCM TDM Bus SUT Streaming PSTN SUT In this configuration, the customer application is designed to expect time slots in the range 1 to 240 to be assigned to the DM/V2400A media resources for transmitting data and time slots in the range 2001 to 2240 for receiving data (see table following). SUT Boards Static Tx Time Slots Tx Time Slots Rx Time Slots Time Slot Pool DM/V2400A 1 to to to Third Party Boards to 4096 The application has an administration component that runs and creates a lookup table that is used by the Resource Manager (RM) for establishing full duplex connections between resources. With the addition of an IPT board into the system configuration, the lookup table is modified as follows: Boards Static Tx Time Slots Tx Time Slots Rx Time Slots Time Slot Pool DM/V2400A 1 to to to IPT to to 480 Third Party Boards to 4096 The time slot ranges in bold are reserved by the administration component of the application. If more IPT boards are included, additional transmit time slots are assigned to the IP Media resources. Note that for the IPT2400 board, the transmit (Tx) time slot range is 241 to 480 as statically assigned at board initialization, but these time slots can be changed at runtime using this feature. Use Case 1 This use case describes the validation of DTMF quality sent to and received from the 3G GSM Gateway in the figure above. The application allocates a voice resource (dxxb1c1) and IP Media resource (ipmb1c100) for establishing a media session between the 3G GSM Gateway and a test tool. Using this feature, the Resource Manager (RM) changes the transmit time slot of the ipmb1c100 device (which is statically allocated to time slot #341) to time slot 15

16 System Release 6.0 for cpci on Linux Operating Systems: Release Update #2001 to match the receive time slot of the voice resource (dxxb1c1) thereby establishing a full-duplex connection between the devices as shown in the following table. Device Static Tx Time Slot Tx Time Slot Rx Time Slot Purpose Voice device Generate test DTMF (dxxb1c1) Detect tones returned from SUT IP Media device (ipmb1c100) Send/receive and encode/decode DTMF from AMR to PCM and PCM to AMR Once the test is completed, the devices are closed and any transmit time slot allocations freed. Devices that are subsequently opened default to the static transmit time slot assignment, unless explicitly changed using the ipm_setparm( ) function. Note: It is the responsibility of the application to keep track of the resource and time slot status. The sequence of activities that comprise this use case is as follows: 1. The user makes a request to set up a connection with a 3G GSM SUT to validate DTMF and audio quality. 2. The test application establishes the connection with the remote SUT using IPT (network) and IPM (media) resources. 3. The user selects the DTMF tones to send and the test application generates and sends DTMF tones to the SUT. The tones are generated using a DM/V2400A voice resource and G.711 encoding. 4. The DTMF is received by the IPM resource listening to transmit time slot #1 of the DM/V2400A board voice resource. 5. The IPM resource encodes the PCM data stream to AMR and sends the RTP packet to the SUT. 6. The SUT receives the RTP stream and interprets the payload as a DTMF tone. 7. The SUT transmits the received DTMF back to the IPM resource in AMR format. 8. The IPM resource transcodes the AMR RTP stream to PCM which is then transmitted on time slot #2001 to the DM/V2400A board voice resource for tone detection. 9. The DM/V2400A board voice resource signals the application that a tone has been received. Using this scenario, the user can verify if the 3G GSM Gateway is receiving, detecting, and generating DTMF correctly. Use Case 2 The same scenario as use case 1 above can be performed between the 3G GSM Gateway IPM and voice resources to verify voice quality. The customer can use a recorded voice file which is sent to the SUT. Then, some form of perceptual measurement (PESQ or PSQM) can be used to evaluate the voice quality of the recorded voice received versus that which was sent. Use Case 3 Another use case for this feature is the verification of the behavior of a specialized switch (for example, a customer switched configured for China) when receiving specific tones. These tests are typically run remotely to ensure the switch is recognizing the tones and responding appropriately. The tones typically tested are call progress, SIT, and fax tones. Using This Feature The following is the sequence of function calls involved when using this feature: 1. ipm_open( ) - Opens an IP Media device and returns a valid handle. The transmit time slot is allocated to the static time slot number. 2. ipm_setparm( ) - Sets the transmit time slot to a specific number. This is achieved by setting up an IPM_PARM_INFO structure where the eparm field is PARMCH_TX_TIMESLOT and the *pvparmvalue field is a pointer to the parameter value, that is, the time slot number to be allocated. See the ipm_setparm( ) function reference page in the IP Media Library API Library Reference for more detail. 3. ipm_getparm( ) (optional) - Validates that the time slot has been changed to the desired time slot. This can be used at any time to get the active transmit time slot of an IP Media device. This functionality is equivalent to that provided by the ipm_getxmitslot( ) function. 16

17 Post-Release Developments 4. ipm_close( ) - Closes an IPM device deallocating all time slots. This should be the final step before the resource is returned to the free resource pool. New PARMCH_TX_TIMESLOT Parameter A new PARMCH_TX_TIMESLOT parameter has been created to support this feature. Details are as follows: eip_parm Define Description and Values PARMCH_TX_TIMESLOT Identifies a transmit time slot value for an IP Media device that can be dynamically set or retrieved at runtime. Type: unsigned short. Valid values: 0 to Restrictions and Limitations The following restrictions and limitations apply: Caution: Assigning transmit time slots incorrectly can have a destructive effect on the IPT board when two or more devices are transmitting on the same time slot. This is particularly true when the devices are not physically resident on the same board. It is the responsibility of the application to ensure that the transmit time slot of each IP Media device is allocated to a time slot that has no other device transmit time slots allocated to it. This feature is applicable to IPT boards only. It is the responsibility of the application to manage time slot allocation when using this feature. See the Caution above. The default static time slot assignment applies if not explicitly changed using this feature. It is assumed that the system is operating in Passive mode, where the customer application is responsible for the establishment and management of H.110 clocking (primary clock, signal reference, and any associated fallback strategies respectively). When a single board stop operation is performed (that is, an IPT board is stopped without stopping the system), all dynamically assigned transmit time slots associated with the IP Media devices on the IPT board are deallocated. - If the IPT board is restarted without any other boards being stopped prior to the restart, the same set of static time slots are allocated to the IPT board. - If multiple boards are stopped, then the static time slot allocations may change depending on the order in which the boards are restarted. It is the responsibility of the application to ensure that a time slot value specified is in the range 0 to The ipm_setparm( ) and ipm_getparm( ) functions do not perform any validation on the value specified. The ipm_getxmitslot( ) function, which returns the currently allocated transmit time slot for an IP Media device, has not changed as a result of this feature. Closing an IP Media device, then reopening it, resets the transmit time slot back to the static time slot allocated during board initialization (firmware download). The application should not access the Device Mapper to obtain the transmit time slot allocated to an IP Media device, since the Device Mapper maintains the transmit time slots statically allocated at board initialization time and the transmit time slots may have been changed at runtime using this feature. Documentation The online bookshelf provided with System Release 6.0 CompactPCI for Linux contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about the IP Media Library API, see the following documents: IP Media Library API Programming Guide IP Media Library API Library Reference Note: The online bookshelf has not been updated for this feature, so the manuals above do not contain information relating to this feature. 17

18 System Release 6.0 for cpci on Linux Operating Systems: Release Update Hot Swap Support on Additional Compute Platform With the Service Update, like-for-like hot swap is now supported on the Concurrent chassis with PP200 Single Board Computer (SBC). This solution does not require installation of the Hot Swap Kit (HSK) software. The only requirement for removing the board is that it must be in the INITED state. If the board is not in the INITED state, the stopbrd utility must be run to bring the board to the INITED state before ejecting the board. dx_stopch( ) EV_NOSTOP Mode Support for DM3 Boards With the Service Update, the dx_stopch( ) function EV_NOSTOP mode can now be used with DM3 boards. The dx_stopch( ) function forces termination of currently active I/O functions on a specified channel. It forces a channel in the busy state to become idle. When issued on a channel that is already idle and EV_NOSTOP is specified, the application receives a TDX_NOSTOP event to indicate that the dx_stopch( ) function completed and that no STOP was needed (that is, the channel was already idle when dx_stopch( ) was issued). Previously, no event was returned in this situation for DM3 boards. Feature Description EV_NOSTOP can be ORed with any of the other mode flags supported by dx_stopch( ), for example: dx_stopch(chdev, EV_ASYNC EV_NOSTOP) dx_stopch( ) with EV_NOSTOP operates as follows: If issued on an idle channel, TDX_NOSTOP is returned. If issued on an active channel, the active channel is stopped and a media termination event (e.g., TDX_PLAY) is returned with termination reason TM_USRSTOP. (TDX_NOSTOP is not returned.) If issued in synchronous mode (EV_SYNC EV_NOSTOP), no event is sent to application. dx_stopch( ) will return only when the channel comes to idle state. Note that it is possible to get both events (TDX_PLAY and TDX_NOSTOP) in a race condition, that is, if dx_stopch( ) is issued for a channel that transitioned to idle just before the stop request, before the application received the TDX_PLAY event. In this case, the termination reason for the TDX_PLAY is not TM_USRSTOP. Documentation The online bookshelf provided with System Release 6.0 CompactPCI for Linux contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about the dx_stopch( ) function and the Voice API, see the following documents: Voice API for Linux Operating Systems Programming Guide Voice API for Linux Operating Systems Library Reference GSM-AMR-NB Coder Support for Intel NetStructure IPT Boards With the Service Update, Groupe Speciale Mobile (GSM) Adaptive Multi-Rate (AMR) Narrow Band (NB) coders are supported on Intel NetStructure IPT boards. Any AMR-NB allowable rate of 4.75 to 12.2 kbps may be used. Full density of AMR coders (up to 480 channels) is supported. Note: In order to support this feature, the IPT board must have a revision D0 Digital Signal Processor (DSP). Older revision boards do not support this feature. To determine if your board can use the AMR-NB coders, check the Configured Assembly (CA) label, which is located on the same side of the board as the four MAC address labels. (It is in close proximity to the front panel and parallel to it.) Your board must have one of the CA numbers listed in the following table to use the AMR-NB coders. 18

19 Post-Release Developments Feature Description Board Model CA Number IPT6720C C or C IPT4800C C IPT2400C C IPT1200C C or C Coder information can be specified using either the IP Media Library API or the Global Call API. Using the IP Media Library API to Specify the Coder The ipm_startmedia( ) function in the IP Media Library API sets media properties and starts a media session. Coder information is provided in the IPM_MEDIA_INFO data structure. The IPM_MEDIA_INFO structure references IPM_MEDIA, which in turn references IPM_CODER_INFO for coder information. The following new values are supported for the ecodertype field of the IPM_CODER_INFO structure: CODER_TYPE_AMRNB_4_75k GSM-AMR-NB 4.75 kbps CODER_TYPE_AMRNB_5_15k GSM-AMR-NB 5.15 kbps CODER_TYPE_AMRNB_5_9k GSM-AMR-NB 5.9 kbps CODER_TYPE_AMRNB_6_7k GSM-AMR-NB 6.7 kbps CODER_TYPE_AMRNB_7_4k GSM-AMR-NB 7.4 kbps CODER_TYPE_AMRNB_7_95k GSM-AMR-NB 7.95 kbps CODER_TYPE_AMRNB_10_2k GSM-AMR-NB 10.2 kbps CODER_TYPE_AMRNB_12_2k GSM-AMR-NB 12.2 kbps Note: These coder types are supported only on Intel NetStructure IPT boards. When using any of these coders: Coder frame size is fixed at 20 ms. Frames per packet (fpp) is: - 1 or 2 (transmit) - 1, 2, or 3 (receive) VAD must be disabled. Using the Global Call API to Specify the Coder Terminal capabilities are exchanged during call establishment. The terminal capabilities are sent to the remote side as notification of coder supported. When using Global Call, coder information can be set in the following ways: On a system wide basis using gc_setconfigdata( ) On a per line device basis using gc_setuserinfo( ) with a duration parameter value of GC_ALLCALLS On a per call basis using gc_makecall( ) or gc_setuserinfo( ) with a duration parameter value of GC_SINGLECALL In each case, a GC_PARM_BLK is set up to contain the coder information. The GC_PARM_BLK must contain the GCSET_CHAN_CAPABILITY parameter set ID with the IPPARM_LOCAL_CAPABILITY parameter ID, which is of type IP_CAPABILITY. The following new values are supported for the capability field of the IP_CAPABILITY structure: GCCAP_AUDIO_AMRNB_4_75k GSM-AMR-NB 4.75 kbps GCCAP_AUDIO_AMRNB_5_15k GSM-AMR-NB 5.15 kbps GCCAP_AUDIO_AMRNB_5_9k GSM-AMR-NB 5.9 kbps GCCAP_AUDIO_AMRNB_6_7k GSM-AMR-NB 6.7 kbps GCCAP_AUDIO_AMRNB_7_4k GSM-AMR-NB 7.4 kbps GCCAP_AUDIO_AMRNB_7_95k GSM-AMR-NB 7.95 kbps GCCAP_AUDIO_AMRNB_10_2k GSM-AMR-NB 10.2 kbps GCCAP_AUDIO_AMRNB_12_2k GSM-AMR-NB 12.2 kbps 19

20 System Release 6.0 for cpci on Linux Operating Systems: Release Update Note: These coder types are supported only on Intel NetStructure IPT boards. When using any of these coders: Coder frame size is fixed at 20 ms. Frames per packet (fpp) is: - 1 or 2 (transmit) - 1, 2, or 3 (receive) VAD must be disabled. Release Documentation The online bookshelf provided with System Release 6.0 CompactPCI for Linux contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about the IP Media Library API, see the following documents: IP Media Library API Programming Guide IP Media Library API Library Reference For more information about the Global Call API, see the following documents: Global Call API Programming Guide Global Call API Library Reference Global Call IP Technology User s Guide Fixed Problems The problems listed below were fixed in this release. For each PTR, the following information is provided: PTR No. - A unique identification number that is used to track each issue reported via a formal Problem Tracking Report (PTR). Additional information on PTRs may be available via the PTR Lookup tool at (Note that when you select this link, you will be asked to either LOGIN or JOIN.) SU No. - For PTRs that were resolved in a Service Update, indicates the Service Update number. For PTRs that were resolved when the base release was generally available (before any Service Updates), a -- is shown. Product or Component - The product or component to which the issue relates, typically one of the following: A system-level component; for example, DM3 Admin A hardware product; for example, Intel NetStructure DM/V boards A software product; for example, the Global Call library A software component; for example, ISDN Firmware Description - A summary description of the issue. PTR No. SU No. Product or Component Description DM3 voice At varying and random times during a run, applications would experience a loss of voice data when trying to route voice channels to network time slots over the CT Bus DM3 host runtime library After running for several days, a DM/V2400A board voice device was blocked and could not be stopped by dx_stopch( ) DM3 firmware After running for several weeks, half or all voice channels on DM/V2400A board are blocked. They stayed in stopped state and could not go back to idle state DM3 voice Cadence tone detection does not yield the proper number of events when a string of cadence tones is played DM3 voice After successfully starting dx_playiottdata( ) in async mode, no TDX_PLAY or TDX_ERROR termination event occurs. 20