.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .sp 1P .ce 1000 \v'3P' SECTION\ 3 .ce 0 .sp 1P .ce 1000 \fBDATA\ USER\ PART\ (DUP)\fR \v'1P' .ce 0 .sp 1P .sp 2P .LP \fBRecommendation\ Q.741\fR .RT .sp 2P .sp 1P .ce 1000 \fBSIGNALLING\ SYSTEM\ No.\ 7\ \(em\ DATA\ USER\ PART\fR .EF '% Fascicle\ VI.8\ \(em\ Rec.\ Q.741'' .OF '''Fascicle\ VI.8\ \(em\ Rec.\ Q.741 %' .ce 0 .sp 1P .PP (This Recommendation appears in Fascicle VIII.3 of the Blue Book, as Recommendation\ X.61.) .sp 1P .RT .LP .rs .sp 25P .ad r Blanc .ad b .RT .LP .bp .LP \fBMONTAGE: PAGE 2 = PAGE BLANCHE\fR .sp 1P .RT .LP .bp .sp 1P .ce 1000 \v'3P' SECTION\ 5 .ce 0 .sp 1P .ce 1000 \fBINTEGRATED\ SERVICES\ DIGITAL\ NETWORK\ USER\ PART\ (ISUP)\fR .ce 0 .sp 1P .sp 2P .LP \fBRecommendation\ Q.761\fR .RT .sp 2P .ce 1000 \fBFUNCTIONAL\ DESCRIPTION\ OF\ THE\ ISDN\ USER\ PART\fR .EF '% Fascicle\ VI.8\ \(em\ Rec.\ Q.761'' .OF '''Fascicle\ VI.8\ \(em\ Rec.\ Q.761 %' .ce 0 .sp 1P .ce 1000 \fBOF\ SIGNALLING\ SYSTEM\ No.\ 7\fR .ce 0 .sp 1P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP The ISDN User Part is the Signalling System No. 7 protocol which provides the signalling functions required to support basic bearer services and supplementary services for voice and non\(hyvoice applications in an integrated services digital network. .PP The ISDN User Part is also suited for application in dedicated telephone and circuit switched data networks and in analogue and mixed analogue/digital networks. In particular the ISDN User Part meets the requirements defined by CCITT for worldwide international semi\(hyautomatic and automatic telephone and circuit switched data traffic. .PP The ISDN User Part is furthermore suitable for national applications. Most signalling procedures, information elements and message types specified for international use are also required in typical national applications. Moreover, coding space has been reserved in order to allow national administrations and recognized private operating agencies to introduce network specific signalling messages and elements of information within the internationally standardized protocol structure. .PP The ISDN User Part makes use of the services provided by the Message Transfer Part (MTP) and in some cases by the Signalling Connection Control Part (SCCP) for the transfer of information between ISDN User Parts. .PP The ISDN User Part protocol which supports the basic bearer service is described in Recommendations\ Q.761 to\ Q.764 and\ Q.766. A general description of ISDN User Part signals and messages is provided in Recommendation\ Q.762. Message formats and message field codings are defined in Recommendation\ Q.763, while the signalling procedures are described in Recommendation\ Q.764. Recommendation\ Q.766 deals with ISDN User Part performance objectives. .PP ISDN User Part protocol elements which support supplementary services are described in Recommendation\ Q.730. .PP \fINote\fR \ \(em\ The message set, message formats and procedures specified in this version of the ISDN User Part protocol are not in complete alignment with those of the 1984\ version (Red Book). The two versions of the protocol are therefore not compatible in all aspects. .bp .RT .sp 2P .LP \fB2\fR \fBServices supported by the ISDN User Part\fR .sp 1P .RT .PP The ISDN User Part protocol supports the basic bearer service, i.e. the establishment, supervision and release of 64\ kbit/s circuit switched network connections between subscriber line exchange terminations. .PP In addition to the basic bearer service the ISDN User Part also supports the following supplementary services: .RT .LP \(em calling line identification, .LP \(em call forwarding, .LP \(em closed user groups, .LP \(em directing dialling in, and .LP \(em user\(hyto\(hyuser signalling. .sp 2P .LP \fB3\fR \fBServices assumed from the Message Transfer Part (MTP)\fR .sp 1P .RT .sp 1P .LP 3.1 \fIGeneral\fR .sp 9p .RT .PP This section describes the functional interface presented by the Message Transfer Part to the ISDN User Part. In accordance with the description techniques defined by the Open System Interconnection (OSI) model, information is transferred to and from the MTP in the form of Parameters carried by Primitives. .PP The general syntax of a primitive is as follows: .RT .ce \fBH.T. [T1.761]\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; lw(12p) | lw(60p) | lw(60p) | lw(60p) . .T& cw(12p) | cw(60p) | cw(60p) | cw(60p) . X Generic name Specific name Parameter .T& lw(192p) . .TE .nr PS 9 .RT .ad r \fBTableau du \(sc\ 3.1 [T1.761], p.\fR .sp 1P .RT .ad b .RT .LP where .LP X designates the function providing the service (the MTP, in this case), .LP the Generic name describes an action by X, .LP the Specific name indicates the purpose of the primitive, i.e. whether it conveys a request for service, an indication that service related information has been received, a response to a service request or a confirmation that the requested service has been performed, and .LP the Parameters contain the elements of supporting information transferred by the primitive. .sp 1P .LP 3.2 \fIDescription of\fR \fIprimitives\fR .sp 9p .RT .PP The following paragraphs describe the primitives used across the ISDN User Part\(hyMessage Transfer Part functional interface. The primitives together with the parameters carried by each primitive are also shown in Table\ 1/Q.761. .RT .sp 1P .LP 3.2.1 \fITransfer\fR .sp 9p .RT .PP The MTP\(hyTRANSFER primitive is used either by the ISDN User Part to access the Signalling Message Handling function of the Message Transfer Part or by the latter to deliver signalling message information to the ISDN User Part. .bp .RT .sp 1P .LP 3.2.2 \fIPause\fR .sp 9p .RT .PP The MTP\(hyPAUSE primitive is sent by the Message Transfer Part to indicate its inability to transfer messages to the destination specified as a parameter. .RT .sp 1P .LP 3.2.3 \fIResume\fR .sp 9p .RT .PP The MTP\(hyRESUME primitive is sent by the Message Transfer Part to indicate its ability to resume unrestricted transfer of messages to the destination specified as a parameter. .RT .sp 1P .LP 3.2.4 \fIStatus\fR .sp 9p .RT .PP The MTP\(hySTATUS primitive is sent by the Message Transfer Part to indicate that the signalling route to a specific destination is congested or the ISDN User Part at the destination is unavailable. The affected destination and the congestion indication are carried as parameters (see Table\ 1/Q.761) in the primitive. .RT .ce \fBH.T. [T2.761]\fR .ce TABLE\ 1/Q.761 .ce \fBMessage transfer part service primitives\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(72p) sw(54p) | cw(54p) , c | c | ^ . Primitives Parameters Generic name Specific name _ .T& lw(72p) | lw(54p) | lw(54p) . MTP\(hyTRANSFER Request indication { OPC DPC SLS SIO Signalling info. } _ .T& lw(72p) | lw(54p) | lw(54p) . MTP\(hyPAUSE Indication Affected DPC _ .T& lw(72p) | lw(54p) | lw(54p) . MTP\(hyRESUME Indication Affected DPC _ .T& lw(72p) | lw(54p) | lw(54p) . MTP\(hySTATUT Indication { Affected DPC Cause (see Note) } .TE .LP OPC Originating point code DPC Destination point code SLS Signaling link selection code SIO Service information octet .LP \fINote\ \(em\ \fR The cause parameter can assume two values: \(em signalling network congested (level), where level is included only if natioal options with congestion priorities and multiple signalling states without congestion priorities (see Recommendation\ Q.704). .LP \(em remote user unavailable. .nr PS 9 .RT .ad r \fBTableau 1/Q.761 [T2.761], p.\fR .sp 1P .RT .ad b .RT .sp 2P .LP \fB4\fR \fBEnd\(hyto\(hyend signalling\fR .sp 1P .RT .sp 1P .LP 4.1 \fIGeneral\fR .sp 9p .RT .PP End\(hyto\(hyend signalling is defined as the capability to transfer signalling information of end points significance directly between signalling end points in order to provide a requesting user with a basic or supplementary service. .bp .PP End\(hyto\(hyend signalling is used typically between call originating and terminating local exchanges, to request or to respond to requests for additional call related information, to invoke a supplementary service or to transfer user\(hyto\(hyuser information transparently through the network. .PP End\(hyto\(hyend signalling procedures are described in Recommendation\ Q.764, \(sc\ 3. .PP The following two methods of end\(hyto\(hyend signalling are supported: .RT .sp 1P .LP 4.2 \fISCCP method of end\(hyto\(hyend signalling\fR .sp 9p .RT .PP Connection\(hyoriented or connectionless transfer of end\(hyto\(hyend signalling information can be accomplished by using the service provided the Signalling Connection Control Part (SCCP) of Signalling System\ No.\ 7. The relevant procedures are described in Recommendation\ Q.764, \(sc\ 3.4. .RT .sp 1P .LP 4.3 \fIPass\(hyalong method of end\(hyto\(hyend signalling\fR .sp 9p .RT .PP The pass\(hyalong method of end\(hyto\(hyend signalling provides transfer of signalling information without requiring the services of the SCCP. .PP This method may be used between two exchanges when the information to be transferred relates to an existing call for which a physical connection between the same two exchanges has been established. The information transfer in this case occurs over the same signalling path as that used to set up the call and establish the physical connection. .PP The relevant procedures are described in Recommendation Q.764, \(sc\ 3.3. .RT .sp 2P .LP \fB5\fR \fBFuture enhancements\fR .sp 1P .RT .PP Requirements for additional protocol capabilities, such as the ability to support new supplementary services, will result from time to time in the need to add to or modify existing protocol elements and thus to create a new protocol version. .PP In order to ensure adequate service continuity, the insertion of a new protocol version into one part of a network should be transparent to the remainder of the network. Compatible interworking between protocol versions is optimized by adhering to the following guidelines when specifying a new version: .RT .LP 1) Existing protocol elements, i.e. procedures, messages, parameters and codes, should not be changed unless a protocol error needs to be corrected or it becomes necessary to change the operation of the service that is being supported by the protocol. .LP 2) The semantics of a message, a parameter or of a field within a parameter should not be changed. .LP 3) Established rules for the formatting and encoding messages should not be modified. .LP 4) The addition of parameters to the mandatory part of an existing message should not be allowed. If needed, a new message should be defined containing the desired set of existing and new mandatory parameters. .LP 5) A parameter may be added to an existing message as long as it is allocated to the optional part of the message. .LP 6) The addition of new octets to an existing mandatory fixed length parameter should be avoided. If needed, a new optional parameter should be defined containing the desired set of existing and new information fields. .LP 7) The sequence of fields in an existing variable length parameter should remain unchanged. New fields may be added at the end of the existing sequence of parameter fields. If a change in the sequence of parameter fields is required, a new parameter should be defined. .LP 8) The all zeros code point should be used exclusively to indicate an unallocated (spare) or insignificant value of a parameter field. This avoids an all zeros code, sent by one protocol version as a spare value, to be interpreted as a significant value in another version. .bp .sp 2P .LP \fBRecommendation\ Q.762\fR .RT .sp 2P .sp 1P .ce 1000 \fBGENERAL\ FUNCTION\ OF\ MESSAGES\ AND\ SIGNALS\fR .EF '% Fascicle\ VI.8\ \(em\ Rec.\ Q.762'' .OF '''Fascicle\ VI.8\ \(em\ Rec.\ Q.762 %' .ce 0 .sp 1P .PP This Recommendation describes the elements of signalling information used by the ISDN User Part protocol and their function. The encoding of these elements, the format of the messages in which they are conveyed and their application in the ISDN User Part signalling procedures are described in Recommendations\ Q.763 and Q.764. Table\ 1/Q.762 gives the mandatory or optional parameters in the ISDN user part messages and Table\ 2/Q.762 the list of abbreviations of these messages. .sp 1P .RT .sp 2P .LP \fB1\fR \fBSignalling messages\fR .sp 1P .RT .sp 1P .LP 1.1 \fBAddress complete message (ACM)\fR .sp 9p .RT .PP A message sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received. .RT .sp 1P .LP 1.2 \fBAnswer message (ANM)\fR .sp 9p .RT .PP A message sent in the backward direction indicating that the call has been answered. In semi\(hyautomatic working this message has a supervisory function. In automatic working this message is used in conjunction with charging information in order to: .RT .LP \(em start metering the charge to the calling subscriber (see Recommendation\ Q.28), and .LP \(em start measurement of call duration for international accounting purposes (Recommendation\ E.260). .sp 1P .LP 1.3 \fBBlocking message (BLO)\fR .sp 9p .RT .PP A message sent only for maintenance purposes to the exchange at the other end of a circuit, to cause an engaged condition of that circuit for subsequent calls outgoing from that exchange. When a circuit is used in the bothway mode of operation an exchange receiving the blocking message must be capable of accepting incoming calls on the concerned circuit unless it has also sent a blocking message. Under certain conditions, a blocking message is also a proper response to a reset circuit message. .RT .sp 1P .LP 1.4 \fBBlocking acknowledgement message (BLA)\fR .sp 9p .RT .PP A message sent in response to a blocking message indicating that the circuit has been blocked. .RT .sp 1P .LP 1.5 \fBCall modification completed message (CMC)\fR .sp 9p .RT .PP A message sent in response to a call modification request message indicating that the requested call modification (e.g.\ from voice to data) has been completed. .RT .sp 1P .LP 1.6 \fBCall modification reject message (CMRJ)\fR .sp 9p .RT .PP A message sent in response to a call modification request message indicating that the request has been rejected. .RT .sp 1P .LP 1.7 \fBCall modification request message (CMR)\fR .sp 9p .RT .PP A message sent in either direction indicating a calling or called party request to modify the characteristics of an established call (e.g.\ from data to voice). .RT .sp 1P .LP 1.8 \fBCall progress message (CPG)\fR .sp 9p .RT .PP A message sent in the backward direction indicating that an event has occurred during call set\(hyup which should be relayed to the calling party. .RT .sp 1P .LP 1.9 \fBCharge information message (CRG)\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in either direction for accounting and/or call charging purposes. .bp .RT .sp 1P .LP 1.10 \fBCircuit group blocking message (CGB)\fR .sp 9p .RT .PP A message sent to the exchange at the other end of an identified group of circuits to cause an engaged condition of this group of circuits for subsequent calls outgoing from that exchange. An exchange receiving a circuit group blocking message must be able to accept incoming calls on the group of blocked circuits unless it has also sent a blocking message. Under certain conditions, a circuit group blocking message is also a proper response to a reset circuit message. .RT .sp 1P .LP 1.11 \fBCircuit group blocking acknowledgement message (CGBA)\fR .sp 9p .RT .PP A message sent in response to a circuit group blocking message to indicate that the requested group of circuits has been blocked. .RT .sp 1P .LP 1.12 \fBCircuit group reset message (GRS)\fR .sp 9p .RT .PP A message sent to release an identified group of circuits when, due to memory mutilation or other causes, it is unknown whether for example, a release or release complete message is appropriate for each of the circuits in the group. If at the receiving end a circuit is remotely blocked, reception of this message should cause that condition to be removed. .RT .sp 1P .LP 1.13 \fBCircuit group reset acknowledgement message (GRA)\fR .sp 9p .RT .PP A message sent in response to a circuit group reset message and indicating that the requested group of circuits has been reset. The message also indicates the maintenance blocking state of each circuit. .RT .sp 1P .LP 1.14 \fBCircuit group unblocking message (CGU)\fR .sp 9p .RT .PP A message sent to the exchange at the other end of an identified group of circuits to cause cancellation in that group of circuits of an engaged condition invoked earlier by a blocking or circuit group blocking message. .RT .sp 1P .LP 1.15 \fBCircuit group unblocking acknowledgement message (CGUA)\fR .sp 9p .RT .PP A message sent in response to a circuit group unblocking message to indicate that the requested group of circuits has been unblocked. .RT .sp 1P .LP 1.16 \fBCircuit group query message (CQM)\fR .sp 9p .RT .PP A message sent on a routine or demand basis to request the far\(hyend exchange to give the state of all circuits in a particular range. .RT .sp 1P .LP 1.17 \fBCircuit group query response message (CQR)\fR .sp 9p .RT .PP A message sent in response to a circuit group query message to indicate the state of all circuits in a particular range. .RT .sp 1P .LP 1.18 \fBConfusion message (CFN)\fR .sp 9p .RT .PP A message sent in response to any message (other than a confusion message) if the exchange does not recognize the message or detects a part of the message as being unrecognized. .RT .sp 1P .LP 1.19 \fBConnect message (CON)\fR .sp 9p .RT .PP A message sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received and that the call has been answered. .RT .sp 1P .LP 1.20 \fBContinuity message (COT)\fR .sp 9p .RT .PP A message sent in the forward direction indicating whether or not there is continuity on the preceding circuit(s) as well as of the selected circuit to the following exchange, including verification of the communication path across the exchange with the specified degree of reliability. .bp .RT .sp 1P .LP 1.21 \fBContinuity check request message (CCR)\fR .sp 9p .RT .PP A message sent by an exchange for a circuit on which a continuity check is to be performed, to the exchange at the other end of the circuit, requesting continuity checking equipment to be attached. .RT .sp 1P .LP 1.22 \fBDelayed release message (DRS)\fR \fI(national use)\fR .sp 9p .RT .PP A message sent in either direction indicating that the called or calling party has disconnected but that the network is holding the connection. .RT .sp 1P .LP 1.23 \fBFacility accepted message (FAA)\fR .sp 9p .RT .PP A message sent in response to a facility request message indicating that the requested facility has been invoked. .RT .sp 1P .LP 1.24 \fBFacility reject message (FRJ)\fR .sp 9p .RT .PP A message sent in response to a facility request message to indicate that the facility request has been rejected. .RT .sp 1P .LP 1.25 \fBFacility request message (FAR)\fR .sp 9p .RT .PP A message sent from an exchange to another exchange to request activation of a facility. .RT .sp 1P .LP 1.26 \fBForward transfer message (FOT)\fR .sp 9p .RT .PP A message sent in the forward direction on semi\(hyautomatic calls when the outgoing international exchange operator wants the help of an operator at the incoming international exchange. The message will normally serve to bring an assistance operator (see Recommendation\ Q.101) into the circuit if the call is automatically set up at the exchange. When the call is completed via an operator (incoming or delay operator) at the incoming international exchange, the message should preferably cause this operator to be recalled. .RT .sp 1P .LP 1.27 \fBInformation message (INF)\fR .sp 9p .RT .PP A message sent to convey information in association with a call, which may have been requested in an information request message. .RT .sp 1P .LP 1.28 \fBInformation request message (INR)\fR .sp 9p .RT .PP A message sent by an exchange to request information in association with a call. .RT .sp 1P .LP 1.29 \fBInitial address message (IAM)\fR .sp 9p .RT .PP A message sent in the forward direction to initiate seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call. .RT .sp 1P .LP 1.30 \fBLoop back acknowledgement message (LPA)\fR \fI(national use)\fR .sp 9p .RT .PP A message sent in the backward direction in response to a continuity check request message indicating that a loop (or transceiver in the case of a 2\(hywire circuit) has been connected. .RT .sp 1P .LP 1.31 \fBOverload message (OLM)\fR \fI(national use)\fR .sp 9p .RT .PP A message sent in the backward direction, on non\(hypriority calls in response to an IAM, to invoke temporary trunk blocking of the circuit concerned when the exchange generating the message is subject to load control. .RT .sp 1P .LP 1.32 \fBPass\(hyalong message (PAM)\fR .sp 9p .RT .PP A message that may be sent in either direction to transfer information between two signalling points along the same signalling path as that used to establish a physical connection between those two points. .bp .RT .sp 1P .LP 1.33 \fBRelease message (REL)\fR .sp 9p .RT .PP A message sent in either direction to indicate that the circuit is being released due to the reason (cause) supplied and is ready to be put into the idle state on receipt of the release complete message. In case the call was forwarded or is to be rerouted, the appropriate indicator is carried in the message together with the redirection address and the redirecting address. .RT .sp 1P .LP 1.34 \fBRelease complete message (RLC)\fR .sp 9p .RT .PP A message sent in either direction in response to the receipt of a released message, or if appropriate to a reset circuit message, when the circuit concerned has been brought into the idle condition. .RT .sp 1P .LP 1.35 \fBReset circuit message (RSC)\fR .sp 9p .RT .PP A message sent to release a circuit when, due to memory mutilation or other causes, it is unknown whether for example, a release or a release complete message is appropriate. If, at the receiving end, the circuit is remotely blocked, reception of this message should cause that condition to be removed. .RT .sp 1P .LP 1.36 \fBResume message (RES)\fR .sp 9p .RT .PP A message sent in either direction indicating that the calling or called party, after having been suspended, is reconnected. .RT .sp 1P .LP 1.37 \fBSubsequent address message (SAM)\fR .sp 9p .RT .PP A message that may be sent in the forward direction following an initial address message, to convey additional called party number information. .RT .sp 1P .LP 1.38 \fBSuspend message (SUS)\fR .sp 9p .RT .PP A message sent in either direction indicating that the calling or called party has been temporarily disconnected. .RT .sp 1P .LP 1.39 \fBUnblocking message (UBL)\fR .sp 9p .RT .PP A message sent to the exchange at the other end of a circuit to cancel, in that exchange, the engaged condition of the circuit caused by a previously sent blocking or circuit group blocking message. .RT .sp 1P .LP 1.40 \fBUnblocking acknowledgement message (UBA)\fR .sp 9p .RT .PP A message sent in response to an unblocking message indicating that the circuit has been unblocked. .RT .sp 1P .LP 1.41 \fBUnequipped circuit identification code message (UCIC)\fR \fI(national use)\fR .sp 9p .RT .PP A message sent from one exchange to another when it receives an unequipped circuit identification code. .RT .sp 1P .LP 1.42 \fBUser\(hyto\(hyuser information message (USR)\fR .sp 9p .RT .PP A message to be used for the transport of user\(hyto\(hyuser signalling independent of call control messages. .RT .sp 2P .LP \fB2\fR \fBSignalling information\fR .sp 1P .RT .sp 1P .LP 2.1 \fBAccess transport\fR .sp 9p .RT .PP Information generated on the access side of a call and transferred transparently in either direction between originating and teminating local exchanges. The information is significant to both users and local exchanges. .RT .sp 1P .LP 2.2 \fBAddress presentation restricted indicator\fR .sp 9p .RT .PP Information sent in either direction to indicate that the address information is not to be presented to a public network user, but can be passed to another public network. It may also be used to indicate that the address cannot be ascertained. .bp .RT .sp 1P .LP 2.3 \fBAddress signal\fR .sp 9p .RT .PP An element of information in a network number. The address signal may indicate digit values\ 0 to\ 9, code\ 11 or code\ 12. One address signal value (ST) is reserved to indicate the end of the called party number. .RT .sp 1P .LP 2.4 \fBAutomatic congestion level\fR .sp 9p .RT .PP Information sent to the exchange at the other end of a circuit to indicate that a particular level of congestion exists at the sending exchange. .RT .sp 1P .LP 2.5 \fBCall forwarding may occur indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating that call forwarding may occur, depending on the response received (or lack thereof) from the called party. .RT .sp 1P .LP 2.6 \fBCall identity\fR .sp 9p .RT .PP Information sent in the call reference parameter indicating the identity of a call in a signalling point. .RT .sp 1P .LP 2.7 \fBCall reference\fR .sp 9p .RT .PP Circuit independent information identifying a particular call. .RT .sp 1P .LP 2.8 \fBCalled party number\fR .sp 9p .RT .PP Information to identify the called party. .RT .sp 1P .LP 2.9 \fBCalled party's category indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating the category of the called party, e.g.\ ordinary subscriber or payphone. .RT .sp 1P .LP 2.10 \fBCalled party's status indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating the status of the called party, e.g.\ subscriber free. .RT .sp 1P .LP 2.11 \fBCalling party number\fR .sp 9p .RT .PP Information sent in the forward direction to identify the calling party. .RT .sp 1P .LP 2.12 \fBCalling party address request indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating a request for the calling party address to be returned. .RT .sp 1P .LP 2.13 \fBCalling party address response indicator\fR .sp 9p .RT .PP Information sent in response to a request for the calling party address, indicating whether the requested address is included, not included, not available or incomplete. .RT .sp 1P .LP 2.14 \fBCalling party number incomplete indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating that the complete calling party number is not included. .RT .sp 1P .LP 2.15 \fBCalling party's category\fR .sp 9p .RT .PP Information sent in the forward direction indicating the category of the calling party and, in case of semi\(hyautomatic calls, the service language to be spoken by the incoming, delay and assistance operators. .RT .sp 1P .LP 2.16 \fBCalling party's category request indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating a request for the calling party's category to be returned. .RT .sp 1P .LP 2.17 \fBCalling party's category response indicator\fR .sp 9p .RT .PP Information sent in response to a request for the calling party's category, indicating whether or not the requested information is included in the response. .bp .RT .sp 1P .LP 2.18 \fBCause value\fR .sp 9p .RT .PP Information sent in either direction indicating the reason for sending the message (e.g.\ release message). Definitions for each cause value are listed below. .RT .LP a) \fINormal class\fR .LP Cause\ 1\ \(em\ Unallocated (unassigned) number This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned). .LP Cause\ 2\ \(em\ No route to specified transit network This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network, while it does exist, does not serve the equipment which is sending this cause. This cause is supported on a network\(hydependent basis. .LP Cause\ 3\ \(em\ No route to destination This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network\(hydependent basis. .LP Cause\ 4\ \(em\ Send special information tone This cause indicates that the called party cannot be reached for reasons that are of long\(hyterm nature and that the special information tone should be returned to the calling party. .LP Cause\ 5\ \(em\ Misdialled trunk prefix This cause indicates the erroneous inclusion of a trunk prefix in the called party number (for national use only). .LP Cause\ 16\ \(em\ Normal call clearing This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situation, the source of this cause is not the network. .LP Cause\ 17\ \(em\ User busy This cause is used when the called party has indicated the inability to accept another call. It is noted that the user equipment is compatible with the call. .LP Cause\ 18\ \(em\ No user responding This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time. .LP Cause\ 19\ \(em\ No answer from user (user alerted) This cause is used when the called party has been alerted but does not respond with a connect indication within the prescribed period of time. .LP Cause\ 21\ \(em\ Call rejected This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy or incompatible. .LP Cause\ 22\ \(em\ Number changed This cause is returned to a calling party when the called number indicated by the calling party is no longer assigned. The new called number may optionally be included in the diagnostic field. If a network does not support this capability, cause number\ 1 shall be used. .LP Cause\ 27\ \(em\ Destination out of order This cause indicates that the destination requested by the user cannot be reached because the interface to the destination is not functioning correctly. The term \*Qnot functioning correctly\*U indicates that a signalling message was unable to be delivered to the remote party; e.g.\ a physical layer or data link layer failure at the remote party, user equipment off\(hyline,\ etc. .LP Cause\ 28\ \(em\ Address incomplete This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. This condition may be determined in the incoming international exchange (or in the national destination network): .LP \(em immediately after reception of an ST signal, or .LP \(em on time\(hyout after the last received digit. .bp .LP Cause\ 29\ \(em\ Facility rejected This cause is returned when a supplementary service requested by the user cannot be provided by the network. .LP Cause\ 31\ \(em\ Normal, unspecified This cause is used to report a normal event only when no other cause in the normal class applies. .LP b) \fIResource Unavailable class\fR .LP Cause\ 34\ \(em\ No circuit available This cause indicates that there is no appropriate circuit presently available to handle the call. .LP Cause\ 38\ \(em\ Network out of order This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time, e.g.\ immediately re\(hyattempting the call is not likely to be successful. .LP Cause\ 41\ \(em\ Temporary failure This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time, e.g.\ the use may wish to try another call attempt almost immediately. .LP Cause\ 42\ \(em\ Switching equipment congestion This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic. .LP Cause\ 47\ \(em\ Resource unavailable, unspecified This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies. .LP c) \fIService or Option Not Available class\fR .LP Cause\ 50\ \(em\ Requested facility not subscribed This cause indicates that the user has requested a supplementary service which is implemented by the equipment which generated this cause, but the user is not authorized to use. .LP Cause\ 55\ \(em\ Incoming calls barred within CUG This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed within this CUG. .LP Cause\ 57\ \(em\ Bearer capability not authorized This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but the user is not authorized to use. .LP Cause\ 58\ \(em\ Bearer capability not presently available This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time. .LP Cause\ 63\ \(em\ Service or option not available, unspecified This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies. .LP d) \fIService or Option Not Implemented class\fR .LP Cause\ 65\ \(em\ Bearer capability not implemented This cause indicates that the equipment sending this cause does not support the bearer capability requested. .LP Cause\ 69\ \(em\ Requested facility not implemented This cause indicates that the equipment sending this cause does not support the requested supplementary service. .LP Cause\ 70\ \(em\ Only restricted digital information bearer capability is available This cause indicates that the calling party has requested an unrestricted bearer service but that the equipment sending this cause only supports the restricted version of the requested bearer capability. .LP Cause\ 79\ \(em\ Service or option not implemented, unspecified This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies. .bp .LP e) \fIInvalid Message (e.g. Parameter out of Range) class\fR .LP Cause\ 87\ \(em\ Called user not member of CUG This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG. .LP Cause\ 88\ \(em\ Incompatible destination This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility or high layer compatibility or other compatibility attributes (e.g.\ data rate) which cannot be accommodated. .LP Cause\ 91\ \(em\ Invalid transit network selection This cause indicates that a transit network identification was received which is of an incorrect format as defined in Annex\ C of Recommendation\ Q.931. .LP Cause\ 95\ \(em\ Invalid message, unspecified This cause is used to report an invalid message event only when no other cause in the invalid message class applies. .LP f ) \fIProtocol error (e.g. Unknown Message) class\fR .LP Cause\ 97\ \(em\ Message type non\(hyexistent or not implemented This cause indicates that the equipment sending this cause has received a message which it does not recognize either because this is a message type not defined or defined but not implemented by the equipment sending this cause. .LP Cause\ 99\ \(em\ Parameter non\(hyexistent or not implemented \(em discarded This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending the cause. The cause indicates that the parameter(s) were discarded. .LP Cause\ 103\ \(em\ Parameter non\(hyexistent or not implemented \(em passed on This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending the cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed on unchanged. .LP Cause\ 111\ \(em\ Protocol error, unspecified This cause is used to report a protocol error event only when no other cause in the protocol error class applies. .LP g) \fIInterworking class\fR .LP Cause\ 127\ \(em\ Interworking, unspecified This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained. .sp 1P .LP 2.19 \fBCharge indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating whether or not the call is chargeable. .RT .sp 1P .LP 2.20 \fBCharge information request indicator\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in either direction requesting charge information to be returned. .RT .sp 1P .LP 2.21 \fBCharge information response indicator\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in response to a request for charge information indicating whether or not the requested information is included. .RT .sp 1P .LP 2.22 \fBCircuit group supervision message type indicator\fR .sp 9p .RT .PP Information sent in a circuit group blocking or unblocking message, indicating whether blocking (unblocking) is maintenance oriented or hardware oriented. .bp .RT .sp 1P .LP 2.23 \fBCircuit identification code\fR .sp 9p .RT .PP Information identifying the physical path between a pair of exchanges. .RT .sp 1P .LP 2.24 \fBCircuit state indicator\fR .sp 9p .RT .PP Information indicating the state of a circuit according to the sending exchange. .RT .sp 1P .LP 2.25 \fBClosed user group call indicator\fR .sp 9p .RT .PP Information indicating whether or not the concerned call can be set up as a closed user group call and, if a closed user group call, whether or not outgoing access is allowed. .RT .sp 1P .LP 2.26 \fBClosed user group interlock code\fR .sp 9p .RT .PP Information uniquely identifying a closed user group within a network. .RT .sp 1P .LP 2.27 \fBCoding standard\fR .sp 9p .RT .PP Information sent in association with a parameter (e.g. cause indicators) identifying the standard in which the parameter format is described. .RT .sp 1P .LP 2.28 \fBConnected number\fR .sp 9p .RT .PP Information sent in the backward direction to identify the connected party. .RT .sp 1P .LP 2.29 \fBConnection request\fR .sp 9p .RT .PP Information sent in the forward direction on behalf of the signalling connection control part requesting the establishment of an end\(hyto\(hyend connection. .RT .sp 1P .LP 2.30 \fBContinuity check indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating whether or not a continuity check will be performed on the circuit(s) concerned or is being (has been) performed on a previous circuit in the connection. .RT .sp 1P .LP 2.31 \fBContinuity indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating whether or not the continuity check on the outgoing circuit was successful. A continuity check successful indication also implies continuity of the preceding circuits and successful verification of the path across the exchange with the specified degree of reliability. .RT .sp 1P .LP 2.32 \fBCredit\fR .sp 9p .RT .PP Information sent in a connection request, indicating the window size requested by the signalling connection control part for an end\(hyto\(hyend connection. .RT .sp 1P .LP 3.33 \fBDiagnostic\fR .sp 9p .RT .PP Information sent in association which a cause value and which provides supplementary information about the reason for sending the message. .RT .sp 1P .LP 2.34 \fBEcho control device indicator\fR .sp 9p .RT .PP Information indicating whether or not a half echo control device is included in the connection. .RT .sp 1P .LP 2.35 \fBEnd\(hyto\(hyend information indicator\fR .sp 9p .RT .PP Information sent in either direction indicating whether or not the sending exchange has further call information available for end\(hyto\(hyend transmission. In the forward direction, an indication that end\(hyto\(hyend information is available will imply that the destination exchange may obtain the information before alerting the called party. .bp .RT .sp 1P .LP 2.36 \fBEnd\(hyto\(hyend method indicator\fR .sp 9p .RT .PP Information sent in either direction indicating the available methods, if any, for end\(hyto\(hyend transfer of information. .RT .sp 1P .LP 2.37 \fBEvent indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating the type of event which caused a call progress message to be sent to the originating local exchange. .RT .sp 1P .LP 2.38 \fBEvent presentation restricted indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating that the event should not be presented to the calling party. .RT .sp 1P .LP 2.39 \fBExtension indicator\fR .sp 9p .RT .PP Information indicating whether or not the associated octet has been extended. .RT .sp 1P .LP 2.40 \fBFacility indicator\fR .sp 9p .RT .PP Information sent in facility related messages identifying the facility or facilities with which the message is concerned. .RT .sp 1P .LP 2.41 \fBHolding indicator\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in either direction indicating that holding of the connection is requested. .RT .sp 1P .LP 2.42 \fBHold provided indicator\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in either direction indicating that the connection will be held after the calling or called party has attempted to release. .RT .sp 1P .LP 2.43 \fBIn\(hyband information indicator\fR .sp 9p .RT .PP Information sent in the backward direction indicating that in\(hyband information or an appropriate pattern is now available. .RT .sp 1P .LP 2.44 \fBInternal network number indicator\fR .sp 9p .RT .PP Information sent to the destination exchange indicating whether or not the call is allowed should the called party number prove to be an internal network number (e.g.\ mobile access point). .RT .sp 1P .LP 2.45 \fBInterworking indicator\fR .sp 9p .RT .PP Information sent in either direction indicating whether or not Signalling System\ No.\ 7 is used in all parts of the network connection. .RT .sp 1P .LP 2.46 \fBISDN access indicator\fR .sp 9p .RT .PP Information sent in either direction indicating whether or not the access signalling protocol is ISDN. .RT .sp 1P .LP 2.47 \fBISDN user part indicator\fR .sp 9p .RT .PP Information sent in either direction to indicate that the ISDN user part is used in all preceding parts of the network connection. When sent in the backward direction, the preceding parts are those towards the called party. .RT .sp 1P .LP 2.48 \fBISDN user preference indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating whether or not the ISDN user part is required or preferred in all parts of the network connection. .bp .RT .sp 1P .LP 2.49 \fBLocal reference\fR .sp 9p .RT .PP Information sent in the connection request, indicating the local reference allocated by the signalling connection control part to an end\(hyto\(hyend connection. .RT .sp 1P .LP 2.50 \fBLocation\fR .sp 9p .RT .PP Information sent in either direction indicating where an event (e.g.\ release) was generated. .RT .sp 1P .LP 2.51 \fBMalicious call identification request indicator\fR \fI\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in the backward direction to request the identity of the calling party for the purpose of malicious call idenification. .RT .sp 1P .LP 2.52 \fBModification indicator\fR .sp 9p .RT .PP Information sent in the call modification indicators parameter indicating whether the call modification is to service\ 1 or service\ 2. .RT .sp 1P .LP 2.53 \fBNational/international call indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating in the destination national network whether the call has to be treated as an international call or as a national call. .RT .sp 1P .LP 2.54 \fBNature of address indicator\fR .sp 9p .RT .PP Information sent in association with an address indicating the nature of that address, e.g.\ ISDN international number, ISDN national significant number, or ISDN subscriber number. .RT .sp 1P .LP 2.55 \fBNumbering plan indicator\fR .sp 9p .RT .PP Information sent in association with a number indicating the numbering plan used for that number (e.g.\ ISDN number, Telex number). .RT .sp 1P .LP 2.56 \fBOdd/even indicator\fR .sp 9p .RT .PP Information sent in association with an address, indicating whether the number of address signals contained in the address is even or odd. .RT .sp 1P .LP 2.57 \fBOriginal called number\fR .sp 9p .RT .PP Information sent in the forward direction when a call is redirected and identifies the original called party. .RT .sp 1P .LP 2.58 \fBOriginal redirection reason\fR .sp 9p .RT .PP Information sent in either direction indicating the reason why the call was originally redirected. .RT .sp 1P .LP 2.59 \fBPoint code\fR .sp 9p .RT .PP Information sent in the call reference parameter indicating the code of the signalling point in which the call identity allocated to the call reference is relevant. .RT .sp 1P .LP 2.60 \fBProtocol class\fR .sp 9p .RT .PP Information sent in the connection request parameter indicating the protocol class requested by the signalling connection control part for the end\(hyto\(hyend connection. .RT .sp 1P .LP 2.61 \fBProtocol control indicator\fR .sp 9p .RT .PP Information consisting of the end\(hyto\(hyend method indicator, the interworking indicator, the end\(hyto\(hyend information indicator, the SCCP method indicator and the ISDN user part indicator. The protocol control indicator is contained in both the forward and backward call indicators parameter field and describes the signalling capabilities within the network connection. .bp .RT .sp 1P .LP 2.62 \fBRange\fR .sp 9p .RT .PP Information sent in a circuit group supervision message (e.g.\ circuit group blocking) to indicate the range of circuits affected by the action in the message. .RT .sp 1P .LP 2.63 \fBRecommendation indicator\fR .sp 9p .RT .PP Information sent in association with a cause value identifying the Recommendation to which the cause value applies. .RT .sp 1P .LP 2.64 \fBRedirecting indicator\fR .sp 9p .RT .PP Information sent in either direction indicating whether the call has been forwarded or rerouted and whether or not presentation of redirection information to the calling party is restricted. .RT .sp 1P .LP 2.65 \fBRedirecting number\fR .sp 9p .RT .PP Information sent in the forward direction when a call is redirected more than once, indicating the number from which the call was last redirected. .RT .sp 1P .LP 2.66 \fBRedirecting reason\fR .sp 9p .RT .PP Information sent in either direction indicating, in the case of calls undergoing multiple redirections, the reason why the call has been redirected. .RT .sp 1P .LP 2.67 \fBRedirection counter\fR .sp 9p .RT .PP Information sent in either direction indicating the number of redirections which have occurred on a call. .RT .sp 1P .LP 2.68 \fBRedirection number\fR .sp 9p .RT .PP Information sent in the backward direction indicating the number towards which the call must be rerouted or has been forwarded. .RT .sp 1P .LP 2.69 \fBRouting label\fR .sp 9p .RT .PP Information provided to the message transfer part for the purpose of message routing (see Recommendation\ Q.704, \(sc\ 2.2). .RT .sp 1P .LP 2.70 \fBSatellite indicator\fR .sp 9p .RT .PP Information sent in the forward direction indicating the number of satellite circuits in the connection. .RT .sp 1P .LP 2.71 \fBSCCP method indicator\fR .sp 9p .RT .PP Information sent in either direction indicating the available SCCP methods, if any, for end\(hyto\(hyend transfer of information. .RT .sp 1P .LP 2.72 \fBScreening indicator\fR .sp 9p .RT .PP Information sent in either direction to indicate whether the address was provided by the user or network. .RT .sp 1P .LP 2.73 \fBSignalling point code\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in a release message to identify the signalling point in which the call failed. .RT .sp 1P .LP 2.74 \fBSolicited information indicator\fR .sp 9p .RT .PP Information sent in an information message to indicate whether or not the message is a response to an information request message. .bp .RT .sp 1P .LP 2.75 \fBStatus\fR .sp 9p .RT .PP Information sent in a circuit group supervision message (e.g.\ circuit group blocking) to indicate the specific circuits, within the range of circuits stated in the message, that are affected by the action specified in the message. .RT .sp 1P .LP 2.76 \fBSuspend/Resume indicator\fR .sp 9p .RT .PP Information sent in the suspend and resume messages to indicate whether suspend/resume was initiated by an ISDN subscriber or by the network. .RT .sp 1P .LP 2.77 \fBTemporary trunk blocking after release\fR \fI(national use)\fR .sp 9p .RT .PP Information sent to the exchange at the other end of a circuit (trunk) to indicate low level of congestion at the sending exchange and that the circuit (trunk) should not be re\(hyoccupied by the receiving exchange for a short period of time after release. .RT .sp 1P .LP 2.78 \fBTransit network selection\fR \fI(national use)\fR .sp 9p .RT .PP Information sent in the initial address message indicating the transit network(s) requested to be used in the call. .RT .sp 1P .LP 2.79 \fBTransmission medium requirement\fR .sp 9p .RT .PP Information sent in the forward direction indicating the type of transmission medium required for the connection (e.g.\ 64\ kbit/s unrestricted, speech). .RT .sp 1P .LP 2.80 \fBUser service information\fR .sp 9p .RT .PP Information sent in the forward direction indicating the bearer capability requested by the calling party. .RT .sp 1P .LP 2.81 \fBUser\(hyto\(hyuser indicators\fR .sp 9p .RT .PP Information sent in association with a request (or response to a request) for user\(hyto\(hyuser signalling supplementary service(s). .RT .sp 1P .LP 2.82 \fBUser\(hyto\(hyuser information\fR .sp 9p .RT .PP Information generated by a user and transferred transparently through the interexchange network between the originating and terminating local exchanges. .RT .LP .rs .sp 16P .ad r Blanc .ad b .RT .LP .bp .ce \fBH.T. [T1.762]\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(348p) . TABLE\ 1/Q.762 (Sheet 1 of 3) .T& cw(348p) . { \fBMandatory or optional parameters in the ISDN\fR \fBuser part messages\fR } .TE .nr PS 9 .RT .ad r \fBTableau 1/Q.762 (feuillet 1 sur 3) [T1.762]\ \ \ A L'ITALIENNE, p. 3\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [1T2.762]\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(348p) . TABLE\ 1/Q.762 (Sheet 2 of 3) .T& cw(348p) . { \fBMandatory or optional parameters in the ISDN\fR \fBuser part messages\fR } .TE .nr PS 9 .RT .ad r \fBTableau 1/Q.762 (feuillet 2 sur 3) [1T2.762]\ \ \ A L'ITALIENNE, p. 4\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [2T2.762]\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(348p) . TABLE\ 1/Q.762 (Sheet 3 of 3) .T& cw(348p) . { \fBMandatory or optional parameters in the ISDN\fR \fBuser part messages\fR } .TE .nr PS 9 .RT .ad r \fBTableau 1/Q.762 (feuillet 3 sur 3) [2T2.762]\ \ \ A L'ITALIENNE, p. 5\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [T3.762]\fR .ce TABLE\ A\(hy2/Q.762 .ce \fBISDN user part message acronyms\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; lw(30p) | lw(30p) | lw(30p) | lw(138p) . .TE .nr PS 9 .RT .ad r \fBTableau 2/Q.762 [T3.762], p. 6\fR .sp 1P .RT .ad b .RT .LP .bp .sp 2P .LP \fBRecommendation\ Q.763\fR .RT .sp 2P .sp 1P .ce 1000 \fBFORMATS\ AND\ CODES\fR .EF '% Fascicle\ VI.8\ \(em\ Rec.\ Q.763'' .OF '''Fascicle\ VI.8\ \(em\ Rec.\ Q.763 %' .ce 0 .sp 1P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP ISDN user part messages are carried on the signalling link by means of signal units the format of which is described in Recommendation\ Q.703, \(sc\ 2.2. .PP The format of and the codes used in the service information octet are described in Recommendation\ Q.704, \(sc\ 14.2. The service indicator for the ISDN user part is coded\ 0101. .PP The signalling information field of each message signal unit containing an ISDN user part message consists of an integral number of octets and encompasses the following parts (see Figure\ 1/Q.763): .RT .LP a) routing label; .LP b) circuit identification code; .LP c) message type code; .LP d) the mandatory fixed part; .LP e) the mandatory variable part; .LP f ) the optional part, which may contain fixed length and variable length parameter fields. .PP \fINote\fR \ \(em\ The service information octet, the routing label and circuit identification code are not included in the SCCP user data parameter transferred between the ISDN user part and signalling connection control part. .PP A description of the various message parts is given in the following sections. .RT .LP .rs .sp 28P .ad r \fBFigure 1/Q.763, (M), p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 1.1 \fIRouting label\fR .sp 9p .RT .PP The format and codes used for the routing label are described in Recommendation\ Q.704, \(sc\ 2.2. For each individual circuit connection, the same routing label must be used for each message that is transmitted for that connection. .RT .sp 1P .LP 1.2 \fICircuit identification code\fR .sp 9p .RT .PP The format of the circuit identification code (CIC) is shown in Figure\ 2/Q.763. .RT .LP .rs .sp 10P .ad r \fBFigure 2/Q.763, (M), p.\fR .sp 1P .RT .ad b .RT .PP The allocation of circuit identification codes to individual circuits is determined by bilateral agreement and/or in accordance with applicable predetermined rules. .PP For international applications, the four spare bits of the circuit identification field are reserved for CIC extension, provided that bilateral agreement is obtained before any increase in size is performed. For national applications, the four spare bits can be used as required. .PP Allocations for certain applications are defined below: .RT .sp 1P .LP a) \fI2048 kbit/s digital path\fR .sp 9p .RT .LP For circuits which are derived from a 2048\ kbit/s digital path (Recommendations\ G.732 and G.734) the circuit identification code contains in the 5\ least significant bits a binary representation of the actual number of the time slot which is assigned to the communication path. .LP The remaining bits in the circuit identification code are used, where necessary, to identify these circuits uniquely among all other circuits of other systems interconnecting an originating and destination point. .sp 1P .LP b) \fI8448 kbit/s digital path\fR .sp 9p .RT .LP For circuits which are derived from a 8448\ kbit/s digital path (Recommendations\ G.744 and G.747) the circuit identification code contains in the 7 least significant bits an identfication of the circuit which is assigned to the communication path. The codes in Table\ 1/Q.763 are used. .LP The remaining bits in the circuit identification code are used, where necessary, to identify these circuits uniquely among all other circuits of other systems interconnecting an originating and destination point. .sp 1P .LP c) \fIFrequency division multiplex (FDM) systems in networks\fR \fIusing the 2048 kbit/s pulse code modulation standard\fR .sp 9p .RT .LP For frequency division multiplex systems existing in networks that also use the 2048 kbit/s pulse code modulation standard, the circuit identification code contains in the 6\ least significant bits the identification of a circuit within a group of 60\ circuits carried by 5\ basic frequency division multiplex groups which may or may not be part of the same supergroup. The codes in Table\ 2/Q.763 are used. .LP The remaining bits in the circuit identification code are used, where necessary, to identify these circuits uniquely among all other circuits of other systems interconnecting an originating and destination point. .bp .ce \fBH.T. [T1.763]\fR .ce TABLE\ 1/Q.763 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(42p) | cw(42p) . 0\ 0\ 0\ 0\ 0\ 0\ 0 Circuit 1\ \ _ .T& cw(42p) | cw(42p) . 0\ 0\ 0\ 0\ 0\ 0\ 1 Circuit 2\ \ .T& cw(42p) | cw(42p) . @ left | right | @ .T& cw(42p) | cw(42p) . 0\ 0\ 1\ 1\ 1\ 1\ 1 Circuit 32\ _ .T& cw(42p) | cw(42p) . 0\ 1\ 0\ 0\ 0\ 0\ 0 Circuit 33\ .T& cw(42p) | cw(42p) . @ left | right | @ .T& cw(42p) | cw(42p) . 1\ 1\ 1\ 1\ 1\ 1\ 0 Circuit 127 _ .T& cw(42p) | cw(42p) . 1\ 1\ 1\ 1\ 1\ 1\ 1 Circuit 128 _ .TE .nr PS 9 .RT .ad r \fBTableau 1/Q.763 [T1.763], p.\fR .sp 1P .RT .ad b .RT .ce \fBH.T. [T2.763]\fR .ce TABLE\ 2/Q.763 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(42p) | cw(42p) | lw(66p) . 0\ 0\ 0\ 0\ 0\ 0 Unallocated _ .T& cw(42p) | cw(42p) | lw(66p) . { 0\ 0\ 0\ 0\ 0\ 1 [Unable to Convert Formula] Circuit 12 } 1st basic (FDM) group _ .T& cw(42p) | cw(42p) | lw(66p) . { 0\ 0\ 1\ 1\ 0\ 1 0\ 0\ 1\ 1\ 1\ 0 0\ 0\ 1\ 1\ 1\ 1 0\ 1\ 0\ 0\ 0\ 0 0\ 1\ 0\ 0\ 0\ 1 [Unable to Convert Formula] Circuit 12 } 2nd basic (FDM) group _ .T& cw(42p) | cw(42p) | lw(66p) . { 0\ 1\ 1\ 0\ 1\ 0 @ left | 0\~1\~1\~1\~1\~1~1\~0\~0\~0\~0\~0~1\~0\~0\~0\~0\~1 right | @ 1\ 0\ 0\ 1\ 1\ 0 } { Circuit 1\ @ left | Circuit~6\~~Unallocated~Circuit~7\~ right | @ Circuit 12 } 3rd basic (FDM) group _ .T& cw(42p) | cw(42p) | lw(66p) . { 1\ 0\ 0\ 1\ 1\ 1 [Unable to Convert Formula] Circuit 9\ Unallocated Circuit 10 Circuit 11 Circuit 12 } 4th basic (FDM) group _ .T& cw(42p) | cw(42p) | lw(66p) . { 1\ 1\ 0\ 1\ 0\ 0 [Unable to Convert Formula] Circuit 12 } 5th basic (FDM) group _ .TE .nr PS 9 .RT .ad r \fBTableau 2/Q.763 [T2.763], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 1.3 \fIMessage type code\fR .sp 9p .RT .PP The message type code consists of a one octet field and is mandatory for all messages. The message type code uniquely defines the function and format of each ISDN user part message. .PP The allocation with reference to the appropriate descriptive section of this Recommendation is summarized in Table\ 3/Q.763. .RT .sp 1P .LP 1.4 \fIFormatting principles\fR .sp 9p .RT .PP Each message consists of a number of PARAMETERS listed and described in \(sc\ 2. Each parameter has a NAME which is coded as a single octet (see Table\ 4/Q.763). The length of a parameter may be fixed or variable, and a LENGTH INDICATOR of one octet for each parameter may be included as described below. .PP The detailed format is uniquely defined for each message type as described in \(sc\ 3. .PP A general format diagram is shown in Figure\ 3/Q.763. .RT .sp 1P .LP 1.5 \fIMandatory fixed part\fR .sp 9p .RT .PP Those parameters that are mandatory and of fixed length for a particular message type will be contained in the \fImandatory fixed part\fR . The position, length and order of the parameters is uniquely defined by the message type, thus the names of the parameters and the length indicators are not included in the message. .RT .sp 1P .LP 1.6 \fIMandatory variable part\fR .sp 9p .RT .PP Mandatory parameters of variable length will be included in the \fImandatory variable part\fR . Pointers are used to indicate the beginning of each parameter. Each pointer is encoded as a single octet. The name of each parameter and the order in which the pointers are sent is implicit in the message type. Parameter names are, therefore, not included in the message. The details of how pointers are encoded is found in \(sc\ 2.3. The number of parameters, and thus the number of pointers is uniquely defined by the message type. .PP A pointer is also included to indicate the beginning of the optional part. If the message type indicates that no optional part is allowed, then this pointer will not be present. If the message type indicates that an optional part is possible, but there is no optional part included in this particular message than a pointer field containing all zeros will be used. It is recommended that all future message types with a mandatory variable part indicate that an optional part is allowed. .PP All the pointers are sent consecutively at the beginning of the mandatory variable part. Each parameter contains the parameter length indicator followed by the contents of the parameters. .RT .sp 1P .LP 1.7 \fIOptional part\fR .sp 9p .RT .PP The optional part consists of parameters that may or may not occur in any particular message type. Both fixed length and variable length parameters may be included. Optional parameters may be transmitted in any order. Each optional parameter will include the parameter name (one octet) and the length indicator (one octet) followed by the parameter contents. .RT .sp 1P .LP 1.8 \fIEnd of optional parameters octet\fR .sp 9p .RT .PP If optional parameters are present and after all optional parameters have been sent, an \*Qend of optional parameters\*U octet containing all zeros will be transmitted. .RT .sp 1P .LP 1.9 \fIOrder of transmission\fR .sp 9p .RT .PP Since all the fields consist of an integral number of octets, the formats are presented as a stack of octets. The first octet transmitted is the one shown at the top of the stack and the last is the one at the bottom (see Figure\ 3/Q.763). .PP Unless otherwise indicated, within each octet and subfield the bits are transmitted with the least significant bit first. .RT .sp 1P .LP 1.10 \fICoding of spare bits\fR .sp 9p .RT .PP Spare bits are coded 0 unless indicated otherwise. .bp .RT .LP .rs .sp 40P .ad r \fBFigure 3/Q.763, (M), p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 1.11 \fINational message types and parameters\fR .sp 9p .RT .PP If message type codes and parameter name codes are required for national uses not included in this Recommendation, the codes chosen should be from the highest code downwards, that is, starting at code 11111111. Codes in the range 11111111 to 11100000 are reserved exclusively for this purpose. .RT .sp 2P .LP \fB2\fR \fBParameter formats and codes\fR .sp 1P .RT .sp 1P .LP 2.1 \fIMessage type codes\fR .sp 9p .RT .PP The encoding of the message type is shown in Table\ 3/Q.763. .bp .RT .ce \fBH.T. [T3.763]\fR .ce TABLE\ 3/Q.763 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(156p) | cw(36p) | cw(36p) . Message type Reference (Table) Code _ .T& lw(156p) | cw(36p) | cw(36p) . Address complete \ 5/Q.763 00000110 .T& lw(156p) | cw(36p) | cw(36p) . Answer \ 6/Q.763 00001001 .T& lw(156p) | cw(36p) | cw(36p) . Blocking 23/Q.763 00010011 .T& lw(156p) | cw(36p) | cw(36p) . Blocking acknowledgement 23/Q.763 00010101 .T& lw(156p) | cw(36p) | cw(36p) . Call modification completed 24/Q.763 00011101 .T& lw(156p) | cw(36p) | cw(36p) . Call modification request 24/Q.763 00011100 .T& lw(156p) | cw(36p) | cw(36p) . Call modification reject 24/Q.763 00011110 .T& lw(156p) | cw(36p) | cw(36p) . Call progress \ 7/Q.763 00101100 .T& lw(156p) | cw(36p) | cw(36p) . Circuit group blocking 25/Q.763 00011000 .T& lw(156p) | cw(36p) | cw(36p) . { Circuit group blocking acknowledgement } 25/Q.763 00011010 .T& lw(156p) | cw(36p) | cw(36p) . Circuit group query 26/Q.763 00101010 .T& lw(156p) | cw(36p) | cw(36p) . Circuit group query response \ 8/Q.763 00101011 .T& lw(156p) | cw(36p) | cw(36p) . Circuit group reset 26/Q.763 00010111 .T& lw(156p) | cw(36p) | cw(36p) . { Circuit group reset acknowledgement } \ 9/Q.763 00101001 .T& lw(156p) | cw(36p) | cw(36p) . Circuit group unblocking 25/Q.763 00011001 .T& lw(156p) | cw(36p) | cw(36p) . { Circuit group unblocking acknowledgement } 25/Q.763 00011011 .T& lw(156p) | cw(36p) | cw(36p) . { Charge information | ua\d\u)\d } (see Note) 00110001 .T& lw(156p) | cw(36p) | cw(36p) . Confusion 10/Q.763 00101111 .T& lw(156p) | cw(36p) | cw(36p) . Connect 11/Q.763 00000111 .T& lw(156p) | cw(36p) | cw(36p) . Continuity 12/Q.763 00000101 .T& lw(156p) | cw(36p) | cw(36p) . Continuity check request 23/Q.763 00010001 .T& lw(156p) | cw(36p) | cw(36p) . Delayed release | ua\d\u)\d 21/Q.763 00100111 .T& lw(156p) | cw(36p) | cw(36p) . Facility accepted 27/Q.763 00100000 .T& lw(156p) | cw(36p) | cw(36p) . Facility reject 13/Q.763 00100001 .T& lw(156p) | cw(36p) | cw(36p) . Facility request 27/Q.763 00011111 .T& lw(156p) | cw(36p) | cw(36p) . Forward transfer 21/Q.763 00001000 .T& lw(156p) | cw(36p) | cw(36p) . Information 14/Q.763 00000100 .T& lw(156p) | cw(36p) | cw(36p) . Information request 15/Q.763 00000011 .T& lw(156p) | cw(36p) | cw(36p) . Initial address 16/Q.763 00000001 .T& lw(156p) | cw(36p) | cw(36p) . { Loop back acknowledgement | ua\d\u)\d } 23/Q.763 00100100 .T& lw(156p) | cw(36p) | cw(36p) . Overload | ua\d\u)\d 23/Q.763 00110000 .T& lw(156p) | cw(36p) | cw(36p) . Pass\(hyalong 28/Q.763 00101000 .T& lw(156p) | cw(36p) | cw(36p) . Release 17/Q.763 00001100 .T& lw(156p) | cw(36p) | cw(36p) . Release complete 18/Q.763 00010000 .T& lw(156p) | cw(36p) | cw(36p) . Reset circuit 23/Q.763 00010010 .T& lw(156p) | cw(36p) | cw(36p) . Resume 22/Q.763 00001110 .T& lw(156p) | cw(36p) | cw(36p) . Subsequent address 19/Q.763 00000010 .T& lw(156p) | cw(36p) | cw(36p) . Suspend 22/Q.763 00001101 .T& lw(156p) | cw(36p) | cw(36p) . Unblocking 23/Q.763 00010100 .T& lw(156p) | cw(36p) | cw(36p) . Unblocking acknowledgement 23/Q.763 00010110 .T& lw(156p) | cw(36p) | cw(36p) . Unequipped CIC | ua\d\u)\d 23/Q.763 00101110 .T& lw(156p) | cw(36p) | cw(36p) . { User\(hyto\(hyuser information } 20/Q.763 00101101 _ .T& lw(156p) | cw(36p) | cw(36p) . { Reserved (used in 1984 version) } { 00001010 00001011 00001111 00100010 00100011 00100101 00100110 } .TE .LP \ua\d\u)\d\ For national use only .LP \fINote\fR \ \(em\ The format of this message is a national matter. .nr PS 9 .RT .ad r \fBTableau 3/Q.763 [T3.763], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 2.2 \fICoding of the length indicator\fR .sp 9p .RT .PP The length indicator field is binary coded to indicate the number of octets in the parameter content field. The length indicated does not include the parameter name octet or the length indicator octet. .RT .sp 1P .LP 2.3 \fICoding of the pointers\fR .sp 9p .RT .PP The pointer value (in binary) gives the number of octets between the pointer itself (included) and the first octet (not included) of the parameter associated with that pointer. .PP The pointer value all zeros is used to indicate that, in the case of optional parameters, no optional parameter is present. .RT .sp 2P .LP \fB3\fR \fBISDN user part parameters\fR .sp 1P .RT .sp 1P .LP 3.1 \fIParameter names\fR .sp 9p .RT .PP The parameter name codes are given in Table\ 4/Q.763 together with references to the subsections in which they are described. .RT .sp 1P .LP 3.2 \fIAccess transport\fR .sp 9p .RT .PP The format of the access transport parameter field is shown in Figure\ 4/Q.763. .RT .LP .rs .sp 9P .ad r \fBFigure 4/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .PP The information element is coded as described in Recommendation\ Q.931, \(sc\ 4.5. Multiple\ Q.931 information elements can be included within the access transport parameter. The information elements applicable to a particular usage of the access transport parameter are dependent on, and will be determined by, the relevant procedures. .sp 1P .LP 3.3 \fIAutomatic congestion level\fR .sp 9p .RT .PP The format of the automatic congestion level parameter field is shown in Figure\ 5/Q.763. .RT .LP .rs .sp 7P .ad r \fBFigure 5/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [T4.763]\fR .ce TABLE\ 4/Q.763 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(156p) | cw(36p) | cw(36p) . Parameter name Reference ( \(sc ) Code _ .T& lw(156p) | cw(36p) | cw(36p) . Access transport 3.2\ 00000011 .T& lw(156p) | cw(36p) | cw(36p) . Automatic congestion level 3.3\ 00100111 .T& lw(156p) | cw(36p) | cw(36p) . Backward call indicators 3.4\ 00010001 .T& lw(156p) | cw(36p) | cw(36p) . Call modification indicators 3.5\ 00010111 .T& lw(156p) | cw(36p) | cw(36p) . Call reference 3.6\ 00000001 .T& lw(156p) | cw(36p) | cw(36p) . Called party number 3.7\ 00000100 .T& lw(156p) | cw(36p) | cw(36p) . Calling party number 3.8\ 00001010 .T& lw(156p) | cw(36p) | cw(36p) . Calling party's category 3.9\ 00001001 .T& lw(156p) | cw(36p) | cw(36p) . Cause indicators 3.10 00010010 .T& lw(156p) | cw(36p) | cw(36p) . { Circuit group supervision message type indicator } 3.11 00010101 .T& lw(156p) | cw(36p) | cw(36p) . Circuit state indicator 3.12 00100110 .T& lw(156p) | cw(36p) | cw(36p) . { Closed user group interlock code } 3.13 00011010 .T& lw(156p) | cw(36p) | cw(36p) . Connected number 3.14 00100001 .T& lw(156p) | cw(36p) | cw(36p) . Connection request 3.15 00001101 .T& lw(156p) | cw(36p) | cw(36p) . Continuity indicators 3.16 00010000 .T& lw(156p) | cw(36p) | cw(36p) . End of optional parameters 3.17 00000000 .T& lw(156p) | cw(36p) | cw(36p) . Event information 3.18 00100100 .T& lw(156p) | cw(36p) | cw(36p) . Facility indicator 3.19 00011000 .T& lw(156p) | cw(36p) | cw(36p) . Forward call indicators 3.20 00000111 .T& lw(156p) | cw(36p) | cw(36p) . Information indicators 3.21 00001111 .T& lw(156p) | cw(36p) | cw(36p) . { Information request indicators } 3.22 00001110 .T& lw(156p) | cw(36p) | cw(36p) . { Nature of connection indicators } 3.23 00000110 .T& lw(156p) | cw(36p) | cw(36p) . { Optional backward call indicators } 3.24 00101001 .T& lw(156p) | cw(36p) | cw(36p) . { Optional forward call indicators } 3.25 00001000 .T& lw(156p) | cw(36p) | cw(36p) . Original called number 3.26 00101000 .T& lw(156p) | cw(36p) | cw(36p) . Range and status 3.27 00010110 .T& lw(156p) | cw(36p) | cw(36p) . Redirecting number 3.28 00001011 .T& lw(156p) | cw(36p) | cw(36p) . Redirection information 3.29 00010011 .T& lw(156p) | cw(36p) | cw(36p) . Redirection number 3.30 00001100 .T& lw(156p) | cw(36p) | cw(36p) . { Signalling point code | ua\d\u)\d } 3.31 00011110 .T& lw(156p) | cw(36p) | cw(36p) . Subsequent number 3.32 00000101 .T& lw(156p) | cw(36p) | cw(36p) . Suspend/Resume indicators 3.33 00100010 .T& lw(156p) | cw(36p) | cw(36p) . { Transit network selection | ua\d\u)\d } 3.34 00100011 .T& lw(156p) | cw(36p) | cw(36p) . { Transmission medium requirement } 3.35 00000010 .T& lw(156p) | cw(36p) | cw(36p) . User service information 3.36 00011101 .T& lw(156p) | cw(36p) | cw(36p) . User\(hyto\(hyuser indicators 3.37 00101010 .T& lw(156p) | cw(36p) | cw(36p) . { User\(hyto\(hyuser information } 3.38 00100000 _ .T& lw(156p) | cw(36p) | cw(36p) . { Reserved (used in 1984 version, Red Book) } { 00010100 00011001 00011011 00011100 00011111 } .T& lw(156p) | cw(36p) | cw(36p) . { Reserved for multi\(hyslot identifier } 00100101 .TE .LP \ua\d\u)\d\ For national use only .nr PS 9 .RT .ad r \fBTableau 4/Q.763 [T4.763], p.\fR .sp 1P .RT .ad b .RT .LP .bp .PP The following codes are used in the automatic congestion level parameter field: .LP 00000000 spare .LP 00000001 congestion level 1 exceeded .LP 00000010 congestion level 2 exceeded .LP 00000011 .LP \ | o spare .LP 11111111 .sp 1P .LP 3.4 \fIBackward call indicators\fR .sp 9p .RT .PP The format of the backward call indicators parameter field is shown in Figure\ 6/Q.763. .RT .LP .rs .sp 10P .ad r \fBFigure 6/Q.763, (MC), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the backward call indicators parameter field: .LP bits B A: Charge indicator .LP 0 0 no indication .LP 0 1 no charge .LP 1 0 charge .LP 1 1 spare .LP bits D C: Called party's status indicator .LP 0 0 no indication .LP 0 1 subscriber free .LP 1 0 connect when free .LP 1 1 spare .LP bits F E: Called party's category indicator .LP 0 0 no indication .LP 0 1 ordinary subscriber .LP 1 0 payphone .LP 1 1 spare .LP bits H G: End\(hyto\(hyend method indicator (Note) .LP 0 0 no end\(hyto\(hyend method available (only link\(hyby\(hylink method available) .LP 0 1 pass along method available .LP 1 0 SCCP method available .LP 1 1 pass along and SCCP methods available .LP bit I: Interworking indicator (Note) .LP 0 no interworking encountered .LP 1 interworking encountered .LP bit J: End\(hyto\(hyend information indicator (Note) .LP 0 no end\(hyto\(hyend information available .LP 1 end\(hyto\(hyend information available .LP bit K: ISDN User Part indicator (Note) .LP 0 ISDN User Part not used all the way .LP 1 ISDN User Part used all the way .LP bit L: Holding indicator (national use) .LP 0 holding not requested .LP 1 holding requested .bp .LP bit M: ISDN access indicator .LP 0 terminating access non\(hyISDN .LP 1 terminating access ISDN .LP bit N: Echo control device indicator .LP 0 incoming half echo control device not included .LP 1 incoming half echo control device included .LP bits P O: SCCP method indicator .LP 0 0 no indication .LP 0 1 connectionless method available .LP 1 0 connection oriented method available .LP 1 1 connectionless and connection oriented methods available .PP \fINote\fR \ \(em\ Bits G\(hyK and O\(hyP constitute the protocol control indicator. .sp 1P .LP 3.5 \fICall modification indicators\fR .sp 9p .RT .PP The format of the call modification indicators parameter field is shown in Figure\ 7/Q.763. .RT .LP .rs .sp 8P .ad r \fBFigure 7/Q.763, (MC), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the call modification indicators parameter field: .LP bits B A: Modification indicator .LP 0 0 spare .LP 0 1 modify to service 1 .LP 1 0 modify to service 2 .LP 1 1 spare .LP bits H C: Spare .PP \fINote\fR \ \(em\ Service 1 and 2 are described by the transmission medium requirement. .sp 1P .LP 3.6 \fICall reference\fR .sp 9p .RT .PP The format of the call reference parameter is shown in Figure\ 8/Q.763. .RT .LP .rs .sp 15P .ad r \fBFigure 8/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .LP .bp .PP The following codes are used in the subfields of the call reference parameter field: .sp 1P .LP a) \fICall identity\fR .sp 9p .RT .LP A code expressing in pure binary representation the identification number allocated to the call. .sp 1P .LP b) \fIPoint code\fR .sp 9p .RT .LP The code of the signalling point in which the call identity is relevant. .sp 1P .LP 3.7 \fICalled party number\fR .sp 9p .RT .PP The format of the called party number parameter field is shown in Figure\ 9/Q.763. .RT .LP .rs .sp 15P .ad r \fBFigure 9/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the subfields of the called party number parameter field: .sp 1P .LP a) \fIOdd/even indicator\fR .sp 9p .RT .LP 0\ \ even number of address signals .LP 1\ \ odd number of address signals .sp 1P .LP b) \fINature of address indicator\fR .sp 9p .RT .LP 0000000 spare .LP 0000001 subscriber number .LP 0000010 spare, reserved for national use .LP 0000011 national (significant) number .LP 0000100 international number .LP 0000101 .LP \ | o spare .LP 1101111 .LP 1110000 .LP \ | o reserved for national use .LP 1111110 .LP 1111111 spare .sp 1P .LP c) \fIInternal network number indicator (INN ind.)\fR .sp 9p .RT .LP 0\ \ routing to internal network number allowed .LP 1\ \ routing to internal network number not allowed .bp .sp 1P .LP d) \fINumbering plan indicator\fR .sp 9p .RT .LP 000\ \ spare .LP 001\ \ ISDN (Telephony) numbering plan (Recommandation E.164,\ E.163) .LP 010\ \ spare .LP 011\ \ Data numbering plan (Recommandation\ X.121) .LP 100\ \ Telex numbering plan (Recommendation\ F.69) .LP 101\ \ reserved for national use .LP 110\ \ reserved for national use .LP 111\ \ spare .sp 1P .LP e) \fIAddress singal\fR .sp 9p .RT .LP 0000\ \ digit 0 .LP 0001\ \ digit 1 .LP 0010\ \ digit 2 .LP 0011\ \ digit 3 .LP 0100\ \ digit 4 .LP 0101\ \ digit 5 .LP 0110\ \ digit 6 .LP 0111\ \ digit 7 .LP 1000\ \ digit 8 .LP 1001\ \ digit 9 .LP 1010\ \ spare .LP 1011\ \ code\ 11 .LP 1100\ \ code\ 12 .LP 1101\ \ spare .LP 1110\ \ spare .LP 1111\ \ ST .LP The most significant address signal is sent first. Subsequent address signals are sent in successive 4\(hybit fields. .sp 1P .LP f ) \fIFiller\fR .sp 9p .RT .LP In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. .sp 1P .LP 3.8 \fICalling party number\fR .sp 9p .RT .PP The format of the calling party number parameter field is shown in Figure\ 10/Q.763. .RT .LP .rs .sp 18P .ad r \fBFigure 10/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .LP .bp .PP The following codes are used in the calling party number parameter field. .sp 1P .LP a) \fIOdd/even indicator\fR : .sp 9p .RT .LP See \(sc\ 3.7\ a). .sp 1P .LP b) \fINature of address indicator\fR .sp 9p .RT .LP 0000000 spare .LP 0000001 subscriber number .LP 0000010 spare, reserved for national use .LP 0000011 national (significant) number .LP 0000100 international number .LP 0000101 .LP \ | o spare .LP 1101111 .LP 1110000 .LP \ | o reserved for national use .LP 1111110 .LP 1111111 spare .LP \fINote\fR \ \(em\ Other types of nature of address indications (e.g.\ transit exchange identity) are for further study. .sp 1P .LP c) \fICalling party number incomplete indicator (NI)\fR .sp 9p .RT .LP 0\ \ complete .LP 1\ \ incomplete .sp 1P .LP d) \fINumbering plan indicator\fR .sp 9p .RT .LP See \(sc\ 3.7\ d). .sp 1P .LP e) \fIAddress presentation restricted (Pres. Restric.) indicator\fR .sp 9p .RT .LP 00\ \ presentation allowed .LP 01\ \ presentation restricted .LP 10\ \ address not available (Note) .LP 11\ \ spare .LP \fINote\fR \ \(em\ When the address is unavailable, the subfields in items a), b), c) and d) are coded with 0's. .sp 1P .LP f ) \fISceening indicator\fR .sp 9p .RT .LP 00\ \ reserved (Note) .LP 01\ \ user provided, verified and passed .LP 10\ \ reserved (Note) .LP 11\ \ network provided .LP \fINote\fR \ \(em\ Code 00 and 10 are reserved for \*Quser provided, not verified\*U and \*Quser provided, verified and failed\*U respectively. .sp 1P .LP g) \fIAddress signal\fR .sp 9p .RT .LP 0000 digit\ 0 .LP 0001 digit\ 1 .LP 0010 digit\ 2 .LP 0011 digit\ 3 .LP 0100 digit\ 4 .LP 0101 digit\ 5 .LP 0110 digit\ 6 .LP 0111 digit\ 7 .LP 1000 digit\ 8 .LP 1001 digit\ 9 .bp .LP 1010 spare .LP 1111 code 11 .LP 1100 code 12 .LP 1101 .LP \ to spare .LP 1111 .sp 1P .LP h) \fIFiller\fR .sp 9p .RT .LP See \(sc\ 3.7\ f). .sp 1P .LP 3.9 \fICalling party's category\fR .sp 9p .RT .PP The format of the calling party's category parameter field is shown in Figure\ 11/Q.763. .RT .LP .rs .sp 8P .ad r \fBFigure 11/Q.763, (MC), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the calling party's category parameter field. .LP 00000000 calling party's category unknown at this time .LP 00000001 operator, language French .LP 00000010 operator, language English .LP 00000011 operator, language German .LP 00000100 operator, language Russian .LP 00000101 operator, language Spanish .LP 00000110 available to Administrations for .LP 00000111 selecting a particular language .LP 00001000 by mutual agreement .LP 00001001 reserved (see Recommendation\ Q.104) (Note) .LP 00001010 ordinary calling subscriber .LP 00001011 calling subscriber with priority .LP 00001100 data call (voice band data) .LP 00001101 test call .LP 00001110 spare .LP 00001111 payphone .LP 00010000 .LP \ | o spare .LP 11011111 .LP 11100000 .LP \ | o reserved for national use .LP 11111110 .LP 11111111 spare .LP \fINote\fR \ \(em\ In national networks code 00001001 may be used to indicate that the calling party is a national operator. .sp 1P .LP 3.10 \fICause indicators\fR .sp 9p .RT .PP The format of the cause indicators parameter field is shown in Figure\ 12/Q.763. .bp .RT .LP .rs .sp 15P .ad r \fBFigure 12/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the subfields of the cause indicators parameter field: .sp 1P .LP a) \fIExtension indicator (ext)\fR .sp 9p .RT .LP 0\ \ octet continues through the next octet (e.g. octet\ 1 to\ 1a) .LP 1\ \ last octet .sp 1P .LP b) \fICoding standard\fR .sp 9p .RT .LP 00\ \ CCITT standard, as described below .LP 01\ \ reserved for other international standards (Note) .LP 10\ \ national standard (Note) .LP 11\ \ standard specific to identified location (Note) .LP \fINote\fR \ \(em\ These other coding standards should be used only when the desired cause cannot be represented with the CCITT standard. .sp 1P .LP c) \fILocation\fR .sp 9p .RT .LP 0000 user .LP 0001 private network serving the local user .LP 0010 public network serving the local user .LP 0011 transit network .LP 0100 public network serving the remote user .LP 0101 private network serving the remote user .LP 0111 international network .LP 1010 beyond an interworking point, all other values are reserved. .LP \fINote\fR \ \(em\ Depending on the location of the users, the public network serving the local user may be the same network serving the remote user. Rules for coding the location field are defined in Recommendation\ Q.931 Annex\ J. .sp 1P .LP d) \fIRecommendation\fR .sp 9p .RT .LP 0000000 Rec. Q.763 .LP 0000011 Rec. X.21 .LP 0000100 Rec. X.25 .LP 0000101 Public land mobile networks, Q.1000\ Series. .LP All other values are reserved. .LP \fINote\fR \ \(em\ If octet 1a is omitted, Recommendation\ Q.763 is assumed. .bp .sp 1P .LP e) \fICause value\fR .sp 9p .RT .LP The cause value is divided into two fields, a class (bits\ 5 through\ 7) and a value within a class (bits\ 1 through\ 4). The decimal equivalent of the cause value is shown in brackets beside the cause value. .LP Class 000 and 001\ \(em\ normal event: 0000001 (1) unallocated (unassigned) number .LP 0000010 (2) no route to specified transit network (national use) .LP 0000011 (3) no route to destination .LP 0000100 (4) send special information tone .LP 0000101 (5) misdialled trunk prefix .LP 0010000 (16) normal call clearing .LP 0010001 (17) user busy .LP 0010010 (18) no user responding .LP 0010011 (19) no answer from user (user alerted) .LP 0010101 (21) call rejected .LP 0010110 (22) number changed .LP 0011011 (27) destination out of order .LP 0011100 (28) address incomplete .LP 0011101 (29) facility rejected .LP 0011111 (31) normal \(em unspecified .LP Class 010\ \(em\ resource unavailable: 0100010 (34) no circuit available .LP 0100110 (38) network out of order .LP 0101001 (41) temporary failure .LP 0101010 (42) switching equipment congestion .LP 0101100 (44) requested channel not available .LP 0101111 (47) resource unavailable \(em unspecified .LP Class 011\ \(em\ service or option not available: 0110010 (50) requested facility not subscribed .LP 0110111 (55) incoming calls barred within CUG .LP 0111001 (57) bearer capability not authorized .LP 0111010 (58) bearer capability not presently available .LP 0111111 (63) service/option not available \(em unspecified .LP Class 100\ \(em\ service or option not implemented: 1000001 (65) bearer capability not implemented .LP 1000101 (69) requested facility not implemented .LP 1000110 (70) only restricted digital information bearer capability is available .LP 1001111 (79) service or option not implemented \(em unspecified .LP Class 101\ \(em\ invalid mesage (e.g. parameter out of range): 1010111 (87) called user not member of CUG .LP 1011000 (88) incompatible destination .LP 1011011 (91) invalid transit network selection (national use) .LP 1011111 (95) invalid message \(em unspecified .LP Class 110\ \(em\ protocol error (e.g. unknown message): 1100001 (97) message type non\(hyexistant or not implemented .LP 1100011 (99) parameter non\(hyexistant or not implemented \(em discarded .LP 1100101 (103) parameter non\(hyexistent or not implemented \(em passed on .LP 1101111 (111) protocol error \(em unspecified .LP Class 111\ \(em\ interworking: 1111111 (127) interworking unspecified .bp .LP f ) \fIDiagnostic\fR .LP The format and existence of the diagnostic field is dependant on the cause value and the location of generation. For causes generated by a public network, the following diagnostics may be included: .LP \fICause\fR \fIDiagnostic\fR \fIFormat\fR .LP \ \ 1 Condition See below .LP \ \ 2 Transit Network identity See \(sc\ 3.34 (Note) .LP \ \ 3 Condition See below .LP \ 16 Condition See below .LP \ 21 Condition See below .LP \ 22 Called party number (new) See \(sc\ 3.7 (Note) .LP \ 29 Rejected parameter (Note) .LP \ 50 Rejected parameter (Note) .LP \ 57 Attribute identity See below .LP \ 58 Attribute identity See below .LP \ 65 Attribute identity See below .LP \ 69 Rejected parameter (Note) .LP \ 97 Message type See Table 3/Q.763 .LP \ 99 Parameter name(s) See Table 4/Q.763 .LP 103 Parameter name(s) See Table 4/Q.763 .LP \fINote\fR \ \(em\ These diagnostics shall also include the parameter name and length octets. .LP 1) \fIDiagnostic with attribute identity\fR .LP The format of the diagnostic field when coded with an attribute identity is shown in Figure\ 13/Q.763. .LP .rs .sp 9P .ad r \fBFigure 13/Q.763, (N), p.\fR .sp 1P .RT .ad b .RT .LP The attribute number subfield identifies the rejected attribute as follows: .LP 0110001 Information transfer capability .LP 0110010 Information transfer mode .LP 0110011 Information transfer rate .LP 0110100 Structure .LP 0110101 Configuration .LP 0110110 Etablishment .LP 0110111 Symmetry .LP 0111000 Information transfer rate (dest to orig) .LP 0111001 Layer identification and corresponding user information .LP The rejected attribute and available attribute subfields are coded the same as in the equivalent octet of the user service information parameter field (see \(sc\ 3.36) which contains the relevant attribute. Bits not related to the rejected attribute are coded\ 0. If more than one bearer capability attribute was rejected, the diagnostic field can be repeated. .LP The extension bit (ext), when coded 0, indicates that this diagnostic continues to the next octet (e.g. octet\ 3a to\ 3b). The inclusion of the available attribute subfield is optional. .bp .LP 2) \fICondition diagnostic\fR .LP A condition diagnostic is a 1 octet field containing an extension bit (bit\ 8) and one of the following codes in bits\ 2\(hy1: .LP 00\ \ unknown .LP 01\ \ permanent .LP 10\ \ transient .LP 11\ \ spare .LP Bits 3 to 7 of a condition diagnostic are spare. .sp 1P .LP 3.11 \fICircuit group supervision message type indicator\fR .sp 9p .RT .PP The format of the circuit group supervision message type indicator parameter field is shown in Figure\ 14/Q.763. .RT .LP .rs .sp 9P .ad r \fBFigure 14/Q.763, (MC), p.\fR .sp 1P .RT .ad b .RT .PP The following codes are used in the circuit group supervision message type indicator parameter field: .LP bits B A: Type indicator .LP 0 0 maintenance oriented .LP 0 1 hardward failure oriented .LP 1 0 reserved for national use (used in 1984 version) .LP 1 1 spare .LP bits C H: Spare .LP .rs .sp 22P .sp 2P .LP \fBMONTAGE : SUITE RECOMMANDATION Q.763 SUR LE RESTE DE CETTE PAGE\fR .sp 1P .RT .LP .bp