Intel NetStructure Host Media Processing Software Release 1.1 for Windows

Transcription

1 Intel NetStructure Host Media Processing Software Release 1.1 for Windows Release Update January 12,

2 About This Publication This section contains information about the following topics: Purpose Intended Audience How to Use This Publication Related Information Purpose This Release Update addresses issues associated with Intel NetStructure Host Media Processing Software 1.1 for Windows. In addition to summarizing issues that were known as of this release, the Release Update will continue to be updated to serve as the primary mechanism for communicating new issues that arise after the release date. Intended Audience This Release Update is intended for all users of Intel NetStructure Host Media Processing Software 1.1 for Windows. How to Use This Publication This Release Update is organized into four sections (click the section name to jump to the corresponding section): Document Revision History: This section summarizes the ongoing changes and additions that are made to this Release Update after its original release. This section is organized by document revision and document section. Post-Release Developments: This section describes significant changes to the release subsequent to the general availability release date. For example, the new features provided in Service Updates are described here. Release Issues: This section lists issues that may affect the performance of the HMP software. The lists include both known issues as well as issues that have been resolved since the last release. Also included are restrictions and limitations that apply to this release, as well as notes on compatibility. Documentation Updates: This section contains corrections and other changes that apply to the HMP software release documentation set that could not be made to the documents prior to the release. The updates are organized by documentation category and by individual document. HMP Windows 1.1 Release Update, Rev 14 January 12,

3 Related Information See the following for additional information: For further information on issues that have an associated PTR number, you may use the web-enabled PTR Lookup tool at: When you select this link, you will be asked to either LOGIN or JOIN. If you have any questions about this tool or wish to provide feedback regarding this tool, please use the contact page on the Telecom Support Services Web site at: For information about the features supported in this release, see the Intel NetStructure Host Media Processing Software 1.1 for Windows Service Update Release Notes that is included as part of the documentation bookshelf for this release. For information about new features provided by the Service Update, see the Post-Release Developments section of this Release Update. HMP Windows 1.1 Release Update, Rev 14 January 12,

4 Document Revision History This revision history summarizes the changes made in each published version of the Release Update for Intel NetStructure Host Media Processing Software 1.1 for Windows, which is a document that is subject to updates during the lifetime of the release. Document Rev 14, published January 12, 2007 Updated for Service Update 49. In the Release Issues chapter, Issues section: Added the following defects to the Resolved Issues table: IPY Document Rev 13, published October 31, 2006 Updated for Service Update 47. In the Release Issues chapter, Issues section: Added the following defects to the Resolved Issues table: IPY , IPY Document Rev 12, published August 4, 2006 Updated for Service Update 44. In the Release Issues chapter, Issues section: Added the following defects to the Resolved Issues table: IPY , IPY , and IPY Document Rev 11, published June 19, 2006 Updated for Service Update 42. In the Release Issues chapter, Issues section: In the Issues section, added information on Defect No. and revised PTR No. description. Added the following defect to the Resolved Issues table: IPY In the Documentation Updates chapter: Added documentation corrections for the Global Call IP for Host Media Processing Technology Guide: added revised information for section , gc_makecall( ) Variances for SIP (IPY or PTR 36646). HMP Windows 1.1 Release Update, Rev 14 January 12,

5 Document Rev 10, published March 31, 2006 Updated for Service Update 41. In the Release Issues chapter, Issues section: Added the following PTRs to the Resolved Issues table: 36338, In the Documentation Updates chapter: Added documentation corrections for the Global Call IP for Host Media Processing Technology Guide: (1) added new information for section 4.22 Registration (this information supercedes doc updates previously published for PTR 34967); (2) added note to section Gatekeeper Registration Failure (PTR 36696); (3) added more detail to IP_H221NONSTANDARD field descriptions. Document Rev 09, published February 7, 2006 Updated for Service Update 40. In the Post-Release Developments chapter: Added information about preserving user configuration data in User Configuration Files section. In the Release Issues chapter, Issues section: Added the following PTR to the Resolved Issues table: (was not fixed in Service Update 37). Document Rev 08, published January 6, 2006 Updated for Service Update 37. In the Release Issues chapter, Issues section: Added the following PTRs to the Resolved Issues table: 35810, 36497, Document Rev 07, published October 26, 2005 Updated for Service Update 35. In the Release Issues chapter, Issues section: Added the following PTRs to the Resolved Issues table: 36029, 36082, In the Documentation Updates chapter: Added documentation corrections for the IP Media Library API for Host Media Processing Library Reference: IPM_QOS_THRESHOLD_DATA structure (PTR 35692). HMP Windows 1.1 Release Update, Rev 14 January 12,

6 Added documentation corrections for the IP Media Library API for Host Media Processing Programming Guide: section 8.2 QoS Alarm Types and section 8.3 QoS Threshold Attributes (PTR 35692). Document Rev 06, published September 30, 2005 Updated for Service Update 34. In the Release Issues chapter, Issues section: Added the following PTRs to the Resolved Issues table: 34936, 35798, 35928, 35940, In the Documentation Updates chapter: Added documentation corrections for the Global Call IP for Host Media Processing Technology Guide: section 4.2 Fast Start and Slow Start Call Setup and its subsections. Document Rev 05, published August 11, 2005 Updated for Service Update 33. In the Release Issues chapter, Issues section: Added the following PTR to the Resolved Issues table: Document Rev 04, published July 20, 2005 Updated for Service Update 31. In the Release Issues chapter, Issues section: Added the following PTRs to the Resolved Issues table: 35174, 35220, 35337, 35446, In the Documentation Updates chapter: Added documentation correction for the IP Media Library API for Host Media Processing Library Reference (PTR 33921). Added documentation correction for the IP Media Library API for Host Media Processing Programming Guide (PTR 33826). Document Rev 03, published June 3, 2005 Updated for Service Update 26. In the Post-Release Developments chapter: Added a note about changing IP address in Installing the Service Update section (PTR 35158). HMP Windows 1.1 Release Update, Rev 14 January 12,

7 In the Release Issues chapter, Issues section: Removed PTR from the Known Issues table and added this info as a note in Installing the Service Update section. Added the following PTRs to the Resolved Issues table: 34784, 34953, 35008, 35088, 35089, 35144, 35156, 35200, In the Documentation Updates chapter: Added documentation corrections for the Global Call IP for Host Media Processing Technology Guide: section Sending an INFO Message and section Responding to an INFO Message. Document Rev 02, published April 8, 2005 Updated for Service Update 23. In the Post-Release Developments chapter: Added a section on Windows XP SP2 Support. Added instructions for uninstalling service update software in Installing the Service Update section. In the Release Issues chapter, Issues section: Combined the two Resolved Issues tables into one. PTRs in the Resolved Issues table are now sorted in descending order. Added the following PTRs to the Resolved Issues table: 34378, 34429, 34666, 34674, 34715, 34751, 34768, 34779, 34838, Removed the following PTRs from the Known Issues table: 34352, 34378, PTRs in the Known Issues table are now sorted in descending order. Moved PTR about rtfconfig.xml from Known Issues table to Restrictions and Limitations section, General category. Added two bullets on RTF tool and RTF logging in the Restrictions and Limitations section, General category. Revised next to last bullet on UDP packets in the Restrictions and Limitations section, Global Call, IP, and IPML category. Moved PTR about SIP call termination from Known Issues table to Restrictions and Limitations section, Global Call, IP, and IPML category. In the Documentation Updates chapter: Added an update for the Service Update Release Notes in a new section, Release Documentation. Updated description for PTR (limitation on number of channels that can be run for a demo) for the following documents: (1) Continuous Speech Processing for Host Media Processing on Windows Demo Guide, (2) Host Media Processing Conferencing Demo Guide, and (3) IP Media Server (Global Call) Demo Guide for Windows Operating Systems. HMP Windows 1.1 Release Update, Rev 14 January 12,

8 Added several documentation updates for the Global Call IP for Host Media Processing Technology Guide: section Sending OPTIONS Requests, section Sending NOTIFY Requests, section 4.2 Registration, section gc_extension( ) Variances for SIP, and section gc_open( ) Variances for IP. Document Rev 01, published February 2005 Initial version of document for Service Update 20. HMP Windows 1.1 Release Update, Rev 14 January 12,

9 1.Post-Release Developments 1 This section describes significant changes to the Intel NetStructure Host Media Processing Software 1.1 for Windows subsequent to the general availability release date. Service Update for HMP Software 1.1 for Windows Installing the Service Update Service Update Features Service Update for HMP Software 1.1 for Windows This Service Update for Intel NetStructure Host Media Processing Software 1.1 for Windows 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. 1.2 Installing the Service Update Note: If the IP address that was entered by the user when HMP Software was installed is changed, the software will still use the original IP address set at the time of installation. (Typical reasons for the IP address changing are that Dynamic Host Configuration Protocol (DHCP) has been implemented or the network configuration has changed.) To use the new IP address, you must manually edit the appropriate registry key (HKEY_LOCAL_MACHINE\SOFTWARE\SBLabs\dm3ssp\IP_Addr0) after changing the IP address and then restart the Intel Dialogic System Service. [PTR 35158] The process for installing the Service Update differs depending on the HMP Windows software currently installed on a system: If this is an initial HMP software installation, you will first need to install HMP Windows 1.1 software before installing the Service Update software. If you have previously installed a feature pack or service update, you will need to uninstall that software before installing the latest Service Update software. Note: Do not use the Add/Remove Programs from the Control Panel to uninstall the feature pack or previous service update prior to installing this Service Update. Use the following procedure to uninstall the feature pack or previous service update prior to installing this Service Update: 1. Run the Setup.exe program provided with this Service Update software. This will correctly uninstall the feature pack or previous service update from the system. 2. Reboot the system. HMP Windows 1.1 Release Update, Rev 14 January 12,

10 3. Rerun the Setup.exe program provided with this Service Update software to install this Service Update on your system. 4. Reboot the system. This procedure for uninstalling the Service Update supersedes the procedure in the Uninstalling the Service Update Software section of the Intel NetStructure Host Media Processing Software 1.1 for Windows Service Update Release Notes. 1.3 Service Update Features Features supported by this Service Update include: User Configuration Files Windows XP SP2 Support Transaction Record Call Control RTF Logging Additional IP Protocol Features User Configuration Files Configuration settings unique to your environment can now be preserved and re-applied whenever an HMP license is changed or reactivated. Previously, customized settings in the.config file were lost every time a new Service Update was installed or a new HMP license was activated, and had to be re-entered. A new file called the user configuration file, HMP.Uconfig, is introduced. This file, which has the same format as the.config file, contains the parameters and parameter values that differ from the default that are used in your environment. Rather than editing the generated.config file, you create a separate HMP.Uconfig file in the data directory under INTEL_DIALOGIC_DIR, the environment variable for the directory in which the HMP software is installed. The contents of the HMP.Uconfig file are not overwritten but are merged into the generated configuration file whenever a new Service Update is installed or a new HMP license is activated. You should make a copy of the HMP.Uconfig file and save it in a safe location as a backup. Example The following is a sample HMP.Uconfig file, where the default AGC setting has been changed and a new parameter has been added: [encoder] SetParm=0x400,0 [0xe] SetParm=0xb17,4!AGC Enabled (1=Enable, 0=Disable)!QFC3_ PrmResponseTimeout default 3 seconds HMP Windows 1.1 Release Update, Rev 14 January 12,

11 The following is a sample merged HMP.config file (the generated file). It shows the new AGC setting in the [encoder] section followed by the default value for AGC, introduced by!^. It also shows a new parameter in [0xe], introduced by the!<add>. [encoder] SetParm=0x400,0!AGC Enabled (1=Enable, 0=Disable)!^SetParm=0x400,1!AGC Enabled (1=Enable, 0=Disable) [0xe]...!<add> SetParm=0xb17,4!</add>!QFC3_ PrmResponseTimeout default 3 seconds Windows XP SP2 Support Windows XP SP2 is now a supported operating system for HMP Software Transaction Record Transaction Record enables the recording of a two-party conversation by allowing two time slots from a single channel to be recorded. This feature is useful in call center applications where it is necessary to archive a verbal transaction or record a live conversation. Voice activity on two channels can be summed and stored in a single file or combination of files, devices, and memory. The voice API function dx_mreciottdata() is used to implement the transaction record feature. It is an extension of the dx_reciottdata() function. Information about Transaction Record can be found in Section 1.4.3, Transaction Record of Section 1, Introduction to Voice Features of the Voice Software Reference: Features Guide for Windows and in the dx_mreciottdata() function description in Section 7, Voice Function Reference of the Voice Software Reference: Programmer s Guide for Windows Call Control RTF Logging The Global Call IP Call Control Library uses the Runtime Trace Facility (RTF) system that is used by other Intel telephony software libraries to write underlying call control library and stack information to a consolidated log file while an application is running. This information can help trace the sequence of events and identify the source of a problem. This information is also useful when reporting problems to technical support personnel. See Chapter 6, Debugging Global Call IP Applications in the Global Call IP for Host Media Processing Technology Guide for information about debugging the Global Call IP application. HMP Windows 1.1 Release Update, Rev 14 January 12,

12 1.3.5 Additional IP Protocol Features The following new IP protocol features are documented in the Global Call IP for Host Media Processing Technology Guide: SIP Call Transfer Section 3.3, Call Transfer Scenarios When Using SIP Section , Call Transfer When Using SIP SIP Outbound Proxy Section 4.1.1, Setting a SIP Outbound Proxy plus IP_VIRTBOARD structure description SIP over TCP Section 4.1.2, Configuring SIP Transport Protocol Section 4.8. Specifying Transport for SIP Messages plus IP_VIRTBOARD structure description SIP Request Retry Section 4.9, Handling SIP Transport Failures plus IP_VIRTBOARD structure description Access to Additional SIP Message Headers Section 4.6, Setting and Retrieving SIP Message Headers plus Section 8.1, Overview of Parameter Usage Section , IPSET_SIP_MSGIFNO MIME-Encoded SIP Message Bodies (SIP-T) Section 4.7, Using SIP Messages with MIME Bodies (SIP-T) plus Section 8.1, Overview of Parameter Usage Section , IPSET_MIME and IPSET_MIME_200OK_TO_BYE SIP INFO Messages Section 4.10, Sending and Receiving SIP INFO Messages plus Section 4.6, Setting and Retrieving SIP Message Headers Section 4.7, Using SIP Messages with MIME Bodies (SIP-T) Section , IPSET_MSG_SIP SIP OPTIONS Messages Section 4.11, Sending and Receiving SIP OPTIONS Messages plus Section 4.6, Setting and Retrieving SIP Message Headers Section 4.7, Using SIP Messages with MIME Bodies (SIP-T) HMP Windows 1.1 Release Update, Rev 14 January 12,

13 Section , IPSET_MSG_SIP SIP SUBSCRIBE and NOTIFY Messages Section 4.12, Using SIP SUBSCRIBE and NOTIFY Messages plus Section 4.6, Setting and Retrieving SIP Message Headers Section 4.7, Using SIP Messages with MIME Bodies (SIP-T) Section , IPSET_MSG_SIP Getting RTP Addresses of a Call Section 4.14, Getting Media Streaming Status and Connection Information plus Section , IPSET_RTP_ADDRESS Getting SIP-specific Origination and Destination Addresses for a Call Section 7.2.9, gc_getcallinfo() Variances for IP Host LAN Cable Disconnect Alarm Section 4.26, Host LAN Disconnection Alarms HMP Windows 1.1 Release Update, Rev 14 January 12,

14 2.Release Issues 2 This chapter includes the following topics that relate to release issues: Issues Restrictions and Limitations Compatibility Notes Issues This section describes resolved issues and known issues in Intel NetStructure Host Media Processing Software 1.1 for Windows: Resolved An issue that has been resolved in this release or a previous release of the product (usually either fixed or documented). See Table 1, Resolved Issues, on page 15. Known A minor issue that affects the performance of the Host Media Processing (HMP) Software. This category includes interoperability issues and compatibility issues. Known issues are still open but may or may not be fixed in the future. See Table 2, Known Issues, on page 22. The following information is provided for each issue: Defect No. A unique identification number that is used to track each issue reported via a formal Change Control System. Additional information on defects may be available via the Defect Query tool at: (Note that when you select this link, you will be asked to either LOGIN or JOIN.) PTR No. Number from problem tracking system prior to June 19, For customer convenience, both the PTR number and the corresponding defect number are shown. For issues reported after June 19, 2006, this column contains -- and only the defect number is used to track the issue. SU No. The Service Update number when the PTR was resolved. Only provided for Resolved Issues. Product or Component The product or component to which the problem relates, typically one of the following: a system-level component; for example, HMP 1.1 Windows a software product; for example, the Global Call Library a software component; for example, Continuous Speech Processing HMP Windows 1.1 Release Update, Rev 14 January 12,

15 PTR Description A summary description of the issue. For non-resolved issues, a workaround is included when available. Table 1. Resolved Issues Defect No. PTR No. SU No. Product or Component PTR Description IPY IP A few seconds of silence duration is created in recorded file while switching between two RTP stream. IPY Media dx_play( ) function does not detect end of file. IPY HMP Recording file is empty (no audio data is contained) due to a change that occurred in the middle of the recording. IPY HMP System may freeze due to conflict with PCI bus analyzer. IPY IP A condition seen with RTCP may cause a system crash. IPY HMP APIC calibration routine may provide inaccurate data and may cause choppy audio. IPY Voice The dx_playiottdata( ) function sometimes plays the last bytes of a file continuously Voice Inability to play a file forever using uio IP Some defines in ipmlib.h were incorrectly followed by semi-colons IP Failure to send the registration request (RRQ) message during LAN disconnect IP GCEV_TASKFAIL event is returned after the first gc_regservice( ) call SRL Access violation during ipm_close( ) may occur Voice When calling dx_playiottdata( ) asynchronously, the function received an error. The resources that control the termination events in the firmware were exhausted Fax Fax error handling after a bad checksum on a V.21 HDLC frame did not restart a protocol timer. This resulted in a channel hang if the sender subsequently hung up without retrying the frame Voice ATDX_STATE( ) results in unexpected State for VoiceChannelPlayUnSetPatternsDisconnec t condition. HMP Windows 1.1 Release Update, Rev 14 January 12,

16 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description Fax After switching to the Sonus* GSX 9000 Gateway, HMP no longer successfully receives T.38 faxes. This is due to an incorrect packet being sent; synchronization timeouts are observed Fax The T.38 fax fails the training session, and the fax cannot complete. There is a compatibility issue: the T.38 input coder checks the length of the V.21 preamble (which should be 1 second +/- 15%); if it is longer than 2 seconds, it times out Voice Sound quality is poor when playing OKI ADPCM encoded file IP If the incoming SIP call (INVITE) contains any user-defined fields in the SDP (such as a=silencesupp:off), HMP copies the fields in the SDP of the answer Voice Call progress analysis incorrectly deciphers certain answering machine messages as positive voice detection (PVD) IP When making a call from a Uniden phone that has a coder list (G.711 Mu-law, G.711 A-law, G.723, G.729) and HMP is set for A- law, no audio is heard on the bus Install HMP 1.1 SU23 and SU26 installation does not correctly disable the APIC driver when unsupported, resulting in degraded voice quality Global Call IP HMP may fail if the application does not receive a response from the SIP registrar during registration Global Call IP HMP may fail when an application attempts to have SIP calls send out-of-band digits (which is not supported by SIP) Global Call IP Outgoing SIP messages may fail ( Transaction failed to identify the destination address ) due to a DNS addressing problem Conferencing The audio volume level for a conference call may sometimes be lower than for a nonconference call Global Call If a DTMF is pressed when gc_unlisten() is called, the next call results in half-duplex only lp One way audio is sometimes present when negotiating coder lists. HMP Windows 1.1 Release Update, Rev 14 January 12,

17 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description NCM If using DHCP and upgrading from HMP1.1SU20 to HMP1.1SU23, the system will not be able to obtain the IP address properly after the upgrade Global Call RFC2833 digits are sometimes delayed when using SIP Fax A blue screen may occur when sending faxes IP When calling ipm_stop() asynchronously, it does not return immediately Global Call Using SIP, if the display-name ends with '', the call is not offered Global Call gc_answercall fails using SIP on a Cisco PGW2200 softswitch, Cisco AS5850 media gateway IP Asymmetric codecs may result in no audio on the line HMP Any changes to network settings revert back to their original values when a Service Update is uninstalled Conferencing HMP audio is not transmitted in a conference when a COACH party is changed to a NULL party. (If the COACH party is deleted and re-added, audio is transmitted without a problem.) Voice When placing bulk IP calls, some receive silence when using third party tool Global Call IP Using gc_reqservice( ) to register a service produces an error Global Call IP Outbound calls containing nonstandarddata fail Voice The dx_stopch( ) function sometimes doesn t stop a play Voice Play is silence on a SIP call when DTMF is set to INBAND and RFC Global Call IP HMP does not send "MSD" message when HMP receives "TCS= non 0" after receiving "TCS=0" HMP The operating system may freeze when running HMP with NetMerge 3.0 along with an active port scanner utility Global Call IP During the first call when operating in H.323 fast-start mode, HMP incorrectly sends H.245 process messages (e.g. TCS/MSD). HMP Windows 1.1 Release Update, Rev 14 January 12,

18 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description Gobal Call IP HMP produces an error when playing a DTMF digit using SIP Fax Problem when running T.38 fax from HMP to Panasonic KX-FL503 fax machine when using ECM for fax transmission. ECM disturbs the fax device, causing the device to stop responding. ECM (Error Correction Mode) is a T.30 recommendation that provides more efficient error handling for noisy or distorted fax transmissions. It enables the receiver to check for and request retransmission for garbled data. The use of ECM for fax transmission is determined during Phase B negotiations and is based on the capabilities of the receiving station Fax When using T.38 to receive faxes, the channels sometime hang in a state where the system stops receiving events after calling fx_rcvfax() Conferencing Modifying gc_basic_call_model, with four Polycom IP phone sets, running SIP stack, establish conference, between Sets 1 & 2, and a second conference between sets 3 & 4, remove party 1 from the first conference, an move party 1 to the second conference. This results in a conference with phone sets 1, 3 & 4. However, after the move is complete, Conference 1 hears Conference Fax HMP T.38 is doing the Training check (TCF) incorrectly, allowing faxes to proceed at a higher bit rate with more error retries. The TCF sequence should force the bit rate to drop when a connection has a 5% or higher bit error rate Global Call Demo Parameter missing from the gc_basic_call_model demo configuration file Fax HMP operation with Cisco 2600 router using CallManager Express does not work for Fax Conferencing Noise occurs when parties are removed from a conference HMP System locks up after running for 24 to 26 days. HMP Windows 1.1 Release Update, Rev 14 January 12,

19 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description HMP Operating System locks when HMP services have been started (no call traffic running), and an attempt is made to do heavy data transfer from CD ROM to hard drive or any I/O function performed Voice Call analysis does not detect pvd/pamd accurately Fax Intermittent multi-page fax problem Global Call IP SDP portion of SIP invite indicates that RFC2833 digits 0-16 are supported. HMP only supports digits Voice Information on termination conditions returned by ATDX_TERMMSK( ) was added to the Documentation Updates chapter of this Release Update, in the Compatibility Guide for Dialogic R4 API on DM3 Products for Linux and Windows section Global Call IP HMP doesn't allow the setting of the Request URI field in the BYE message using SIP IP Media Server Demo When running the IP MediaServer Demo, cannot barge-in into the prompt after 2 seconds of starting the prompt CSP In Continuous Speech Processing, the MAXSIL/INIT and MAXSIL timers do not start at the correct time Fax During a T.38 fax transmission, we do not send an RTC (Return to Control) bit sequence after each page Voice gc_setalarmparm() fails after the application is abruptly stopped. Error returns a value of Voice dx_listen() function returns before a route (voice path to listen) has been fully completed (in ASYNC mode despite it being a SYNC function) making it possible to lose audio data if I/O function calls are made directly following Global Call IP RTP/RTCP packet timeout alarms are not generated to the application HMP When starting/stopping HMP, the following error information appears in IPTConf.log and IPTConf_Shutdown.log files: INFO: FindH323Component() failed. Board number 0 INFO: Board 0 was detected as a non IPLink board. Skipping HMP Windows 1.1 Release Update, Rev 14 January 12,

20 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description Conferencing Buzzing noise occurs when removing party from Conference in HMP Global Call IP SIP calls outgoing from HMP1.1 SU B.3 to a Nuance Voice Platform System disconnect immediately DCM DCM Help About description incorrect on HMP 1.1 Service Update Fax Fax transmission fails with error 110 (EFX_INVALRSPTX) after a previous fax transmission was interrupted using fx_stopch() Global Call IP HMP is not compatible with Cisco 2600 Gateway when switching to T.38 fax Global Call IP When remote SIP IP gateway accepts T38 REINVITE and then sends a BYE within 10ms, the GCEV_EXTENSION does not arrive and HMP IP channel hangs NCM NCMApi.h and NCMTypes.h are not updated for NCM_ function calls required for Semi-Automatic mode in HMP1.1FP Voice Audio signal delay occurred after HMP1.1 FP1 was installed HMP Blue screens encountered in Windows 2003 when terminating an application using Ctrl- C Global Call After sending approximately 1300 Q.931 FACILITY messages with NONSTANDARDDATA using gc_extension(ipextid_sendmsg), the H.323 stack will run out of internal resources and print the following messages on the screen/console: raaddext (VT tree): Array full ( elements) raaddext (TRANSPORT Hosts): Array full (207 elements) Global Call IP If a SIP REGISTER request is rejected by the registrar with a 42x - 7xxx response code, Global Call will not notify the application of the response code with a TASKFAIL event Voice SIT tones cannot be detected properly when performing Call Progress Analysis on HMP1.1 SP1. HMP Windows 1.1 Release Update, Rev 14 January 12,

21 Table 1. Resolved Issues (Continued) Defect No. PTR No. SU No. Product or Component PTR Description Global Call IP A SIP INVITE failure with the reason "IPEC_SIPReasonStatus486BusyHere", is erroneously reported to the application as TASKFAIL. Resolution: All failures (4xx-7xx) are reported as GCEV_DISCONNECTED IP Whenever the function ipm_getqosthreshold(), ipm_getqosalarmstatus(), ipm_resetqosalarmstatus() or ipm_getsessioninfo() is called by an application, 24 bytes of non-paged memory will be lost IP Illegal data in the setup message causes the RadVision* stack to crash Fax Retrain Negative (RTN) messages are encountered when sending T.38 multipage fax tiff files and no pages are sent after the first page Fax Some multipage fax tiff files cannot be sent over T.38. After the first page has been sent correctly, the receiving end fails with error EFX_NXTCMDTX (Timeout waiting for next send page command). Only the first page is received - the second page is blank. Table 2 lists known issues in Intel NetStructure Host Media Processing Software 1.1 for Windows. HMP Windows 1.1 Release Update, Rev 14 January 12,

22 Table 2. Known Issues PTR No. Product or Component PTR Description HMP ICMP Destination Unreachable responses to RTP and RTCP packets reset the RTP/RTCP Timeout alarm timers. These alarms are never generated unless there is an actual disconnect in the wire. Workaround: None Global Call IP When A Global Call application uses multiple virtual boards for SIP in the same application process, certain functions may receive a delayed successful or failed response event. The delay may be up to 32 seconds and may be caused by network and/or protocol stack errors. If this error occurs during a make call, the application will receive GCEV_DISCONNECTED with reason IPEC_SIPReasonStatus503ServiceUnavailable. If this error occurs during drop call, application will receive GCEV_DROCALL delayed up 32 seconds. Workaround: None Conferencing Demo Sometimes the Conferencing Demo does not release calls properly when the demo application is terminated. This may result in an application failure on the first call the next time the demo is run. Workaround: No workaround is required as the demo application will work correctly for the remaining calls Voice No audio is heard when dx_playiottdata() plays more than one file using DX_UIO. Workaround: Specify the length of the file in bytes to hear the files play. For example, you might define the DX_IOTT structure as follows: iottplay[0].io_fhandle = fdplay[0]; iottplay[0].io_bufp = 0; iottplay[0].io_offset = 0; iottplay[0].io_length = 32256; iottplay[0].io_type = IO_DEV IO_UIO IO_CONT; iottplay[1].io_fhandle = fdplay[1]; iottplay[1].io_bufp = 0; iottplay[1].io_offset = 0; iottplay[1].io_length = 16128; iottplay[1].io_type = IO_DEV IO_UIO IO_EOT; HMP If using Debug View, when an application calls ipm_close(), an error message is printed to Debug View. Workaround: None. This message can be safely ignored Voice If using Debug View, an error message is printed to Debug View when a multicast session is started. Workaround: None. This message can be safely ignored Fax If using Debug View when making T.38 fax calls with a Cisco AS5300, there may be an occasional "QT38[3]: ExecIFPInProcessHSHDLC: unexpected ind: 0" error message. Workaround: None. This message can be safely ignored. HMP Windows 1.1 Release Update, Rev 14 January 12,

23 Table 2. Known Issues (Continued) PTR No. Product or Component PTR Description Fax If using Debug View when making T.38 fax calls, there may be an occasional "FC3_ReadFrame call FAILED" error message. Workaround: None. This message can be safely ignored HMP If an application exits abnormally, is restarted by re-downloading HMP, and exits abnormally again, an exception may be generated. For Windows 2003, this exception will result in a blue screen. Workaround: None Fax HMP is unable to send multiple faxes during a session with the Cisco AS5300 Gateway. Workaround: Have the Cisco Gateway initiate a re-invite to HMP or disconnect the first session after the first fax has been sent and start a new session for the second fax HMP After several cycles of starting and stopping the System Service, or a single device (HMP), the System Service may hang if any Debug View 1 client (DBMON or Debug View) is active. Workaround: Close Debug View Voice During in-house testing a very low percentage of DTMF tone leakage was observed on low bit rate coders when the ipm_receivedigits() was used with the DTMF transfer mode set to Out-of-Band. A typical call control application, however, will not be adversely affected by this because, during Out-of-Band transfer mode, H.245 UII messages are typically used to relay DTMF event information. These H.245 UII messages have higher priority. Workaround: None Voice The gc_unlisten() function sometimes returns an unknown error. Workaround: Retry calling gc_unlisten() after the error occurs Voice When a program is run that calls dx_getdig() on a particular channel with the tpt set to terminate on max silence, and max time is greater than the max silence time and no digits are provided as stimulus, the function call will always terminate on max time instead of max silence. Workaround: Refer to Setting Termination Conditions for dx_getdig() in the Compatibility Notes section of this document Device Management If an error occurs when executing a Device Management API library function, a value of -1 is returned. When SRL function ATDV_LASTERR() is called, it returns 0 to indicate no error. This is not a problem if an error occurs within a subsystem (e.g., IP Media library) as ATDV_LASTERR() will return the correct error code. Workaround: None HMP Windows 1.1 Release Update, Rev 14 January 12,

24 Table 2. Known Issues (Continued) PTR No. Product or Component PTR Description Conferencing When playing a long file (e. g., music on hold) during conferencing, dropouts may be experienced. Workaround: Please add the following to the Config file and generate a new fcd file using fcdgen.exe. [0x3B] SetParm=0x3B12,0x7FFFAD SetParm=0x3B16,3 SetParm=0x3B1F,0x51EB SetParm=0x3B2F,3 After generating the fcd file, re-start the Intel Dialogic System via DCM HMP A Qerror warning may appear in DM3 standard error when conferencing tests are run on 120 timeslots. This message is displayed when the HMP kernel resizes the pools. This occurs only once and can be ignored. Workaround: None Licensing For the Command Line License Manager, download fails if relative paths are used for the -d option when the license is activated. Workaround: Use the absolute path name or place license files in the Program Files\Dialogic\data directory and do not use the -d option Fax The TO: field in the fax header for polled faxes is empty. Workaround: None HMP Error messages are not descriptive when HMP fails to download on a machine with inadequate resources (i.e. 128 MB RAM). HMP 1.1 requires a minimum of 512 MB RAM to function properly. Workaround: Use recommended machine or upgrade existing machine to meet the minimum memory requirements HMP Voice/Fax devices and IPML devices return different Device Family values when used with the xxx_getctinfo() function call on an HMP 1.1 platform. Workaround: None HMP A number of log files are created in the Windows System32 directory, which should be for system files only. Workaround: None (Does not impact performance.) 1. Copyright Mark Russinovich 2.2 Restrictions and Limitations Known restrictions and limitations in this release can be categorized as follows: General Conferencing Fax Global Call, IP, and IPML HMP Windows 1.1 Release Update, Rev 14 January 12,

25 Voice General High I/O activity (for example, updatedb) during heavy HMP activity may cause an increase in error rates, such as degraded digit detection and voice quality. HMP may not run properly on a computer if Advanced Configuration and Power Interface (ACPI) is installed. See the Apic Timer and HMP information in the Compatibility Notes section. HMP will not operate properly on some computers with Numega SoftICE* with versions previous to 2.7 installed. The HMP system does not operate with Intel Dialogic or Intel NetStructure board level products, or with Intel System Release software installed on the same machine. The rtfconfig.xml file has cheetah logging entries that should be removed since that logging is done through cheetah_cfg.exe. Due to the internal buffers used by the Runtime Tracking Facility (RTF) tool, the actual size of the log file may be up to 1 MB larger than the size attribute s value. For example, if the size attribute is set to 1000 KB, the actual log file may grow up to 2000 KB. If you run full RTF logging on high-density systems, you may experience I/O throughput degradation (specifically if you enable tracing on the MClient name MUTEX). It is recommended that you do not run RTF with full logging on high-density systems or any field-deployed systems. Instead, use just the default error-enabled logging. Contact technical support before enabling extensive logging. Conferencing The dcb_setbrdparm() function fails when attempting to set MSG_ALGORITHM to ALGO_LOUD and ATDV_ERRMSGP returns "Bad global parameter value". Do not set this parameter. By default, the algorithm uses the Loudest Talker. Fax For fax applications, the header file srllib.h must appear before the header file faxlib.h in the #include directive. Global Call, IP, and IPML Only IP-specific Global Call features will be provided as described in the Global Call IP for Host Media Processing Technology Guide. G.711 µ-law and A-Law IP Encoding/Decoding only support 64 Kbps. If a call is made to HMP using NetMeeting* from a machine that does not have a sound card, the coder negotiation will fail and the call will be disconnected before a GCEV_ANSWERED event is generated. If a call is made to HMP using NetMeeting, the "secure outgoing calls" option must not be selected. HMP Windows 1.1 Release Update, Rev 14 January 12,

26 Global Call applications using T.38 should call gc_setuserinfo(ipparm_t38_connect) after GCEV_OFFERED, but before the next GC function call, for T.38 only calls. Otherwise, the call will fail and the application will get a GCEV_TASKFAIL event. The ipm_sendrfc2833signaltoip() function is not supported on HMP. The application cannot use this API to generate RFC2833 digits on a call. Use the voice device to dial digits and set up RFC2833 transfer mode in a call. Host applications should always clean up resources before exiting. If the application terminates irregularly (resources are not cleaned up as described below), the HMP devices should be restarted using DCM to stop and then start the devices. If the application is using Global Call for call control, the application should terminate all calls by issuing gc_dropcall() followed by gc_releasecallex(), or use gc_resetlinedev(). Any open devices should then be closed using gc_close(). The Global Call Libraries should then be stopped using gc_stop() to release reserved resources. If the application is using IPML for call control, the application should stop the IPML devices using ipm_stop(). Any open devices should then be closed using ipm_close(). All other resource types should be stopped and closed using the appropriate xx_stop() and xx_close() API function. (For conferencing applications, dcb_delconf() should be issued on existing conferences before closing the DCB device handle). When running Global Call H.323 applications on HMP with Cisco 2600 Gatekeeper (IOS Version 12.3 (1a)), the Cisco 2600 sends packets to the wrong destination port after switching a voice call to T.38 Fax. This can be avoided by enabling tunneling on both sides. Network conditions may cause UDP packets to be lost, some of which may contain the SIP "100 Trying" or 180 Ringing non-reliable response messages that correspond to the GCEV_PROCEEDING and GCEV_ALERTING events respectively. Because SIP does not require retransmission of 1xx response messages, these events will not be generated when a UDP packet containing the corresponding 1xx response is lost. Applications should be written to continue processing a call when GCEV_CONNECTED is received, regardless of whether GCEV_PROCEEDING or GCEV_ALERTING was received. During SIP call termination, the Global Call application may fail to receive a BYE message from the remote user agent due to excessive network errors. Voice The dx_reciottdata() and dx_playiottdata() functions do not support recording or playing in WAVE format to/from memory; only VOX format. Global Tone Detection (GTD) does not support detecting user defined tones as digits via the digit queue; the tones are only detected as tone events via the event queue. For dual tone definition, the frequency deviation that is defined in the tone template for each frequency must be not less than ± 30 Hz. HMP Windows 1.1 Release Update, Rev 14 January 12,

27 For single tone definition, the frequency deviation that is defined in the tone template for each frequency must be not less than ± 30 Hz. The number of tone templates which can be added to a voice device and enabled for detection is limited. The maximum number of events for each instance is 10. The dx_dial() function only detects CED tones for CR_FAXTONE event. CNG tones cannot be detected. The dx_playtoneex() function will not terminate after the time specified by the DX_MAXTIME termination parameter has elapsed. DTMF digits not processed by the user application with dx_getdig() or other means remain in the device after it is closed with dx_close(), and remain with the device even after the application terminates. To ensure that the buffer is empty, clear the digit buffer using dx_clrdigbuf(). The dx_getctinfo() and fx_getctinfo() functions return incorrect values for Device Family and Bus Mode. 2.3 Compatibility Notes Adjusting the TimedWait State Running ONLY call control on 10 or more timeslots may cause the following error: "IPEC_Q931Cause18NoUserResponding" Each IP call uses a Windows socket which binds the call to a unique TCP address/port. The Global Call stack uses these ports starting at port address When an IP call is completed, the socket associated with that call closes and then enters into a TimedWait state, during which the socket's associated address/port is not available for use until the time expires. The default time for this TimedWait state is 240 seconds. If an application is stopped and then immediately restarted before the TimedWait state expires, as may be the case during application development and debugging, calls may fail. Reducing the duration of the TimedWait state can alleviate this problem. Another problem that may result from the TimedWait state duration is when a server experiences a high call rate. Even though the maximum number of TCP connections that can be opened simultaneously is large, in a high call rate scenario the potential exists for hundreds of TCP sockets to be in the TimedWait state causing the system to reach the maximum number of TCP connections. Again, reducing the duration of the TimedWait state can alleviate this problem. Changing the TimedWait state to a value less than the 240 second default requires a change to the registry: System Key: Parameter Name: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ Tcpip\Parameters TcpTimedWaitDelay HMP Windows 1.1 Release Update, Rev 14 January 12,

28 Value Type: Valid Range: REG_DWORD (DWORD Value) seconds Also, see the following Microsoft information at these links: Windows Windows XP Windows 2003 Server APIC Timer and HMP HMP uses the Advanced Programmable Interrupt Controller (APIC) timer for its high resolution timer. The APIC timer operation may conflict with certain modes of the Advanced Configuration and Power Interface (ACPI). During the installation process, the install program checks to determine if the ACPI is enabled. If ACPI is enabled and does not meet the minimum version requirement, a message is displayed stating that the local APIC timer is incompatible with this release and that the setup program will disable the Intel NetStructure HMP APIC driver. After the HMP software has been installed and it has been determined that the ACPI is enabled, you must determine if the ACPI is incompatible with HMP by performing the following: 1. Start the HMP media subsystem through the Configuration Manager (DCM). (Refer to the Intel NetStructure Host Media Processing Software Release 1.1 for Windows Installation and Configuration Guide for information about using DCM.) 2. Start the IP Media Server (Global Call) Demo. (Refer to the IP Media Server (Global Call) Demo Guide for information about starting the demo.) 3. Launch Microsoft* NetMeeting* from another computer, with a sound card, connected on the same LAN. 4. Make sure that the Outgoing Calls security option in NetMeeting (Tools>Options>Security) is unselected. 5. Make sure the default coder in NetMeeting is set to "CCITT u-law, khz, 8 Bit, Mono". This is set via the Advanced option in the Audio property sheet accessed via Tools>Options. 6. From NetMeeting, connect to the machine running HMP (by typing the IP address or computer name and clicking the telephone icon) and identify if the audio is acceptable. 7. If the audio is acceptable, no further action is necessary. If there is no audio or poor audio, then you must completely disable ACPI in order to run HMP on this system. Disabling ACPI requires that you re-install Microsoft Windows. Microsoft Knowledge Base Article # Q provides instructions for installing Windows without automatically enabling some form of ACPI. HMP Windows 1.1 Release Update, Rev 14 January 12,