Manpage of CC_RELEASE_CON

CC_RELEASE_CON

Section: Call Control Interface (CCI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

CC_RELEASE_CON - call release confirmation

SYNOPSIS

The format of this message is one M_PROTO message block. The structure of the M_PROTO block is as follows:

typedef struct CC_release_con {
    ulong cc_primitive;         /* always CC_RELEASE_CON */
    ulong cc_user_ref;          /* user call reference */
    ulong cc_call_ref;          /* call reference */
    ulong cc_opt_length;        /* optional parameter length */
    ulong cc_opt_offset;        /* optional parameter offset */
} CC_release_con_t;

DESCRIPTION

This primitive indicates to the releasing CCS user that the release of the associated circuit is complete.

Parameters

This primitive contains the following parameters:

cc_primitive: indicates the primitive type. Always CC_RELEASE_CON.
cc_user_ref: Indicates the user call reference of the CC_SETUP_REQ(7) when the CC_RELEASE_CON primitive is used in response to the CC_SETUP_REQ(7) and before a CC_SETUP_CON(7) is issued. Otherwise, this parameter is coded zero and is ignored by the CCS provider.
cc_call_ref: Indicates the call reference of the CC_SETUP_IND(7) when the CC_RELEASE_CON primitive is used in response to the CC_SETUP_IND(7) on a listening stream. Otherwise, this parameter is coded zero and is ignored by the CCS provider.
cc_opt_length: Indicates the length of the optional parameters associated with the release confirmation. If no optional parameters are associated with the release confirmation, then this parameter must be coded zero.
cc_opt_offset: Indicates the offset of the optional parameters from the start of the M_PROTO message block.

State

This primitive is valid in state CCS_WCON_RELREQ. The new state is CCS_IDLE.

Modes

This primitive is valid in UNI (User or Network) and NNI modes.

Originator

This primitive is issued by the CC Provider.

NOTES

Considerations for Q.764 and ANSI T1.113 conformance:

CCS providers conforming to Q.764 or ANS T1.113 adhere to the following additional rules: (See also cci_isup(7) for address format and isup(4))

Considerations for Q.931/932 conformance:

CCS providers conforming to Q.931/932 adhere to the following additional rules: (See also cci_isdn(7) for address format and isdn(4))

Considerations for H.225.0 conformance:

CCS providers conforming to H.225.0 adhere to the following additional rules: (See also cci_h225(7) for address format and h225(4))

Considerations for BSSAP conformance:

CCS providers conforming to BSSAP adhere to the following additional rules: (See also cci_bssap(7) for address format and bssap(4))

FILES

<ss7/cci.h>.

VERSIONS

This manpage was written for strss7-0.8.4.
The Call Control Interface (CCI) is specific to OpenSS7 and first appeared in strss7-0.8.4.
This is Version 0.8.4 of the CCI interface.

REFERENCES

[1]: CCI Revision 1.0.0, Call Control Interface (CCI) Specification, Draft 1, April 2003, (Edmonton), B. Bidulock, OpenSS7 Corporation. <http://www.openss7.org/docs/cci.pdf>