CC_BLOCKING_RES

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

NAME

CC_BLOCKING_RES - circuit management blocking response

SYNOPSIS

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

typedef struct CC_blocking_res {
    ulong cc_primitive;         /* always CC_BLOCKING_RES */
    ulong cc_flags;             /* blocking flags */
    ulong cc_addr_length;       /* address length */
    ulong cc_addr_offset;       /* address offset */
} CC_blocking_res_t;

DESCRIPTION

This primitive requests that the CCS provider respond to the previous blocking indication.

Parameters

This primitive contains the following parameters:

cc_primitive: specifies the primitive type. Always CC_BLOCKING_RES.
cc_flags: Specifies options flags for the operation. (See "Flags" below.)
cc_addr_length: Specifies the length of the call control address (signalling interface and circuit or circuit group identifiers) upon which local blocking is requested.
cc_addr_offset: Specifies the offset of the call control address(es) from the beginning of the M_PROTO message block.

Flags

The options flags are protocol and provider-specific. For additional information, see the specific Addendum.

State

This primitive is only valid for the previous CC_BLOCKING_IND(7) (call control addresses in the CCS_WRES_BLIND state). The new blocking state of the previously specified call controla addresses is the CCS_BLOCKED state.

Modes

This primitive is only valid for indications for signalling interfaces in the NNI mode.

Originator

This primitive is issued by the CC Provider.

ACKNOWLEDGMENTS

The CCS provider should generate one of the following acknowledgments upon receipt of this primitive:

Successful:
Successful completion is indicated via the CC_OK_ACK(7) primitive.
Unsuccessful:
Unsuccessful completion is indicated via the CC_RELEASE_IND(7) or CC_RESET_IND primitive. Non-fatal errors: Errors are indicated via the CC_ERROR_ACK(7) primitive.

ERRORS

The applicable non-fatal errors are defined as follows:

[CCACCESS]: The user did not have sufficient permission to invoke the operation.
[CCOUSTATE]: The primitive was issued from an invalid state.
[CCSYSERR]: A system error occurred and the UNIX system error is indicated in the CC_ERROR_ACK(7) primitive.

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>