User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 379
Dialogic Corporation
Update to gc_DropCall( ) (PTR# 34237)
On the gc_DropCall( ) function reference page, the following caution should be
added:
• With CAS protocols, the GCEV_DROPCALL event may be delayed when gc_DropCall( ) is
called. GCEV_DROPCALL is sent to the application only when the channel becomes Idle.
This is expected behavior of a CAS protocol. In the Offered state (ringing), there is no way for
the receiving side to tell the calling side to stop ringing. It will not happen until the CO times
out (ring no answer) and drops their bits to IDLE. That is why the GCEV_DROPCALL event
may seem to be “delayed” in this situation; it is affected by the time-out time governed by CO.
Updates to gc_GetCallInfo( )
Because of a new feature in the Service Update, the gc_GetCallInfo( )
CATEGORY_DIGIT parameter is now supported on Dialogic
®
DM3 Boards. The
gc_GetCallInfo( ) function reference page (in particular, Table 6, gc_GetCallInfo( )
info_id Parameter ID Definitions) should be updated to indicate this.
Because of a new feature in the Service Update, a new billing type has been added to
CALLINFOTYPE called “CHARGE WITH CLEARING FROM INBOUND.” The
gc_GetCallInfo( ) function reference page (in particular, Table 6, gc_GetCallInfo( )
info_id Parameter ID Definitions) should be updated to indicate this. In addition,
gc_GetCallInfo(CALLINFOTYPE) is now supported on Dialogic
®
DM3 Boards. For
information about this feature and the new billing type, see Section 1.27, “Support for
Reporting Billing Type”, on page 92 of this Release Update.
Update to gc_GetLinedevState( ) (PTR# 32616)
In the gc_GetLinedevState( ) function example, there is an error in two of the printf
statements.
Instead of:
printf("D Channel Status: %s\n", statebuf);
printf("B Channel Status: %s\n", statebuf);
the %s arguments should be changed to %d. The correct statements are:
printf("D Channel Status: %d\n", statebuf);
printf("B Channel Status: %d\n", statebuf);
Update to gc_InitXfer( ) (IPY00038401)
In the code example, the gc_InitXfer( ) parameters are shown in the wrong order. The
line:
if (gc_InitXfer(pline->crn, NULL, &gc_pRetParmBlk, EV_ASYNC) == -1)
should be changed to:
if (gc_InitXfer(pline->crn, &gc_pRetParmBlk, NULL, EV_ASYNC) == -1)
Updates to gc_MakeCall( )
On the gc_MakeCall( ) function reference page, the following caution should be
added (PTR# 33852):
• In synchronous mode, calls to gc_MakeCall( ) must be serialized. Multiple gc_MakeCalls
cannot be made on the same channel from multiple threads.
On the gc_MakeCall( ) function reference page, on page 226, there is a change to
the following paragraph (PTR# 35965):
In the asynchronous mode, if the function is successfully initiated but connection is not achieved
(no GCEV_CONNECTED event returned), then the application must issue gc_DropCall( ) and