Diva QSIG abstraction

This commit is contained in:
MelwareDE 2010-09-15 06:36:40 +00:00
parent 83ba42f167
commit 6611940b58
1 changed files with 15 additions and 0 deletions

View File

@ -14,6 +14,13 @@ equipment Dialogic(R) Diva(R) interfaces as well.
The coding of the messages and the type of the transfer invoked, depends
on the QSIG dialect and on the vendor-specific implementation of QSIG dialect.
+-------------------------------------------------------------------+
| Use Diva QSIG abstraction with chan_capi |
+-------------------------------------------------------------------+
To use Diva QSIG abstraction please do not set (remove if set) 'qsig'
configuratioin variable(s) from capi.conf.
+-------------------------------------------------------------------+
| QSIG abstraction |
+-------------------------------------------------------------------+
@ -21,6 +28,14 @@ on the QSIG dialect and on the vendor-specific implementation of QSIG dialect.
Dialogic(R) Diva(R) System Release Software abstraction allows to write
QSIG applications independent of the used QSIG dialect.
Name and Display information elements
Name (Calling Pary Name, Called Party Name, Connected Party Name,
Busy Party Name) and Display information elementss are converted to protocol
independent format and delivered to (received from) application using
Diva manufacturer extensions. Information elements encoded as facility array
(for example in CONNECT_REQ) are converted in accordance with rules of active
QSIG protocol.
Unassisted call transfer:
The application can use CAPI call deflection. The Diva System Release software
will automatically translate the call deflection request in the appropriate