User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 333
Dialogic Corporation
Resolved IPY00008592 32678 18 Springware
Firmware
Two bytes of corrupt data are observed in the D-
channel trace whenever cc_SetInfoElem( ) is called
to set the value for the CALLING_LINE_ID number in
a SETUP message.
Resolved IPY00008537 32161 18 Springware
Firmware
CTR4 firmware responds with STATUS message
when Calling Party Subaddress contains 0xF9 (or
similar value). On some networks, the status message
may cause the network to tear down the call.
Resolved IPY00007984 32104 18 Springware
Firmware
When running into PDK R2 glare conditions, false
R2MF time-outs occur in the spanplus firmware,
resulting in calls not connecting properly.
Resolved IPY00007421 25633 18 Springware
Firmware
Incorrect response to Release message when using
Dialogic
®
D/600JCT-2E1 Board.
Resolved IPY00007308 31896 22 Springware
Firmware
On a Dialogic
®
D/82JCTU Board using CSP firmware,
multiple channels dialing at the same time cause the
board to become non-responsive and report device
busy errors. The system stops responding with an
assert.
Resolved IPY00007241 31840 18 Springware
Firmware
When there is a call collision between an outbound
and inbound call, gc_GetSigInfo(...U_IES...)
sometimes fails with error 0x303=Information not
available. The functions gc_GetANI( ) and
gc_GetDNIS( ) return the correct information.
Resolved IPY00007235 29328 18 Springware
Firmware
When using gc_SetInfoElem( ) to set the calling party
number in a SETUP message, the first two digits are
missing.
Resolved IPY00041345 -- 178 Springware ISDN
Firmware
Firmware assert occurs due to zero length User-User
IE message, and Dialogic
®
board stops responding to
the switch.
Table 9. Issues Sorted By Type, Dialogic
®
System Release 6.0 PCI for Windows
®
(Continued)
Issue Type Defect No.
PTR
No.
SU
No.
Dialogic
®
Product(s) or
Component(s)
Description