User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 395
Dialogic Corporation
Update to Section 3.1.24, Non-Call Associated Signaling (Synchronous Mode)
(PTR# 32165 and PTR# 35249)
In Section 3.1.24, Non-Call Associated Signaling (Synchronous Mode) on page
70, the first two paragraphs provide incorrect information. The following paragraphs
provide the correct information:
Non-Call Associated Signaling (NCAS) allows users to communicate by user-to-user signaling
without setting up a circuit-switched connection (this signaling does not occupy B channel
bandwidth). A temporary signaling connection is established (and cleared) in a manner similar to
the control of a circuit-switched connection. The NCAS feature is supported for 4ESS, 5ESS,
CTR4, and QSIG protocols.
Since NCAS calls are not associated with any B channel, applications should receive and transmit
NCAS calls on the D channel. For T1 interfaces, this is channel 24, that is, dtiB#T24. For E1
interfaces, there is no channel (dtiB#T#) that corresponds to a D channel line device, therefore
NCAS calls (identified by the Bearer Capabilities IE content) are automatically associated with the
D channel internally on dtiB#T30. Once the NCAS connection is established, the application can
transmit user-to-user messages using the CRN associated with the NCAS call. The Dialogic
®
software and firmware support 16 simultaneous NCAS calls per D channel.
Application
Device
Driver
Network
State
Firmware
CONNECTED
gc_DropCall ( )*
Driver Releases
CRN Return
F/W Releases CRN
CALL_DEALLOC_ACK
CALL_CLEAR
IDLE
Disc
Release
CALL_DISCONNECTED
Rel_Comp
Call_Dealloc
ISDN_Block_Ts
(Sync Model Only)
DISCONNECTED
Call_Disconnected
(Cause Value = 0)
GCEV_DISCONNECTED
Firmware Does
Nothing Until
Release is Sent
GCEV_DROPCALL
gc_ReleaseCall ( )**
NULL
Notes:
* = Application Should Set a "Drop Call" Flag
** = Application should ignore GCEV _DISCONNECTED if "Drop Call" Flag is Set
***= gc_ReleaseCall ( ) always clears "Drop Call" Flag