DC-Signalling supports UNI and PNNI signalling as defined by the ATM Forum, including the Q.SAAL and SSCF/SSCOP reliable transport layers.
DC-Signalling includes exit points in the core code to allow OEMs to provide value-add services to the base functionality. For example, such exit points allow the customisation of
- the allocation of VPCI and VCI values
- support for additional Information Elements not recognised by the core code.
Functions and Features
DC-Signalling provides the following signalling functions.
- UNI V3.0, V3.1, and V4.0
- Level of UNI support (3.0, 3.1 or 4.0) configurable per port
- IISP V3.0 and V3.1
- PNNI Signalling as required by PNNI routing V1.0
- Q.SAAL and SSCF/SSCOP reliable transport layers
- Point-to-point and point-to-multipoint signalling
- Public and private UNI variants
- AToM MIB (Definition of Supplemental Managed Objects)
- Support for an external management component providing SNMP or ILMI Management
- OEM-Specific Customisation Points
Supported Messages
DC-Signalling supports the following messages. (The messages marked * are handled internally by the signalling stack rather than being passed up to Call Control.)
- ADD PARTY
- NOTIFY
- ADD PARTY ACKNOWLEDGE
- PARTY ALERTING
- ADD PARTY REJECT
- PROGRESS
- ALERTING
- RELEASE
- CALL PROCEEDING
- RELEASE COMPLETE
- CONNECT
- RESTART
- CONNECT ACKNOWLEDGE
- RESTART ACKNOWLEDGE
- DROP PARTY
- SETUP
- DROP PARTY ACKNOWLEDGE
- STATUS *
- LEAF SETUP REQUEST
- STATUS ENQUIRY *
- LEAF SETUP FAILURE
For more information about Data Connection's ATM products and expertise contact .