Intel Dialogic System Release Feature Pack 1 for Windows* Service Update 149

Size: px
Start display at page:

Download "Intel Dialogic System Release Feature Pack 1 for Windows* Service Update 149"

Transcription

1 Intel Dialogic System Release Feature Pack 1 for Windows* Service Update 149 Release Notes August 22,

2 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 Intel Dialogic System Release Feature Pack 1 for Windows* Service Update 149 Release Notes 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 22, 2007 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: System Release FP1 for Windows Service Update, Rev 66 August 22, 2007

3 Contents Document Revision History About This Publication Release Overview New Features Host Diagnostic Utility Replaces Serial Diagnostics for PBX Integration Boards New ANI/DNIS-Enabled Parsing Tool (ADEPT) for PBX Integration Boards Runtime Trace Facility (RTF) Description Installing RTF RTF Configuration File Restrictions and Limitations rtftool Command Example RTF Configuration Files New Fax Parameter for Modem Receive Level Reduced Dial Tone Delay with MWI Adjusting Pre-Record Beep Tone Characteristics through the CONFIG File Feature Description Documentation Change in ipmedia.log Implementation Reducing the Delay in Reporting the GCEV_CONNECTED Event During Call Progress Analysis Feature Description Documentation SIP re-invite Support on DI0408LSAR2 Boards Receiving a SIP re-invite Request Receiving Proposed Media Session Properties Rejecting a re-invite Request Accepting a re-invite Request SIP Digest Authentication Support on DI0408LSAR2 Boards Early Media Support on DM/IP Boards Support for NULL IP Address on Media Session Start New Bitmask Value for dx_stopch( ) Mode Parameter for Synchronous Operation PBX Integration Support for Mitel Superset 4150 Telephone Feature Description New Channel Block Timer for NTT Protocol Feature Description New Parameter Implementation of ROLM Call Waiting LED Optional Use of Sharing of Timeslot (SOT) Algorithm ISDN Network Side Conformance to Network Protocol Standards ITU-T Q921 and Q Intel Telecom Subsystem Summary Tool (its_sysinfo) Speed Control on DM3 Boards Using 6 khz Coders DPNSS Support on D/300JCT-E1, D/600JCT-1E1, and D/600JCT-2E1 Boards System Release FP1 for Windows Service Update August 22,

4 Contents 2.22 IP Support on DI0408LSAR2 Boards Feature Description Configuring the Software Restrictions and Limitations DI0408LSAR2 Product Support for Host Systems with Multiple NICs Circular Logging Capability for gc_h3r.log New Features for Intel Dialogic PBX Integration Boards ms_setmsgwaitind( ) Async Mode Support Enhanced GCAMS on DM3 Boards New E1 Alarms New T1 Alarms Modifying Default Threshold Values for New Alarms Support for New Alarms in GCAMS Functions Enhanced Special Information Tone Frequency Detection on DM3 Boards New SIT Sequence Definitions ATDX_CRTNID( ) Support on DM3 Boards Improved Accuracy of Call Progress Analysis Support for ANI Category Digit Retrieval on DM3 Boards Support for CompactPCI Boards New Boards Supported End of Support for Specified Boards End of Support for Embedded H.323 IP Stack End of Support for Windows NT and TAPI Interfaces System Requirements Installing the Software Prerequisites for Software Installation Order of Procedures Saving Existing Configuration Data Before You Install the Service Update After You Install the Service Update Uninstalling Existing Software Overview of Uninstall Procedures Uninstalling Existing Point Releases, Service Packs, Feature Packs, and Obsolete Service Updates Uninstalling the Base Release Uninstalling the New Version of the System Release Feature Pack 1 Service Update Installing the Service Update Performing a Silent Install Creating an InstallShield Response File Installing the Software Using the InstallShield Response File Resolved Problems Known Problems System Release FP1 for Windows Service Update August 22,

5 Document Revision History This revision history summarizes the changes made in each published version of this document. Document number , published 22 August 2007 Updated for Service Update 149. In the Resolved Problems section, added IPY , IPY Document number , published 24 July 2007 Updated for Service Update 148. In the Resolved Problems section, added IPY (PTR 35816), IPY , IPY , IPY , IPY , IPY , IPY , IPY , IPY In the Known Problems section, added IPY Document number , published 24 May 2007 Updated for Service Update 144. In the Resolved Problems section, added IPY , IPY , IPY Document number , published 26 April 2007 Updated for Service Update 143. In the System Requirements section, added Windows Server 2003 SP2 to the operating systems supported with the Service Update. In the Resolved Problems section, added IPY , IPY , IPY Also added the following resolved problems that were fixed in Service Update 136: IPY (PTR 36524), IPY (PTR 36636), IPY (PTR 36118). In the Known Problems section, added IPY (PTR 33837), IPY (PTR 36510), IPY (PTR 25019). Document number , published 21 March 2007 Updated for Service Update 140. System Release FP1 for Windows Service Update August 22,

6 Document Revision History In the Resolved Problems section, added IPY , IPY , IPY , IPY , IPY , IPY Document number , published 1 March 2007 Updated for Service Update 138. In the Resolved Problems section, added IPY , IPY , IPY , IPY , IPY , IPY , IPY , IPY Also added IPY (PTR 36577) (resolved in Service Update 136). In the Known Problems section, added IPY Document number , published 26 January 2007 Updated for Service Update 136. In the Resolved Problems section, added IPY , IPY , IPY , IPY Document number , published 3 January 2007 Updated for Service Update 134. In the Resolved Problems section, added IPY , IPY Also, added IPY (PTR 33780) (resolved in Service Update 133). Document number , published 18 December 2006 Updated for Service Update 133. In the Resolved Problems section: Added IPY The following defects were resolved in Service Update 133, not Service Update 128: IPY , IPY (36575), IPY (36795). The following defect was resolved in Service Update 133, not Service Update 95: IPY (PTR 36281). Document number , published 11 December 2006 Updated for Service Update 132. In the Resolved Problems section, added IPY , IPY , IPY , IPY , IPY , IPY System Release FP1 for Windows Service Update August 22,

7 Document Revision History Document number , published 21 November 2006 Updated for Service Update 131. In the Resolved Problems section, added IPY , IPY , IPY , IPY , PY , IPY , IPY Document number , published 6 October 2006 Updated for Service Update 128. In the New Features section, added a note to Optional Use of Sharing of Timeslot (SOT) Algorithm that the SOT algorithm is now supported on the DM/V600-4E1 board with media load ml1_4x2_r2mf. In the Resolved Problems section, added IPY (36756), IPY (36795), IPY (36575). Document number , published 4 August 2006 Updated for Service Update 125. In the Resolved Problems section: Added IPY (PTR 36801), IPY Deleted IPY (PTR 35332). A fix for this defect will be provided in a future Service Update. It had to be removed because it caused a problem with sr_getboardcnt( ) (defect IPY now resolved). Document number , published 27 July 2006 In the Known Problems section, added IPY Document number , published 19 July 2006 Updated for Service Update 123. In the New Features section: Added Host Diagnostic Utility Replaces Serial Diagnostics for PBX Integration Boards. Added New Channel Block Timer for NTT Protocol for DM3 boards. Document number , published 30 June 2006 Updated for Service Update 120. In the New Features section, added New ANI/DNIS-Enabled Parsing Tool (ADEPT) for PBX Integration Boards. System Release FP1 for Windows Service Update August 22,

8 Document Revision History In the Resolved Problems section, added IPY (PTR 35636), IPY , IPY Document number , published 26 June 2006 Updated for Service Update 119. In the Resolved Problems section, added IPY , IPY Document number , published 14 June 2006 Updated for Service Update 118. In the Resolved Problems section, added IPY , IPY (PTR 36755), IPY , IPY In the Known Problems section, added IPY Note: This problem first appears in SU118. Customers running R2MF on a cpci DM/IP board should not upgrade beyond SU114 until the issue is resolved. Document number , published 22 May 2006 Updated for Service Update 114. In the Resolved Problems section, added IPY (36740), IPY , IPY , IPY Document number , published 15 May 2006 Updated for Service Update 113. In the Resolved Problems section, added IPY (PTR 36371). Also added IPY (PTR 35332) (fixed in Service Update 112). Document number , published 3 May 2006 Updated for Service Update 111. In the Resolved Problems section, added IPY (PTR 35592), IPY (PTR 35164), IPY (PTR 36738), IPY (PTR 36370), IPY (PTR 36739), IPY (PTR 36573), IPY (PTR 35790), IPY (PTR 36814), IPY (PTR 36637), IPY (PTR 36859), IPY (PTR 36853), IPY (PTR 36845), IPY (PTR 36750), IPY Also added IPY (fixed in Service Update 110). Document number , published 27 April 2006 Updated for Service Update 110. System Release FP1 for Windows Service Update August 22,

9 Document Revision History In the New Features section, added Runtime Trace Facility (RTF). Document number , published 12 April 2006 Updated for Service Update 107. In the Resolved Problems section, added IPY (PTR 35636), IPY (PTR 36354), IPY (PTR 36711), IPY (PTR 36852), IPY (PTR 36793), IPY (PTR 36769). Document number , published 3 April 2006 Updated for Service Update 106. Note: The Resolved Problems section has been modified to show issues by Change Control System defect number and by PTR number. Issues reported prior to March 27, 2006, will be identified by both numbers. Issues reported after March 27, 2006, will only have a defect number. In the New Features section: Added New Fax Parameter for Modem Receive Level. Added Reduced Dial Tone Delay with MWI. In the Resolved Problems section, added IPY (PTR 36229), IPY (PTR 36057), IPY (PTR 36881), IPY (PTR 35331), IPY (PTR 35201), IPY (PTR 36698), IPY (PTR 36735). Document number , published 14 March 2006 Updated for Service Update 102. In the New Features section, added Adjusting Pre-Record Beep Tone Characteristics through the CONFIG File. In the System Requirements section, added Windows Server 2003 R2 and Windows 2000 Update Rollup 1 for SP4 to the operating systems supported with the Service Update. In the Resolved Problems section: Added PTRs 35658, 36528, 36625, Revised information about PTR (resolved in Service Update 100, not Service Update 64). Document number , published 3 March 2006 Updated for Service Update 100. In the New Features section, added Change in ipmedia.log Implementation. System Release FP1 for Windows Service Update August 22,

10 Document Revision History In the Resolved Problems section, added PTRs 35746, 36115, 36134, 36315, 36319, 36329, 36529, 36587, 36623, Document number , published 31 January 2006 Updated for Service Update 98. In the New Features section, updated End of Support for Specified Boards and End of Support for Embedded H.323 IP Stack. See these sections for important information about DM/IP boards and features that will not operate correctly on new Service Updates after Service Update 89. In the Resolved Problems section, added PTR Document number , published 24 January 2006 Updated for Service Update 97. In the Resolved Problems section, added PTR In the Known Problems section, added PTR Document number , published 9 January 2006 Updated for Service Update 95. In the New Features section: Added Reducing the Delay in Reporting the GCEV_CONNECTED Event During Call Progress Analysis. Added SIP re-invite Support on DI0408LSAR2 Boards. Added SIP Digest Authentication Support on DI0408LSAR2 Boards. Added Early Media Support on DM/IP Boards. Added Support for NULL IP Address on Media Session Start. Updated the Intel Telecom Subsystem Summary Tool (its_sysinfo) section to add information about running the tool from the command line. Added a note in the IP Support on DI0408LSAR2 Boards section about statically configuring the IP addresses of the NICs. In the Resolved Problems section, added PTRs 32680, 34159, 34161, 34592, 34801, 34858, 35001, 35292, 35423, 35440, 35558, 35797, 35942, 36106, 36135, 36167, 36244, 36246, 36281, 36356, 36621, Also added (fixed in Service Update 58), (fixed in Service Update 63), and (fixed in Service Update 82). System Release FP1 for Windows Service Update August 22,

11 Document Revision History Document number , published 18 November 2005 Updated for Service Update 89. In the New Features section, added New Bitmask Value for dx_stopch( ) Mode Parameter for Synchronous Operation. In the Resolved Problems section, added PTRs 32208, 33414, 35237, 35899, 36047, 36050, 36085, 36205, Document number , published 4 November 2005 Updated for Service Update 88. In the New Features section, added PBX Integration Support for Mitel Superset 4150 Telephone. In the Resolved Problems section, added PTRs 30654, 32415, 32759, 32772, 33514, 33750, 34239, 34284, 35102, 35235, 35274, 35279, 35407, 35634, 35921, 35947, 36032, 36063, 36110, 36204, 36213, Document number , published 24 October 2005 Updated for Service Update 85. In the Resolved Problems section, added PTRs 30234, 35707, 35832, 35901, 35903, 36133, Document number , published 14 October 2005 Updated for Service Update 84. In the Resolved Problems section, added PTRs 32241, 33717, 34095, 35600, Document number , published 10 October 2005 Updated for Service Update 83. In the System Requirements section, added note stating that Terminal Services Application Server Mode and Active Directory Application Server Mode are not supported (PTR 36031). In the Resolved Problems section, added PTRs 29038, 34814, 35270, 35755, 35775, 35790, 35799, 35937, Document number , published 26 September 2005 Updated for Service Update 82. System Release FP1 for Windows Service Update August 22,

12 Document Revision History In the New Features section, added End of Support for Windows NT and TAPI Interfaces. In the Installing the Software section, added a note under Prerequisites for Software Installation about needing the psapi.dll file on a Windows NT system. In the Resolved Problems section, added PTRs 35218, 35388, 35670, In the Known Problems section, added PTR Document number , published 24 August 2005 Updated for Service Update 78. In the New Features section: Added New Channel Block Timer for NTT Protocol. Added End of Support for Specified Boards. Added End of Support for Embedded H.323 IP Stack. In the Resolved Problems section, added PTRs 33815, 35342, 35590, 35650, Document number , published 4 August 2005 Updated for Service Update 76. In the Resolved Problems section, added PTRs 34032, 34800, 35251, 35283, 35523, Document number , published 29 July 2005 Updated for Service Update 75. In the Resolved Problems section, added PTRs 35011, 35359, Document number , published 14 July 2005 Updated for Service Update 74. In the New Features section, added Implementation of ROLM Call Waiting LED. In the System Requirements section, under Requirements for Global Call Protocols Package with Service Update, changed references to Global Call Protocols Version 4.3 to say 4.3 or later. In the Resolved Problems section, added PTRs 31675, 32136, 32712, 34476, 35104, 35139, 35154, System Release FP1 for Windows Service Update August 22,

13 Document Revision History Document number , published 17 June 2005 Updated for Service Update 69. Note: The procedure for installing the Service Update has changed. The new procedure is documented in Chapter 4, Installing the Software. In the System Requirements section, specified that System Release for Windows (and not Feature Pack 1) must be installed before installing the Service Update. In the Resolved Problems section, added PTRs 32606, 34569, 34646, 34719, 35012, 35176, 35224, 35289, Document number , published 23 May 2005 Updated for Service Update 66. In the New Features section: Under ms_setmsgwaitind( ) Async Mode Support, corrected the data type for the mode parameter (int, not unsigned short) (PTR 35191). Added the Intel Dialogic D/4PCIUF and D/4PCIU4S Combined Media Boards to the New Boards Supported section. Note: The D/4PCIUF and D/4PCIU4S boards have been supported since Service Update 53. In the Resolved Problems section, added PTRs 32952, 33506, 33932, 34160, 34205, 34999, 35007, Document number , published 13 May 2005 Updated for Service Update 65. Added support for Windows Server 2003 SP1 to the System Requirements section. Document number , published 4 May 2005 Updated for Service Update 64. In the Resolved Problems section, added PTRs 32764, 32841, 33052, 33316, 34243, 34281, 34283, 34347, Document number , published 21 April 2005 Updated for Service Update 63. In the New Features section: Added Optional Use of Sharing of Timeslot (SOT) Algorithm. System Release FP1 for Windows Service Update August 22,

14 Document Revision History Added ISDN Network Side Conformance to Network Protocol Standards ITU-T Q921 and Q931. Revised the supported boards for Speed Control on DM3 Boards Using 6 khz Coders. In the System Requirements section, provided additional information about the Requirements for Global Call Protocols Package with Service Update. In the Resolved Problems section, added PTRs 29163, 33375, Document number , published 25 March 2005 Updated for Service Update 58. In the New Features section, added: Intel Telecom Subsystem Summary Tool (its_sysinfo) Speed Control on DM3 Boards Using 6 khz Coders In the Resolved Problems section, added PTRs 33286, 34121, 34241, 34269, 34345, 34393, 34558, 34561, 34633, 34753, Document number , published 18 March 2005 Updated for Service Update 56. Changed the document formatting. In the New Features section, added DPNSS Support on D/300JCT-E1, D/600JCT-1E1, and D/600JCT-2E1 Boards. In the Resolved Problems section: Added PTRs 32495, 33607, Added SU column to the Resolved Problems table, and listed the PTRs by the Service Update number in which they were fixed. Document number , published 11 February 2005 Updated for Service Update 53. Additional PTR fixes: 29382, 29698, 30102, 32548, 33249, 33528, 33754, 33759, In the IP Support on DI0408LSAR2 Boards section, deleted restrictions about systems with multiple NICs. Made other minor changes. Added DI0408LSAR2 Product Support for Host Systems with Multiple NICs to the Features section. Added Circular Logging Capability for gc_h3r.log to the Features section. Added New Features for Intel Dialogic PBX Integration Boards to the Features section. System Release FP1 for Windows Service Update August 22,

15 Document Revision History Added support for Windows XP SP2 to the System Requirements section. Added Requirements for Global Call Protocols Package with Service Update to the System Requirements section. Document number , published 4 February 2005 Updated for Service Update 52. Additional PTR fixes: 30390, 31124, 32102, 32118, 32248, 32322, 32498, 32528, 32538, 32644, 32760, 32979, 33018, 33516, 33981, 33994, Added IP Support on DI0408LSAR2 Boards to the Features section. Added ms_setmsgwaitind( ) Async Mode Support to the Features section. Revised Installing the Software section and added New Procedure for Silent Install. Document number , published 27 December 2004 Updated for Service Update 46. Added Enhanced GCAMS on DM3 Boards section. Added PTRs and to the Known Problems section. Document number , published 10 December 2004 Updated for Service Update 44. Additional PTR fixes: 32697, 33908, 34044, Document number , published 29 November 2004 Updated for Service Update 43. Additional PTR fixes: 33885, 33962, Added Support for CompactPCI Boards section. Document number , published 19 November 2004 Updated for Service Update 42. Additional PTR fixes: 33175, Document number , published 5 November 2004 Updated for Service Update 41. Additional PTR fixes: 32162, 32640, 33715, 33758, Added the D60E1P to the New Boards Supported section. Document number , published 21 October 2004 Updated for Service Update 39. Additional PTR fixes: 28554, 28559, 33011, 33099, 33247, 33338, 33511, 33598, 33690, System Release FP1 for Windows Service Update August 22,

16 Document Revision History Document number , published 7 October 2004 Updated for Service Update 38. Additional PTR fixes: 33012, 33623, Document number , published 27 September 2004 Updated for Service Update 37. Additional PTR fixes: 32408, 32555, 32730, 33471, 33472, Document number , published 10 September 2004 Updated for Service Update 36. Additional PTR fixes: 26745, 32164, 32276, 32877, 32914, 33007, 33068, Added New Boards Supported to the Features section. Document number , published 17 August 2004 Updated for Service Update 33. Additional PTR fixes: 32361, 32597, 32610, 32855, 32856, 32975, 33444, 33450, Added PTR to the Known Problems section. Document number , published 10 August 2004 Updated for Service Update 32. Additional PTR fixes: 32612, 32827, 32931, 32977, 33055, 33184, Added Support for ANI Category Digit Retrieval on DM3 Boards to the Features section. Document number , published 13 July 2004 Updated for Service Update 31. Additional PTR fixes: 29866, 32207, 32323, 32539, Document number , published 30 June 2004 Updated for Service Update 30. Additional PTR fixes: 31404, 31776, 31791, 32019, 32103, 32723, 32810, Added Features section for new features in the Service Update. Added PTR to the Known Problems section. Document number , published 9 June 2004 Updated for Service Update 28. Additional PTR fixes: 25633, 27336, 29328, 29859, 31912, 32161, 32318, 32416, 32435, 32625, 32678, 32704, System Release FP1 for Windows Service Update August 22,

17 Document Revision History Document number , published 25 May 2004 Updated for Service Update 27. Additional PTR fixes: 17567, 28550, 31495, 31840, 31955, 32209, 32471, In Prerequisites for Software Installation and Installing the Software sections, emphasized that any previous version of the Service Update must be uninstalled before installing the current Service Update. Document number , published 17 May 2004 Updated for Service Update 26. Additional PTR fixes: 31681, 31682, 31895, 31968, 32120, 32171, 32199, Document number , published 3 May 2004 Updated for Service Update 23. Additional PTR fixes: 19364, 27714, 28058, 28955, 29293, 30274, 30334, 30687, 30907, 31094, 31177, 31201, 31242, 31287, 31368, 31390, 31426, 31500, 31557, 31583, 31647, 31670, 31703, 31708, 31710, 31744, 31747, 31768, 31777, 31778, 31782, 31792, 31832, 31841, 31850, 31853, 31892, 31930, 31954, 31966, 32004, 32015, 32026, 32065, 32068, 32104, 32134, 32156, 32192, 32274, 32283, 32478, In Release Overview section, added information about new boards supported. Added Saving Existing Configuration Data section. Added PTR to the Known Problems section. Document number , published January 2004 Initial version of document for Service Update 15. System Release FP1 for Windows Service Update August 22,

18 About This Publication This section contains information about the following topics: Purpose Intended Audience How to Use This Publication Related Information Purpose These Release Notes give information about the known problems for Intel Dialogic System Release Feature Pack 1 for Windows that have been fixed with this Service Update. It is a supplement to the known and fixed problems documented in the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Release Update. The Release Notes also discuss the new features that are provided in the Service Update. Intended Audience These Release Notes are 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 Publication Use these Release Notes to learn about new features that are supported in this Service Update, and also to learn about the known problems for Intel Dialogic System Release Feature Pack 1 that have been fixed with this Service Update. (Note: These are in addition to the known and fixed problems previously documented in the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Release Update.) The following sections are included: Chapter 1, Release Overview - Provides an overview of this Service Update. System Release FP1 for Windows Service Update August 22,

19 About This Publication Chapter 2, New Features - Describes the new features in the Service Update. Chapter 3, System Requirements - Provides information about hardware and software requirements for this Service Update. Chapter 4, Installing the Software - Explains the prerequisites for installing the Service Update and gives the installation procedure. Also explains how to uninstall the Service Update. Chapter 5, Resolved Problems - Lists problems that have been resolved in this release. Chapter 6, Known Problems - Lists problems with the software that could not be fixed prior to shipment. Related Information See the following for additional information: For information about the products and features supported in this release, see the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Release Guide ( ). It is available as part of the documentation accompanying the Feature Pack release. For further information on issues that have an associated defect number, you may use the Defect Tracking tool at When you select this link, you will be asked to either LOGIN or JOIN. (for Dialogic technical support) (for Dialogic product information) System Release FP1 for Windows Service Update August 22,

20 1.Release Overview 1 This Service Update for Intel Dialogic System Release Feature Pack 1 provides fixes to many known problems for that release, as well as some new features. In addition, with this Service Update, Windows 2003, Windows 2000 SP4, and Windows XP SP2 are now supported operating systems for System Release Feature Pack 1. See Chapter 3, System Requirements for additional information. System Release FP1 for Windows Service Update August 22,

21 2.New Features 2 The following sections describe the new features provided in this Service Update: Host Diagnostic Utility Replaces Serial Diagnostics for PBX Integration Boards22 New ANI/DNIS-Enabled Parsing Tool (ADEPT) for PBX Integration Boards.. 22 Runtime Trace Facility (RTF) New Fax Parameter for Modem Receive Level Reduced Dial Tone Delay with MWI Adjusting Pre-Record Beep Tone Characteristics through the CONFIG File.. 42 Change in ipmedia.log Implementation Reducing the Delay in Reporting the GCEV_CONNECTED Event During Call Progress Analysis SIP re-invite Support on DI0408LSAR2 Boards SIP Digest Authentication Support on DI0408LSAR2 Boards Early Media Support on DM/IP Boards Support for NULL IP Address on Media Session Start New Bitmask Value for dx_stopch( ) Mode Parameter for Synchronous Operation70 PBX Integration Support for Mitel Superset 4150 Telephone New Channel Block Timer for NTT Protocol Implementation of ROLM Call Waiting LED Optional Use of Sharing of Timeslot (SOT) Algorithm ISDN Network Side Conformance to Network Protocol Standards ITU-T Q921 and Q Intel Telecom Subsystem Summary Tool (its_sysinfo) Speed Control on DM3 Boards Using 6 khz Coders DPNSS Support on D/300JCT-E1, D/600JCT-1E1, and D/600JCT-2E1 Boards85 IP Support on DI0408LSAR2 Boards Note: With the inclusion of this new feature in the Service Update, installation of the Service Update will make modifications as needed to the System Network Configuration settings in the Windows Registry in order to allow the IP Media Service to modify the Type of Service (ToS) IP packet header fields of RTP packets. This happens regardless of whether you use the ToS feature. DI0408LSAR2 Product Support for Host Systems with Multiple NICs Circular Logging Capability for gc_h3r.log System Release FP1 for Windows Service Update August 22,

22 New Features for Intel Dialogic PBX Integration Boards ms_setmsgwaitind( ) Async Mode Support Enhanced GCAMS on DM3 Boards Enhanced Special Information Tone Frequency Detection on DM3 Boards Improved Accuracy of Call Progress Analysis Support for ANI Category Digit Retrieval on DM3 Boards Support for CompactPCI Boards New Boards Supported End of Support for Specified Boards End of Support for Embedded H.323 IP Stack End of Support for Windows NT and TAPI Interfaces Host Diagnostic Utility Replaces Serial Diagnostics for PBX Integration Boards With the Service Update, you no longer need a special serial cable to gather board diagnostic messages, and messages are no longer restricted to tracing one channel at a time. Now, no cable is required and all messages are available simultaneously on all channels. Serial port output has been disabled. Diagnostic output can be sent directly to the host system and saved in a log file. To take advantage of the new diagnostic capabilities, execute C:\program files\dialogic\bin\d82diagutil.exe. 2.2 New ANI/DNIS-Enabled Parsing Tool (ADEPT) for PBX Integration Boards With the Service Update, you can now use a tool called the ANI/DNIS-Enabled Parsing Tool (ADEPT), which is a set of software modules that functions as a portable, generic, Calling Party Identification (CPID), Automatic Number Identification (ANI), and Dialed Number Identification Service (DNIS) display parser. By using ADEPT, a user can very easily update display parsing rules that are specific to a site or an application. Previous display parsers for the PBX Integration Boards could not be modified without rebuilding the firmware. With the ADEPT implementation, the CPID parsing is no longer controlled in the firmware. Instead, it is controlled in the d42 library with appropriate rules changes. The advantage of ADEPT is that a customer can change the display parser just by changing the rules file. The rules file is implemented as a simple text file. ADEPT provides significant productivity advantages by eliminating the need to rebuild firmware. No recompilation is needed in any subsystem. Both the Intel Dialogic D/82JCT-U and D/42JCT-U boards support the ADEPT functionality. System Release FP1 for Windows Service Update August 22,

23 Detailed information about this feature is provided in a new document, ADEPT for PBX Integration Boards User Guide, which has been added to the online bookshelf for System Release Feature Pack 1 for Windows. 2.3 Runtime Trace Facility (RTF) This Service Update introduces the Runtime Trace Facility (RTF) diagnostics feature. Detailed information about the RTF is given in this section Description RTF provides a mechanism for tracing the execution path of the runtime libraries for the Intel Dialogic system release software. All libraries that use RTF write their trace messages to a log file. The resulting log file helps troubleshoot runtime issues for applications that are built with Intel Dialogic system release software. RTF obtains trace control settings and output formatting from an RTF configuration file (RtfConfigLinux.xml for Linux and RtfConfigWin.xml for Windows). Each runtime library has several levels of tracing that can be dynamically enabled/disabled by editing the RTF configuration file while your application runs. This allows RTF to be configured to meet specific needs. Major RTF components include: Client library (librtfmt.dll for Windows, librtf.so for Linux): Dynamic loaded library that provides the software interface to make use of RTF functionality. Configuration file (RtfConfigWin.xml for Windows, RtfConfigLinux.xml for Linux): Editable file that allows you to customize the tracing and output capabilities of RTF (for example, which runtime libraries RTF will trace, the trace levels, location and size of backup log files). Note: You must have administrative rights to modify the RtfConfig*.xml files. Server application (RtfServer.exe for Windows, RtfServer for Linux): Service that communicates to all RTF clients, receives trace data from clients, and dispatches data to disk. Utility program (rtftool.exe for Windows, rtftool for Linux): Command line application that allows you to execute RTF functionality from command line or shell scripts. Utility program (RtfTrace.exe): Command line application that allows you to execute RTF functionality from command line or shell scripts. This is provided for backward compatibility only. All of this utility s functionality is covered in rtftool.exe Installing RTF RTF files are installed as part of the Intel Dialogic system software installation. The RTF configuration file s default installation directory is determined by the INTEL_DIALOGIC_CFG environment variable. Because the RTF configuration file s trace attribute is set to 1, RTF tracing is enabled by default. Other than editing the RTF System Release FP1 for Windows Service Update August 22,

24 configuration file to customize trace settings for your development environment, there are no special configuration steps for starting RTF RTF Configuration File To make full use of RTF, you will want to modify the RTF configuration file (RtfConfigLinux.xml for Linux, RtfConfigWin.xml for Windows). This configuration file allows you to define which trace messages will be included in the RTF output. This subsection provides some guidelines for modifying the RTF configuration file and reference information about the file s XML tags and attributes. Note: You must have administrative rights to modify the RtfConfig*.xml files. The RTF configuration file uses a number of esoteric terms that should be understood before attempting to edit the file. The following definitions should be kept in mind as you edit the RTF configuration file: module a binary file, typically an executable or a shared object library file (.so). An RTF module corresponds to a library or software module that has internal RTF APIs incorporated into its source code. client an entity for identifying a device (e.g., dxxxb1c1 ), component (e.g., WaveFileSource ) or a function (e.g., dx_play( ) ) that is to be traced by RTF. label an attribute associated with a trace statement (e.g., Error, Warning, Info, External API entry, External API exit, etc.). A trace statement s label is used by the trace data output for categorization purposes. trace entry individual entries in the trace data output. The trace data output is typically sent to a file or debug stream. 0 1 when a 0 appears next to a configuration item in the RTF configuration file, it indicates that the configuration item is disabled. when a 1 appears next to a configuration item in the RTF configuration file, it indicates that the configuration item is enabled. The RTF configuration file s top-level document tag is the RTFConfig tag. The following tags are child tags of the RTFConfig tag: Logfile Global Module System Release FP1 for Windows Service Update August 22,

25 The following figure shows the XML tag structure and tag attributes of the RTF configuration file: RTFConfig trace tracelocation timestamp Logfile path size maxbackups preserve_size preserve_maxbackups duplicate_to_debug_console log_format Global Module name state GLabel name state GClient name state MLabel name state MClient name state GClientLabel name state MClientLabel name state Convention Used: Tag name attribute 1 attribute 2... child Tag name attribute 1 attribute RTFConfig Tag RTFConfig is the document tag. This tag is a mandatory component of the RTF configuration file; it can be found at the top of the RTF configuration file. A sample RTFConfig tag entry is shown below: <RTFConfig trace= 1 tracelocation= TRACE_LOG timestamp= 1 logformat= ALIGN > <!-- Logfile section goes here --> <!-- Global section goes here --> <!-- Module sections go here --> </RTFConfig> The RTFConfig tag includes the following attributes: System Release FP1 for Windows Service Update August 22,

26 trace This attribute is used to enable or disable the RTF tracing capabilities. Valid values are as follows: 0 1 RTF tracing is disabled. RTF tracing is enabled. This is the default setting. tracelocation This attribute has no effect and will be removed in a future release. By default, trace output is sent to a log file. timestamp This attribute has no effect and will be removed in a future release. By default, each log file name includes a time stamp. logformat This attribute defines the format of the log file. The following values are supported: ALIGN Aligns the trace entry fields in the log file into comma separated columns. The top of each column includes a header that provides a description of the column s content. This is the default setting. UNALIGN Separates the trace entry fields in the log files with commas. Column alignment is not done. Notes:1. If you set the logformat attribute to ALIGN, you can customize the widths of the various columns. The following attributes in the RTF configuration file allow you to define the aligned column widths: ModuleWidth number - Allows you to customize the number of characters that appear in the Module column. The default setting is 10. There is no maximum setting. ClientWidth number - Allows you to customize the number of characters that appear in the Client column. The default setting is 15. There is no maximum setting. LabelWidth number - Allows you to customize the number of characters that appear in the Label column. The default setting is 10. There is no maximum setting. 2. Using the ALIGN setting makes the log file easier to read but it does not make efficient use of hard drive space. This inefficiency is exacerbated as the log file grows. The UNALIGN format is separated by commas so it can be parsed by a spreadsheet or database program to make the file easier to read. System Release FP1 for Windows Service Update August 22,

27 Logfile Tag The Logfile tag is the first child tag of the RTFConfig tag. The Logfile tag provides logistical information about the log file(s) used to store trace output. If you would like to customize the appearance and settings of the log file, edit the Logfile tag within the RTF configuration file. The Logfile tag appears under the RTFConfig tag in the RTF configuration file. A sample Logfile tag entry from the RtfConfigLinux.xml file is shown below: <Logfile path= $(INTEL_DIALOGIC_DIR)/log size= 300 maxbackups= 10 preserve_size= 300 preserve_maxbackups= 10 duplicate_to_debug_console= 0 log_format= text /> A sample Logfile tag entry for the RtfConfigWin.xml file is shown below: <Logfile path= $(INTEL_DIALOGIC_DIR)\log size= 300 maxbackups= 10 preserve_size= 300 preserve_maxbackups= 10 duplicate_to_debug_console= 0 log_format= text /> The Logfile tag includes the following attributes: path Indicates a valid directory path for the log file. The default path for Linux is $(INTEL_DIALOGIC_DIR)/log. The default path for Windows is $(INTEL_DIALOGIC_DIR)\log. The INTEL_DIALOGIC_DIR environment variable is defined as part of the system release software installation routine. size Sets the maximum size, in Kilobytes (KB), of the log file when RTF is run with preservation mode turned OFF. The default setting is 300. When the file reaches its maximum size, RTF rolls over the log file, much like a circular buffer. The previous log file is saved as a time-stamped text file. RTF aligns the entries so that the oldest entry is always at the top of the log file and the newest entry is always at the bottom of the log file. Notes:1. Due to the internal buffers used by RTF, 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. 2. This attribute is only applicable when RTF preservation mode is turned OFF. When RTF preservation mode is ON, the preserve_size attribute determines the size of the log file. Refer to Section , Running RTF in Preservation Mode, on page 38 for information about preservation mode. maxbackups Indicates the maximum number of backup log files the RTF creates when the RTF is run with preservation mode turned OFF. If this attribute is set to 0, all trace information is written to one log file. If this attribute is set to 1 or greater, all trace information is initially System Release FP1 for Windows Service Update August 22,

28 written to one log file. When the size of this initial log file reaches the threshold defined in the Logfile tag s size attribute, the RTF trace data rolls over into a second log file. When the size threshold is reached in the second log file, the RTF trace data rolls over into a third log file. This sequence occurs until the number of backup log files created equals the maxbackups attribute setting. When the roll over occurs, the previous log file is saved under the following time-stamped name: rtflog-<year><month><day>-<hour>h<minute>m.<second>s.txt If the number of backup log files exceeds the number defined in maxbackups, the oldest backup file will be deleted and a new one will be created, on a first in, first out basis. The default maxbackups value is 10. Note: This attribute is only applicable when RTF preservation mode is turned OFF. When RTF preservation mode is ON, the preserve_maxbackup attribute determines the number of backup log files. Refer to Section , Running RTF in Preservation Mode, on page 38 for information about preservation mode. preserve_size Sets the maximum size, in Kilobytes (KB), of the log file when the RTF is run with preservation mode turned ON. The default setting is 300. When the file reaches its maximum size, RTF rolls over the log file, much like a circular buffer. The previous log file is saved as a time-stamped text file. RTF aligns the entries so that the oldest entry is always at the top of the log file and the newest entry is always at the bottom of the log file. Note: This attribute is only applicable when RTF preservation mode is turned ON. When RTF preservation mode is OFF, the size attribute determines the size of the log file. Refer to Section , Running RTF in Preservation Mode, on page 38 for information about preservation mode. preserve_maxbackups Indicates the maximum number of backup log files the RTF creates when the RTF is run with preservation mode turned ON. If this attribute is set to 0, all trace information is written to one log file. If this attribute is set to 1 or greater, all trace information is initially written to one log file. When the size of this initial log file reaches the threshold defined in the Logfile tag s preserve_size attribute, the RTF trace data rolls over into a second log file. When the size threshold is reached in the second log file, the RTF trace data rolls over into a third log file. This sequence occurs until the number of backup log files created equals the preserve_maxbackups attribute setting. When the roll over occurs, the previous log file is saved under the following time-stamped name: rtflog-<year><month><day>-<hour>h<minute>m.<second>s_p.txt Note: The _p suffix appears in the log file name because preservation mode is turned ON. System Release FP1 for Windows Service Update August 22,

29 The default preserve_maxbackups value is 10. Note: This attribute is only applicable when RTF preservation mode is turned ON. When RTF preservation mode is OFF, the maxbackups attribute determines the number of backup log files. Refer to Section , Running RTF in Preservation Mode, on page 38 for information about preservation mode. duplicate_to_debug_console This attribute determines whether or not trace information is duplicated in the debug console (Windows) or the standard error output (Linux). Possible settings are as follows: 1 0 The trace output information will be duplicated on the debug console for Windows systems or the standard error output for Linux systems. The trace output information will not be duplicated on the debug console for Windows systems or the standard error output for Linux systems. This is the default setting. log_format Global Tag This attribute determines the format of the output log file. This is always set to text (the trace output log is written in readable, text file format). The Global tag is the second child tag of the RTFConfig tag. The Global tag is used to specify the global configuration. Global configuration settings are valid for all modules included in the RTF configuration file. However, the Global tag has the lowest priority in the RTF configuration file. Therefore, the global configuration settings can be overridden by individual settings at the Module tag level (see Section , Module Tag, on page 32). The Global tag cannot occur more than one time in the RTF configuration file. The Global tag can either be empty: <Global> <!-- This is an example of an empty Global tag --> </Global> or the Global tag can have GLabel and/or GClient child tags. There are no attributes associated with the Global tag GLabel Tag The GLabel tag is a child tag of the Global tag; it is used to configure global labels. If a label is defined at the GLabel level, then all module and client behavior will be governed by this configuration (unless overridden for a given module at the MLabel level). The following line may appear in the default RtfConfigLinux.xml file: System Release FP1 for Windows Service Update August 22,

30 <GLabel name = Error state = 1 /> This line indicates that tracing of all Error labels is turned on by default. To disable this default behavior, you can delete this line or change the Error state attribute setting to 0. The following lines appear in the default RtfConfigWin.xml file: <GLabel name = Error state = 1 /> <GLabel name = Exception state = 1 /> These lines indicate that tracing of all Error labels and all Exception labels is turned on by default. To disable this default behavior, you can delete these lines or change the Error state attribute and Exception state attribute setting to 0. The GLabel tag has the following attributes: name Indicates the name of the global label to be configured. You must define the name of the global label; there is no default value. Examples of possible labels include: Error (enabled at the Global level by default) Debug Info Warning Note: Refer to the default RTF configuration file s MLabel name attributes. These default entries are for the Intel Dialogic runtime libraries. Any of these runtime library label names can be included in a GLabel tag. state Specifies the state of the label. Valid values are as follows: 1 Label is enabled at the global level. All trace messages associated with this label will be sent to the trace output. This is the default value. 0 Label is disabled at the global level. Trace messages associated with this label will not be sent to the trace output GClient Tag The GClient tag is a child tag of the Global tag; it is used to configure global clients (devices). If a client is defined at the GClient level, then all client behavior will be governed by this configuration (unless overridden for a given client at the MClient level). The GClient tag can be empty or have GClientLabel children tags. The GClient tag has the following attributes: System Release FP1 for Windows Service Update August 22,

31 name Indicates the name of the client to be configured. You must define the name of the global client; there is no default value. Examples of possible client names include: dxxxb1c1 (voice device) dxxxb2c2 (voice device) ipmb2c2 (IP media device) Note: Refer to the Voice Software Reference: Standard Runtime Library for Windows for more information about client names for Intel Dialogic libraries and devices. state Specifies the state of the client. Valid values are as follows: 1 Client is enabled at the global level. All trace messages associated with this client will be sent to the trace output. This is the default value. 0 Client is disabled at the global level. Trace messages associated with this client will not be sent to the trace output GClientLabel Tag The GClientLabel tag is a child tag of the GClient tag; it is used to specify a label for a global client. The GClientLabel tag has the following attributes: name Indicates the name of a client label to be configured. You must define the name of the client label; there is no default value. Examples of possible client labels include: Error Warning Entry Note: Refer to the default RTF configuration file s MLabel name attributes. These default entries are for the Intel Dialogic runtime libraries. Any of these runtime library label names can be included in a GClientLabel tag. state Specifies the state of the label. Valid values are as follows: 1 Client label is enabled at the global level. Trace messages associated with this label will be sent to the trace output. This is the default value. System Release FP1 for Windows Service Update August 22,

32 0 Client label is disabled at the global level. Trace messages associated with this label will not be sent to the trace output Module Tag This tag is used to specify configuration for various modules. Module tags have a higher priority than global tags so settings at the module level override settings at the global level. For example, if the state of a label Error is set to 1 in the global section and Error is set to 0 for an individual module, then the label Error will not be traced for that particular module. The module section must exist in the configuration file, even if the section is empty. Possible child tags of the Module tag are MClient and MLabel. The RTF configuration file contains modules for the Intel Dialogic runtime libraries. The following example shows that the module name for the Fax Library is spwrfax : <!-- Fax Library --> - <Module name="spwrfax" state="1"> <MLabel name="debg" state="0" /> <MLabel name="info" state="0" /> <MLabel name="appl" state="0" /> <MLabel name="warn" state="0" /> <MLabel name="err1" state="1" /> <MLabel name="exce" state="0" /> </Module> You can edit the state attributes of the modules to enable (set state = 1 ) or disable (set state = 0 ) the tracing. Alternatively, you can delete one or more modules from the default RTF configuration file if you are not interested in tracing certain runtime libraries. Note: The RTF configuration file contains some older sections that have been retained for backward compatibility. The Module tag includes the following attributes: name Indicates the name of a module to be configured. Intel Dialogic runtime libraries have module names in the default RTF configuration file. Example module names in the RTF configuration file include: gc libsrl spwrdevmgmt state Specifies the state of the module. Valid values are as follows: 1 Module is enabled. Trace messages associated with this label will be sent to the trace output. This is the default value. System Release FP1 for Windows Service Update August 22,

33 0 Module is disabled. Trace messages associated with this label will not be sent to the trace output MLabel Tag The MLabel tag is a child tag of the Module tag. The MLabel tag is used to configure module labels. If a label is defined at the global level and the same label is defined at the module level, the module level configuration overrides the global configuration for the module. The MLabel tag has the following attributes: name Indicates the name of the label to be configured. The Intel Dialogic runtime libraries have module label names in the default RTF configuration file. Example module label names in the RTF configuration file include: APPL DEBG WARN state Specifies the state of the label. Valid values are as follows: 1 Label is enabled. Trace messages associated with this label will be sent to the trace output. This is the default value. 0 Label is disabled. Trace messages associated with this label will not be sent to the trace output. Note: When the state attribute is not included or not defined, the default value is 1. However, the Intel Dialogic runtime library module labels that exist in the default RTF configuration file have their state attribute initially set to MClient Tag The MClient tag is a child tag of the Module tag; it is used to configure a specific client for the module. The MClient tag can be empty or have MClientLabel children tags. The MClient tag has the following attributes: name Indicates the name of the client to be configured. The Intel Dialogic runtime libraries have pre-defined module client names in the default RTF configuration file. Example clients include: dxxxb1c1 (voice device) System Release FP1 for Windows Service Update August 22,

34 dxxxb2c2 (voice device) ipmb2c2 (IP media device) Note: Refer to the Voice Software Reference: Standard Runtime Library for Windows for more information about client names for Intel Dialogic libraries and devices. state Specifies the state of the client. Valid values are as follows: 1 Client is enabled. Trace messages associated with this client will be sent to the trace output. This is the default value. 0 Client is disabled. Trace messages associated with this client will not be sent to the trace output. Note: When the state attribute is not included or not defined, the default value is MClientLabel Tag The MClientLabel tag is a child tag of the MClient tag; it is used to specify a label for a client. The MClientLabel tag has the following attributes: name Indicates the name of a label to be configured. You must define the name of the label; there is no default value. Example labels include: APPL DEBG WARN Note: A complete list of labels for a given library can be found in the RTF configuration file. state Specifies the state of the label. Valid values are as follows: 1 Label is enabled. Trace messages associated with this label will be sent to the trace output. This is the default value. 0 Label is disabled. Trace messages associated with this label will not be sent to the trace output. System Release FP1 for Windows Service Update August 22,

35 Precedence Scheme for Module/Client Labels This section summarizes the precedence scheme of settings in RTF module/client labels. Basically, RTF has three types of handles for use in determining if a trace statement will be filtered. They are modules, clients, and labels. A trace statement can use filtering of either of the following: module+label For trace statements that use module+label, the trace will only be stored in a file when both module and label are enabled. module+client+label For trace statements that use module+client+label, the trace will only be stored in a file when module, client, and label are all enabled. When it is not provided in the configuration file, default enable/disable settings for the three types of handles are: Module: disabled Client: enabled Label: disabled For handles set in the configuration file, the precedence order is: Module: No precedence order since it is only available at a module level. No global level. Client: Settings in the module section override settings in the global section. Label: For trace statements without client handles, settings in the module section override settings in the global section. For trace statements with client handles, settings in the module/client section override settings in the client/label section; settings in the client/label section override settings in the module section; and settings in the module section override settings in the global section Restrictions and Limitations Keep the following restrictions and limitations in mind when using RTF: If you run full RTF logging on high-density systems, you may experience I/O throughput degradation. 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. If you install the Intel Dialogic system release software on a FAT32 formatted hard drive, the RTF tool will generate an Error after install attempting to launch error message. The error message appears because FAT32 does not support file system access control. However, RTF will continue to function. The Intel Dialogic system software installation routine creates a usr\dialogic\log directory. When the system software is installed on a Mandriva* (formerly Mandrakesoft) Linux system, the Mandriva security utility (msec), which automatically runs every hour, may reset the access permissions to this...\log directory. To avoid the resetting of permissions, you must perform the following before running RTF: System Release FP1 for Windows Service Update August 22,

36 Issue the echo $SECURE_LEVEL command. The Mandriva Linux system will return a number that indicates the current system security setting. Add the following line to the perm.n file (located in /usr/share/msec/perm.n), where n indicates the security setting number returned in the previous step: \var\log\dialogic\* current xxx Where xxx indicates the desired access permission setting for the directory. After you change the perm.n file, run msec n so that the change will take effect immediately. When RTF logging is enabled, logs are stored in the $(INTEL_DIALOGIC_DIR)\log directory. You should take necessary precautions to ensure that the directory never fills Guidelines for Editing the RTF Configuration File Keep the following rules in mind when editing the RTF configuration file: Do not change the name of the file. The filename must remain at its default setting. The RTF configuration file is broken down into four sections. The sequence of the sections must always be as follows: 1. RTFconfig 2. Logfile configuration 3. Global configuration 4. Module configuration RTF uses the following default log file names: rtflog-<year><month><day>-<hour>h<minute>m.<second>s.txt when preservation mode is OFF. rtflog-<year><month><day>-<hour>h<minute>m.<second>s_p.txt when preservation mode is turned ON. The Global configuration section can only appear one time in the RTF configuration file. If a there is configuration information which conflicts in the global and module sections (for example, the global section enables a trace label for a client, but the module section disables this same label for the same client), then the module configuration overrides the global configuration. Configuration information that is repeated later in the file will take precedence. For example, if there are two module configurations for spwrvoice, the configuration information lower in the file will dictate tracing behavior for that module. Note: This should not be done, but it is mentioned here so the behavior can be recognized if this situation occurs by error. RTF is case sensitive. Therefore, the trace labels Error and error are considered to be two distinctly different trace labels. Simultaneous tracing of multiple Intel Dialogic libraries may have an adverse effect on system performance. 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 System Release FP1 for Windows Service Update August 22,

37 MUTEX). It is recommended that you do not run RTF with full logging on high density systems or any field-deployed systems. Contact customer support before enabling extensive logging. Instead, use just the default error-enabled logging. RTF affects running processes/applications only. If you enable RTF prior to starting your application, the RTF will not provide trace information until your application has started. If you wish to dynamically edit the RTF trace levels while your application runs, it is not necessary to stop RTF. Instead, perform the following: 1. Open the RTF configuration file. 2. Customize the settings in the RTF configuration file. 3. Save and close the RTF configuration file. 4. Issue the rtftool reload command to reload the RTF configuration file and restart the RTF engine. Note: Keep in mind that changes made to the RTF configuration file will not be reflected in the RTF output until the tool has been reloaded. At any time, you can issue the rtftool command to pause/restart RTF. RTF will not provide trace output while it is paused. Refer to Section 2.3.5, rtftool Command, on page 37 for more information. Save the original RtfConfigWin.xml file or RtfConfigLinux.xml file, as it is advisable to return to the original logging level when finished using the RTF logging mechanism rtftool Command This section explains the rtftool command, which is used to control RTF and modify the trace output. The rtftool command is issued from the command line. The rtftool command can be issued from any directory Pausing and Reloading RTF RTF tracing is enabled by default. Use the rtftool command to pause, resume, and reload the RTF tracing capabilities. The rtftool command has the following pause and reload variations: rtftool pause Pauses RTF tracing. Trace output will not be written to the log file while RTF is paused. rtftool resume Resumes RTF tracing. Issue this command to resume tracing after RTF has been paused. rtftool reload Reloads an updated RTF configuration file (RtfConfigLinux.xml or RtfConfigWin.xml) and restarts RTF, using the settings from the updated RTF configuration file. Note: You do not need to pause RTF tracing before issuing the rtftool reload command. RTF supports dynamic updates to the RTF configuration file. Simply edit and save the file, then issue the rtftool reload command to begin tracing with the updated RTF configuration file settings. System Release FP1 for Windows Service Update August 22,

38 Clearing the RTF Trace Log File Contents Use the rtftool command to clear all trace data from the RTF log file. The following command line option clears the RTF log file contents: rtftool clean [-f] Clears the RTF log file contents. When the -f option is used, RTF will not ask the user for confirmation before clearing the log file Running RTF in Preservation Mode You can set RTF to run in preservation mode. Preservation mode allows you to determine whether old trace data is overwritten or preserved in a separate file when the log file grows to its maximum size. When preservation mode is turned ON, RTF will append a _p to the end of each RTF log file name; RTF will not delete or overwrite these _p log files. Use the preserve_size and preserve_maxbackup Logfile tag attributes to set the size and number of backup log files, respectively. Use the following command line option to enable/disable preservation mode: rtftool preservation {on off} Turns RTF preservation mode ON and OFF Example RTF Configuration Files This section provides a number of example RtfConfig*.xml files along with a brief explanation of how the file settings affect the RTF trace output. Note that the same rules/examples covered in this section apply to both the RtfConfigWin.xml and RftConfigLinux.xml file Example 1: Tracing disabled - RtfConfigWin.xml <?xml version="1.0" standalone="no"?> <RTFConfig trace="0" tracelocation= TRACE_LOG logformat= ALIGN timestamp= 1 > <Logfile path="$(intel_dialogic_dir)\log" size="1000" maxbackups= 2 preserve_size= 300 preserve_max_backups= 10 duplicate_to_debug_console= 0 log_format= text /> <Global> </Global> <Module name="spwrvoice" state = "1"> <MLabel name="err1" state = "1"/> <MLabel name="warn" state = "0"/> </Module> </RTFConfig > System Release FP1 for Windows Service Update August 22,

39 Explanation The RTFConfig tag s trace attribute is set to 0 so tracing is disabled. Trace output will not be created. Set the trace attribute to 1 to activate tracing Example 2: Tracing enabled, logfile path and size specified, preservation mode OFF, one module configured - RTFConfigLinux.xml <?xml version="1.0" standalone="no"?> <RTFConfig trace="1" tracelocation= TRACE_LOG timestamp= 1 logformat= ALIGN > <Logfile path="$(intel_dialogic_dir)/log" size="1000" maxbackups= 2 preserve_size= 300 preserve_max_backups= 10 duplicate_to_debug_console= 0 log_format= text /> <Global> </Global> <Module name="spwrvoice" state = "1"> <MLabel name="err1" state = "1"/> <MLabel name="warn" state = "1"/> </Module> </RTFConfig > Explanation The RTFConfig tag s trace attribute is set to 1 so tracing is enabled. The Global tag is empty, so there is no global configuration. For this example, tracing is only configured at the module level. The path for the log file is $(INTEL_DIALOGIC_DIR)/log. Preservation mode is OFF, so the size and maxbackup attributes apply while the preserve_size and preserve_max_backups attributes are ignored. The maximum logfile size is 1000 KB. The system maintains a maximum of 2 backup log files. The only module configured for trace is spwrvoice. This means that all clients (devices) for this module are configured to trace ERR1 and WARN labels Example 3: Tracing enabled, logfile path and size specified, several modules configured, global configuration used - RTFConfigWin.xml <?xml version="1.0" standalone="no"?> <RTFConfig trace="1" tracelocation= TRACE_LOG logformat= ALIGN > <Logfile path="$(intel_dialogic_dir)\log" size="1000" maxbackups= 2 preserve_size= 300 preserve_max_backups= 10 duplicate_to_debug_console= 0 log_format= text /> System Release FP1 for Windows Service Update August 22,

40 <Global> <GLabel name="entry" state = "1"/> <GClient name="dxxxb1c2" > <GClientLabel name="exit" state = 1 /> </GClient> </Global> <Module name="spwrvoice" state = "1"> <MLabel name="err1" state = "1"/> <MLabel name="warn" state = "0"/> </Module> <Module name="spwrvoice"> <MLabel name="err1" state = "0"/> <MLabel name="warn" state = "1"/> <MClient name="dxxxb1c2" > <MClientLabel name="err1"/> /MClient> </Module> <Module name="faxntf" state = "1"> <MLabel name="warn" state = "1"/ </Module> <Module name="dtintf"> <MClient name="dxxxb2c1"> <MClientLabel name="exce"/ </MClient> </Module> </RTFConfig > Explanation The trace attribute of the RTFConfig tag is set to 1 so tracing is enabled. The logfile path is $(INTEL_DIALOGIC_DIR)\log. Preservation mode is ON, so the size and maxbackup attributes are ignored while the preserve_size and preserve_max_backups attributes apply. The maximum logfile size is 300 KB. The system maintains a maximum of 10 backup log files (filenames appended with a _p). The Global section is present in the configuration file, so all modules will have this global configuration. This configures Entry as a global label and dxxxb1c2 is a global client for label Exit. In the module section there are two configurations for spwrvoice so the later configuration will take precedence. Since the state of spwrvoice is not specified, it takes default value 1. Tracing is enabled for the module spwrvoice but only for the WARN label. The client dxxxb1c2 is also configured to trace in the spwrvoice module with the label ERR1. Therefore the client dxxxb1c2 in spwrvoice is traced for the label ERR1, even though it is disabled in the module section. All other clients of spwrvoice are configured to be traced for only label WARN, as WARN is the only label configured to be traced for the module. System Release FP1 for Windows Service Update August 22,

41 The faxntf module is configured to trace WARN (from the module section) and Entry (from the global section). The dtintf module is configured to trace Entry (from the global section). dxxxb1c2 in dtintf is configured to trace Entry (from the global section) and Exit (from the global client). The other client dxxxb2c1 is configured to trace Entry (from the global configuration) and EXCE (from the module client section). All other clients of this module are configured to trace Entry (from the global section) since these labels are configured for the module. 2.4 New Fax Parameter for Modem Receive Level With the Service Update, a new fax parameter, FC_MDM_RX_LVL, has been added to allow setting of the fax modem receiver sensitivity from -43 dbm to -47 dbm. This parameter is supported on Intel Dialogic Springware fax boards only. The FC_MDM_RX_LVL parameter is set with the fx_setparm( ) function and can be retrieved with the fx_getparm( ) function. Valid settings are: 0 = -43 dbm 1 = -44 dbm 2 = -45 dbm 3 = -46 dbm (default) 4 = -47 dbm For example: int parmvalue = 3; // set parameter fx_setparm(devicehandle, FC_MDM_RX_LVL, (void*)&parmvalue); // get current setting fx_getparm(devicehandle, FC_MDM_RX_LVL, (void*)&parmvalue); For further information about the fx_setparm( ) and fx_getparm( ) functions, see the Fax Software Reference for Windows on the online bookshelf for System Release Feature Pack 1 for Windows. 2.5 Reduced Dial Tone Delay with MWI The ms_setmsgwaitind( ) function generates an FSK signal to illuminate the message waiting LED. When a user of a station goes off-hook before the ms_setmsgwaitind( ) function is complete, a slight delay occurs before hearing the dial tone. With the Service Update, this delay has been reduced by 12%. System Release FP1 for Windows Service Update August 22,

42 2.6 Adjusting Pre-Record Beep Tone Characteristics through the CONFIG File With the Service Update, several Intel NetStructure and Intel Dialogic boards now support the ability to modify the pre-record beep tone characteristics. This new functionality is provided through the configuration file set. Changed values take effect at the time the firmware is downloaded to the board using the configuration manager (DCM) utility. This new functionality is supported on the following Intel Dialogic boards: DI0408LSAR2 DMV160LP This new functionality is supported on the following Intel NetStructure DM/V-A boards: DM/V480A-2T1-PCI DM/V600A-2E1-PCI DM/V960A-4T1-PCI DM/V1200A-4E1-PCI This new functionality is supported on the following Intel NetStructure DM/IP boards: DM/IP241-1T1-PCI-100BT DM/IP301-1E1-PCI-100BT DM/IP481-2T1-PCI-100BT DM/IP601-2E1-PCI-100BT Feature Description A beep tone is used in some applications to indicate the start of recording. This beep tone is enabled through the RM_TONE value in the mode parameter of various record functions (for example, dx_reciottdata( )) in the Voice API library. The characteristics of the pre-record beep tone were previously hardcoded and differed on Springware boards versus DM3 boards. With the Service Update, you can modify the beep tone values, such as the amplitude, in the Tone Templates [tonegen] section of a particular media load CONFIG file. Default values are provided that are consistent with previous service updates and system releases to preserve backward compatibility. After adjusting a beep tone parameter value in a CONFIG file, you must run the fcdgen utility to update the corresponding FCD file, and then download the firmware to the board using the configuration manager (DCM) utility. For more information on modifying FCD file parameters, see the DM3 Configuration File Reference. System Release FP1 for Windows Service Update August 22,

43 Pre-Record Beep Tone Characteristics and Default Values Two pre-record beep tones are defined: a digital sounding pre-record beep tone, BEEP_DGSD, defined as 444 Hz. the traditional pre-record beep tone, BEEP_DLGC, defined as 1000 Hz. This corresponds to the beep tone definition on Springware boards and is the default setting. The [recorder] section of the CONFIG file includes the following parameter, which specifies the tone to be used in the application: BeepSignalID (Pre-Record Beep Tone) Number: 0x203 Description: The BeepSignalID parameter is the signal identifier of the beep tone preceding the recording. Values: 0x21: 444 Hz tone for 400 ms 0x22: 1000 Hz tone for 400 ms (default) The pre-record beep tone characteristics for the two beep tones, stored in the Tone Templates [tonegen] section of the CONFIG file, are described as follows: Record Beep Tone Characteristic Default Value BEEP_DGSD Signal Id 33 Label (blank) Segment Count 1 Segment Signal Type 2 Segment Frequency 1 (Hz) 444 Segment Amplitude 1 (.25 dbm) -40 Segment Frequency 2 (Hz) 0 Segment Amplitude 2 (.25 dbm) 0 Segment On Duration (125 microsecs) 3200 Segment Off Duration (125 microsecs) 320 Segment Reps 1 Next Segment System Release FP1 for Windows Service Update August 22,

44 Record Beep Tone Characteristic Default Value BEEP_DLGC Signal Id 34 Label (blank) Segment Count 1 Segment Signal Type 2 Segment Frequency 1 (Hz) 1000 Segment Amplitude 1 (.25 dbm) -40 Segment Frequency 2 (Hz) 0 Segment Amplitude 2 (.25 dbm) 0 Segment On Duration (125 microsecs) 3200 Segment Off Duration (125 microsecs) 320 Segment Reps 1 Next Segment Media Loads Supported The following media loads support the new functionality to modify pre-record beep tone parameter values: On DI0408LSAR2 boards, all media loads support the new functionality. On DMV160LP boards, all media loads support the new functionality. On DM/V480A-2T1-PCI boards, Media Loads 1b and 10 support the new functionality. On DM/V600A-2E1-PCI boards, Media Loads 1b and 10 support the new functionality. On DM/V960A-4T1-PCI boards, Media Loads 1b and 5 support the new functionality. On DM/V1200A-4E1-PCI boards, Media Load 1b and Universal Media Load 1 support the new functionality. On DM/IP boards, Media Load 11 supports the new functionality Documentation For more information about configuration files, configuration parameters, and configuration procedures, see the DM3 Configuration File Reference. 2.7 Change in ipmedia.log Implementation With the Service Update, the ipmedia.log file is no longer overwritten when the system is restarted. The ipmedia.log file is generated whenever IP Media Services are run. If there is an existing log file when the system is restarted, it is saved and renamed ipmedia.log.bak. If ipmedia.log.bak already exists, it is overwritten (only one backup file is saved). System Release FP1 for Windows Service Update August 22,

45 2.8 Reducing the Delay in Reporting the GCEV_CONNECTED Event During Call Progress Analysis With the Service Update, an application running call progress analysis with positive voice detection (PVD) can receive the GCEV_CONNECTED event as soon as voice is detected on the remote side. Previously, the reporting of this event did not occur until the positive answering machine detection (PAMD) algorithm was completed, which sometimes resulted in missed initial speech. This new functionality, called quick connect, must be enabled manually through a new parameter in the configuration file set. Changed values take effect at the time the firmware is downloaded to the board using the configuration manager (DCM) utility. When the functionality is enabled, the PAMD algorithm will still run if configured to do so, but the return of GCEV_CONNECTED will no longer be delayed until PAMD completes. This new functionality is supported on the following Intel Dialogic boards: DI0408LSAR2 DMV160LP Notes:1. The quick connect feature provides an earlier connected event only in the case where voice is detected; that is, it does not cover the case where the remote side goes off hook and there is no audio. 2. The quick connect feature is enabled on a per board basis only; it cannot be enabled or disabled per channel Feature Description To specify that the GCEV_CONNECTED event be sent to the application as soon as voice is detected on the remote side, you must manually add a parameter to the particular media load CONFIG file. This new parameter is contained in the [sigdet] section of a CONFIG file and is described as follows: Note: There is a msec delay from the start of speech until GCEV_CONNECTED is received. Quick Connect (Reduce Delay in GCEV_CONNECTED Reporting) Parameter Number: 0x711 Description: The Quick Connect parameter enables the GCEV_CONNECTED event to be sent to the application as soon as voice is detected on the remote side. Values: 1 Guidelines: Quick Connect is disabled by default. To enable this feature, you must manually add this parameter to the [sigdet] section of the CONFIG file (using the SetParm System Release FP1 for Windows Service Update August 22,

46 format) and specify a value of 1. This parameter is supported on Intel Dialogic DI0408LSAR2 and Intel Dialogic DMV160LP boards only. Example The following shows the parameter added in the [sigdet] section of a CONFIG file: [sigdet]... SetParm=0x711,1...! Enable quick connect After adding this parameter in a CONFIG file, you must run the fcdgen utility to update the corresponding FCD file, and then download the firmware to the board using the configuration manager (DCM) utility. For more information about modifying FCD file parameters, see the DM3 Configuration File Reference Documentation For more information about configuration files, configuration parameters, and configuration procedures, see the DM3 Configuration File Reference. 2.9 SIP re-invite Support on DI0408LSAR2 Boards With the Service Update, SIP re-invite is supported on Intel Dialogic DI0408LSAR2 Switching Boards. Support for SIP re-invite requests is provided by the IP-specific Global Call APIs gc_acceptmodifycall( ) and gc_rejectmodifycall( ), which are documented in detail elsewhere in this document, and IP-specific event types. Following a description of the feature, function reference pages for the new functions and a data structure reference page for RTP_ADDR are provided. RFC 3261 specifies that User Agents must be able to send and respond to additional INVITE requests after a dialog has been established to allow modification of the dialog or the media session. Additional INVITE requests in an existing dialog are known as re- INVITE requests to distinguish them from an initial INVITE request that would initiate a new dialog. Re-INVITE requests contain the same Call-ID, To, and From headers as the original INVITE request that established the dialog. Either party in a dialog can issue a re- INVITE, and only one re-invite can be pending at any given time. The Global Call IP Call Control Library (IP CCLib) in the System Release Service Update line supports the reception of SIP re-invite requests for the specific purpose of changing the RTP address of the remote endpoint. System Release FP1 for Windows Service Update August 22,

47 2.9.1 Receiving a SIP re-invite Request REF3261 specifies that either party in a SIP dialog can initiate a re-invite transaction, so Global Call applications must be able to receive and handle incoming re-invite requests. When the IP Call Control Library receives a re-invite request, the library first examines the request to determine whether it specifies media properties that are acceptable by the local endpoint. If the received re-invite request specifies media capabilities that are not supported by the local system, the call control library automatically sends a 488 Not Acceptable Here response to the requesting party and generates a GCEV_REQ_MODIFY_UNSUPPORTED event to the application. This unsolicited event contains a CCLIB cause code of IPEC_SIPReasonStatus488NotAcceptableHere. This event is sent for informational purposes only because the library has already sent the appropriate response to the remote UA; the local application does not need to take any action upon receiving this informational event. If the received re-invite request does not contain an SDP offer, or if it contains an SDP offer that specifies media capabilities that are supported by the local media device, the call control library generates an unsolicited GCEV_REQ_MODIFY_CALL event to notify the application. The METAEVENT associated with this event contains a pointer to a GC_PARM_BLK structure that the library has populated with the following information from the SDP offer contained in the re-invite request: one or more parameter elements that contain the media session properties that were specified in the SDP offer a parameter element that contains the remote RTP transport address from the SDP offer Receiving Proposed Media Session Properties The SDP offer in the received re-invite request will contain proposed media capabilities that may or may not match the properties of the current media session. Because the Global Call IP Call Control Library implementation in the System Release Service Update line only supports re-invite for changing the RTP transport address, any re- INVITE request that proposes any other change to the media properties must be rejected. It is the application s responsibility to analyze the media properties proposed in the SDP offer and to reject the re-invite request if it contains properties that differ from the current session s properties. The METAEVENT associated with the GCEV_REQ_MODIFY_CALL event that is used to notify the application of a re-invite request contains a pointer to a GC_PARM_BLK that contains parameter elements which identify the supported media properties that were proposed in the request. Each proposed media capability is handled as a parameter element of the following type: GCSET_CHAN_CAPABILITY IPPARM_LOCAL_CAPABILITY value = IP_CAPABILITY data structure (see the reference page in the Global Call IP over Host-based Stack Technology User s Guide for full details) System Release FP1 for Windows Service Update August 22,

48 The number of these parameter elements depends on the specifics of what change the re- INVITE is requesting: If the re-invite is seeking to place the call on hold, there will be only a single GCSET_CHAN_CAPABILITY/IPPARM_LOCAL_CAPABILITY element with the direction field of the IP_CAPABILITY structure set to either IP_CAP_DIR_LCLRTPINACTIVE or IP_CAP_DIR_LCLRTPRTCPINACTIVE. This operation is not supported in the System Release SU code, and the application must reject the re-invite request in this case. If the re-invite is proposing a change to a full duplex media session, there will be a pair of GCSET_CHAN_CAPABILITY/IPPARM_LOCAL_CAPABILITY parameter elements for each proposed media capability that is supported on the local platform. Within each parameter pair, all fields of the of the IP_CAPABILITY structure will be the same except for the direction fields, one of which is set to IP_CAP_DIR_LCLTRANSMIT and the other is set to IP_CAP_DIR_LCLRECEIVE. After the application retrieves the channel capability parameters from the parameter block, it must compare them to the properties of the current media session. If the properties match (in other words, if no change in media properties is being proposed), the application can accept the re-invite request. If the proposed properties do not match the properties of the current session, the application must call gc_rejectmodifycall( ) to reject the re-invite request Receiving Remote RTP Transport Addresses The GC_PARM_BLK that is referenced by the METAEVENT that is associated with the GCEV_REQ_MODIFY_CALL event will include a parameter element that contains the remote RTP transport address. The RTP transport address is handled as a parameter element of the following type: IPSET_RTP_ADDRESS IPPARM_REMOTE value = RTP_ADDRESS data structure (see the reference page for New Channel Block Timer for NTT Protocol on page 74 for full details) SDP does not explicitly communicate RTCP port addresses, but these can be inferred from RTP addresses by the use of the plus one offset convention Rejecting a re-invite Request If an application determines that the received re-invite request is attempting to change the media properties of the current session or if it decides that it does not want to accept the request to change the RTP transport address, it simply calls gc_rejectmodifycall( ) to send a final response message with the specified 3xx 6xx reason code. When the remote UA acknowledges the rejection response, the library generates a GCEV_REJECT_MODIFY_CALL completion event and the session is unchanged, just as if a re-invite had never been issued. System Release FP1 for Windows Service Update August 22,

49 If the transmission of the rejection message fails for some reason, the library generates a GCEV_REJECT_MODIFY_CALL_FAIL event. In the case of such a failure, the re-invite transaction is still in progress, and the application should make another attempt to respond via gc_rejectmodifycall( ) or gc_acceptmodifycall( ) Accepting a re-invite Request If the received re-invite is not attempting to change the media properties of the current session and the application is willing to change the RTP transport address, the application calls gc_acceptmodifycall( ) to accept the re-invite request. When this function is called, the library sends a 200 OK response message and immediately changes the remote RTP address locally. There may be a slight audible artifact if the remote endpoint is not capable of streaming on the new RTP address until it has received and processed the 200 OK it received. Because the IP Call Control Library implementation in the System Release SU line does not support changing the media properties of the current media session, the application does not need to construct a GC_PARM_BLK to reference in the function call. In other words, the parmblkp parameter in the function call can be NULL to allow the library to send an SDP answer that matches the current session s properties in the 200 OK response. When the remote UA acknowledges the 200 OK response, the library generates a GCEV_ACCEPT_MODIFY_CALL event to notify the application that the re-invite transaction has completed successfully. If the transmission of the 200 OK message fails for some reason, the library generates a GCEV_ACCEPT_MODIFY_CALL_FAIL event. In the case of such a failure, the re-invite transaction is still in progress, and the application should make another attempt to respond to the re-invite via gc_rejectmodifycall( ) or gc_acceptmodifycall( ). Reference Information Reference pages for the new functions and data structure are provided below. System Release FP1 for Windows Service Update August 22,

50 gc_acceptmodifycall( ) accept proposed modification of call characteristics Name: int gc_acceptmodifycall (crn, parmblkp, mode) Inputs: CRN crn call reference number of call targeted for modification GC_PARM_BLK *parmblkp pointer to GC_PARM_BLK which contains attributes of call which are being accepted (optional) unsigned long mode completion mode (EV_ASYNC) Returns: 0 if successful <0 if unsuccessful Includes: gclib.h Category: Call Modification Mode: Asynchronous only Description The gc_acceptmodifycall( ) function is used to accept a request from the network or remote party to change one or more attributes of the current SIP dialog (call). This function initiates a 200 OK response code to an incoming re-invite request (an INVITE request on an established call), which has been indicated to the application as an unsolicited GCEV_REQ_MODIFY_CALL event on the respective call object. The metadata associated with this event references a GC_PARM_BLK which contains parameter elements that communicate the contents of the re-invite request to the application. The 200 OK response sent by this function indicates acceptance of the change(s) proposed in the re-invite request, which may be changes to one or more signaling attributes or attributes of the media session. Parameter crn parmblkp mode Description call reference number of call targeted for modification pointer to GC_PARM_BLK which contains call attributes that are being accepted (optional) completion mode; must be EV_ASYNC Receiving SDP Offer in Re-INVITE: In instances in which one or more media sessions are present in an SDP offer within the re- INVITE, those session proposals that are supported by the given media platform will be indicated within the associated parameter block passed within the GCEV_REQ_MODIFY_CALL event. Each proposed media type is indicated by a separate parameter within the parameter block using the following: GCSET_CHAN_CAPABILITY IPPARM_LOCAL_CAPABILITY value = IP_CAPABILITY structure System Release FP1 for Windows Service Update August 22,

51 For a symmetrical, full-duplex media proposal, at least two such parameters one for transmit and one for receive will be forwarded in the parameter block. For a half-duplex proposal or for an onhold request, it may be possible to receive only a single transmit or receive parameter with the given set of codec attributes. In addition to being informed of the media session proposals, the application is also informed of the remote RTP transport addresses. Each RTP port that is proposed in an SDP offer received within a re-invite (one per m= line) is indicated as a separate parameter within the parameter block associated with the GCEV_REQ_MODIFY_CALL event. These remote RTP address parameters are identified as follows: IPSET_RTP_ADDRESS IPPARM_REMOTE value = RTP_ADDR structure Because SDP does not communicate RTCP ports, only RTP ports are exchanged; the RTCP port will have the typical plus one offset from the RTP port. The application must retrieve and analyze the proposed capabilities to determine whether they are acceptable before calling gc_acceptmodifycall( ). Sending SDP Answer in 200OK: The application formulates the SDP answer by inserting the selected media session parameters (GCSET_CHAN_CAPABILITY / IPPARM_LOCAL_CAPABILITY) into the GC_PARM_BLK parameter block that it passes to gc_acceptmodifycall( ). A full-duplex connection requires two such parameters, one for each direction. Rather than specifying the capabilities to send in the SDP answer, the application can indicate that the codec preferences from the initial INVITE dialog should be used in formulating the SDP answer by passing a NULL pointer when calling gc_acceptmodifycall( ). If the capabilities to be used in the SDP answer whether specified by the application or derived from the initial INVITE do not match the capabilities that were contained in the SDP offer (both codec capability and direction), the library treats the situation as a rejection of the call modification request. A 488 Not Acceptable Here response is sent to the remote party to terminate the re- INVITE dialog, and a GCEV_REJECT_MODIFY_CALL event is generated to the application. The function returns either GC_SUCCESS or GC_ERROR depending upon the validity of the parameters. The function return does not indicate any status as to the success or failure of the sending of the response message. The final result of the attempt to send the response is provided in termination events. Termination Events GCEV_ ACCEPT_MODIFY_CALL Successful termination event. Indicates that the 200OK response was successfully sent, and an ACK reply has been received. It also indicates that the requested call attribute(s) has been modified locally. System Release FP1 for Windows Service Update August 22,

52 GCEV_ACCEPT_MODIFY_CALL_FAIL Unsuccessful termination event. Indicates that the signaling of the modification acceptance response has failed. This could be caused by a failure in the message transport, a failure in the attempt to change the call attribute, or the expiration of a response timer for the request. The re-invite transaction is still in progress and the application may make another attempt to respond via a new call to gc_acceptmodifycall( ) or gc_rejectmodifycall( ). No modifications to the existing media session are performed and the current state remains as it was prior to the incoming modification request. GCEV_REJECT_MODIFY_CALL Unsuccessful termination event. Indicates that the capabilities the application intended to signal in the SDP answer do not match any of the capabilities that were received in the SDP offer. This event implies that a 488 Not Acceptable Here final response was sent to the remote UA and that an ACK has been received, meaning that the re-invite dialog is terminated. No modifications to the existing media session are performed and the current state remains as it was prior to the incoming modification request. Cautions Only one modification transaction can be pending in a call at any given time. Until the pending re-invite has been accepted, rejected, or canceled, no additional re-invite can be sent by either party. Only one attempt to send a response to a re-invite request can be pending at a time. A response must fail (as indicated by a failure termination event) before a new response is attempted, otherwise the function call will fail. The GCEV_REQ_MODIFY_CALL event will only arrive when a call is connected. But if the call is dropped either locally via gc_dropcall( ) or remotely as indicated by a GCEV_DISCONNECTED event before a response is initiated via gc_acceptmodifycall( ), the request is invalid and the response can no longer be sent. The potential for glare situations exist with a CANCEL being received from the remote party as the local application intends to send 200OK. If the library receives the CANCEL before the gc_acceptmodifycall( ), the function call fails because the re-invite dialog is terminated and the application receives an informational GCEV_MODIFY_CALL_CANCEL event. Errors The function returns GC_ERROR if any of the parameters is invalid, if the call is not in the connected state, or if there is no re-invite request pending. Use the gc_errorinfo( ) function to retrieve further information. Upon receiving a GCEV_ACCEPT_MODIFY_FAIL event, use the gc_resultinfo( ) function to retrieve information about the failure event. See the Error Handling section in the Global Call API Programming Guide. All Global Call error codes are defined in the gcerr.h file while IP-specific error codes are specified in gcip_defs.h. On failure, no modifications to the existing dialog or media session are performed and the current state remains as it was prior to the attempting the modification request. System Release FP1 for Windows Service Update August 22,

53 Example... /* Dialogic Header Files */ #include <gcip.h> #include <gclib.h>... /* SRL event handler: */ for (;;) { if (-1!= sr_waitevt(500)) } process_event(); void process_event(void) { METAEVENT metaevent; GC_INFO t_info; /* Populate the metaevent structure */ if(gc_success!= gc_getmetaevent(&metaevent)) /* process GlobalCall events */ if ((metaevent.flags & GCME_GC_EVENT) == 0) return; return; switch (metaevent.evttype) {... case GCEV_REQ_MODIFY_CALL: /* request to modify call attribute */ { EXTENSIONEVTBLK *extblkp = metaevent.extevtdatap; GC_PARM_BLKP parm_blkp = &extblkp->parmblk; GC_PARM_BLKP replyparmblkp = NULL; GC_PARM_DATAP curparm = NULL; IP_CAPABILITY cap; RTP_ADDR rtp; unsigned char proposal_accepted = FALSE; while ((curparm = gc_util_next_parm(parm_blkp, curparm))!= NULL) { if ((curparm->set_id == GCSET_CHAN_CAPABILITY) && (curparm->parm_id == IPPARM_LOCAL_CAPABILITY)) { memcpy(&cap, curparm->value_buf, curparm->value_size); /* determine if capability is acceptable (logic not shown) */ if (iscapabilityacceptable(cap) == TRUE) { /* insert parameter with accepted capability in parameter block reply */ /* (logic not shown) */ insertcapintoreply(cap,replyparmblkp); proposal_accepted = TRUE; } } else if ((curparm->set_id == IPSET_SIP_MSGINFO) && (curparm->parm_id == IPPARM_SIP_HDR)) { /* parse SIP header and make appropriate updates (logic not shown) */ proposal_accepted = TRUE; } else if ((curparm->set_id == IPSET_RTP_ADDRESS) && (curparm->parm_id == IPPARM_REMOTE)) System Release FP1 for Windows Service Update August 22,

54 } { } memcpy(&rtp, curparm->value_buf, curparm->value_size); if (ismediarerouteacceptable(rtp) == TRUE) { /* update RTP transport addresses in GUI (logic not shown) */ updatertpgui(&rtp); proposal_accepted = TRUE; } /* if proposal is acceptable accept the request */ /* format accepted attributes (i.e. media types) in a parmblk (optional, */ /* NULL if none) */ if (proposal_accepted) { if (gc_acceptmodifycall(crn, replyparmblkp, EV_ASYNC) < 0) /* failure logic here*/ } else /* not acceptable so respond with SIP Client Error */ /* final response of 488 Not Acceptable Here */ if (gc_rejectmodifycall(crn, 488, EV_ASYNC) < 0) /* failure logic here */ } break; case GCEV_ACCEPT_MODIFY_CALL:... /* notify user of changed attribute */... break; case GCEV_ACCEPT_MODIFY_CALL_FAIL: /* process failure to change attribute */ if (gc_resultinfo(&metaevent, &t_info) < 0) { /* failure logic here */ } /* process information contained in t_info */ /* can optionally call gc_rejectmodifycall( ) to retry */... break; case GCEV_REJECT_MODIFY_CALL:... /* notify user of rejected attribute */... break; case GCEV_REJECT_MODIFY_CALL_FAIL: /* process failure to reject request */ if (gc_resultinfo(&metaevent, &t_info) < 0) { /* failure logic here */ } /* process information contained in t_info */ System Release FP1 for Windows Service Update August 22,

55 /* can optionally call gc_rejectmodifycall( ) to retry */... break;... } /* endof switch */ } /* endof process_event function */ See Also gc_rejectmodifycall( ) System Release FP1 for Windows Service Update August 22,

56 gc_rejectmodifycall( ) reject proposed modification of call attributes Name: int gc_rejectmodifycall (crn, reason, mode) Inputs: CRN crn call reference number of call targeted for modification unsigned long reason reason for rejecting request to change call attribute unsigned long mode completion mode (EV_ASYNC) Returns: 0 if successful <0 if unsuccessful Includes: gclib.h Category: Call Modification Mode: Asynchronous only Description The gc_rejectmodifycall( ) function is used to reject a request from the network or remote party to change an attribute of the current call. This function initiates a 3xx thorough 6xx response code to an incoming re-invite request, as indicated by an incoming GCEV_REQ_MODIFY_CALL event on the respective call object. The actual response code that is sent is specified by the reason parameter. Parameter crn reason mode Description call reference number of the call targeted for modification; must match the CRN contained in the GCEV_REQ_MODIFY_CALL event code number to indicate the reason for rejecting the request to modify call attributes must be EV_ASYNC The function returns either GC_SUCCESS or GC_ERROR depending upon the validity of the parameters. The function return does not indicate any status as to the success or failure of the sending of the rejection response message. The final result of sending the response is provided to the application in termination events. Termination Events GCEV_ REJECT_MODIFY_CALL Successful termination event. Indicates that rejection of the received re-invite request has completed successfully. This event implies that the specified 3xx through 6xx response was sent and that an ACK was received from the remote party. The requested call attribute modifications are not performed and the call state remains as it was prior to receiving the incoming re-invite request. GCEV_REJECT_MODIFY_CALL_FAIL Unsuccessful termination event. Indicates that the signaling of the rejection response failed. The re-invite transaction is still in progress and the application may make another attempt to System Release FP1 for Windows Service Update August 22,

57 Cautions respond via a new call to gc_acceptmodifycall( ) or gc_rejectmodifycall( ). No modifications to the existing media session are performed and the current state remains as it was prior to receiving the incoming re-invite request. Only one modification transaction can be pending in a call at any given time. Until the pending re-invite has been accepted, rejected, or canceled no additional re-invite can be sent by either party. A GCEV_REQ_MODIFY_CALL event can only arrive when a call is connected. But if the call is dropped either locally via gc_dropcall( ) or remotely as indicated by a GCEV_DISCONNECTED event before a response is initiated via gc_rejectmodifycall( ), the request is invalid and the response can no longer be sent. Only one attempt to respond to a re-invite request can be pending at a time. A response attempt must fail (as indicated by a failure termination event) before a new response is attempted, otherwise the function call will fail. Errors The function returns GC_ERROR if any of the parameters is invalid, if the call is not in the connected state, or if there is no pending re-invite request. Use the gc_errorinfo( ) function to retrieve further information. Upon receiving a GCEV_REJECT_MODIFY_CALL_FAIL event, use the gc_resultinfo( ) function to retrieve information about the event. See the Error Handling section in the Global Call API Programming Guide. All Global Call error codes are defined in the gcerr.h file while IP-specific error codes are specified in gcip_defs.h. On failure, no modifications to the existing dialog or media session are performed and the current state remains as it was prior to the incoming modification request. Example... /* Dialogic Header Files */ #include <gcip.h> #include <gclib.h>... /* SRL event handler: */ for (;;) { if (-1!= sr_waitevt(500)) process_event(); } void process_event(void) { METAEVENT metaevent; GC_INFO t_info; /* Populate the metaevent structure */ if(gc_success!= gc_getmetaevent(&metaevent)) return; System Release FP1 for Windows Service Update August 22,

58 /* process GlobalCall events */ if ((metaevent.flags & GCME_GC_EVENT) == 0) return; switch (metaevent.evttype) {... case GCEV_REQ_MODIFY_CALL: /* request to modify call attribute */ { EXTENSIONEVTBLK *extblkp = metaevent.extevtdatap; GC_PARM_BLKP parm_blkp = &extblkp->parmblk; GC_PARM_BLKP replyparmblkp = NULL; GC_PARM_DATAP curparm = NULL; IP_CAPABILITY cap; RTP_ADDR rtp; unsigned char proposal_accepted = FALSE; } while ((curparm = gc_util_next_parm(parm_blkp, curparm))!= NULL) { if ((curparm->set_id == GCSET_CHAN_CAPABILITY) && (curparm->parm_id == IPPARM_LOCAL_CAPABILITY)) { memcpy(&cap, curparm->value_buf, curparm->value_size); /* determine if capability is acceptable (logic not shown) */ if (iscapabilityacceptable(cap) == TRUE) { /* insert parameter with accepted capability in parameter block reply */ /* (logic not shown) */ insertcapintoreply(cap,replyparmblkp); proposal_accepted = TRUE; } else if ((curparm->set_id == IPSET_SIP_MSGINFO) && (curparm->parm_id == IPPARM_SIP_HDR)) { /* parse SIP header and make appropriate updates (logic not shown) */ proposal_accepted = TRUE; } else if ((curparm->set_id == IPSET_RTP_ADDRESS) && (curparm->parm_id == IPPARM_REMOTE)) { memcpy(&rtp, curparm->value_buf, curparm->value_size); if (ismediarerouteacceptable(rtp) == TRUE) { /* update RTP transport addresses in application (logic not shown) */ updatertpgui(&rtp); proposal_accepted = TRUE; } } } /* if proposal is acceptable accept the request */ /* format accepted attributes (i.e. media types) in a parmblk (optional, */ /* NULL if none) */ if (proposal_accepted) { if (gc_acceptmodifycall(crn, replyparmblkp, EV_ASYNC) < 0) /* failure logic here */ } else /* not acceptable so respond with SIP Client Error */ /* final response of 488 Not Acceptable Here */ if (gc_rejectmodifycall(crn, 488, EV_ASYNC) < 0) /* failure logic here */ break; System Release FP1 for Windows Service Update August 22,

59 case GCEV_ACCEPT_MODIFY_CALL:... /* notify user of changed attribute */... break; case GCEV_ACCEPT_MODIFY_CALL_FAIL: /* process failure to change attribute */ if (gc_resultinfo(&metaevent, &t_info) < 0) /* failure logic here */ /* process information contained in t_info */ /* can optionally call gc_rejectmodifycall( ) to retry */... break; case GCEV_REJECT_MODIFY_CALL:... /* notify user of rejected attribute */... break; case GCEV_REJECT_MODIFY_FAIL: /* process failure to reject request */ if (gc_resultinfo(&metaevent, &t_info) < 0) /* failure logic here */ /* process information contained in t_info */ /* can optionally call gc_rejectmodifycall( ) to retry */... break;... } /* endof switch */ } /* endof process_event function */ See Also gc_acceptmodifycall( ) System Release FP1 for Windows Service Update August 22,

60 RTP_ADDR RTP address typedef struct { int version unsigned short port; unsigned char ip_ver; union { unsigned int ipv4; unsigned int ipv6[4]; } u_ipaddr; } RTP_ADDR, *RTP_ADDRP; Description The RTP_ADDR data structure contains a complete RTP address, which includes both the port number and the IP address. The RTP_ADDR structure is used when retrieving the local and remote RTP addresses from the Global Call completion event when a call is connected. Field Descriptions The fields of the RTP_ADDR data structure are described as follows: version data structure version identification, for library use only port the port number used by an RTP stream ip_ver format of the IP address; currently, the only valid value is IPVER4 ipv4 the IP address used by an RTP stream, in IPv4 format ipv6[4] reserved for future use System Release FP1 for Windows Service Update August 22,

61 2.10 SIP Digest Authentication Support on DI0408LSAR2 Boards With the Service Update, SIP digest authentication is supported on Intel Dialogic DI0408LSAR2 Switching Boards. A new function and data structure are used with this feature. Following a description of the feature, a function reference page for gc_setauthenticationinfo( ) and a data structure reference page for IP_AUTHENTICATION are provided. Authentication is a process which allows a remote endpoint (a User Agent Server, or UAS) to verify the identity of a User Agent Client (UAC) that has sent a request to the UAS. If the UAS rejects a request with a 401 or 407 response, the UAC can re-send the request in a form that includes the sender s username and password to authenticate its identity. Once the UAC has authenticated its identity to the UAS, the UAS may require further verification that the UAC is authorized to make the original request, but that is a separate process from authentication. The standard type of SIP authentication is called digest authentication, which refers to the encryption method used for secure transmission of the user s secret password in the message, and is documented in IETF RFC To be able to respond automatically to authentication challenges, a UAC typically registers one or more triplets containing {realm, username, password}, where realm identifies the protected domain and the username and password identify the specific user. When a UAC receives a 401 or 407 response, it searches the triplets for a realm string that matches the one contained in the WWW-Authenticate or Proxy-Authenticate header field in the response. If it finds a matching realm string, it calculates a digest of the corresponding username and password strings and includes that result in the Authorization header field of the request it re-sends to the UAS. The Global Call implementation of digest authorization extends this model to use quadruplets of {realm, identity, username, password}, where the identity represents the user s URI in the realm. This extension allows applications to either register a single username and password for a given realm, or multiple username/password pairs that are each associated with a different identity URI. For quadruplets that have an empty string as the identity element, the Global Call library matching process uses the realm element only, exactly as if it were using a conventional authentication triplet instead of a quadruplet. If the identity element is a non-empty string, the library compares the identity string against the URI in the From header field of the 401/407 response. When the identity is non-empty, the library re-sends the request with the username/password digest only if both the realm and identity match the appropriate fields in the response message. As an example, if the following header fields are received in a 401 Unauthorized response: From: <sip:bob@example.com>;tag=0-13c4-4129f5f4-3bf3065a-7fc2... WWW-Authenticate: Digest realm="atlanta.com", domain="sip:ss1.carrier.com", qop="auth", nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="", stale=false, algorithm=md5 both of the following quadruplets would be considered to be matches: { atlanta.com, sip:bob@example.com, bob, password1 } System Release FP1 for Windows Service Update August 22,

62 { atlanta.com,, anonymous, } Applications that require multiple identities per realm set multiple quadruplets with different, non-empty identity strings. Such applications may also set a default username and password by setting a quadruplet with an empty identity string. This default username/password is only used when a 401/407 response does not match the identity in any of the triplets for the given realm and may be an anonymous authentication as shown in the preceding example. Applications that require only a single username/password pair per realm set only a single quadruplet with an empty identity string. In this case the application would not set any quadruplets that include non-empty identity strings. Applications that wish to use the authentication mechanism should configure the desired authentication quadruplets before calling any function that may send a SIP request. Any 401 or 407 response that is received for a request that was sent before authentication quadruplets were configured causes the call/request to be terminated and not re-sent by Global Call even if an appropriate authentication quadruplet was configured in the interim. The reason code for such a termination is IPEC_SIPReasonStatus401Unauthorized or IPEC_SIPReasonStatus407ProxyAuthenticationRequired. Digest authentication is supported for the following SIP message types: BYE INFO within a dialog INVITE and re-invite (subsequent INVITE within a dialog) NOTIFY within a dialog OPTIONS within a dialog REFER within a dialog REGISTER SUBSCRIBE Authentication is specifically not supported for the following SIP message types: INFO outside of a dialog NOTIFY outside of a dialog OPTIONS outside of a dialog Applications configure authentication quadruplets for virtual board by constructing a GC_PARM_BLK that contains a separate parameter element for each quadruplet, then calling the gc_setauthenticationinfo( ) function with that parameter block. Authentication quadruplets are removed in the same way but using a different parameter ID in the parameter element. The same function call can configure or remove any number of quadruplets for a given virtual board by including the appropriate combination of parameter elements in the GC_PARM_BLK. For a given function call, each parameter in the GC_PARM_BLK should have a unique realm/identity pair; if multiple parameter elements have the same realm/identity pair, only the last of these elements in the parameter block becomes effective. System Release FP1 for Windows Service Update August 22,

63 To add or modify an authentication quadruplet, the relevant set ID and parameter ID are: IPSET_CONFIG IPPARM_AUTHENTICATION_CONFIGURE parameter value is an IP_AUTHENTICATION data structure containing the desired quadruplet values. If the realm/identity pair is unique for the virtual board, a new quadruplet is added to the library s authentication database. If the realm/identity pair matches an existing quadruplet, the existing username/password pair is replaced by the new username/password pair. To remove an existing authentication quadruplet, the relevant set ID and parameter ID are: IPSET_CONFIG IPPARM_AUTHENTICATION_REMOVE parameter value is an IP_AUTHENTICATION data structure that identifies the realm and identity of the quadruplet to be removed. The username and password elements of this structure are ignored. If the specified realm and identity do not match those of an existing quadruplet, the function call produces an IPERR_UNAVAILABLE error. The elements of the authentication quadruplets are contained in an IP_AUTHENTICATION data structure, with each element having the following characteristics: realm a case-insensitive string that defines the protected domain name. This element must always contain a non-empty string. identity for a single-user realm, an empty string for a multi-user realm, either a case-insensitive string that identifies the user in the given realm, or else an empty string to allow specification of a default username/password pair. Non-empty strings must conform to the conventions for a SIP URI, and must begin with a sip: or sips: scheme. username a case-sensitive, null-terminated string that is the user s name. This element must always contain a non-empty string when configuring an authentication quadruplet. This value of this structure element is ignored when removing an authentication quadruplet. password a case-sensitive, null-terminated string that is the user s secret password in clear text. This element can optionally be an empty string, for example, if the quadruplet contains an anonymous username. This value of this structure element is ignored when removing an authentication quadruplet. When preparing to configure a quadruplet, the application should begin by initializing the IP_AUTHORIZATION structure with the INIT_IP_AUTHORIZATION( ) function, which configures the structure with the correct version number and with NULL string pointers for each element. The application should then populate each element with the desired string, System Release FP1 for Windows Service Update August 22,

64 including any empty strings. If any of the elements is left with a NULL pointer when passed to the function, the function call fails with IPERR_BAD_PARM. Note that the gc_setconfigdata( ) and gc_setuserinfo( ) functions cannot be used to configure authentication quadruplets. If a GC_PARM_BLK containing either of the authentication parameter IDs is passed to either of those functions, the function call fails with IPERR_BAD_PARM. Reference Information Reference pages for the new gc_setauthenticationinfo( ) function and IP_AUTHENTICATION data structure are provided below. System Release FP1 for Windows Service Update August 22,

65 gc_setauthenticationinfo( ) set IP authentication information Name: int gc_setauthenticationinfo(target_type, target_id, infoparmblkp) Inputs: int target_type type of target object (virtual board) long target_id target object ID GC_PARM_BLKP pointer to GC_PARM_BLK with user information infoparmblkp Returns: 0 if successful <0 if failure Includes: gclib.h gcerr.h Mode: synchronous Description The gc_setauthenticationinfo( ) function is used to configure or remove authentication information on an IPT virtual board. This is the only Global Call function that can be used to set this information; the generic Global Call functions gc_setconfigdata( ) and gc_setuserinfo( ) functions cannot be used for this IP-specific configuration operation. This function should be called before using any Global Call function that sends a SIP request that may provoke a 401/407 response. A 401/407 response to any SIP request that was sent before authentication is configured causes the request to be terminated (with the reason code IPEC_SIPReasonStatus401Unauthorized or IPEC_SIPReasonStatus407ProxyAuthenticationRequired), and Global Call will not attempt to resend the request. Parameter target_type target_id infoparmblklp Description specifies the type of target object; must be set to GCTGT_CCLIB_NETIF. specifies the virtual board ID that the authentication information applies to points to a GC_PARM_BLK structure that contains the authentication information. The parm block contains one or more parameters that use the IPSET_CONFIG set ID and IPPARM_AUTHENTICATION_CONFIGURE or IPPARM_AUTHENTICATION_REMOVE as the parameter ID. In either case, the parameter data is an IP_AUTHENTICATION data structure that contains an authentication quadruplet of {realm, identity, username, password}. An IPSET_CONFIG/IPPARM_AUTHENTICATION_CONFIGURE parameter in infoparmblkp adds a new authentication quadruplet to the Global Call database if the realm and identity strings in the IP_AUTHENTICATION structure are unique. If both the realm and identity strings match a quadruplet that already exists, the existing username and password are overwritten with the new strings. If the identity field in the IP_AUTHENTICATION structure is an empty string, the function will set the specified username and password as the defaults for the specified realm. System Release FP1 for Windows Service Update August 22,

66 An IPSET_CONFIG/IPPARM_AUTHENTICATION_REMOVE parameter in infoparmblkp removes the existing authentication quadruplet that matches the realm and identity strings that are specified in the IP_AUTHENTICATION structure. When removing a quadruplet, the username and password elements in the IP_AUTHENTICATION structure are ignored. Cautions The gc_setauthenticationinfo( ) function can only be called on a virtual board device. If the GC_PARM_BLK contains multiple parameter elements with the same realm/identity pair in their IP_AUTHENTICATION structures, all of those parameters are ignored except for the one that is last in the GC_PARM_BLK. Errors If this function returns <0 to indicate failure, use the gc_errorinfo( ) function to retrieve the reason for the error. See the Error Handling section in the Global Call API Programming Guide. All Global Call error codes are defined in the gcerr.h file. Possible errors include: IPERR_BAD_PARM returned if any of the string pointers in an IP_AUTHENTICATION structure is NULL or if there is any other invalid parameter IPERR_UNAVAILABLE returned when the realm/identity does not exist in the Global Call database when the application attempts to remove the quadruplet IPERR_UNSUPPORTED returned when the function is called on a line device or CRN rather than a virtual board Examples The following code example illustrates how to add or modify a digest authentication quadruplet. #include <gcip.h> #include <gclib.h> /* This example adds or modifies the quadruplet with realm "example.com" and * identity "sip:bob@example.com". If this realm/identity do not exist on this * virtual board, this quadruplet will be added. If this realm/identity exist * already, it will be override by this quadruplet. */ void configureauthquadruplet (long boarddev) { GC_PARM_BLK *parmblkp = NULL; char realm[] = "example.com"; char identity[] = "sip:bob@example.com"; char username[] = "bob"; char password [] = "password1"; IP_AUTHENTICATION authentication; INIT_IP_AUTHENTICATION (&authentication); authentication.realm = realm; authentication.identity = identity; authentication.username = username; authentication.password = password; System Release FP1 for Windows Service Update August 22,

67 gc_util_insert_parm_ref(&parmblkp, IPSET_CONFIG, IPPARM_AUTHENTICATION_CONFIGURE, (unsigned char)(sizeof(ip_authentication)), &authentication); gc_setauthenticationinfo(gctgt_cclib_netif, boarddev, parmblkp); } gc_util_delete_parm_blk(parmblkp); The following code example illustrates how to remove a digest authentication quadruplet. #include <gcip.h> #include <gclib.h> /* This example deletes the quadruplet with realm "example.com" and * identity "sip:bob@example.com". */ void removeauthquadruplet (long boarddev) { GC_PARM_BLK *parmblkp = NULL; char realm[] = "example.com"; char identity[] = "sip:bob@example.com"; IP_AUTHENTICATION authentication; INIT_IP_AUTHENTICATION (&authentication); authentication.realm = realm; authentication.identity = identity; gc_util_insert_parm_ref(&parmblkp, IPSET_CONFIG, IPPARM_AUTHENTICATION_REMOVE, (unsigned char)(sizeof(ip_authentication)), &authentication); gc_setauthenticationinfo(gctgt_cclib_netif, boarddev, parmblkp); } gc_util_delete_parm_blk(parmblkp); See Also None. System Release FP1 for Windows Service Update August 22,

68 IP_AUTHENTICATION SIP digest authentication data typedef struct { unsigned short version; char* realm; char* identity; char* username; char* password; } IP_AUTHENTICATION; Description The IP_AUTHENTICATION data structure is used when setting or removing SIP authentication quadruplets. Applications should use the INIT_IP_AUTHENTICATION( ) function to initialize the structure with the correct version number and void pointers for each of the strings before setting the appropriate values. Field Descriptions The fields of the IP_AUTHENTICATION data structure are described as follows: version The version number of the data structure. The correct value is set by the INIT_IP_AUTHENTICATION( ) initialization function and should not be overridden. realm A null-terminated string that defines the protected domain. This string is case-insensitive and must always be supplied. identity A null-terminated string that allows applications to optionally specify different username/ password pairs for different identities in the same realm. The identity is a URI and must conform to URI syntax, including starting with the scheme (namely sip: or sips: ). If only one username and password applies to a given realm or if setting a default username and password for a multi-identity realm, use an empty string ( ) for this field. This field is caseinsensitive. username A null-terminated string providing the user s name in the specified realm. This field is casesensitive. This field must always contain a non-empty string when the structure is associated with an IPPARM_AUTHENTICATION_CONFIGURE parameter. This field is ignored when the structure is associated with an IPPARM_AUTHENTICATION_REMOVE parameter. password A null-terminated string providing password associated with the user s name in the specified realm. This field is case-sensitive. This field is ignored when the structure is associated with an IPPARM_AUTHENTICATION_REMOVE parameter. System Release FP1 for Windows Service Update August 22,

69 2.11 Early Media Support on DM/IP Boards With the Service Update, early media is now supported on Intel NetStructure DM/IP boards that use the host-based IP call control stack. Early media refers to media (e.g., audio) transfer before a particular session is accepted by the called party. Note: When enabling early media, be aware of the following limitation (this limitation will be lifted in a future release). When a Global Call application is running on a DM/IP board with early media enabled (through.config/.fcd file), any call that results in the selection of asymmetric coders will fail to connect and will result in a GCEV_TASKFAIL event. Asymmetric coders are defined as different coders/frame rates for transmit and receive, for example, G ms for transmit and G ms for receive. The probability of symmetric coder selection during H.323 calls can be improved by using Fast Start mode, and specifying only the smallest frame rate supported for each coder specified. To enable early media on a board level, add the following PrmEarlyMedia parameter content in the CONFIG file (.config) that corresponds to the PCD file in use on your board: [0x40] SetParm=0x400a,1! PrmEarlyMedia (0=Disabled, 1=Enabled) After the parameter is added, use the fcdgen utility to generate an updated FCD file. Then start system services on the board. See the DM3 Configuration File Reference for more information on CONFIG files, PCD files, and the fcdgen utility. Note: Early media support can only be enabled/disabled at the board level via the CONFIG file. Early media support cannot be set at runtime and cannot be set at the channel level Support for NULL IP Address on Media Session Start Intel NetStructure DM/IP boards now support the start of a media RTP/RTCP session with a NULL address (a IP address), received in an OLCAck, faststart element, or SDP descriptor in SIP. Previously this would have been flagged as an error. This feature is supported for H.323 and SIP protocols. In pseudo-code: ipm_startmedia() -> coder, UnicastMode=Full-Duplex, RTCP Port=1, Remote IP Address= Anytime a transmit Unicast mode is specified (either Full-Duplex or Transmit Only) and a IP address is specified, the DM/IP board firmware will temporarily suppress the transmittal of any RTP packets, until a valid remote media address is provided in a subsequent request. System Release FP1 for Windows Service Update August 22,

70 2.13 New Bitmask Value for dx_stopch( ) Mode Parameter for Synchronous Operation With the Service Update, the dx_stopch( ) function has a new bitmask value added for the mode parameter. This is for applications that require dx_stopch( ), in synchronous mode, to return after the reception of the TDX_ termination event (e.g., TDX_RECORD or TDX_PLAY). The new mode value, DX_WAITFORTERMEVENT_ENABLE, is supported only on Springware JCT boards, and is only applicable with dx_rec( ) and dx_play( ) (record and play) functions. The purpose of the dx_stopch( ) function is to force termination of currently active I/O functions on a channel. Currently, in synchronous mode, dx_stopch( ) does not wait for the actual termination event to be posted before returning. This can mislead applications into assuming that the termination event has indeed been posted. With the new DX_WAITFORTERMEVENT_ENABLE mode bitmask, dx_stopch( ) will block until a termination event is posted. DX_WAITFORTERMEVENT_ENABLE can be ORed with EV_SYNC, for example: dx_stopch(chdev, EV_SYNC DX_WAITFORTERMEVENT_ENABLE) If ORed with EV_ASYNC, DX_WAITFORTERMEVENT_ENABLE is ignored. Note that a time-out of 14 seconds is set when the DX_WAITFORTERMEVENT_ENABLE mode is used. If no termination event is posted in 14 seconds, dx_stopch( ) returns with -1 and error time-out. The time-out period of 14 seconds is not configurable. For more information about the dx_stopch( ) function and the Voice API, see the following documents: Voice Software Reference: Features Guide for Windows Voice Software Reference: Programmer s Guide for Windows 2.14 PBX Integration Support for Mitel Superset 4150 Telephone With the Service Update, PBX integration boards now support the Mitel* Superset* 4150 telephone when used in conjunction with Mitel Superswitch* SX-200 or SX-2000 PBX systems. The boards that support this feature are: Intel Dialogic D/42JCT-U Intel Dialogic D/82JCT-U System Release FP1 for Windows Service Update August 22,

71 Feature Description The level of support for the Mitel Superset 4150 is similar to that provided for the Mitel Superset 430. In the PBX Integration Board User Guide, support for the Superset 430 is described in the Mitel Superswitch PBXs section. The information provided below supplements the Superset 430 information with information specific to Superset Mitel Superswitch The complete list of Mitel Superset phones supported by the PBX integration boards and the Mitel phones that can be used with each Mitel Superswitch PBX are given in the following table. Mitel Phone Mitel SuperSwitch PBX SX-50 SX-200 SX-2000 Mitel Superset 420 Yes Yes, but not preferred Yes, but not preferred Mitel Superset 430 No Yes, preferred Yes, preferred Mitel Superset 4150 No Yes Yes Note: Mitel Superset 4150 phone emulation should be used with SX-200 and SX-2000 PBXs. The Message Waiting Indicator (MWI) feature access code must be programmed in specific personal keys in the Mitel Superset 4150 emulation for the PBX integration board to function successfully. Phone-Side Programming for Superset 4150 SX-200 and SX2000 PBXs and Mitel Superset 4150 Emulation: Personal Key 10 should store the MWI OFF feature access code and Personal Key 11 should store the MWI ON feature access code (see figure below). The procedure for configuring these settings is the same as that described for the Superset 430 phone. See the PBX Integration Board User s Guide. Using the PBX Integration Board to Emulate a Superset 4150 Phone The PBX integration board emulates functions available to the Superset 4150 phone. This emulation can be used with Superswitch SX-200 and SX-2000 PBXs. The Superset 4150 phone is shown in following figure: System Release FP1 for Windows Service Update August 22,

72 Function Keys (Q, N, S, P) Display (Soft) Keys (0 to 5) Display Area Message Lamp Q N S P ABC DEF GHI JKL MNO PQRS TUV WXYZ * 0 # Not Used Personal Keys (0 to 11) Line Indicators (on Personal Keys 0 to 11) Programmable Personal Keys for Superset 4150 Emulation As shown in the figure, there are 14 Personal Keys on the Superset 4150 telephone, two of which are not used. Some of these keys are configured when the PBX is programmed to select preassigned lines. Keys that are not configured can be defined by the user (using the telephone set or the PBX integration board) as speed dial or Feature Keys. There is an LCD line indicator integrated into each Feature Key. The states that the LCD line indicators can take are the same as those for the Superset 430 phone as described in the PBX Integration Board User s Guide. Also, the PBX integration board can determine the status of an LCD line indicator by using the d42_indicators( ) function. This function places the LCD line indicator data (12 bytes) in an application buffer. Bytes 0-11 contain the indicator status for Feature Keys 0 to 11 respectively. The format of this data is the same as that for the Superset 430 as described in the PBX Integration Board User s Guide. Function Keys on the Superset 4150 The PBX integration board can simulate the pressing of any function key using the dx_dial( ) function. Each function key on the Superset 4150 telephone is assigned a dial string sequence (see the following table). By using the dx_dial( ) function and the System Release FP1 for Windows Service Update August 22,

73 appropriate dial string, the PBX integration board can dial any of its function keys. See the PBX Integration Board Software Reference for more information about dialing programmable keys. Dial String <ESC>KM <ESC>KN <ESC>KO <ESC>KP <ESC>KQ <ESC>KR <ESC>KS <ESC>KT <ESC>KU <ESC>KV Key Description Not used SuperKey Not used Microphone Hold Not used Speaker Not used Not used Not used Display (Soft) Keys on the Superset 4150 The display keys (also known as soft keys) on the Superset 4150 are similar to the display keys on the Superset 430. See the table titled Mitel Superset 430 Direct Key Dialing Strings for Display Keys in the PBX Integration Board User s Guide. Alphanumeric Display on the Superset 4150 The alphanumeric display on the Superset 4150 is similar to the display on the Superset 430. To retrieve the information on the Superset 4150 display, the PBX integration board can use the d42_displayex( ) function with a buffer size of 160 bytes. See the PBX Integration Board User s Guide. Direct Dial Key Sequence Identifiers The following figure shows the identifiers that are used in direct key dialing sequences to identify a specific key. The actual direct dial key sequences are the same as those for the Superset 430 phone as described in the PBX Integration Software Reference. System Release FP1 for Windows Service Update August 22,

74 Function Keys (Q, N, S, P) Display (Soft) Keys (0 to 5) Display Area Message Lamp Q N S P ABC DEF GHI JKL MNO PQRS TUV WXYZ * 0 # Not Used Personal Keys (0 to 11) Line Indicators (on Personal Keys 0 to 11) Retrieving the Switch Type The d42_getparm( ) function can be used to retrieve the switch type using the D4BD_GETSWITCHTTYPE parameter which uses a value of PBX_SX2 to identify a Mitel Superswitch SX-200 or SX This applies to both Superset 430 and Superset 4150 telephone emulations. See the d42_getparm( ) function reference page in the PBX Integration Software Reference for more information New Channel Block Timer for NTT Protocol A new channel block timer parameter has been added to the ntt.prm file (for Springware boards) and to the CONFIG (.config) file (for DM3 boards) for the ISDN NTT protocol. The purpose of this timer is to block the first response (i.e., PROCEEDING, ALERTING, or CONNECT) to an incoming call (i.e., SETUP message) on a channel, if that same channel has just recently had a previous call released. The channel is blocked for the amount of time specified by this new channel block timer parameter. System Release FP1 for Windows Service Update August 22,

75 This feature is supported on the following boards: Springware boards Intel Dialogic D/240JCT-T1, D/480JCT-1T1, and D/480JCT-2T1 Combined Media Boards Intel Dialogic D/240PCI-T1, D/240SC-T1, and D/240SC-2T1 Voice Boards DM3 boards Intel NetStructure DMV/480A-2T1 Intel NetStructure DM/V960A-4T Feature Description On some NTT switches, if a call initiated from the switch is responded to with a PROCEEDING message too quickly (i.e., response to the SETUP message) on a recently released channel, the switch rejects the call with ISDN cause 44 (requested circuit/channel not available) and sends an error message (voice message) to the subscriber. This also applies to other first response messages like ALERTING and CONNECT. For example, the following figure gives an example of a problematical sequence where ISDN cause 44 is returned when channel 12 is reassigned in 31 milliseconds. System Release FP1 for Windows Service Update August 22,

76 T1 Trunk Problematical Sequence NTT ISDN Network SetUp (CRN=104) Preferred/Channel Number=12 Call Proc. (CRN=104) Exclusive/Channel Number=12 Alerting (CRN=104) Connected State Disconnect (CRN=104) Channel Number=12 Release (CRN=104) Channel Number=12 Release Complete (CRN=104) Channel Number=12 4:11:23:496 SetUp (CRN=117) Call Proc. (CRN=117) Preferred/Channel Number=13 Exclusive/Channel Number=12 (Same Channel That Was Just Released) 31 ms - not enough time, so switch rejects the call with ISDN cause 44 4:11:23:527 Alerting (CRN=117) Release Complete (CRN=117) Cause 44: Requested Circuit/Channel Not Available Status (CRN=117) Release (CRN=117) For compatibility with these NTT switches, the new channel block timer can be used in order to avoid sending the first response to the B channel that was just released by the previous call. The channel block time is the amount of time to hold off the first response message from being sent out too quickly to the network on a recently released channel. The amount of channel block time that the switches typically need is in the range of second. This helps to prevent the call rejection described above. Since not all switches operate this way, setting the channel block timer is optional. System Release FP1 for Windows Service Update August 22,

77 When enabled, the channel block timer is started upon the sending or receiving of the final clearing message on a particular channel (clearing message could be RELEASE or RELEASE COMPLETE), and that channel will not be able to accept another call until this timer has expired. If a call is received on a channel while the channel block timer is still running, and if the Channel ID IE is set to Preferred or Any Channel, then the call is simply routed to the next available B channel. However, if the Channel ID IE is set to Exclusive, or if no B channel on the board is available for which the block timer condition is met, then the call is rejected with ISDN cause New Parameter Springware Boards The new parameter in the ntt.prm file to set the channel block timer is: ;--- The NTT Channel Block Delay value. LSB is 10 ms. ;--- This is a 2 byte value, but the maximum that will be considered is 255, or 0xFFH. ;--- If a value more than 255 is specified then 255 will be considered. ; ;--- The default value is 00H. 003C 00 The channel block delay time (003C parameter) can be set from 0 to 255, where the values are increments of 10 milliseconds. For example, a setting of 255 = 255 x 10 milliseconds or 2.55 seconds of delay. Parameter values must be entered in hexadecimal, so 255 would be entered as FF. Typical values for this timer have been found to lie in the range of second. Any non-zero value enables the channel blocking feature for the specified time. The default value for the parameter is zero, which disables the channel blocking feature. The ntt.prm file is installed in the data subdirectory of the Intel Dialogic home directory (normally C:\Program Files\Dialogic\data). For further information about board configuration, see the Installation and Configuration Guide on the online bookshelf for System Release Feature Pack 1 for Windows. DM3 Boards The new parameter is called ChanBlockDelay and is in the [CCS.x] section of the CONFIG file. The parameter is set on a trunk basis, where x equals the trunk number 1, 2, 3, or 4. Each trunk can have a different value. The parameter takes a value from 0 to 255; the parameter times 10 is the milliseconds of channel block time. The value settings are as follows: Any non-zero value enables the channel blocking feature for the specified time. Default value for the parameter is zero, which disables the channel blocking feature. System Release FP1 for Windows Service Update August 22,

78 Any value above 255 is invalid and the firmware defaults to the maximum allowed value, which is 255. Note: You must add the new parameter to the CONFIG file and then use the fcdgen utility to generate an updated FCD (.fcd) file. For more detailed information about modifying the CONFIG file and then running the fcdgen utility to generate a new FCD file, refer to the DM3 Configuration File Reference. The following is an example of a CONFIG file. You add the line, which is highlighted here in bold, under each [CCS.x] section for which the feature is to be enabled. In the example, the feature is disabled for trunk 1 (zero is also the default value), and enabled and set to 1 second for trunk 2. [CCS.1]! Q.931 Timer Values in milliseconds Setparm=0x0b,4000! Q.931 timer 303. Default=4000 msec. Setparm=0x0d,4000! Q.931 timer 305. Default=4000 msec. Setparm=0x0e,4000! Q.931 timer 308. Default=4000 msec. Setparm=0x0f,10000! Q.931 timer 310. Default=10000 msec. Setparm=0x10,4000! Q.931 timer 313. Default=4000 msec. Setparm=0x15,1000! TEI retry timer Default=1000 msec. Setparm=0x16,900! TEI state 4 min stability time. Default=900 msec. Setparm=0x13,0! Symmetrical C.E. protocol. 0=disable 1=enable Setparm=0x17,0! Network Mode. 1=NETWORK 0=USER Setparm=0x9,0! 0=disabled, 1=enable Layer 2 access.! When Layer 2 access is enabled call control is no longer supported for the channels on this line. Setparm=0x20, 0! ChanBlockDelay is disabled. This is also the default value. [CCS.2]! Q.931 Timer Values in milliseconds Setparm=0x0b,4000! Q.931 timer 303. Default=4000 msec. Setparm=0x0d,4000! Q.931 timer 305. Default=4000 msec. Setparm=0x0e,4000! Q.931 timer 308. Default=4000 msec. Setparm=0x0f,10000! Q.931 timer 310. Default=10000 msec. Setparm=0x10,4000! Q.931 timer 313. Default=4000 msec. Setparm=0x15,1000! TEI retry timer Default=1000 msec. Setparm=0x16,900! TEI state 4 min stability time. Default=900 msec. Setparm=0x13,0! Symmetrical C.E. protocol. 0=disable 1=enable Setparm=0x17,0! Network Mode. 1=NETWORK 0=USER Setparm=0x9,0! 0=disabled, 1=enable Layer 2 access.! When Layer 2 access is enabled call control is no longer supported for the channels on this line. Setparm=0x20, 100! ChanBlockDelay is set to 1000 milliseconds (100 x 10). Max value is 255, therefore max ChanBlockDelay is 2550 milliseconds. For further information about board configuration, see the Intel Dialogic System Release Feature Pack 1 for Windows Installation and Configuration Guide and the DM3 Configuration File Reference on the online bookshelf for System Release Feature Pack 1 for Windows. System Release FP1 for Windows Service Update August 22,

79 2.16 Implementation of ROLM Call Waiting LED When using Intel Dialogic D/42JCT-U and D/82JCT-U PBX integration boards and PBX Integration software, the d42_indicators( ) function can now return the LED status of the Call Waiting LED for the ROLMphone 400. The following table and figure show the ROLMphone 400 direct key dialing strings for feature keys and the bytes containing the indicator status. This supersedes the information that is currently in the PBX Integration Board User s Guide and PBX Integration Software Reference for the Siemens ROLM PBX. Table 1. ROLMphone 400 Direct Key Dialing Strings for Feature Keys Byte Key Description Dial String 00 Feature Key 09 - LINE <ESC>KA 01 Feature Key 08 <ESC>KB 02 Feature Key 07 <ESC>KC 03 Feature Key 06 - CLEAR (flash) <ESC>KD 04 Feature Key 05 <ESC>KE 05 Feature Key 04 <ESC>KF 06 Feature Key 03 <ESC>KG 07 Feature Key 02 <ESC>KH 08 Feature Key 01 - MAILBOX <ESC>KI 09 Feature Key 15 <ESC>KJ 10 Feature Key 14 <ESC>KK 11 Feature Key 13 <ESC>KL 12 Feature Key 12 <ESC>KM 13 Feature Key 11 <ESC>KN 14 Feature Key 20 - PROG (program) <ESC>KO 15 Feature Key 19 <ESC>KP 16 Feature Key 18 <ESC>KQ 17 Feature Key 17 <ESC>KR 18 Feature Key 16 <ESC>KS 19 Feature Key 25 <ESC>KT 20 Feature Key 24 <ESC>KU 21 Feature Key 23 <ESC>KV 22 Feature Key 22 <ESC>KW 23 Feature Key 21 <ESC>KX 24 Feature Key 35 <ESC>KY 25 Feature Key 34 <ESC>KZ System Release FP1 for Windows Service Update August 22,

80 Table 1. ROLMphone 400 Direct Key Dialing Strings for Feature Keys (Continued) Byte Key Description Dial String 26 Feature Key 33 <ESC>Ka 27 Feature Key 32 <ESC>Kb 28 Feature Key 31 <ESC>Kc 29 Feature Key 29 <ESC>Kd 30 Feature Key 28 <ESC>Ke 31 Feature Key 27 <ESC>Kf 32 Feature Key 26 <ESC>Kg 33 Feature Key 37 - MWCTR (Message Waiting Control) <ESC>Kh 34 Feature Key 36 - SPEAKER <ESC>Ki Feature Key 40 - Volume Down Feature Key 39 - Volume Up Feature Key 10 Feature Key 30 Feature Key 38 - XFER <ESC>Kj <ESC>Kk <ESC>Kl <ESC>Km <ESC>Kn 35 Call Waiting LED Feature Key 09 Feature Key 08 Feature Key 07 Feature Key 06 Feature Key 05 Feature Key 04 Feature Key 03 Feature Key 02 Feature Key 01 Feature Key 15 Feature Key 14 Feature Key 13 Feature Key 12 Feature Key 11 Feature Key 20 Feature Key 19 Feature Key 18 Feature Key 17 Feature Key 16 Feature Key 25 Feature Key 24 Feature Key 23 Feature Key 22 Feature Key 21 Data Byte Data Byte xx xx xx xx xx xx xx xx xx xx xx xx Feature Key 35 Feature Key 34 Feature Key 33 Feature Key 32 Feature Key 31 Feature Key 29 Feature Key 28 Feature Key 27 Feature Key 26 Feature Key 37 Feature Key 36 Call Waiting Light 2.17 Optional Use of Sharing of Timeslot (SOT) Algorithm The Sharing of Timeslot (SOT) algorithm for DM3 boards maximizes the efficiency of the internal timeslots used for external transmit reference, allowing a full 120 channel density for such features as continuous speech processing and transaction record. The SOT algorithm is enabled by default, regardless of whether continuous speech processing or System Release FP1 for Windows Service Update August 22,

81 transaction record functionality is needed. Its use places certain constraints on an application for performing listen/unlisten functions in a specific sequence. For increased flexibility in application design, it is now possible to disable the SOT algorithm by adding a new parameter, QKERNEL_DISABLE_TIMESLOT_SHARING, to the board s.config file, and then using fcdgen to generate an updated.fcd file. Note: The SOT algorithm is now supported on the DM/V600-4E1 board with media load ml1_4x2_r2mf. For more detailed information about the SOT algorithm, guidelines for enabling or disabling the algorithm, and supported boards and media loads, see the technical note titled Disabling the Sharing of Timeslot (SOT) Algorithm via DM3 config file change on the Intel Telecom Support Resources website at ISDN Network Side Conformance to Network Protocol Standards ITU-T Q921 and Q931 Previously, network-side firmware was provided for back-to-back testing purposes only and was not fully qualified for operation in a deployment environment. This feature provides conformance to network protocol standards ITU-T Q921 and Q931, allowing the Intel NetStructure DMV and DMV-A series of boards to be deployed in network-side mode. Both T1 and E1 and all media loads are supported. Note: The symmetrical command response protocol (SYMMETRICAL_LINK), which allows user-to-user or network-to-network protocol configurations, is still supported for back-toback testing. However, you must disable symmetrical data link operations before enabling network-side mode. Refer to the DM3 Configuration File Reference for details. Following are the details about the standards involved: Network side T1 has been tested against protocol conformance suites compliant with the ITU-T Q921 and Q931 standards and Telcordia TR-NWT specifications. The Abstract Test Suite used is based on the Telcordia TR-NWT specifications. Network side E1 has been tested against protocol conformance suites compliant with ITU-T Q921 and Q931 standards. The Abstract Test Suite used is compliant with ETSI standard ETS and ETS The procedure for setting the parameter to network side has not changed. The CCS_PROTOCOL_MODE parameter sets the network user-side protocol. User-side protocol is also known as TE (terminal emulation) protocol and network-side protocol is also known as NT (network termination) protocol. Since the parameter is set by default to user side, you must change the CCS_PROTOCOL_MODE parameter value from 0 (User) to 1 (Network) in the.config file as described in the DM3 Configuration File Reference. System Release FP1 for Windows Service Update August 22,

82 2.19 Intel Telecom Subsystem Summary Tool (its_sysinfo) The Intel Telecom Subsystem Summary Tool (its_sysinfo) provides a simple way to collect information about systems built using Intel telecom products. The its_sysinfo tool collects data from the system on which you execute it and provides you with information about the system environment: the operating system, computer architecture, Intel Dialogic System Release, and operational logs. The its_sysinfo tool also enables you to collect baseline information about the system for quick review of configuration issues when determining system configuration consistency. This information is collected in a file, compressed, and archived as part of the complete system information collection in an archive file named its_sysinfo.zip (or a name you specify). If the installed system is configured in such a way that the baseline information is not available, the its_sysinfo tool will indicate No Information Available. The its_sysinfo tool can be executed from the command line (including programmatically) or via a graphical user interface (GUI). When executed from the command line, once started, the its_sysinfo tool runs without user intervention. In addition to the standard information captured by the its_sysinfo tool, you can manually add files to the archive that is created by its_sysinfo.exe after you run the tool so you can preserve additional information that might help with resolving issues. The following information is collected under its_sysinfo.htm, which is one of the files that is added to the archive: Installed Boards its_sysinfo collects information about devices detected in Intel Telecom Subsystem configurations and startup. DCM Board Configuration its_sysinfo captures the stored values used by the DCM configuration tool for Intel Telecom Subsystem configurations and startup. Environment Variables its_sysinfo collects information about the operating system environment variables. Firmware Files its_sysinfo collects information about the files listing all firmware file names and version numbers. FCD Files its_sysinfo collects information about the.fcd files used by the DCM configuration tool for Intel Telecom Subsystem configurations and startup. PCD Files its_sysinfo collects information about the.pcd files used by the DCM configuration tool for Intel Telecom Subsystem configurations and startup. Config files its_sysinfo collects information about the.config files used by the DCM configuration tool for Intel Telecom Subsystem configurations and startup. Build Information its_sysinfo collects information about the contents of the bildinfo.ini file used for the installed Intel Telecom Software Subsystem. The bildinfo.ini file contains information about what is in the build of the software. Event Viewer Data its_sysinfo collects information about the last events reported to the operating system and to the event logger from the Intel Telecom Subsystem. System Release FP1 for Windows Service Update August 22,

83 Memory and Processor its_sysinfo collects information about the platform s available and used memory and CPU type and number as of the time you executed the its_sysinfo tool. Operating System its_sysinfo collects information about the operating system s version, service pack, and language. Global Call Configuration its_sysinfo collects information about the Global Call PDK subsystem configuration, which is contained in the pdk.cfg file. This file specifies the Global Call protocol modules and the country dependent parameter settings downloaded to each device. ISA/PCI Board Memory Dump its_sysinfo collects firmware assert information (source file, line number, etc.) as well as other data like firmware version and memory usage. The its_sysinfo tool also checks for the following and, if found, adds them to the archive: Operations, Administration, and Maintenance (OA&M) files in %INTEL_DIALOGIC_DIR%\log Internet Protocol (IP) files in C:\WINDOWS\System32 DebugAngel files in %INTEL_DIALOGIC_DIR%\log Dr. Watson dump and log files Runtime Trace Facility (RTF) files Note: Some log files may not be found by the its_sysinfo tool, depending on their storage location. If desired, you can manually add files to the archive that is created by its_sysinfo.exe after you run the tool. Running the its_sysinfo Tool from the GUI Follow this procedure to use its_sysinfo to collect system data. 1. Start the its_sysinfo tool by clicking on its_sysinfo.exe in %INTEL_DIALOGIC_DIR%\bin. 2. When the Intel Telecom System & Diagnostic Information dialog box appears, the default archive file where the information will be collected is displayed. If desired, you can specify a different archive file. 3. Click the Start Gathering button to begin collecting information. 4. A pop-up window displaying Finished Data Collection will appear to indicate completion of its_sysinfo.exe execution. Click the OK button and then click the Close button on the Intel Telecom System & Diagnostic Information dialog box. The archive file is in the location specified in the tool. 5. Use any standard compression/un-compression tool (such as WinZip*) to extract and review the data. System Release FP1 for Windows Service Update August 22,

84 Running the its_sysinfo Tool from the Command Line The syntax for running its_sysinfo from the command line is: its_sysinfo [filename -?] filename specifies the name for the archive file. If you do not specify a filename, then the information gets compressed in a zip file with the default name its_sysinfo.zip in the current directory from which its_sysinfo was started.? displays the command syntax. Any unrecognized command line argument displays usage information to the standard error output defined by the operating system Speed Control on DM3 Boards Using 6 khz Coders This release supports speed control on DM3 boards using the following coders: 24 kbps OKI ADPCM (6 khz 4-bit) 48 kbps G.711 A-law PCM (6 khz 8-bit) 48 kbps G.711 mu-law PCM (6 khz 8-bit) This feature is not currently documented in the Release Guide or in the Compatibility Guide in the System Release Feature Pack 1 for Windows bookshelf. Previously, speed control was available on DM3 boards only when using 8 khz coders. This feature is supported only on the following boards: DM/V2400A-cPCI DM/V2400A-PCI DM/V960A-4T1-PCI DM/V1200A-4E1-PCI DM/V480A-2T1-PCI DM/V600A-2E1-PCI Note: If an attempt is made to adjust speed on an unsupported board, the firmware will ignore the request and play will continue at normal speed. Users can adjust speed via DTMF or programmatically using the dx_adjsv( ) API. For further information about speed control capabilities with the Voice API, see the Voice Software Reference: Features Guide for Windows. For information about specific functions, see the Voice Software Reference: Programmer s Guide for Windows and the Compatibility Guide for the Dialogic R4 API on DM3 Products. System Release FP1 for Windows Service Update August 22,

85 2.21 DPNSS Support on D/300JCT-E1, D/600JCT-1E1, and D/600JCT-2E1 Boards The DPNSS ISDN protocol is now supported on the D/300JCT-E1, D/600JCT-1E1, and D/600JCT-2E1 boards. Previously, DPNSS was only supported on D/300SC-E1, D/300SC-2E1, D/600SC-2E1, D/300PCI-E1, DTI/300SC, DTI/301SC, DTI/600SC, and DTI/601SC Springware boards. The new firmware file for DPNSS support is spisdpns.fwl. To configure the board to use the DPNSS protocol, set ISDNProtocol=DPNSS in the configuration manager (DCM) IP Support on DI0408LSAR2 Boards This release supports Voice over IP (VoIP) capability on Intel Dialogic DI0408LSAR2 Switching Boards. This capability allows a VoIP call to be connected to the CT Bus. Using the DI0408LSAR2 board equipped with a PSTN network front end, you can build a singleboard IP-to-PSTN gateway application. The IP resource implementation of the DI0408LSAR2 is equivalent to that developed for the Intel NetStructure DM/IP Series as defined in the following documents located in your System Release Feature Pack 1 for Windows bookshelf: Global Call IP over Host-Based Stack Technology User s Guide IP Media Library API Programming Guide IP Media Library API Library Reference The IP resource implementation of the DI0408LSAR2 board has unique design elements illustrated in the following figure. Unlike the DM/IP board implementation, there is no onboard Ethernet NIC interface on the DI0408LSAR2 board; therefore, both the IP call control and media processing are done through the host Ethernet NIC. The IP call control is implemented by host-based stack technology (call control library, IPT CCLib). The System Release FP1 for Windows Service Update August 22,

86 media processing of the RTP/RTCP packets is performed by the IP Media Service developed for DI0408LSAR2 media loads 3 and 5. Application Global Call API IP Signaling IP Signaling CC Lib IP Media Library IP Network RTP/RTCP IP Media Service (IPMEDIA.EXE) IP Media Commands Host NIC DM3 Device Driver Host Computer DI0408LSAR2 Board Notes:1. It is now possible to specify one NIC for RTP/RTCP and, via Global Call, assign a different NIC for signaling and data. See Section 2.23, DI0408LSAR2 Product Support for Host Systems with Multiple NICs, on page When using VoIP on DI0408LSAR2 boards, it is recommended that you avoid configuring the Host NICs on the system to use DHCP and instead statically configure the IP addresses of the NICs. In addition to this, whenever the IP address of the Host NIC used for IP media processing changes, you should specify the new IP address of the NIC in DCM prior to downloading as explained in Section 2.23, DI0408LSAR2 Product Support for Host Systems with Multiple NICs, on page 93. These recommendations apply to single NIC systems as well as multiple NIC systems. When the system is rebooted (or when the DHCP IP address lease is renewed), the NIC can be assigned a different IP address. This can result in future DI0408LSAR2 IP downloads to fail until you explicitly specify the new IP address of the NIC in DCM. System Release FP1 for Windows Service Update August 22,

87 Feature Description This release introduces support for media load 3 on the DI0408LSAR2 board. Media load 3 provides the same features as media load 2 with the addition of IP. (For more information about media loads, see the DI0408LSAR2 Media Loads section below. There is also an IP-only media load, media load 5.) The following new features are supported on the DI0408LSAR2 board when using media load 3: Call control implemented on the host by host-based stack technology (call control library, IPT CCLib). Media processing (RTP/RTCP processing) performed on the host, implemented via the IP Media Service developed for DI0408LSAR2 media load 3. Host-based IP stacks Global Call API support for IP IPML support for IP RADVISION* stack; compliant with ITU-T H.323 V.4 specification, including provision for periodic registration with gatekeeper RADVISION SIP stack; compliant with IETF RFC 3261, the Session Initiation Protocol (SIP) Full-duplex communication with all coders. Supported coders are: Coder Frames per Packet Frame Size (milliseconds) VAD G , 30 N/A G.723.1, 5.3 kbps 2, 3 30 Supported G.723.1, 6.3 kbps 2, 3 30 Supported G.729 Annex A Disabled G.729 Annex A with Annex B Enabled GSM FR 2, 3 Supported H.245 tunneling Fast Start and Slow Start compatibility QoS/ToS RFC 2833 IP Service Quality - jitter and packet loss Threshold alarms Simple Network Management Protocol (SNMP): TCP/IP level SNMP Support for standard Internet protocols, including TCP/IP, UDP, and RTP/RTCP Object ID support when sending non-standard command Support for non-standard information element in the Facility message over Q.931 port Vendor-specific information sending during call setup Voice quality parameters Basic DTMF and MF detection System Release FP1 for Windows Service Update August 22,

88 The following features, supported in System Release Feature Pack 1 for Windows for DM/IP boards, are not supported on the DI0408LSAR2 board using media load 3: G.711 with 10 msec frame size. It is recommended that applications use 20 or 30 msec frame size with G.711. RTP/RTCP processing on the host system may cause voice quality issues at 10 msec frame size under heavy system loading. Multicasting T.38 Single board start/stop (SBSS) Multiprocessor systems DI0408LSAR2 Media Loads Media loads are pre-defined sets of features supported by DM3 boards. A media load consists of a configuration file set (PCD, FCD, and CONFIG files) and associated firmware loads that are downloaded to each board. In most cases, the PCD/FCD/CONFIG file names indicate the associated media load and protocol. For example, the files for media load 3 are di0408lsa_rev2_ml3.pcd, di0408lsa_rev2_ml3.fcd, and di0408lsa_rev2_ml3.config. See the DM3 Configuration File Reference for more information about media loads and configuration file sets. There are five media loads for the DI0408LSAR2 board. The feature sets available in each media load are described below: Media Load 1 Media load 1 provides the following features: Trunks: call control, caller ID, and dedicated voice (player, recorder, tone generator, signal detector) for the four analog loop start interfaces Stations: call control, caller ID, and dedicated voice (player, recorder, tone generator, signal detector) for the eight analog station interfaces Capability to switch the signal from the audio input to the CT Bus/SCbus Support for up to three conferences with a total of nine parties max between all conferences. Conference resources are shareable across the system via the CT Bus/SCbus. Two channels of V.17 fax shareable across the system via the CT Bus/SCbus Media Load 2 Media load 2 provides the following features: Eight channels of voice (player, recorder, tone generator, signal detector) shareable across the system via the CT Bus/SCbus Trunks: call control, caller ID, and dedicated tone generation and signal detection capability for the four analog loop start interfaces Stations: call control, caller ID, and dedicated tone generation and signal detection capability for the eight analog station interfaces Capability to switch the signal from the audio input to the CT Bus/SCbus System Release FP1 for Windows Service Update August 22,

89 Support for up to three conferences with a total of nine parties max between all conferences. Conference resources are shareable across the system via the CT Bus/SCbus. Two channels of V.17 fax shareable across the system via the CT Bus/SCbus Media Load 3 Media load 3 provides the same features as media load 2 with the addition of: Four channels of IP telephony shareable across the system via the CT Bus/SCbus Media Load 4 Media load 4 provides the same features as media load 2 with the addition of: Four channels of Continuous Speech Processing (CSP) Media Load 5 Media load 5 provides the following features: Twelve channels of IP telephony shareable across the system via the CT Bus/SCbus DI0408LSAR2 Devices For the DI0408LSAR2 media loads, device enumeration follows the rules listed below. Note: The scenario below assumes that the DI0408LSAR2 is the only board in the system. Call the dx_getfeaturelist( ) function to return information about the features supported on the device. (Refer to the Voice Software Reference: Programmer s Guide for function details.) IPT Board Device - A virtual entity that represents a NIC or NIC address (if one NIC supports more than one IP address). The format of the device name is iptbx, where x is the logical board number that corresponds to the NIC or NIC address. See the Global Call IP over Host-Based Stack Technology User s Guide for more information. IPT Network Device - Represents a logical channel over which calls can be made. This device is used for call control (call setup and tear down). The format of the device name is iptbxty, where x is the logical board number and y is the logical channel number. See the Global Call IP over Host-Based Stack Technology User s Guide for more information. IP Media Device - Represents a media resource that is used to control RTP streaming, monitoring Quality of Service (QoS), and the sending and receiving of DTMF digits. The format of the device name is ipmbxcy, where x is the logical board number and y is the logical channel number. See the Global Call IP over Host-Based Stack Technology User s Guide and the IP Media Library API Programming Guide for more information. The four loop start analog interfaces are enumerated as dtib1t1-dtib1t4. Trunk call control is supported via Global Call APIs. Voice devices associated with the four loop start interfaces are dxxxb1c1-dxxxb1c4. For media load 1, a subset of the dx_ APIs provides support for basic voice functionality. For media loads 2, 3, and 4, a subset of the dx_ APIs provides tone generation and detection support. System Release FP1 for Windows Service Update August 22,

90 The eight analog station interfaces are enumerated as msib1c1-msib1c8. Station call control is supported via the msi_ APIs. Voice devices associated with the eight analog station interfaces are dxxxb2c1- dxxxb2c4 and dxxxb3c1-dxxxb3c4. For media load 1, a subset of the dx_ APIs provides support for basic voice functionality. For media loads 2, 3, and 4, a subset of the dx_ APIs provides tone generation and detection support. For media loads 2, 3, and 4, eight channels of voice are enumerated as dxxxb4c1- dxxxb4c4 and dxxxb5c1-dxxxb5c4. A subset of the dx_ APIs provides support for basic voice, including transaction record. The audio input is enumerated as aib1. Switching is controlled via the ai_ APIs. Conferencing is enumerated as dcbb1d1. Application control of conferencing is provided by either the dcb_ APIs or the ms_ conferencing APIs. The two fax channels are enumerated as follows: For media load 1: dxxxb4c1 and dxxxb4c2 For media load 2: dxxxb6c1 and dxxxb6c2 For media load 3: dxxxb6c1 and dxxxb6c2 For media load 4: dxxxb7c1 and dxxxb7c2 Application control is provided by the fx_ APIs. For media load 3 only: the four channels of IP are designated as follows: For IPT network devices: iptb1t1-iptb1t4 For IP media devices: ipmb1c1-ipmb1c4 For multiple DI0408LSAR2 board configurations: board 2: IPT network devices: iptb1t5-iptb1t8; IP media devices: ipmb2c1- ipmb2c4 board 3: IPT network devices: iptb1t9-iptb1t12; IP media devices: ipmb3c1-ipmb3c4... For media load 5 only: the 12 channels of IP are designated as follows: For IPT network devices: iptb1t1-iptb1t12 For IP media devices: ipmb1c1-ipmb1c12 For media load 4 only: the four channels of continuous speech processing (CSP) are enumerated as dxxb6c1-dxxb6c4. Application control is provided by the ec_ APIs. Demos Supported The following demos, which are provided in System Release Feature Pack 1, are supported on the DI0408LSAR2 board: IP Gateway (Global Call) demo IPTMail_R4 demo System Release FP1 for Windows Service Update August 22,

91 For detailed information about these demos, see the IP Gateway (Global Call) Demo Guide and the IPTMail_R4 Demo Guide on your System Release Feature Pack 1 for Windows bookshelf. The following sections provide supplementary information about using these demos with DI0408LSAR2 boards. IP Gateway (Global Call) Demo The IP Gateway (Global Call) demo shows how to build a PSTN-IP gateway using the Global Call API. The gateway is between the IP and trunk interfaces. (Station interfaces are not used in this demo.) When running this demo with a DI0408LSAR2 board, use the following command line switches: -f1 use digital T1 front end. (DI0408LSAR2 analog trunks are accessed via the dti library.) -n4 use 4 channels. If -n4 is left out of the command line, the demo will attempt to open 24 IP ports, and failures will occur for p1 send DTMF digits to the PSTN front ends (necessary when outbound PSTN calls will be made). For information about other command line switches, see the IP Gateway (Global Call) Demo Guide. IPTMail_R4 Demo The IPTMail_R4 demo shows how to build a simple Internet telephony voic application using the Global Call API. Before running this demo with a DI0408LSAR2 board, a source code change is required for the getvoicechannels( ) function in the voice.c file. The getvoicechannels( ) function gets the number of voice channels available in the system. This code change is needed because dxxxb4 and dxxxb5 are the voice resources on the DI0408LSAR2 board; dxxxb1-dxxxb3 are DTI and MSI resources. Change the following lines of the getvoicechannels( ) function in the voice.c file: From: /* For all boards open the board to get the sub devices */ for ( index = 1; index <= boardnum; index++) { To: /* For all voice resource boards not associated with a dti or msi device, open the board to get the sub devices */ for ( index = 4; index = 5; index++) { When running this demo with a DI0408LSAR2 board, use the following command line switches: -n4 to specify 4 channels of IP. For information about other command line switches, see the IPTMail_R4 Demo Guide Configuring the Software This section contains information about configuring IP parameters on DI0408LSAR2 boards; this information supplements the configuration information in the DM3 Configuration File Reference on your System Release Feature Pack 1 for Windows bookshelf. System Release FP1 for Windows Service Update August 22,

92 Selecting a Firmware File The first time you run the configuration manager (DCM) with a DM3 board in your system, you are prompted to select the firmware files (PCD and FCD) to be downloaded to each board. As discussed above in the DI0408LSAR2 Media Loads section, the PCD/FCD files determine the media load supported by the board. DCM displays a list of PCD files. Select the PCD file for the media load that you want, for example, di0408lsa_rev2_ml3.pcd for media load 3. The selected PCD file and corresponding FCD file will be downloaded when the boards are started. Setting the ToS Parameter in DCM With this release, a new parameter for enabling or disabling ToS has been added to DCM for DI0408LSAR2 boards. The parameter is called DI_TOS and it appears on the Misc property sheet. The default value for DI_TOS is Enable. If DI_TOS is set to Disable, the IP Media Service disables ToS processing for RTP packets transmitted from IP Media channels. In this configuration, all RTP packets transmitted from DI0408LSAR2 board IP Media channels will have the ToS field in their IP packet header set to zero. Configuring ToS in the CONFIG File With this release, a new parameter for configuring ToS has been added to the DI0408LSAR2 board CONFIG files that support IP. Previously, this parameter was applicable to DM/IP boards only. Note: For more detailed information about modifying the CONFIG file and then running the fcdgen utility to generate a new FCD file, refer to the DM3 Configuration File Reference. Type of Service (ToS) is a category of Quality of Service (QoS) that performs Layer 3 tagging of packets to improve the mobility of the packets. When the ToS feature is used, four bits are specified in the packet header to determine the type of service as follows: 1000: minimize delay selects a minimum delay link or circuit for the datagram 0100: maximize throughput selects a high throughput link or circuit for the datagram 0010: maximize reliability selects a high reliability link or circuit for the datagram 0001: minimize monetary cost selects a minimum cost link or circuit for the datagram 0000: normal service (not activated) the datagram has no priority assigned The above are defined RFC-1349 specified values. Note that other values are valid; however, they have not been explicitly characterized in the RFC-1349 specification. The feature allows setting of any combinations of the four bits. The processing of packets with such combinations is assumed understood by the administrator and downstream routers. System Release FP1 for Windows Service Update August 22,

93 There are two ways to implement the ToS feature (the same as when using ToS with DM/IP boards): ToS can be activated on a channel by channel basis at run time by using the Global Call API functions gc_setconfigdata( ), gc_setuserinfo( ), and gc_makecall( ). The Set ID = IPSET_CONFIG and the Parameter ID = IPPARM_CONFIG_TOS. For further information, see the Global Call IP over Host-Based Stack Technology User s Guide. Settings made at run time are not persistent. ToS can be set at the board level, before board initialization, via the CONFIG file. This causes the ToS bits to be set to the designated value in all RTP packets transmitted. To specify the ToS in the CONFIG file, set the following parameter: [0x1d] SetParm=0x1d01,0! PrmTOS (LOWDELAY 0x10 THROUGHPUT 0x08 RELIABILITY 0x04 MINCOST 0x02 No Priority 0) This parameter sets the ToS bits in the IP header of transmitted datagrams to improve the mobility of packets. Values are: 0x10: LOWDELAY selects a minimum delay link or circuit for the datagram 0x08: THROUGHPUT selects a high throughput link or circuit for the datagram 0x04: RELIABILITY selects a high reliability link or circuit for the datagram 0x02: MINCOST selects a minimum cost link or circuit for the datagram 0x00: No Priority the datagram has no priority assigned Restrictions and Limitations The following restrictions and limitations exist for IP support on the DI0408LSAR2 boards: Single processor systems only DI0408LSAR2 ML3 and ML5 are not supported on multiprocessor systems. PTR 30285: When using VAD with G.729A/B codec, the application must explicitly set the VAD field in the IP_AUDIO_CAPABILITY structure to GCPV_ENABLE. Otherwise, the application could hang when invoking gc_answercall( ) DI0408LSAR2 Product Support for Host Systems with Multiple NICs This release provides the capability to specify an explicit IP address for use by all DI0408LSAR2 boards for RTP/RTCP processing in the system. Previously, the first System Release FP1 for Windows Service Update August 22,

94 Network Interface Card (NIC) address returned from the socket function call gethostbyname( ) was selected automatically and assigned as the IP address. The explicit IP address can be set with the configuration manager (DCM) as well as with the NCM API (NCM_SetValue( ) and NCM_GetValue( ) functions). The new parameter is HostIpMediaNetworkAddress and appears on the Misc property sheet in DCM. It is a global-level parameter that applies to all DI0408LSAR2 boards in the system. Enter the parameter value using standard decimal notation, xxx.xxx.xxx.xxx. Note: This is the IP address for the IP media (not the IP call control signaling) and only for boards using the Host IP Media Service (not DM/IP boards with on-board NICs). Refer to the figure below. Application IP Network GlobalCall API Host NIC IP Signaling IP Signaling CC Lib IP Media Library IP Network RTP/RTCP IP Media Service IP Media Commands Host NIC DM3 Device Driver Host Computer DI0408LSAR2 Board The IP Media Service uses the specified NIC IP address when establishing RTP media sessions. If no IP address was specified, the selection is done automatically as in the past. The user-specified address is validated at board initialization to ensure that the address is recognized by the operating system. If the specified address is not valid, board initialization will fail with the reason for failure logged (i.e., invalid NIC IP address). As with other configuration parameters, the HostIpMediaNetworkAddress parameter can be changed at any time; however, the change will not take effect until the system has been stopped and restarted. System Release FP1 for Windows Service Update August 22,

95 2.24 Circular Logging Capability for gc_h3r.log The gc_h3r.log file, which is used for call control library and SIP stack debugging, can be configured for circular logging. With circular logging, you set a limit to the physical size of the log file. When the log file expands to this size, older logging information is overwritten. To configure the gc_h3r.log file, use the gc_h3r.cfg file. An excerpt from this file is shown below, with the entries for circular logging shown in bold. # Configuring ipcclib log file paths: # - max path length = 120 characters # - must not contain white spaces # - all directories in path must already exist # - leave commented out to get logs in local working directory # with the default names: gc_h3r.log # - For UNIX only: user must have execute access to # all directories in path, as well as # write access to the last directory # # Configuring ipcclib log file size: # - Set gch3rfilesize to a value from 0 to 0x7FFFFFFF - 2GByte Limit. # A value of 0 will create an unlimited flat debug file (no Limit); # all other valid values will create a circular debug file of indicated size. # The default value is 0 (unlimited flat debug file). # # uncomment to change Windows default log file paths. #gch3rfilename = c:\progra~1\dialogic\cfg\gc_h3r.log # # uncomment to change UNIX default log file paths. #gch3rfilename = /var/tmp/gc_h3r.log # # uncomment to set gch3rfilesize to 10 Mbyes. #gch3rfilesize = 0xA00000 # # # For further information about the gc_h3r.log file and gc_h3r.cfg file, see the Global Call IP over Host-based Stack Technology User s Guide New Features for Intel Dialogic PBX Integration Boards Intel Dialogic D/82JCT-U and D/42JCT-U PBX integration boards now support the following NEC equipment: NEC IVS 2000 PBX System Release FP1 for Windows Service Update August 22,

96 NEC IMX 2400 PBX Electra Elite KTS 2.26 ms_setmsgwaitind( ) Async Mode Support This release supports asynchronous operation of the ms_setmsgwaitind( ) function in the Modular Station Interface API. Previously, this function could be used only in synchronous mode. With support of asynchronous mode, applications can set message waiting indicator (MWI) LEDs without delaying other real time functions. The ms_setmsgwaitind( ) function is supported on the DI family of products and on HDSI boards. API Changes The ms_setmsgwaitind( ) function formerly had two parameters that were reserved for future use (rfu1 and rfu2). The rfu1 parameter is now the mode parameter and can be set to EV_ASYNC for asynchronous mode or EV_SYNC for synchronous mode. If the current default rfu1 value of zero is specified, the mode defaults to synchronous mode. Note: You should recompile your code with this new software release, even if you are keeping the default synchronous mode. All calls to ms_setmsgwaitind( ) must be changed because the third argument was changed from a void * to an int. An updated function reference page is provided below. In addition to the new mode parameter, note the following additional changes to the ms_setmsgwaitind( ) function: a new asynchronous completion event, MSEV_MWISET, for successful setting of the MWI indicator on the addressed device (phone set), and MSEV_MWIERR to indicate that the ms_setmsgwaitind( ) function failed in asynchronous mode a new error code, E_MSIOFFHOOK, to alert the application that the addressed phone is currently off-hook before calling ms_setmsgwaitind( ) System Release FP1 for Windows Service Update August 22,

97 ms_setmsgwaitind( ) toggle message waiting indicator lamp Name: ms_setmsgwaitind (devh, IndicatorState, mode, rfu2) Inputs: int devh station device handle unsigned short IndicatorState indicator ON/OFF state int mode asynchronous/synchronous void* rfu2 reserved for future use Returns: 0 on success -1 on failure Includes: srllib.h dtilib.h msilib.h Category: Station Mode: asynchronous or synchronous Platform: DI, HDSI Description The ms_setmsgwaitind( ) function generates an FSK signal to illuminate the message waiting LED. Parameter devh IndicatorState mode rfu2 Description device handle toggles FSK message waiting indicator (MWI) on a phone set MS_MSGINDON turns the MWI on MS_MSGINDOFF turns the MWI off the operation mode EV_ASYNC asynchronous mode EV_SYNC synchronous mode reserved for future use Termination Events When this function is called in asynchronous mode, a return value of 0 indicates that the function was initiated, while a return value of -1 indicates error. The following events may be received: MSEV_MWISET Indicates that the message waiting indicator on the addressed phone set was set. This event is also returned to the normally registered event handler. The device name is available via ATDV_NAMEP(dev). MSEV_MWIERR Indicates that the ms_setmsgwaitind( ) function failed in asynchronous mode. System Release FP1 for Windows Service Update August 22,

98 Cautions This function can only be issued when the station is on-hook. If issued when the station is off-hook, the function fails, resulting in MSEV_MWIERR. Errors If this function returns -1 to indicate failure, obtain the reason for the error by calling the SRL standard attribute function ATDV_LASTERR( ) or ATDV_ERRMSGP( ) to retrieve either the error code or a pointer to the error description, respectively. Possible errors are: E_MSIOFFHOOK Invalid State, OFF HOOK EDT_BADGLOB Bad device/global parameter number EDT_INVTS Invalid timeslot or channel EDT_NOMEMERR Can t map or allocate memory in driver EDT_TMOERR Timed out waiting for reply from firmware For information about error codes, refer to the Error Codes chapter in the Modular Station Interface API Library Reference. Error defines can be found in dtilib.h or msilib.h. Example - Asynchronous Mode #include <windows.h> /* For Windows application only */ #include <stdio.h> #include <errno.h> #include "srllib.h" #include "dtilib.h" #include "msilib.h" int dev; /* Station Device Descriptor */ int rc; /* Return Code */ int EvtType; unsigned short IndicatorState= MS_MSGINDON; void *RFU2=0; void main() { /* Open board 1, Station 1 device */ if ( (dev = ms_open("msib1c1", 0)) == -1) { printf("cannot open msib1c1, Station 1, Channel 1: errno=%d\n",errno); exit(1); } /* * Continue processing */ /* Set the Message Wait Indicator to ON */ IndicatorState= MS_MSGINDON; if((rc=ms_setmsgwaitind(dev,indicatorstate,ev_async, RFU2))==-1) { System Release FP1 for Windows Service Update August 22,

99 /* process error */ } while (1) { /* Poll for events */ rc = sr_waitevt(-1); dev = sr_getevtdev(0); if (rc == -1) { printf("error Device %s %s\n", ATDV_NAMEP(dev), ATDV_ERRMSGP(dev)); break; } EvtType = sr_getevttype(0); /* Check for MWI event */ if (EvtType == MSEV_MWISET ) { printf("msev_mwiset event received\n"); break; } else if (EvtType == MSEV_MWIERR ) { printf("msev_mwierr event received for error %d message %s\n", ATDV_LASTERR(dev), ATDV_ERRMSGP(dev) ); break; } } /*Let the Message Wait Indicator stay on for 5 seconds */ Sleep(5000); /* For Windows application only */ /* * Continue processing */ /* Set the Message Wait Indicator to OFF */ IndicatorState= MS_MSGINDOFF; if((rc=ms_setmsgwaitind(dev,indicatorstate,ev_async, RFU2))==-1) { /* process error */ } while (1) { // Poll for events rc = sr_waitevt(-1); dev = sr_getevtdev(0); if (rc == -1) { printf("error Device %s %s\n", ATDV_NAMEP(dev), ATDV_ERRMSGP(dev)); break; } EvtType = sr_getevttype(0); /* Check for MWI event */ if (EvtType == MSEV_MWISET ) { printf("msev_mwiset event received\n"); break; } else if (EvtType == MSEV_MWIERR ) { printf("msev_mwierr event received for error %d message %s\n", ATDV_LASTERR(dev), ATDV_ERRMSGP(dev) ); break; } } /* Done processing - close device */ if(ms_close(dev)==-1) System Release FP1 for Windows Service Update August 22,

100 { } printf("cannot close device msib1c1. errno=%d\n",errno); exit(1); } 2.27 Enhanced GCAMS on DM3 Boards This release provides the following enhancements to the Global Call Alarm Management System (GCAMS) for DM/V and DM/V-A Series boards: Ability for the application to be notified of several new T1/E1 alarms, supported on ISDN, CAS, and R2MF protocols through existing GCEV_ALARM, GCEV_BLOCKED, and GCEV_UNBLOCKED Ability to change default threshold values for the new alarms through the configuration file Ability for the GCAMS functions in the Global Call API library to recognize the new alarms Default values of non-blocking and "no notify" for each new alarm with the ability to change each value via gc_setalarmconfiguration( ) Alarm reporting behavior for the new alarms is the same as the behavior on Springware boards Note: Some of the FCD/PCD files have an embedded protocol in System Release 5.x software. The new alarms are not supported when these FCD/PCD files are in use on a board. Specifically, FCD/PCD files that have "t1" or "ts16" in the name do not support the new alarms; for example, the ml2_qsa_t1.fcd and ml2_qsa_t1.pcd do not support the new alarms. Details on these enhancements are provided next New E1 Alarms The following table lists new alarms for E1 technology. These new alarms are nonblocking and not received by default. To change these default values, use the gc_setalarmconfiguration( ) function. Table 2. New Alarms for E1 Technology (DM3) Alarm Meaning Default Threshold Value Range DTE1_BPVS Bipolar violation count saturation to 255 DTE1_CECS CRC4 error count saturation to 255 DTE1_ECS Frame sync bit error count saturation 0 0 to 255 System Release FP1 for Windows Service Update August 22,

101 New T1 Alarms The following table lists new alarms for T1 technology. These new alarms are non-blocking and not received by default. To change these default values, use the gc_setalarmconfiguration( ) function. Table 3. New Alarms for T1 Technology (DM3) Alarm Meaning Default Threshold Value Range DTT1_BPVS Bipolar violation count saturation to 255 DTT1_ECS Frame bit error count saturation 0 0 to 255 DTT1_FERR Two out of four consecutive frame bits (F bit) in error 0 0 to 255 DTT1_OOF Out of frame error count saturation 0 0 to Modifying Default Threshold Values for New Alarms If desired, you can change the default threshold value of a new T1/E1 alarm by adding a parameter in the CONFIG file (.config) that corresponds to the PCD file in use on your board. The change is made per span. After threshold parameters are added, use the fcdgen utility to generate an updated FCD file. Then start system services on the board. If threshold parameters are not added, default threshold values are in effect. See the DM3 Configuration File Reference for more information on CONFIG files, PCD files, and the fcdgen utility. To modify default threshold values for E1 alarms, add one or more of the following parameters (sample value of 100 shown) to the [lineadmin.x] section of a CONFIG file: SetParm=0x1639,100! BPVS threshold range 0-255, default 255 SetParm=0x163c,100! ECS threshold range 0-255, default 0 SetParm=0x163d,100! CECS threshold range 0-255, default 255 To modify default threshold values for T1 alarms, add one or more of the following parameters (sample value of 100 shown) to the [lineadmin.x] section of a CONFIG file: SetParm=0x1639,100! BPVS threshold range 0-255, default 255 SetParm=0x163a,100! OOF threshold range 0-255, default 0 SetParm=0x163b,100! FERR threshold range 0-255, default 0 SetParm=0x163c,100! ECS threshold range 0-255, default Support for New Alarms in GCAMS Functions The new alarms are supported by the GCAMS API functions as documented in the Global Call API Library Reference in the System Release FP1 for Windows bookshelf. System Release FP1 for Windows Service Update August 22,

102 2.28 Enhanced Special Information Tone Frequency Detection on DM3 Boards This release provides the following enhancements to Special Information Tone (SIT) frequency detection on DM3 boards: Broader default SIT sequence definitions to allow greater coverage for SIT sequences detected in the field. Three new SIT sequence definitions in the SIT tone set for DM3 boards. The new SIT sequences are: InterLATA no circuit (TID_SIT_NC_INTERLATA), InterLATA reorder tone (TID_SIT_RO_INTERLATA), and ineffective other (TID_SIT_IO). A new catch all SIT sequence definition to cover SIT sequences that fall outside the range of the defined SIT sequences. DM3 support for the ATDX_CRTNID( ) function to allow retrieval of the SIT ID. Details on these enhancements are provided next New SIT Sequence Definitions The table below provides the default tone definitions for SIT sequences used on DM3 boards. This information is not currently documented in the Compatibility Guide in the System Release Feature Pack 1 for Windows bookshelf. The table describes existing SIT sequences that have broader definitions as well as new SIT sequences. This table is explained in further detail: The values in the Freq. column represent minimum and maximum values in Hz. Time refers to minimum and maximum on time in 10 msec units; the maximum off time between each tone is 5 (or 50 msec). The repeat count is 1 for all SIT segments. N/A means not applicable. For TID_SIT_ANY, the frequency and time of the first and second segments are open; that is, they are ignored. Only the frequency of the third segment is relevant. The tone IDs have aliases: TID_SIT_NO_CIRCUIT (TID_SIT_NC) TID_SIT_OPERATOR_INTERCEPT (TID_SIT_IC) TID_SIT_VACANT_CIRCUIT (TID_SIT_VC) TID_SIT_REORDER_TONE (TID_SIT_RO) TID_SIT_NO_CIRCUIT_INTERLATA (TID_SIT_NC_INTERLATA) TID_SIT_REORDER_TONE_INTERLATA (TID_SIT_RO_INTERLATA) TID_SIT_INEFFECTIVE_OTHER (TID_SIT_IO) System Release FP1 for Windows Service Update August 22,

103 Table 4. Special Information Tone Definitions (DM3) SIT 1st Segment 2nd Segment 3rd Segment Tone ID Description Freq. Time Freq. Time Freq. Time TID_SIT_NC No Circuit Found 950/ / / / /1850 N/A TID_SIT_IC Operator Intercept 874/955 15/ / / /1850 N/A TID_SIT_VC Vacant Circuit 950/ / / / /1850 N/A TID_SIT_RO TID_SIT_NC_ INTERLATA TID_SIT_RO_ INTERLATA Reorder (system busy) InterLATA No Circuit Found InterLATA Reorder (system busy) 874/955 15/ / / /1850 N/A 874/955 32/ / / /1850 N/A 950/ / / / /1850 N/A TID_SIT_IO Ineffective Other 874/955 32/ / / /1850 N/A TID_SIT_ANY Catch all tone definition Open Open Open Open 1725/1825 N/A ATDX_CRTNID( ) Support on DM3 Boards The ATDX_CRTNID( ) function is now supported on DM3 boards. This information is not currently documented in the Compatibility Guide in the System Release Feature Pack 1 for Windows bookshelf. On DM3 boards, the following new tone IDs can now be returned by ATDX_CRTNID( ): Tone ID TID_SIT_IC TID_SIT_OPERATOR_INTERCEPT TID_SIT_IO TID_SIT_INEFFECTIVE_OTHER TID_SIT_NC TID_SIT_NO_CIRCUIT TID_SIT_NC_INTERLATA TID_SIT_NO_CIRCUIT_INTERLATA TID_SIT_RO TID_SIT_REORDER_TONE TID_SIT_RO_INTERLATA TID_SIT_REORDER_TONE_INTERLATA TID_SIT_VC TID_SIT_VACANT_CIRCUIT TID_SIT_ANY Description Operator intercept SIT sequence Ineffective other SIT sequence No circuit found SIT sequence InterLATA no circuit found SIT sequence Reorder (system busy) SIT sequence InterLATA reorder (system busy) SIT sequence Vacant circuit SIT sequence Catch all (returned for a SIT sequence that falls outside the range of known default SIT sequences) System Release FP1 for Windows Service Update August 22,

104 Updated example code is provided for this function as follows. #include <stdio.h> #include <srllib.h> #include <dxxxlib.h> main() { DX_CAP cap_s; int ddd, car; char *chnam, *dialstrg; long tone_id; chnam = "dxxxb1c1"; dialstrg = "L1234"; /* * Open channel */ if ((ddd = dx_open( chnam, NULL )) == -1 ) { /* handle error */ } /* * Dial */ printf("dialing %s\n", dialstrg ); car = dx_dial(ddd,dialstrg,(dx_cap *)&cap_s,dx_callp EV_SYNC); if (car == -1) { /* handle error */ } switch( car ) { case CR_NODIALTONE: switch( ATDX_DTNFAIL(ddd) ) { case 'L': printf(" Unable to get Local dial tone\n"); break; case 'I': printf(" Unable to get International dial tone\n"); break; case 'X': printf(" Unable to get special extra dial tone\n"); break; } break; case CR_BUSY: printf(" %s engaged - %s detected\n", dialstrg, System Release FP1 for Windows Service Update August 22,

105 (ATDX_CRTNID(ddd) == TID_BUSY1? "Busy 1" : "Busy 2") ); break; case CR_CNCT: printf(" Successful connection to %s\n", dialstrg ); break; case CR_CEPT: printf(" Special tone received at %s\n", dialstrg ); tone_id = ATDX_CRTNID(ddd); //ddd is handle that is returned by dx_open() switch (tone_id) { case TID_SIT_NC: break; case TID_SIT_IC: break; case TID_SIT_VC: break; case TID_SIT_RO: break; case TID_SIT_NC_INTERLATA: break; case TID_SIT_RO_INTERLATA: break; case TID_SIT_IO: break; case TID_SIT_ANY: break; } break; default: break; } /* * Set channel on hook */ if ((dx_sethook( ddd, DX_ONHOOK, EV_SYNC )) == -1) { /* handle error */ } } dx_close( ddd ); System Release FP1 for Windows Service Update August 22,

106 2.29 Improved Accuracy of Call Progress Analysis Positive answering machine detection (PAMD) and positive voice detection (PVD) are part of the call progress analysis features that enable applications to determine whether a call has been answered by an answering machine or a live person. Since the original PAMD and PVD algorithms were written, the current business and home environment has been changed so that the original algorithms no longer produce satisfactory results. A tech note was previously written to provide instructions for modifying the PAMD and PVD qualification template parameters on DM3 boards to accomplish higher successful PAMD and PVD rates. The qualification template contains definitions used by the PAMD and PVD algorithms. For further information about these parameters, see the tech note at With this Service Update, the modified parameters have now become the default, so it is no longer necessary to tune the PAMD and PVD parameters as explained in the tech note. And since the modified parameters are now the default, they will automatically be carried forward to new Service Update releases. Operating with these new default values should result in improved accuracy of call progress analysis on DM3 boards. However, although these values are the most commonly used, they may not be suitable for every application environment. If needed, the PAMD and PVD templates are still tunable, as explained in the tech note, to achieve even better results based on the individual application environment. Note: The default values were changed only for DM/V and DM/V-A Series boards. They will be changed for other DM3 products (for example, DM/IP, DI0408LSA, DMV160LP, DM/VF) in future Service Update releases Support for ANI Category Digit Retrieval on DM3 Boards The gc_getcallinfo( ) function, which retrieves information associated with a call, can now be used to retrieve the category digit for DM3 boards. This capability is not currently documented in the Global Call API Library Reference and the Global Call E-1/T-1 CAS/R2 Technology User s Guide in the System Release Feature Pack 1 for Windows bookshelf. Formerly, the gc_getcallinfo( ) CATEGORY_DIGIT parameter was supported for Springware boards only. The category digit is used to determine the origin or type of the calling party (for example, ordinary subscriber, pay phone) so that the application may choose to take a specific action based on the call s origin. The category digit is used mainly with E-1 R2MF protocols, and the categories are determined by the protocol. For further information about using the gc_getcallinfo( ) function, see the Global Call API Library Reference. System Release FP1 for Windows Service Update August 22,

107 2.31 Support for CompactPCI Boards Although System Release Feature Pack 1 and the Service Update support CompactPCI boards, some administrative features for CompactPCI are not supported. Some CompactPCI computer chassis have special features that allow failing components to be exchanged without stopping and restarting the entire system. Peripheral Hot Swap (PHS) supports changing out input/output devices such as Intel telecom boards, and Redundant Host (RH) allows the exchange of a single board computer (SBC). Special software is required to accomplish these operations and is not included with this system release. If you require support for PHS or RH in your applications, please contact your Intel Telecom sales representative to discuss the options available New Boards Supported The following new boards are supported with this Service Update: Intel Dialogic D/4PCIUF Combined Media Board Intel Dialogic D/4PCIU4S Combined Media Board Intel Dialogic D30E1P Voice Board Intel Dialogic D60E1P Voice Board In addition, some new revisions of Intel NetStructure Combined Media Boards are supported: DM/V480A-2T1-CPCI Rev2 (DMV480A2T1CR2) DM/V600A-2E1-CPCI Rev2 (DMV600A2E1CR2) DM/V960A-4T1-CPCI Rev 2 (DMV960A4T1CR2) DM/V1200A-4E1-CPCI Rev 2 (DMV1200A4E1CR2) 2.33 End of Support for Specified Boards Support for the following boards ends on December 31, At that time, fixes for unresolved defects will not be pursued nor released in Point or Service Packages. In addition, the DM/IP boards noted below will not operate correctly on new Service Updates after Service Update 89. Antares 3000/60 PCI BRI/160SC BRI/80SC CP12/SC CP6/SC CPD/220 System Release FP1 for Windows Service Update August 22,

108 CPi/200 CPI/200BRI CPi/400 CPi/400BRI D/160SC D/160SC-8LS D/160SC-HS D/21E D/240SC D/240SC-T1-IDPD D/320-PCI D/320SC D/41ESC D/41H D/640SC D/80-PCI D/80SC DCB/640SC DM/IP0821A-E1 DM/IP0821A-T1 DM/IP1620A-E1 DM/IP1620A-T1 DM/IP241-1T1 DM/IP241-1T1-cPCI DM/IP2431A-T1 DM/IP301-1E1-cPCI DM/IP301-1E1-PCI DM/IP3031A-E1-120 DM/IP481-2T1cPCI DM/IP601-2E1cPCI DM/V480-2T1-PCI DM/V600-2E1-PCI DTI/240SC DTI/241SC DTI/300SC DTI/301SC DTI/480SC DTI/481SC DTI/600SC DTI/601SC LSI/161SC LSI/81SC 10Base-T boards will not operate on any Service Update after SU89. 10Base-T boards will not operate on any Service Update after SU89. 10Base-T boards will not operate on any Service Update after SU89. 10Base-T boards will not operate on any Service Update after SU89. 10Base-T boards will not operate on any Service Update after SU89. 10Base-T boards will not operate on any Service Update after SU89. System Release FP1 for Windows Service Update August 22,

109 VFX/40ESCplus XPI/ End of Support for Embedded H.323 IP Stack Support for the board-based embedded H.323 IP stack for DM/IP boards ends on December 31, An application note is available for those who need to migrate from the board-based embedded H.323 IP stack to the host-based stack. Refer to the Porting Global Call H.323 Applications from Embedded Stack to Host-Based Stack Application Note in the System Release Feature Pack 1 for Windows bookshelf. Also note that use of the embedded H.323 stack will not operate correctly on new Service Updates after Service Update End of Support for Windows NT and TAPI Interfaces Support for the Windows NT operating system for this release ends on December 31, Customers can migrate to any of the other supported operating systems for this release. Refer to the Release Guide and to Chapter 3, System Requirements in this document for supported operating systems. Migration from Windows NT to another supported operating system may require customers to recompile applications. Support for the TAPI programming interface ends on December 31, For ongoing support, customers will be required to redevelop applications from TAPI to R4 Global Call or obtain third party middleware that can translate from TAPI to R4 Global Call. System Release FP1 for Windows Service Update August 22,

110 3.System Requirements 3 Intel Dialogic System Release for Windows must be installed before installing this Service Update. Refer to the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Release Guide for specific hardware and software requirements. In addition to the supported operating systems listed in the Release Guide, the following operating system versions are now supported with this Service Update: Windows Server 2003 Standard Edition Enterprise Edition Windows Server 2003 with SP1 Windows Server 2003 with SP2 Windows Server 2003 R2 Windows 2000 with SP4 Windows 2000 Update Rollup 1 for SP4 Windows XP with SP2 Note: Terminal Services Application Server Mode and Active Directory Application Server Mode are not supported on any operating systems. Requirements for Global Call Protocols Package with Service Update The Service Update now contains.prm files for use with the Global Call Protocols Package. These.prm files supersede some of the.prm files that were provided with Global Call Protocols Version 4.2 and earlier, which are now outdated. Global Call Protocols Version 4.2 (or earlier) will continue to work on the latest Service Update builds as it has been working with earlier builds. However, it is recommended that you use Global Call Protocols Version 4.3 (or later) with the Service Update. With Global Call Protocols Version 4.3 and later, the.prm files are no longer included in the Global Call Protocols Package, and the latest versions of.prm files will always be available via the Service Update. (If you continue to use Global Call Protocols Version 4.2 or earlier, the outdated.prm files in the Global Call Protocols Package will overwrite the.prm files in the Service Update.) Note:.prm files are used with Springware boards only, not with DM3 boards. You must upgrade to Global Call Protocols Version 4.3 (or later) if you are using Springware boards with any of the following.prm files: au_300.prm be_300.prm cl_300.prm System Release FP1 for Windows Service Update August 22,

111 System Requirements cn_300.prm fi_300.prm hu_300.prm id_300.prm it_300.prm nl_300.prm uk_300.prm us_240.prm To upgrade from an earlier version of Global Call Protocols (e.g., Version 4.2), you must uninstall it, reinstall the Service Update, and then install Global Call Protocols Version 4.3 (or later). System Release FP1 for Windows Service Update August 22,

112 4.Installing the Software 4 This chapter describes how to install and uninstall the Intel Dialogic System Release Feature Pack 1 Service Update software and includes the following sections: Prerequisites for Software Installation Order of Procedures Saving Existing Configuration Data Uninstalling Existing Software Installing the Service Update Performing a Silent Install Note: With this new Service Update, Feature Pack 1 and the latest Service Update are installed together, with only one reboot required, which reduces the steps and time involved in installing them. The file size has also been reduced, allowing room for an application to be distributed along with the System Release software on a single CD. 4.1 Prerequisites for Software Installation This section lists the assumptions and prerequisites for installing the System Release Feature Pack 1 Service Update software. Before installing the software, make sure that the following prerequisites are met: If you want to save existing configuration data, refer to Section 4.3, Saving Existing Configuration Data, on page 114. If you have an existing (obsolete) version of the System Release Feature Pack 1 Service Update on your system, you must uninstall all point releases, feature packs, and service packs before installing the new Service Update. You must uninstall these programs in the order given in Section 4.4.2, Uninstalling Existing Point Releases, Service Packs, Feature Packs, and Obsolete Service Updates, on page 116. If you had to uninstall any point releases, feature packs, or service packs as described in the bullet item above, it is strongly recommended that you also uninstall the base release and run the cleanup utility because the uninstall processes for those older programs could potentially damage the base release files. The process for uninstalling the base release and running the cleanup utility is given in Section 4.4.3, Uninstalling the Base Release, on page 117. Intel Dialogic System Release must be installed on your system. Your system must meet the hardware and software requirements described in the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Release Guide. In addition, refer to Chapter 3, System Requirements for a list of additional operating systems supported by this Service Update. System Release FP1 for Windows Service Update August 22,

113 Installing the Software The procedure for installing System Release is provided in Chapter 2 of the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide. These documents are provided with the software or you can access them at Note: This system release is designed for U.S. English versions of the Microsoft Windows Operating System. System directory path names are often spelled using the native language. Therefore if you are using a language other than U.S. English, various manual file copy operations may be necessary to place files in directories with the expected path names. For assistance, please contact the support organization that services your country. If you are using the Global Call Protocols package, see Requirements for Global Call Protocols Package with Service Update in Chapter 3, System Requirements. If you are going to install the new Service Update silently, you must create a new response file. Procedures for creating and using response files are provided in Section 4.6, Performing a Silent Install, on page 122. Before installing the software, make sure all devices are stopped and all applications are closed. Allowing an application to run during installation of the Intel Dialogic software could corrupt the Intel Dialogic software. Note: When installing Service Update 69 or later on a Windows NT system, Win32 APIs contained in the psapi.dll file are used to get information on running processes in order to ensure that programs such as DCM are not running when the install begins. If the psapi.dll file is not present when you start the install procedure, you will get an error message saying that psapi.dll could not be found. You can obtain the dll from the following link: 3D1FBAED-D122-45CF-9D46-1CAE384097AC It is recommended that you back up the drive on which you intend to install the software. You must have administrative privileges to install this software. 4.2 Order of Procedures The following is the order of procedures for installing the System Release Feature Pack 1 Service Update software: 1. Ensure that you have met the prerequisites listed in Section 4.1, Prerequisites for Software Installation, on page If you have existing configuration data, you can optionally save it as described in Section 4.3, Saving Existing Configuration Data, on page If you have any existing software beyond the base release (System Release 5.1.1), you must uninstall it. Refer to Section 4.4, Uninstalling Existing Software, on page 115. System Release FP1 for Windows Service Update August 22,

114 Installing the Software 4. Install System Release if it is not already on your system. Refer to Chapter 2 of the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide. 5. Install the System Release Feature Pack 1 Service Update software using one of the following procedures: Section 4.5, Installing the Service Update, on page 121 Section 4.6, Performing a Silent Install, on page Saving Existing Configuration Data This section describes how to save existing configuration data before installing the System Release Feature Pack 1 Service Update software. You must perform some steps before you install the Service Update and some after you install the Service Update. This section contains the following procedures: Before You Install the Service Update After You Install the Service Update Before You Install the Service Update To save existing configuration data, perform these steps before you install the System Release Feature Pack 1 Service Update software: 1. Identify the directories containing configuration data. The default locations for configuration files (e.g.,.config,.pcd,.fcd,.prm,.cdp, etc.) are: \Program Files\Dialogic\data \Program Files\Dialogic\CFG For more information about these files and how they are used, refer to the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide. 2. Identify the directories containing demo configuration files if you want to save this configuration data also. 3. Copy the files you located in Step 1 and Step 2 to a disk or to any directory that is not a subdirectory of the Intel Dialogic installation directory (the default is \Program Files\Dialogic). 4. Write down the information that currently exists in the DCM configuration manager tool so you can refer to it when configuring the new system release. System Release FP1 for Windows Service Update August 22,

115 Installing the Software At this point you must do the following: Uninstall existing software. Refer to Section 4.4, Uninstalling Existing Software, on page 115 Install the System Release Feature Pack 1 Service Update software using either of these procedures: Section 4.5, Installing the Service Update, on page 121 Section 4.6, Performing a Silent Install, on page 122. However, do not reboot until directed to do so in Section 4.3.2, After You Install the Service Update, on page After You Install the Service Update To make use of the configuration data you saved using the procedure in Section 4.3.1, Before You Install the Service Update, on page 114, perform the following: 1. Copy the files you preserved to the corresponding subdirectories in the new installation. Make backup copies of any files you will overwrite. Note: Overwriting new configuration files with old configuration files preserved from a previous release may result in losing some of the new features and fixes of the new release. A better approach may be to compare the old and new configuration files and selectively edit the new configuration file with the specific modified parameters from the old configuration file that you want to preserve. 2. Reboot your computer. You can now proceed with the board configuration process described in the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide. 4.4 Uninstalling Existing Software This section describes what you need to uninstall and how to uninstall it, and contains the following information: Overview of Uninstall Procedures Uninstalling Existing Point Releases, Service Packs, Feature Packs, and Obsolete Service Updates Uninstalling the Base Release Uninstalling the New Version of the System Release Feature Pack 1 Service Update System Release FP1 for Windows Service Update August 22,

116 Installing the Software Overview of Uninstall Procedures If you have an existing (obsolete) version of the System Release Feature Pack 1 Service Update on your system, you must uninstall all point releases, feature packs, and service packs before installing the new Service Update. You must uninstall these programs in the order given in Section 4.4.2, Uninstalling Existing Point Releases, Service Packs, Feature Packs, and Obsolete Service Updates, on page 116. If you had to uninstall any point releases, feature packs, or service packs as described above, it is strongly recommended that you also uninstall the base release (System Release 5.1.1) and run the cleanup utility because the uninstall processes for those older programs could potentially damage the base release files. The procedure for uninstalling the base release and running the cleanup utility is given in Section 4.4.3, Uninstalling the Base Release, on page 117. If you have the new version of System Release Feature Pack 1 Service Update on your system and you want to uninstall it, use the simplified uninstall procedure to remove the Feature Pack and Service Update as described in Section 4.4.4, Uninstalling the New Version of the System Release Feature Pack 1 Service Update, on page Uninstalling Existing Point Releases, Service Packs, Feature Packs, and Obsolete Service Updates This section describes how to remove everything but the base release (System Release 5.1.1), which must be on your system when you install the Service Update. You must have administrative privileges to uninstall this software. To uninstall all existing Point Releases, Service or Feature Packs, and obsolete Service Updates, perform the following: 1. If the Intel Dialogic System is currently running, close all telephony applications that are currently running in the system and stop the Intel Dialogic system. The system is stopped using the DCM configuration tool. From the DCM main window, click the Stop System option from the System pull-down menu or click the Stop All Enabled Devices icon. After you stop the system, close DCM. Note: Make sure you also perform the above step and close the DCM from every remote connection (if applicable). 2. Using Add/Remove Programs, uninstall the following in the order indicated by the numbering of the list: 1. All Point Releases 2. Feature Pack 2 3. The existing (obsolete) version of the System Release Feature Pack 1 Service Update 4. Feature Pack 1 System Release FP1 for Windows Service Update August 22,

117 Installing the Software 5. Service Pack 1 Reboot after you uninstall each of the above programs. Note: During the uninstall of Feature Pack 1, a dialog box appears asking whether shared files should be deleted. Check the box next to Don t display this message again and click Yes. Note: Some programs may not be listed in Add/Remove Programs. You must remove these via the Start menu. If a program does not appear under Add/Remove Programs, check to see if the program appears in the Start menu. Only the base release (System Release 5.1.1) should be left on your system. Note: Do not run the configuration manager (DCM) until after you install the System Release Feature Pack 1 Service Update and reboot. If you run DCM before you install the new Service Update, boards that were not supported in the base release will be displayed with the name????. To fix this, you must re-run DCM after you install the Service Update and reboot. Then select the specific board named???? and select Restore Device Defaults from DCM s Action menu and click Yes. Any configuration changes made on this board will need to be re-entered. It is possible that the removal of these programs may result in a system configuration that is indeterminate. That is, required backup files may not be restored for some reason, resulting in an incomplete or non-functional system configuration. In such cases, you should also remove System Release (refer to Section 4.4.3, Uninstalling the Base Release, on page 117) and then use the cleanup utility provided with the software (in the \cleanup directory) to restore the system to a clean state. You must reboot the system after you run the cleanup utility. To find out more about what this utility does and how to use it, and to obtain updated versions of the utility (which will continue to be enhanced outside of this release), go to Note: The cleanup utility is not a substitute for performing an uninstall. You must uninstall the software before running the cleanup utility. If you remove the base release, you will have to re-install it before installing the Service Update. The procedure for installing System Release is provided in Chapter 2 of the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide Uninstalling the Base Release In some cases, you should uninstall and then re-install the base release before installing the Service Update. For details, refer to Section 4.4.1, Overview of Uninstall Procedures, on page 116. System Release FP1 for Windows Service Update August 22,

118 Installing the Software To uninstall the base release (System Release 5.1.1), perform the following: 1. If the Intel Dialogic System is currently running, close all telephony applications that are currently running in the system and stop the Intel Dialogic system. The system is stopped using the DCM configuration tool. From the DCM main window, click the Stop System option from the System pull-down menu or click the Stop All Enabled Devices icon. After you stop the system, close DCM. Note: Make sure you also perform the above step and close the DCM from every remote connection (if applicable). 2. Before you remove the base release, you must remove the Global Call Protocols package if it is installed on your system. Invoke the Control Panel and select Add/Remove Programs. In the list of currently installed programs, select the name of the Global Call Protocols package. Figure 1 shows an example of what the selected item might look like. Figure 1. Removing the Global Call Protocols 3. Click Change/Remove. 4. A popup will appear asking you to confirm that you really want to uninstall the software. Click Yes to start uninstalling the software. If you don t want to start uninstalling the software, click If you proceed with the uninstall, you will see a progress bar which shows that the software is being uninstalled. 5. When the uninstall is finished, click OK to proceed. 6. A popup tells you that you should reboot to ensure complete removal of the package. It is not necessary to reboot until after you uninstall the base release, so you can click No and proceed to uninstall the base release. 7. Invoke the Control Panel and select Add/Remove Programs. In the list of currently installed programs, select the name of the base release. Figure 2 shows an example of what the selected item might look like. System Release FP1 for Windows Service Update August 22,

119 Installing the Software Figure 2. Removing the Base Release 8. Click Change/Remove. 9. A popup will appear asking you to confirm that you really want to uninstall the software. Click OK to start uninstalling the software. If you don t want to start uninstalling the software, click Cancel. If you proceed with the uninstall, you will see a progress bar which shows that the software is being uninstalled. You might also see messages asking whether you want to delete shared files. If you do, check the box next to Don t display this message again and click Yes. 10. You will be asked if you want to reboot. You must reboot in order for the uninstall to complete. If you don t reboot now, you will need to reboot manually later. After you complete the uninstall process, some registry keys, files, and the Dialogic directory structure will remain on your system, so you may want to run the cleanup utility that is provided with the System Release Feature Pack 1 Service Update software in the \cleanup directory. To find out more about what this utility does and how to use it, and to obtain updated versions of the utility (which will continue to be enhanced outside of this release), go to Note: The cleanup utility is not a substitute for performing an uninstall. You must perform an uninstall before running the cleanup utility. If you are going to install the System Release Feature Pack 1 Service Update, you must re-install the base release (System Release 5.1.1). The procedure for installing System Release is provided in Chapter 2 of the Intel Dialogic System Release Version Feature Pack 1 on PCI and CompactPCI for Microsoft Windows NT/2000/XP on Intel Architecture Installation and Configuration Guide. You must also re-install the Global Call Protocols package if you had uninstalled it. Note: Global Call Protocols Version 4.2 (or earlier) will continue to work on the latest Service Update builds as it has been working with earlier builds. However, it is recommended that you use Global Call Protocols Version 4.3 with the Service Update. For more information, refer to Chapter 3, System Requirements. System Release FP1 for Windows Service Update August 22,

120 Installing the Software Uninstalling the New Version of the System Release Feature Pack 1 Service Update This section describes how to uninstall a Service Update that is packaged and installed together with Feature Pack 1 (the new way of distributing Service Updates). Note: It is recommended that you back up the drive on which the software is installed before you proceed. 1. If the Intel Dialogic system is currently running, close all telephony applications that are currently running in the system and stop the Intel Dialogic system service. The system service is stopped using the configuration manager (DCM). From the DCM main window, click the Stop System option from the System pull-down menu or click the Stop All Enabled Devices icon. Then close DCM by clicking the close button at the upper right corner of the DCM window. Note: Make sure you also perform the above step and close the DCM from every remote connection (if applicable). 2. If you have any Point Releases, you must uninstall them before the Service Update. Invoke the Control Panel and select Add/Remove Programs. In the list of currently installed programs, select the name of the Point Release. 3. Click Change/Remove. 4. When the uninstall process has completed, reboot your computer. 5. Invoke the Control Panel and select Add/Remove Programs. In the list of currently installed programs, select the name of the Service Update. Figure 3 shows an example of what the selected item might look like. Note that there is a link to support information. Figure 3. Removing the Service Update 6. Click Change/Remove. 7. A popup will appear asking you to confirm that you really want to uninstall the software. Click OK to start uninstalling the software. If you don t want to start uninstalling the software, click Cancel. If you click OK, you will see a progress bar which shows that the software is being uninstalled. A Maintenance Complete screen will appear. System Release FP1 for Windows Service Update August 22,

Event Service API for Windows Operating Systems

Event Service API for Windows Operating Systems Event Service API for Windows Operating Systems Programming Guide October 2005 05-1918-003 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY

More information

Dialogic System Release 6.0 PCI for Windows

Dialogic System Release 6.0 PCI for Windows Dialogic System Release 6.0 PCI for Windows Release Update September 28, 2017 05-2221-108 Copyright and Legal Notice Copyright 2004-2017 Dialogic Corporation. All Rights Reserved. You may not reproduce

More information

Multimedia for Host Media Processing Demo

Multimedia for Host Media Processing Demo Multimedia for Host Media Processing Demo Demo Guide September 2005 05-2456-001 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR

More information

Continuous Speech Processing API for Host Media Processing

Continuous Speech Processing API for Host Media Processing Continuous Speech Processing API for Host Media Processing Demo Guide April 2005 05-2084-003 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED,

More information

Intel Dialogic Global Call Protocols Version 4.1 for Linux and Windows

Intel Dialogic Global Call Protocols Version 4.1 for Linux and Windows Intel Dialogic Global Call Protocols Version 4.1 for Linux and Windows Release Notes December 2003 05-1941-002 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Intel Setup and Configuration Service. (Lightweight)

Intel Setup and Configuration Service. (Lightweight) Intel Setup and Configuration Service (Lightweight) Release Notes Version 6.0 (Technology Preview #3) Document Release Date: August 30, 2009 Information in this document is provided in connection with

More information

Continuous Speech Processing API for Linux and Windows Operating Systems

Continuous Speech Processing API for Linux and Windows Operating Systems Continuous Speech Processing API for Linux and Windows Operating Systems Demo Guide November 2003 05-1701-003 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Continuous Speech Processing API for Linux and Windows Operating Systems

Continuous Speech Processing API for Linux and Windows Operating Systems Continuous Speech Processing API for Linux and Windows Operating Systems Demo Guide June 2005 05-1701-005 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Global Call API for Host Media Processing on Linux

Global Call API for Host Media Processing on Linux Global Call API for Host Media Processing on Linux Programming Guide September 2004 05-2346-001 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED,

More information

Intel Cache Acceleration Software for Windows* Workstation

Intel Cache Acceleration Software for Windows* Workstation Intel Cache Acceleration Software for Windows* Workstation Release 3.1 Release Notes July 8, 2016 Revision 1.3 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Dialogic Continuous Speech Processing API

Dialogic Continuous Speech Processing API Dialogic Continuous Speech Processing API Demo Guide May 2008 05-2084-005 Copyright 2005-2008. All rights reserved. You may not reproduce this document in whole or in part without permission in writing

More information

Intel IXP400 Digital Signal Processing (DSP) Software: Priority Setting for 10 ms Real Time Task

Intel IXP400 Digital Signal Processing (DSP) Software: Priority Setting for 10 ms Real Time Task Intel IXP400 Digital Signal Processing (DSP) Software: Priority Setting for 10 ms Real Time Task Application Note November 2005 Document Number: 310033, Revision: 001 November 2005 Legal Notice INFORMATION

More information

Intel Education Theft Deterrent Release Note WW16'14. August 2014

Intel Education Theft Deterrent Release Note WW16'14. August 2014 Intel Education Theft Deterrent Release Note WW16'14 August 2014 Legal Notices Information in this document is provided in connection with Intel products. No license, express or implied, by estoppels

More information

Intel Dialogic Global Call Protocols Version 3.00 for Linux and Windows Release Notes

Intel Dialogic Global Call Protocols Version 3.00 for Linux and Windows Release Notes Intel Dialogic Global Call Protocols Version 3.00 for Linux and Windows Release Notes Copyright 2002 Intel Corporation 05-1451-003 Copyright Notice Copyright 2002 Intel Corporation. All Rights Reserved.

More information

Native Configuration Manager API for Windows Operating Systems

Native Configuration Manager API for Windows Operating Systems Native Configuration Manager API for Windows Operating Systems Library Reference October 2005 05-1903-007 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

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

Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Update Intel Dialogic System Release 6.0 for CompactPCI on Linux Operating Systems Release Update 05-1808-021 System Release 6.0 for cpci on Linux Operating Systems: Release Update INFORMATION IN THIS DOCUMENT

More information

CSTA Gatekeeper Installation and Configuration Guide

CSTA Gatekeeper Installation and Configuration Guide CSTA Gatekeeper Installation and Configuration Guide Order Number: 05-1417-002 Software/Version: CSTA Gatekeeper Version 1.1 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS.

More information

Native Configuration Manager API for Windows Operating Systems

Native Configuration Manager API for Windows Operating Systems Native Configuration Manager API for Windows Operating Systems Library Reference October 2005 05-1903-006 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Intel Setup and Configuration Service Lite

Intel Setup and Configuration Service Lite Intel Setup and Configuration Service Lite Release Notes Version 6.0 Document Release Date: February 4, 2010 Information in this document is provided in connection with Intel products. No license, express

More information

Intel Platform Administration Technology Quick Start Guide

Intel Platform Administration Technology Quick Start Guide Intel Platform Administration Technology Quick Start Guide 320014-003US This document explains how to get started with core features of Intel Platform Administration Technology (Intel PAT). After reading

More information

Dialogic Multimedia API

Dialogic Multimedia API Dialogic Multimedia API Library Reference August 2007 05-2454-002 Copyright 2005-2007, Dialogic Corporation. All rights reserved. You may not reproduce this document in whole or in part without permission

More information

Intel 82580EB/82580DB GbE Controller Feature Software Support. LAN Access Division (LAD)

Intel 82580EB/82580DB GbE Controller Feature Software Support. LAN Access Division (LAD) Intel 82580EB/82580DB GbE Controller Feature Software Support LAN Access Division (LAD) Revision: 1.3 March 2012 Intel 82580EB/82580DB GbE Controller Legal Legal INFORMATION IN THIS DOCUMENT IS PROVIDED

More information

Host Media Processing Conferencing

Host Media Processing Conferencing Host Media Processing Conferencing Demo Guide March 2004 05-2290-001 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE,

More information

OKI ADPCM, linear A-law and µ-law PCM, and Wave

OKI ADPCM, linear A-law and µ-law PCM, and Wave Intel NetStructure Host Media Processing Software Release 1.1 for the Windows* Operating System Media Processing Software for Building Cost-Effective IP Media Servers Features Implemented as a software-only

More information

Native Configuration Manager API for Windows Operating Systems

Native Configuration Manager API for Windows Operating Systems Native Configuration Manager API for Windows Operating Systems Library Reference August 2006 05-1903-008 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

Intel Desktop Board DH55TC

Intel Desktop Board DH55TC Intel Desktop Board DH55TC Specification Update December 2011 Order Number: E88213-006 The Intel Desktop Board DH55TC may contain design defects or errors known as errata, which may cause the product to

More information

Dialogic PowerMedia HMP for Windows Release 3.0

Dialogic PowerMedia HMP for Windows Release 3.0 Dialogic PowerMedia HMP for Windows Release 3.0 Release Update March 27, 2018 05-2508-110 Copyright and Legal Notice Copyright 2006-2018 Dialogic Corporation. All Rights Reserved. You may not reproduce

More information

Third Party Hardware TDM Bus Administration

Third Party Hardware TDM Bus Administration Third Party Hardware TDM Bus Administration for Windows Copyright 2003 Intel Corporation 05-1509-004 COPYRIGHT NOTICE INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE,

More information

Intel Thread Checker 3.1 for Windows* Release Notes

Intel Thread Checker 3.1 for Windows* Release Notes Page 1 of 6 Intel Thread Checker 3.1 for Windows* Release Notes Contents Overview Product Contents What's New System Requirements Known Issues and Limitations Technical Support Related Products Overview

More information

Intel G31/P31 Express Chipset

Intel G31/P31 Express Chipset Intel G31/P31 Express Chipset Specification Update For the Intel 82G31 Graphics and Memory Controller Hub (GMCH) and Intel 82GP31 Memory Controller Hub (MCH) February 2008 Notice: The Intel G31/P31 Express

More information

OA&M API for Linux Operating Systems

OA&M API for Linux Operating Systems OA&M API for Linux Operating Systems Library Reference August 2005 05-1841-004 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR

More information

Intel Dialogic CPi/200B2 and CPi/400B2 Fax Boards

Intel Dialogic CPi/200B2 and CPi/400B2 Fax Boards Intel Dialogic CPi/200B2 and CPi/00B2 Fax Boards The Intel Dialogic CPi/200B2 and CPi/00B2 analog fax boards bring high transmission and reception speeds to enterprise computer-based fax applications like

More information

Dialogic Brooktrout SR140 Fax Software with Microsoft Exchange Server 2010

Dialogic Brooktrout SR140 Fax Software with Microsoft Exchange Server 2010 Dialogic Brooktrout SR140 Fax Software with Microsoft Exchange Server 2010 June 2010 64-0600-20 www.dialogic.com Copyright and Legal Notice Copyright 2010 Dialogic Corporation. All Rights Reserved. You

More information

Dialogic Media Toolkit API

Dialogic Media Toolkit API Dialogic Media Toolkit API Library Reference February 2008 05-2603-002 Copyright 2008,. All rights reserved. You may not reproduce this document in whole or in part without permission in writing from at

More information

Defining and Implementing Station Feature Sets

Defining and Implementing Station Feature Sets Application Note Defining and Implementing Station Feature Sets Intel in Communications Defining and Implementing Station Feature Sets Application Note Contents Executive Summary 1 Introduction 1 Station

More information

Intel Cache Acceleration Software - Workstation

Intel Cache Acceleration Software - Workstation Intel Cache Acceleration Software - Workstation Version 2.7.0 Order Number: x-009 Contents INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY

More information

8 Digital Station Lines

8 Digital Station Lines Dialogic Media Gateway Installation and Configuration Integration Note 1. Scope This document is intended to detail a typical installation and configuration of a Dialogic Media Gateway when used to interface

More information

Dialogic Global Call API

Dialogic Global Call API Dialogic Global Call API Programming Guide September 2008 05-1867-007 Copyright and Legal Notice Copyright 1996-2008. All Rights Reserved. You may not reproduce this document in whole or in part without

More information

Intel Server Compute Blade SBX82

Intel Server Compute Blade SBX82 Intel Server Compute Blade SBX82 Specification Update Intel Order Number D17793-010 December, 2005 Enterprise Platforms and Services Marketing December, 2005 Intel Server Compute Blade SBX82 Specification

More information

Intel NetStructure DMN160TEC ISDN Call Control Performance Testing

Intel NetStructure DMN160TEC ISDN Call Control Performance Testing Application Note Intel NetStructure DMN160TEC ISDN Call Control Performance Testing Intel in Communications Intel NetStructure DMN160TEC Application Note Abstract The Intel NetStructure DMN160TEC network

More information

Intel Dialogic System Release 5.1 Feature Pack 1 and 2 for Linux Operating Systems on Intel Architecture Release Notes

Intel Dialogic System Release 5.1 Feature Pack 1 and 2 for Linux Operating Systems on Intel Architecture Release Notes Intel Dialogic System Release 5.1 Feature Pack 1 and 2 for Linux Operating Systems on Intel Architecture Release Notes Copyright 2004-2007 Intel Corporation 05-2071-025 INFORMATION IN THIS DOCUMENT IS

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DQ77MK, DQ77CP (Standard BIOS) BIOS Version 0071 - MKQ7710H.86A.0071.2015.0728.1443 Date: June 26, 2015 ROM Image 8MB Checksum: 0x5DEAC6DC ROM Image 4MB Checksum: 0x2719FB88

More information

Dialogic TX Series SS7 Boards

Dialogic TX Series SS7 Boards Dialogic TX Series SS7 Boards Loader Library Developer s Reference Manual July 2009 64-0457-01 www.dialogic.com Loader Library Developer's Reference Manual Copyright and legal notices Copyright 1998-2009

More information

753 Broad Street Phone: Suite 200 Fax: Augusta, GA Copyrights

753 Broad Street Phone: Suite 200 Fax: Augusta, GA Copyrights Ipswitch, Inc. Web: www.imailserver.com 753 Broad Street Phone: 706-312-3535 Suite 200 Fax: 706-868-8655 Augusta, GA 30901-5518 Copyrights 1995-2011 Ipswitch, Inc. All rights reserved. IMail Collaboration

More information

Dialogic Multimedia API

Dialogic Multimedia API Dialogic Multimedia API Library Reference March 2008 05-2454-001_D Copyright 2005-2008. All rights reserved. You may not reproduce this document in whole or in part without permission in writing from.

More information

BIOS Update Release Notes

BIOS Update Release Notes PRODUCTS: DQ77KB (Standard BIOS) BIOS Update Release Notes BIOS Version 0059 - KBQ7710H.86A.0059.2017.0526.1645 Date: May 26, 2017 ME Firmware: 8.1.71.3608 Updated Intel ME firmware to version 8.1.71.3608.

More information

Intel Desktop Board D945GCLF2

Intel Desktop Board D945GCLF2 Intel Desktop Board D945GCLF2 Specification Update July 2010 Order Number: E54886-006US The Intel Desktop Board D945GCLF2 may contain design defects or errors known as errata, which may cause the product

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: STCK1A32WFC, STCK1A8LFC (Standard BIOS) BIOS Version 0038 - FCBYT10H.86A.0038.2018.0802.1745 Date: August 2, 2018 Memory Reference Code: Based on 1.02 Integrated Graphics:

More information

Migration Guide: Numonyx StrataFlash Embedded Memory (P30) to Numonyx StrataFlash Embedded Memory (P33)

Migration Guide: Numonyx StrataFlash Embedded Memory (P30) to Numonyx StrataFlash Embedded Memory (P33) Migration Guide: Numonyx StrataFlash Embedded Memory (P30) to Numonyx StrataFlash Embedded Memory (P33) Application Note August 2006 314750-03 Legal Lines and Disclaimers INFORMATION IN THIS DOCUMENT IS

More information

BIOS Update Release Notes

BIOS Update Release Notes PRODUCTS: DB85FL (Standard BIOS) BIOS Update Release Notes BIOS Version 0131 - FLB8510H.86A.0131.2017.0516.1705 Date: May 16, 2017 ROM Image 8MB Checksum: 0x591F0D92 ROM Image 4MB Checksum: 0x2E8ED563

More information

IEEE1588 Frequently Asked Questions (FAQs)

IEEE1588 Frequently Asked Questions (FAQs) IEEE1588 Frequently Asked Questions (FAQs) LAN Access Division December 2011 Revision 1.0 Legal INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED,

More information

BIOS Update Release Notes

BIOS Update Release Notes PRODUCTS: DH87RL (Standard BIOS) BIOS Update Release Notes BIOS Version 0331 - RLH8710H.86A.0331.2018.0327.1252 Date: March 27, 2018 Integrated Graphics: Option ROM: Build 2179 PC 14.34 SATA RAID UEFI

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: STCK1A32WFC, STCK1A8LFC (Standard BIOS) BIOS Version 0035 - FCBYT10H.86A.0035.2017.0118.1421 Date: January 18, 2017 Memory Reference Code: Based on 1.02 Integrated Graphics

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: D525MW, D525MWV, D425KT, D425KTW (Standard BIOS) BIOS Version 0132 - MWPNT10N.86A.0132.2013.0726.1534 Date: July 26, 2013 Fixed issue where system hangs when plugging

More information

Intel Manageability Commander User Guide

Intel Manageability Commander User Guide Intel Manageability Commander User Guide Document Release Date: October 27, 2016 Legal Information INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED,

More information

Intel Active Management Technology Release 1.0 Host Interface Design Guide

Intel Active Management Technology Release 1.0 Host Interface Design Guide Intel Active Management Technology Release 1.0 Host Interface Design Guide Version 4.0.0 February 2008 Information in this document is provided in connection with Intel products. No license, express or

More information

Intel IXP400 Software Version 1.5

Intel IXP400 Software Version 1.5 Intel IXP400 Software Version 1.5 Order Number: 308225, Revision: 001 Legal Notice Legal Lines and Disclaimers INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

ADEPT for PBX Integration Boards

ADEPT for PBX Integration Boards ADEPT for PBX Integration Boards User s Guide May 2006 Copyright 2006 Intel Corporation 05-2520-001 COPYRIGHT NOTICE INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE,

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DQ77MK, DQ77CP (Standard BIOS) BIOS Version 0062 - MKQ7710H.86A.0062.2013.0902.1328 Date: September 2, 2013 Fixed issue where BIOS password prompt is not displayed when

More information

BIOS Update Release Notes

BIOS Update Release Notes PRODUCTS: DG35EC (Standard BIOS) BIOS Update Release Notes BIOS Version 0118 January 13, 2010 ECG3510M.86A.0118.2010.0113.1426 Fixed unexpected behavior in resume from standby. BIOS Version 0117 July 31,

More information

Intel Desktop Board DZ68DB

Intel Desktop Board DZ68DB Intel Desktop Board DZ68DB Specification Update April 2011 Part Number: G31558-001 The Intel Desktop Board DZ68DB may contain design defects or errors known as errata, which may cause the product to deviate

More information

Installation Guide and Release Notes

Installation Guide and Release Notes Intel C++ Studio XE 2013 for Windows* Installation Guide and Release Notes Document number: 323805-003US 26 June 2013 Table of Contents 1 Introduction... 1 1.1 What s New... 2 1.1.1 Changes since Intel

More information

Global Call IP for Host Media Processing

Global Call IP for Host Media Processing Global Call IP for Host Media Processing Technology Guide January 2005 05-2239-004 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DQ57TM, DQ57TML (Standard BIOS) BIOS Version 0046 - TMIBX10H.86A.0046.2011.0722.0944 Date: July 22, 2011 Integrated Graphics Option ROM Revision on TM: 2114 PC Integrated

More information

Dialogic TX 4000 Series SS7 Boards

Dialogic TX 4000 Series SS7 Boards The Dialogic TX 4000 Series SS7 Boards offer a range of form factor, throughput capacity, and signaling protocol support with Dialogic NaturalAccess Software. The TX 4000 Series architecture combines TDM

More information

Listed below are the specific details of the PBX and gateways used in the testing to construct the following documentation.

Listed below are the specific details of the PBX and gateways used in the testing to construct the following documentation. Dialogic Media Gateway Installation and Configuration Integration Note 1. Scope This document is intended to detail a typical installation and configuration of Dialogic 2000 Media Gateway Series (DMG2000)

More information

IMPORTANT NOTE. Dialogic Brooktrout SR140 Fax Software with Broadvox SIP Trunking Service. Installation and Configuration Integration Note

IMPORTANT NOTE. Dialogic Brooktrout SR140 Fax Software with Broadvox SIP Trunking Service. Installation and Configuration Integration Note Dialogic Brooktrout SR140 Fax Software with Broadvox SIP Trunking Service IMPORTANT NOTE This document is not to be shared with or disseminated to other third parties, in whole or in part, without prior

More information

Application Note. A Performance Comparison of Dialogic DM3 Media Boards for PCI Express and PCI

Application Note. A Performance Comparison of Dialogic DM3 Media Boards for PCI Express and PCI A Performance Comparison of Dialogic DM3 Media Boards for PCI Express and PCI Executive Summary This application note compares the performance of the Dialogic DM3 Media Boards for PCI with the newer DM3

More information

Dialogic Media Gateway Installation and Configuration Integration Note

Dialogic Media Gateway Installation and Configuration Integration Note Dialogic Media Gateway Installation and Configuration Integration Note This document is intended to detail a typical installation and configuration of the Dialogic 2000 Media Gateway Series (DMG2000) when

More information

Intel Server Board S2600CW2S

Intel Server Board S2600CW2S Redhat* Testing Services Enterprise Platforms and Services Division Intel Server Board S2600CW2S Server Test Submission (STS) Report For Redhat* Certification Rev 1.0 This report describes the Intel Server

More information

Application Note. Dialogic 1000 Media Gateway Series Serial CPID Configuration and Timing

Application Note. Dialogic 1000 Media Gateway Series Serial CPID Configuration and Timing Application Note Dialogic 1000 Media Gateway Series Serial CPID Configuration and Timing Application Note Dialogic 1000 Media Gateway Series Serial CPID Configuration and Timing Executive Summary The Dialogic

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DH67BL, DH67CF, DH67CL, DH67GD, DH67VR (Standard BIOS) BIOS Version 0132 - BLH6710H.86A.0132.2011.1007.1505 Date: Oct 07, 2011 ME Firmware: 7.1.20.1119 Integrated Graphics

More information

Intel NetStructure Host Media Processing Software Release 1.1 for Windows Service Update

Intel NetStructure Host Media Processing Software Release 1.1 for Windows Service Update Intel NetStructure Host Media Processing Software Release 1.1 for Windows Service Update Release Notes Copyright 2005 Intel Corporation 05-2294-004 Copyright Notice Copyright 2005 Intel Corporation. All

More information

Intel NetStructure Host Media Processing Software Release 1.2 for Linux Operating Systems

Intel NetStructure Host Media Processing Software Release 1.2 for Linux Operating Systems Datasheet Telecom Software Intel NetStructure Host Media Processing Software Release 1.2 for Linux Operating Systems Media Processing Software for Building Cost-Effective IP Media Servers Introduction

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DP67BA, DP67DE (Standard BIOS) BIOS Version 0082 - BAP6710H.86A.0082.2018.0412.1527 Date: April 12, 2018 ME Firmware: 7.1.60.1193, 8.0.13.1502 SATA RAID Option ROM:

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DH67BL, DH67CF, DH67CL, DH67GD, DH67VR (Standard BIOS) BIOS Version 0160 - BLH6710H.86A.0160.2012.1204.1156 Date: December 4, 2012 ME Firmware: 7.1.60.1193, 8.0.13.1502

More information

Intel Desktop Board D945GCLF

Intel Desktop Board D945GCLF Intel Desktop Board D945GCLF Specification Update July 2010 Order Number: E47517-008US The Intel Desktop Board D945GCLF may contain design defects or errors known as errata, which may cause the product

More information

Dialogic Host Media Processing Software Release 3.1LIN

Dialogic Host Media Processing Software Release 3.1LIN Dialogic Host Media Processing Software Release 3.1LIN Software Installation Guide January 2009 05-2598-002 Copyright and Legal Notice Copyright 2007-2009,. All Rights Reserved. You may not reproduce this

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DZ87KLT-75K (Standard BIOS) BIOS Version 0453 - KLZ8711D.86A.0453.2014.1007.1848 Date: October 7, 2014 Visual Bios: 2.2.5 Production Candidate Build This BIOS includes

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: D53427RKE, DC53427HYE (Standard BIOS) BIOS Version 0052 - RKPPT10H.86A.0052.2018.0719.1935 Date: July 19, 2018 ME Firmware:8.1.72.3002 Integrated Graphics: Option ROM:

More information

BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS)

BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS) BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS) BIOS Version 0069 - SWQ6710H.86A.0069.2018.0410 Date: April 10, 2018 ME Firmware: 5MB SKU 7.1.91.3272 Production Updated CPU Microcode

More information

GUID Partition Table (GPT)

GUID Partition Table (GPT) GUID Partition Table (GPT) How to install an Operating System (OS) using the GUID Disk Partition Table (GPT) on an Intel Hardware RAID (HWR) Array under uefi environment. Revision 1.0 December, 2009 Enterprise

More information

Intel Manycore Platform Software Stack (Intel MPSS)

Intel Manycore Platform Software Stack (Intel MPSS) Intel Manycore Platform Software Stack (Intel MPSS) README (Windows*) Copyright 2012 2014 Intel Corporation All Rights Reserved Document Number: 328510-001US Revision: 3.4 World Wide Web: http://www.intel.com

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: D53427RKE, DC53427HYE (Standard BIOS) BIOS Version 0050 - RKPPT10H.86A.0050.2018.0321.1337 Date: March 21, 2018 ME Firmware: 8.1.72.3002 Integrated Graphics: o Option

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DH67BL, DH67CF, DH67CL, DH67GD, DH67VR (Standard BIOS) BIOS Version 0163 - BLH6710H.86A.0163.2018.1023.1559 Date: October 23, 2018 ME Firmware: 7.1.60.1193, 8.1.20.1336

More information

Intel NetStructure IPT Series on Windows

Intel NetStructure IPT Series on Windows Intel NetStructure IPT Series on Windows Configuration Guide November 2002 05-1752-001 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL

More information

Authentication Services ActiveRoles Integration Pack 2.1.x. Administration Guide

Authentication Services ActiveRoles Integration Pack 2.1.x. Administration Guide Authentication Services ActiveRoles Integration Pack 2.1.x Administration Guide Copyright 2017 One Identity LLC. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright.

More information

BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS)

BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS) BIOS Update Release Notes PRODUCTS: DQ67SW, DQ67OW, DQ67EP (Standard BIOS) BIOS Version 0057 - SWQ6710H.86A. 0057.2011.1111.1537 Date: November 11, 2011 ME Firmware: 5MB SKU 7.1.20.1119 Production Integrated

More information

How to Create a.cibd/.cce File from Mentor Xpedition for HLDRC

How to Create a.cibd/.cce File from Mentor Xpedition for HLDRC How to Create a.cibd/.cce File from Mentor Xpedition for HLDRC White Paper August 2017 Document Number: 052889-1.2 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE,

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: DZ87KLT-75K (Standard BIOS) BIOS Version 0458 - KLZ8711D.86A.0458.2018.0329.1136 Date: March 29, 2018 : : Updated CPU Microcode (Security Advisory-00088). BIOS Version

More information

Intel Solid State Drive Client PCIe* Microsoft* Windows* Driver

Intel Solid State Drive Client PCIe* Microsoft* Windows* Driver Intel Solid State Drive Client PCIe* Microsoft* Windows* Driver Software 3.2.0.1002 Number: 331995-006US Intel may make changes to specifications and product descriptions at any time, without notice. Designers

More information

Intel SRCS28X RAID Controller 814G Firmware Upgrade for Intel Storage System SSR316MJ+

Intel SRCS28X RAID Controller 814G Firmware Upgrade for Intel Storage System SSR316MJ+ Intel SRCS28X RAID Controller 814G Firmware Upgrade for Intel Storage System SSR316MJ+ Firmware Release Notes Revision 1.0 October, 2006 Storage Systems Technical Marketing 2 Revision HistoryIntel SRCS28X

More information

Intel Theft Deterrent Client User Guide

Intel Theft Deterrent Client User Guide Intel Theft Deterrent Client User Guide Legal Notices Information in this document is provided in connection with Intel products. No license, express or implied, by estoppels or otherwise, to any intellectual

More information

LED Manager for Intel NUC

LED Manager for Intel NUC LED Manager for Intel NUC User Guide Version 1.0.0 March 14, 2018 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO

More information

BIOS Update Release Notes

BIOS Update Release Notes PRODUCTS: DB65AL (Standard BIOS) BIOS Update Release Notes BIOS Version 0056 - ALB6510H.86A.0056.2017.0601.1655 Date: June 01, 2017 ME Firmware: 5MB SKU 7.1.91. 3272 Production Updated Intel ME firmware

More information

Installing Dialogic NaturalAccess SS7 Monitor Software 3.0

Installing Dialogic NaturalAccess SS7 Monitor Software 3.0 Installing Dialogic NaturalAccess SS7 Monitor Software 3.0 August 2009 64-0465-01 www.dialogic.com Copyright and legal notices Copyright 2004-2009 Dialogic Corporation. All Rights Reserved. You may not

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: STK1AW32SC, STK1A32SC (Standard BIOS) BIOS Version 0041 - SCCHTAX5.86A.0041.2018.0620.1803 Date: June 08, 2018 XE Firmware: 2.00.05.3105 Security enhancements. Added

More information

Intel IXP400 Software Version 2.1

Intel IXP400 Software Version 2.1 Intel IXP400 Software Version 2.1 Order Number: 310288, Revision: 001 Legal Notice Legal Lines and Disclaimers INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS

More information

BIOS Update Release Notes

BIOS Update Release Notes BIOS Update Release Notes PRODUCTS: NUC5i5MYBE, NUC5i5MYHE (Standard BIOS) BIOS Version 0049 - MYBDWi5v.86A.0049.2018.1107.1046 Date: November 7, 2018 ME Firmware: 10.0.56.3002 Fixed issue where system

More information

Dialogic Media Gateway Installation Site Survey

Dialogic Media Gateway Installation Site Survey Dialogic Media Gateway Installation Site Survey 1. Scope This document is provided by Dialogic for you to use if implementing Microsoft Office Communications Server 2007 or Microsoft Exchange Server 2007

More information