Manpage of CC_SETUP_IND

CC_SETUP_IND

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

NAME

CC_SETUP_IND - call setup indication

SYNOPSIS

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

typedef struct CC_setup_ind {
    ulong cc_primitive;         /* always CC_SETUP_IND */
    ulong cc_call_ref;          /* call reference */
    ulong cc_call_type;         /* call type */
    ulong cc_call_flags;        /* call flags */
    ulong cc_cdpn_length;       /* called party number length */
    ulong cc_cdpn_offset;       /* called party number offset */
    ulong cc_opt_length;        /* optional parameters length */
    ulong cc_opt_offset;        /* optional parameters offset */
    ulong cc_addr_length;       /* connecting address length */
    ulong cc_addr_offset;       /* connecting address offset */
} CC_setup_ind_t;

DESCRIPTION

This primitive indicates to the destination CCS user that a call setup request has been made by the user at the specified source address.

Parameters

This primitive contains the following parameters:

cc_primitive: indicates the primitive type. Always CC_SETUP_IND.
cc_call_ref: Identifies the call reference that can be used by the CCS user to associate this message with the CC_SETUP_RES(7) or CC_RELEASE_REQ(7) primitive that is to follow. This value must be unique among the outstanding CC_SETUP_IND(7) messages.
cc_call_type: Indicates the type of call to be set up. Call types supported are dependent upon the CCS provider and protocol, see the addendum for call types for specific protocols.
cc_call_flags: Indicates a bit field of call options. Call flags supported are dependent upon the CCS provider and protocol, see the addendum for call flags for specific protocols.
cc_cdpn_length: Indicates the length of the called party number address parameter that conveys an address identifying the CCS user to which the call is to be established. This field will accommodate variable length addresses within a range supported by the CCS provider.
cc_cdpn_offset: Is the offset of the called party number address from the beginning of the M_PROTO message block.
cc_opt_length: Indicates the length of the optional parameters that were used in the call setup.
cc_opt_offset: Indicates the offset of the optional parameters from the beginning of the M_PROTO message block.
cc_addr_length: Indicates the length of the connecting address parameter that conveys the call control address the CCS user entity (circuit) on which the call is being established. The semantics of the values in the CC_SETUP_IND(7) is identical to the values in the CC_BIND_ACK(7).
cc_addr_offset: Indicates the offset of the connecting address from the beginning of the M_PROTO message block.

Rules

The rules for issuing the CC_SETUP_IND primitive are as follows:

---: This primitive will only be issued to streams that have been bound with a non-zero negotiated maximum number of setup indications (i.e. on a listening stream), and where the number of outstanding setup indications (call references) for the stream is less than the negotiated maximum number of setup indications.
---: If the call setup indicated is for a normal call, the stream upon which it is indicated was not bound with the CC_TEST, CC_MANAGEMENT or CC_MAINTENANCE flags set.
---: If the call setup indicated is for an ISUP test call, the stream upon which it is indicated was bound with the CC_TEST flag set and a non-zero number of negotiated maximum setup indications.

State

This primitive is valid in state CCS_IDLE for the indicated call reference. The new state depends upon the information provided in the CC_SETUP_IND message as follows:

---: If the setup indication indicates that a continuity check was performed on a previous circuit, the new state is CCS_WIND_CCREP (awaiting the report of continuity test results).
---: If the setup indication indicates that a continuity check is required on the circuit, the new state is CCS_WREQ_CTEST (awaiting confirmation of installation of loop back device on the circuit).
---: If the setup indication indicates that no continuity tests are required on this or a previous circuit and that the called party number contains partial information, the new state is CCS_WREQ_MORE (awaiting the request for more information to confirm the partial address).
---: If the setup indication indicates that no continuity tests are required on this or a previous circuit and that the called party number contains complete information, the new state is CCS_WRES_SIND (awaiting response to the setup indication).

In any event, the number of outstanding setup indications waiting for user response is incremented by one.

Modes

This primitive is valid in all modes.

Originator

This primitive is originated by the CC User.

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>