Manpage of CC_UNBIND_REQ

CC_UNBIND_REQ

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

NAME

CC_UNBIND_REQ - unbind protocol address request

SYNOPSIS

The format of the message is one M_PROTO block, and its structure is as follows:

typedef struct CC_unbind_req {
    ulong cc_primitive;         /* always CC_UNBIND_REQ */
} CC_unbind_req_t;

DESCRIPTION

This primitive request that the CCS provider unbind the CCS user entity that was previously bound to the call control address.

Parameters

This primitive contains the following parameters:

cc_primitive: specifies the primitive type. Always CC_UNBIND_REQ.

State

This primitive is valid in the CCS_IDLE state. The new state is CCS_WACK_UREQ.

Modes

This primitive is valid in all modes.

Originator

This primitive is originated by the CC User.

ACKNOWLEDGMENTS

This primitive requires the CCS provider to generate the following acknowledgments upon receipt of the primitive:

Successful:
Correct acknowledgment of the primitive is indicated via the CC_OK_ACK(7) primitive.
Unsuccessful (Non-fatal errors):
These errors will be indicated via the CC_ERROR_ACK(7) primitive.

ERRORS

The applicable non-fatal errors are as follows:

[CCOUTSTATE]: The primitive was issued from an invalid state.
[CCSYSERR]: A system error has 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>