User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 389
Dialogic Corporation
IPCCLIB_START_DATA data structure reference page
In the absence of the INIT_IPCCLIB_START_DATA( ) and INIT_IP_VIRTBOARD( )
functions, the user must manually initialize the IP_VIRTBOARD and
IPCCLIB_START_DATA data structures before calling gc_Start( ). Refer to the
reference pages for these structures for more details.
Update for IP_H221NONSTANDARD data structure
On the reference page for the IP_H221NONSTANDARD data structure (page 182),
the descriptions of the three data fields are updated as follows:
country_code
The country code. Range: 0 to 255; any value x>255 is treated as x%256.
extension
The extension number. Range: 0 to 255; any value x>255 is treated as x%256.
manufacturer_code
The manufacturer code. Range: 0 to 65535; any value x>65535 is treated as x%65636.
3.4.15 Dialogic
®
Global Call ISDN Technology Guide
Updates for Two B Call Transfer Support (IPY00006590 = PTR# 36501)
Section 1.2, ISDN Features and Benefits, provides incorrect information about Two
B Call Transfer (TBCT) and the level of support provided by Dialogic
®
Global Call
Software. The following is the correct information:
TBCT is a National ISDN-2 (NI2) supplementary service described in the Telcordia GR 2865
standard. The feature enables a user to request the switch to connect together two independent calls
on the user's interface. The user who made the request is released from the calls and the other two
users are directly connected. This feature is supported on 5ESS and DMS switches provisioned to
implement NI2; see Section 3.1, “General ISDN Call Scenarios”, for details.
Section 3.1.23, Network Facility Request - Two B Channel Transfer
(Synchronous Mode) provides the following incorrect statement about TBCT
support: “(this feature is supported for the 5ESS and 4ESS protocols only).” The
correct statement is: “(this feature is supported for 5ESS and DMS switches
implementing the NI2 protocol only).
Dynamically retrieving and modifying selected protocol parameters when using Dialogic
®
DM3 Boards
Because of a new feature in the Service Update, information about retrieving a
protocol ID should be added in the ISDN-Specific Operations chapter. Also,
additional subsections should be added under Using Dynamic Trunk Configuration
for setting the line type and coding for a trunk, and specifying the protocol for a trunk.
For information about this feature, see Section 1.42, “Dynamically Retrieving and
Modifying Selected Protocol Parameters When Using Dialogic
®
DM3 Boards”, on
page 113 of this Release Update. In particular, see Section 1.42.1.2, “Retrieving a
Protocol ID”, on page 115 and Section 1.42.1.6, “Dynamically Configuring a Trunk”,
on page 129.
Support for QSIG NCAS on Dialogic
®
DM3 Boards
Because of a new feature in the Service Update, information regarding support for
making and receiving NCAS calls using the QSIG protocol on Dialogic
®
DM3 Boards