SR 6.0 PCI Windows SU211 available

Post-Release developments:

*New Dialogic® D/42 API function for dialing



Resolved defects:



IPY00045191 - Application error occurs when cc_StartTrace( ) is called right after cc_StopTrace( ).



IPY00045176 - When using the Dialogic® System Release Software version for Windows Vista® and Windows Server® 2008, DCM does not detect Dialogic® Springware Boards in a Windows Server 2008 system.



IPY00045159 - When using the PSTN Diagnostics tool (pstndiag), the

following error occurs after clicking on a channel of an installed Dialogic® DM3 PSTN Board: “Error: Can't read alarms Trans (0x1616): no such element in array.”



IPY00045146 - Problems occur when shutting down a Windows Server® 2008 system with Dialogic® Springware Boards and a USB modem installed. The system does not shut down completely, and a blue screen occurs.



IPY00045136 - When using Dialogic® D/120JCT Media Board under heavy CSP channel utilization, a firmware assertoccurred.



IPY00045132 - Under heavy load on certain Dialogic® DM3 PSTN Boards, calls that are offered to channels might get dropped immediately. They moved from Answering to Disconnected state due to an overlapping of call indexes among multiple network interfaces.



IPY00045128- Blue screen occurs on a specific PCI system using Windows® 2003 SP1 or SP2, when detecting Dialogic® D/240JCT-T1 Board in DCM.



IPY00044932 - A voice stuck channel occurred during a playback operation while running an application that is media intensive (plays/records) due to an internal race condition. No TDX_PLAY event is returned to the application after dx_playiottdata( ) is issued.



IPY00044832 - Under certain conditions and tone templates for a dx_playtone( ) in asynchronous mode, the application does not receive the TDX_PLAYTONE event on the voice channel.



IPY00044811 - A voice stuck channel occurred during a playback operation while running an application that is media intensive (plays/records) due to an internal race condition. No TDX_PLAY event is returned to the application after dx_playiottdata( ) is issued.



IPY00044730 - When using Dialogic® DM3 Boards and ISDN protocol, the incorrect number of called subaddress digits is received by the application. An 8-digit called subaddress was initially sent by the switch, but the application received a 6-digit called subaddress.



IPY00044614 - A potential voice stuck channel condition that could occur on Dialogic® DM/V-B Boards during a record (dx_reciottdata( )) operation was caused by a race condition in the record data stream handling when a stop channel (dx_stopch( )) is issued to terminate the operation.



IPY00044561 - A voice stuck channel condition occurred, caused by the unhandling of tone creation failures during the setting of tone termination conditions for a playback

(dx_playiottdata( )) or record (dx_reciottdata( )) operation. In asynchronous mode the TDX_PLAY or TDX_RECORD events, respectively, would never be received.



IPY00044251- A firmware assert occurred on the Dialogic® D/82JCTU PBX Integration Board, when setting the MWI on a Nortel Norstar phone system PBX.