CC_REJECT_REQ

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

NAME

CC_REJECT_REQ - call reject request The format of this message is one M_PROTO message block. The structure of the M_PROTO block is as follows:

SYNOPSIS

typedef struct CC_reject_req {
    ulong cc_primitive;         /* always CC_REJECT_REQ */
    ulong cc_call_ref;          /* call reference */
    ulong cc_cause;             /* cause value */
    ulong cc_opt_length;        /* optional parameter length */
    ulong cc_opt_offset;        /* optional parameter offset */
} CC_reject_req_t;

DESCRIPTION

This message is used to reject a call before any request for more information, or request for indication of proceeding, alerting, progress, or in-band information has been attempted. The message also includes the cause of the rejection.

Parameters

This primitive contains the following parameters:

cc_primitive: specifies the primitive type. Always CC_REJECT_REQ.
cc_call_ref: Specifies the call reference of the CC_SETUP_IND(7) when the CC_REJECT_REQ 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_cause: Specifies the cause for the rejection. Cause values are provider and protocol specific (see Addendum).
cc_opt_length: Specifies the length of the optional parameters associated with the reject request. If no optional parameters are associated with the reject request, then this parameter must be coded zero.
cc_opt_offset: Specifies the offset of the optional parameters from the start of the M_PROTO message block. If no optional parameters are associated with the reject request, then this parameter must be coded zero.

State

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

Modes

This primitive is only valid in the UNI mode (User or Network). (NNI users should use the CC_RELEASE_REQ(7) primitive in the same situation.)

Originator

This primitive is originated by the CC User.

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 (Non-fatal errors):
Errors are indicated via the CC_ERROR_ACK(7) primitive.

ERRORS

The applicable non-fatal errors are defined as follows:

[CCSYSERR]: A system error occurred and the UNIX system error is indicated in the CC_ERROR_ACK(7) primitive.
[CCBADPRIM]: The primitive was of an incorrect format (i.e. too small, or an offset is out of range)
[CCOUTSTATE]: The primitive was issued from an invalid state.
[CCBADCLR]: The call reference specified in the primitive was incorrect or illegal.
[CCBADOPT]: The options values as specified in the primitive were in an incorrect format, or they contained illegal information.
[CCACCESS]: The user did not have proper permissions to request the operation or to use the options specified.
[CCNOTSUPP]: The specified primitive type is not known to or not supported by the CCS 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>