Bearer Independent Call Control (BICC)

The following preliminary manual pages will be available:

bicc(4) , BICC driver manpage;
bicci(7) , BICC interface manpage;
cci_bicc(7) , BICC CCI interface manpage;
bicc_ioctl(4) , BICC IO Controls manpage;
bicc(8) , BICC administration manpage.

BICC

Section: The OpenSS7 Project Devices (4)
Updated: Tue, 18 Nov 2008 11:04:40 GMT
Index Return to Main Contents

NAME

bicc - Bearer Independent Call Control (BICC) Device Driver

SYNOPSIS

#include <ss7/cci.h>
#include <ss7/bicci.h>
#include <ss7/bicci_ioctl.h>

int bicc_stream = open(device, flags);

DESCRIPTION

BICC
is an implementation of Signalling System No. 7 (SS7(4)) Bearer Independent Call Control (BICC) defined in ITU-T Recommendation Q.BICC and ANSI T1.BICC. BICC provides call control of telephone calls over the ISDN where the bearer is non-traditional. BICC can use the services of the Message Transfer Part (see mtp(4)) to transfer packets using, for example, Annex C/T1.BICC.4-2000 operation. BICC can also use the services of SSCOP or SSCOPMCE (see sccop (4)) to transfer packets using, for example, Annex D/T1.BICC.4-2000 operation.

BICC is implemented as a STREAMS(4) multiplexing driver. mtp(4), m3ua(4), tali(4) or sscop(4) streams are linked under the BICC multiplexing driver using the I_LINK or I_PLINK commands of streamio(7), to provide network services to BICC. Once linked, the streams must be configured using bicc_ioctl(4) IO controls. This function is normally performed by the SS7 configuration daemon, ss7confd(8). See also, bicc(8).

BICC provides the following stream types. To select one of the stream types, the device argument to the open(2) call can be one of the following:

/dev/bicc: This device provides the BICC protocol services using the CC-primitives of the Call Control Interface (CCI) described in cci(7), as integrated for use with BICC as described in cci_bicc(7). This interface is suitable both for use with other SS7 modules and drivers, as well as with the cframe(3) library using the OpenSwitch call framework.

Unlike other SS7 protocol modules and drivers tat the transport level, BICC does not provide a sockets(3) interface. THis is because the special needs of call control are divorced from the sockets paradigm.

IOCTLS

All interfaces support a set of Local Management Interface IO controls using ioctl(2) and I_STR streamio(7) system calls on the bicc_stream file descriptor. The common Local Management Interface IO commands are described in lmi_ioctl(4). The management structure and constant definitions for BICC are described in bicc_ioctl(4).

FILES

<ss7/cci.h>, <ss7/bicci.h>, <ss7/bicci_ioctl.h>.

DEVICES

/dev/bicc.

VERSIONS

The BICC interface is specific to the OpenSS7 SS7(4) stack. This is Version 2 of the interface.

CCI interfaces are consistent with CCI Revsion 0.8.2.

REFERENCES

[1]: ITU-T Recommendation Q.1902.1 to Q.1902.4, Specifications of the Bearer Independent Call Control (BICC), 2001, (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. <http://www.itu.int/rec/T-REC-Q.1902/>
[2]: ANSI T1.BICC.1-2000 to T1.BICC.7-2000, Specifications of the Bearer Independent Call Control (BICC), 2000, ANSI, American National Standards Institute.

TRADEMARKS

OpenSS7tm: is a trademark of OpenSS7 Corporation.
Linux®: is a registered trademark of Linus Torvalds.
UNIX®: is a registered trademark of The Open Group.
Solaris®: is a registered trademark of Sun Microsystems.

Other trademarks are the property of their respective owners.

IDENTIFICATION

The OpenSS7 Project: Package OpenSS7 version 0.9.2 released Tue, 18 Nov 2008 11:04:40 GMT.

This document was created by man2html, using the manual pages.
Time: 11:04:39 GMT, November 18, 2008