User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 322
Dialogic Corporation
Resolved IPY00030679 33146 18 Protocols When using the pdk_us_mf_io protocol, the
GCEV_UNBLOCKED event is not generated when
Layer 1 alarms are cleared after the channel is put
OOS.
Resolved IPY00028595 35538 70 Protocols Basic call control using Korea GDS LS protocol does
not work on Dialogic
®
Springware Boards.
Resolved IPY00028584 35809 84 Protocols A6 should be a terminating tone for pdk_in_r2_io.cdp
protocol.
Resolved IPY00028497 36042 84 Protocols With South Africa with pdk_sw_e1_ac4400_io.cdp, a
disconnect tone does not get detected.
Resolved IPY00028454 36090 84 Protocols When using Lucent Lineside E1 PDK protocol, the
gc_RetrieveCall( ) function failed to transfer the call
state from GCST_ONHOLD to GCST_CONNECTED.
Resolved IPY00028411 34284 84 Protocols When using 5ESS protocol with Dialogic
®
Springware
Boards, outbound calls fail with Cause Value 1100100,
invalid information element, in response to the
Proceeding and Progressing message received.
Resolved IPY00028378 34586 56 Protocols For inbound call, channel is blocked after the remote
caller hangs up before sending DNIS, when using
pdk_hk_dtmf_io.cdp.
Resolved IPY00028363 36020 84 Protocols Dialogic
®
Springware T1 Boards send incorrect
“Interface ID present” to remote side when using T1
ISDN (DMS, 4ESS, 5ESS).
Resolved IPY00028277 32444 18 Protocols A GCEV_MEDIADETECTED event is not generated
on the Dialogic
®
DM/V160-LP Board even though the
call is answered at around 30 seconds.
Resolved IPY00010746 35042 56 Protocols When using the pdk_us_mf_io protocol, if
CDP_OUT_Send_Alerting_After_Dialing = 1 and CPA
is disabled, the user expects to get the
GCEV_ALERTING event right after dialing. However,
if the remote side answers the call too quickly, the
GCEV_CONNECTED event is returned and the
GCEV_ALERTING event never comes in.
Resolved IPY00010664 34063 27 Protocols When you configure a Dialogic
®
DM3 Board with ISDN
4ESS for USER and NETWORK side, the ANI cannot
be extracted properly on an incoming call using
gc_GetCallInfo( ).
Resolved IPY00010621 34537 56 Protocols When using the pdk_us_mf_io protocol in the Feature
Group D configuration, ANI is missing the last digit
when ANI is not terminated with the expected ST digit.
Resolved IPY00010520 34048 27 Protocols When you configure a Dialogic
®
DM3 Board with ISDN
5ESS for the NETWORK side, the ANI cannot be
extracted properly on an incoming call using
gc_GetCallInfo( ).
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