Telephone Network Interconnection Using. ITU-T No. 7 Signalling PART C ISUP Specification

Specification PTC 331 Telephone Network Interconnection using ITU-T No.
7 Signalling PART C ISUP SPECIFICATION

Recommendation Q.763 MESSAGE AND PARAMETER FORMATS AND CODES and Recommendation Q.764 SIGNALLING PROCEDURES
Issue 2: March 2001
PTC 331:2001 Issue 2
(This page intentionally blank)
C-1
CONTENTS Section Title Page C- .
0
0.1 0.2 0.3 0.4 0.5 0.6
Introduction
Scope Relationship with ITU-T Recommendations General Interworking with non-ISUP signalling systems ISUP-ISUP interworking at the Telecom POI exchange Changes from Issue 1
5
5 5 6 6 6 7
1
1.0 1.0.1 1.0.2 1.0.3 1.0.4 1.0.5 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13
General
Scope, references, definitions, abbreviations Scope References Terms and definitions Abbreviations General coding principles Routing label Circuit identification code Message type code Formatting principles Mandatory fixed part Mandatory variable part Optional part End of optional parameters octet Order of transmission Coding of spare bits National message types and parameters Rules for the allocation of message types codes and parameter name codes Meaning of "spare" codes and "reserved" codes
7
7 7 7 8 8 9 10 10 11 13 14 14 14 14 14 15 15 16 16
2
2.1 2.2 2.3
Parameter formats and codes

Message type codes Coding of the length indicator Coding of the pointers
16
16 16 16
3
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10
ISDN user part parameter

Parameter names Access delivery information Access transport Automatic congestion level Backward call indicators Call diversion information Call history information Call reference (national use) Called party number Calling party number
17
17 19 20 21 21 24 24 24 25 27

3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 3.30 3.31 3.32 3.33 3.34 3.35 3.36 3.37 3.38 3.39 3.40 3.41 3.42 3.43 3.44 3.45 3.46 3.47 3.48 3.49 3.50 3.51 3.52 3.53 3.54 3.55 3.56 3.57 3.58 3.59 Calling party's category Cause indicators Circuit group supervision message type Circuit state indicator (national use) Closed user group interlock code Connected number Connection request Continuity indicators Echo control information End of optional parameters Event information Facility indicator Forward call indicators Generic digits (national use) Generic notification indicator Generic notification indicator Reserved (used in 1992 version) Information indicators (national use) Information request indicators (national use) Location number MCID request indicators MCID response indicators Message compatibility information MLPP precedence Nature of connection indicators Network specific facility (national use) Optional backward call indicators Optional forward call indicators Original called number Origination ISC point code Parameter compatibility information Propagation delay counter Range and status Redirecting number Redirection information Redirection number Redirection number restriction Remote operations (national use) Service activation Signalling point code (national use) Subsequent number Suspend/resume indicators Transit network selection (national use) Transmission medium requirement Transmission medium requirement prime Transmission medium used User service information User service information prime User teleservice information
C-2
29 32 46 47 47 47 47 47 47 47 47 48 48 51 51 51 51 51 51 51 51 51 51 51 51 52 52 54 54 55 55 55 55 57 58 60 60 60 60 61 61 61 62 62 63 63 63 64 64
C-3
3.60 3.61 3.62 3.63 3.64 3.65 3.66 3.67 3.68 3.69 3.70 3.71 3.72 3.73 3.74 3.75 3.76 3.77 3.78 3.79 3.80 3.81 User-to-user indicators User-to-user information Backward GVNS CCSS Call transfer number Call transfer reference Forward GVNS Loop prevention indicators Network management controls Circuit assignment map Correlation id SCF id Call diversion treatment indicators Called IN number Call offering treatment indicators Charged party identification (national use) Conference treatment indicators Display information UID action indicators UID capability indicators Hop counter Collect call request

64 65 65 65 65 65 66 66 66 66 66 66 66 66 66 66 66 66 66 66 66 67
4
4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22
ISDN user part messages and codes

General Address Complete Message Answer Call Progress (CPG) Circuit Group Query Response (CQR) Circuit Group Reset Acknowledgement Confusion (CFN) Connect Message (CON) Continuity (COT) Facility Reject (FRJ) Information (INF) Information Request (INR) Initial Address Message (IAM) Release (REL) Release Complete (RLC) Subsequent Address Message (SAM) User-to-User Information (USR) Delayed Release (DRS) Forward Transfer (FOT) Suspend (SUS) Resume (RES) Blocking (BLO), Blocking Acknowledgement (BLA), Continuity Check Request (CCR), Loop Back Acknowledge (LPA), Overload (OLM), Reset Circuit (RSC), Unblocking (UBL), Unblocking Acknowledgement (UBA), Unequipped CIC (UCIC) Call Modification Completed (CMC) Call Modification Request (CMR) Call Modification Reject (CMR)
67
67 67 68 69 70 71 71 71 72 72 72 72 73 74 75 76 76 76 76 76 76
77 78
4.23

4.24 4.25 4.26 4.27 4.28 4.29 4.30 4.31 4.32 4.33 4.34 4.35
C-4
Circuit Group Blocking (CGB), Circuit Group Blocking Acknowledgement (CGBA), Circuit Group Unblocking (CGU), Circuit Group Unblocking Acknowledgement (CGUA) Circuit Group Reset (GRS) Circuit Group Query (CQM) Facility Accepted (FAA) Facility Request (FAR) Pass Along (PAM) User part test (UPT), User part available (UPA) Facility (FAC) Network resource management (NRM) Identification request (IDR) Identification response (IDS) Segmentation (SGM) Loop prevention (LOP)
78 79 80 80 80 80 80 80 80 80 80 80
Annex A Annex B Appendix 1 Appendix 2 Appendix 3 Appendix 4 Appendix 5
Tables for handling of unrecognized parameter values General description of component encoding rules Circuit Identification Code (CIC) Numbering Signalling Interworking Backward Call Indicators Recommendation Q.764 Signalling Procedures Sample Message Sequences Support Of Supplementary Services
81 88 89 94 96 100 101
103
Call Forwarding (CALL DIVERSION) Procedures
C-5
0 0.1
Introduction Scope
0.1.1 Part C of PTC 331 describes the functions and message formats of the ITU-T No.7 Signalling System Integrated Services Digital Network User Part (ISDN User Part or ISUP) as it applies to Telecom's Public Switched Telephone Network (PSTN) and Integrated Services Digital Network (ISDN) on the interconnect interface at a Telecom Point of Interconnect exchange (POI). 0.2 Relationship with ITU-T Recommendations
0.2.1 Clauses 1 to 4 of part C follow, as far as possible, the general format (paragraph, figure and table numbering) of ITU-T Recommendation Q.763 (1997) [14], to facilitate comparisons. However, some descriptions have been revised in the interests of clarity by including explanations from ITU-T Recommendations Q.762 [13] and Q.764 (1997) [15] for example, and aspects specific to Telecom's exchanges. Unless stated, such changes to wording do not imply real departures from the Q.763 recommendations. Section 2 of Q.764 is summarised in Appendix 3. 0.2.2 Some real differences do exist between Q.763 and the version of ISUP described in this part. These are typically: (1) Where less than the full set of ITU-T messages, parameters or facilities are available in the implementation at Telecom's POI or within Telecom's network, or where Telecom has placed a narrower interpretation on some aspects than Q.763. In these cases, except where complete messages and parameters are not implemented, the ITU-T text is reproduced here but is highlighted (as in this sentence) and explanatory text is added. In the case where complete messages and parameters are not implemented in Telecoms POI the ITU-T text is omitted from this document. Where additional messages, parameters or facilities beyond those described by ITU-T are implemented at Telecom's POI. In this case the text is written in bold Italics (as in this sentence). Comments and clarifications are written in Italics. Note that the original ITU-T text also uses Italics for emphasis.
(2)
(3)
The meaning of the different typefaces is illustrated below.

ITU-T feature highlighted text plain text bold italicised text Feature in Telecoms network Feature in Telecoms POI exchange
Where figures and tables have been deleted, subsequent figures and tables have not been renumbered. This maintains the numbering identical to that in ITU-T Recommendations.
C-6
0.3
General
0.3.1 The ISUP is the No.7 Signalling level 4 protocol that provides the signalling functions required to support basic bearer service and supplementary services for voice and non-voice applications in the ISDN and PSTN. 0.3.2 The ISUP makes use of services provided by the No.7 Signalling Message Transfer Part (MTP) comprising levels 1 to 3. The Signalling Connection Control Part (SCCP) is not currently used by Telecom to provide services to the ISUP. The MTP version being implemented by Telecom concurrently with this version of ISUP is based on the 1997 ITU-T Recommendations and is described in part B of this document. 0.3.3 ISUP signalling involves a series of signalling relationships between each pair of adjacent exchanges involved in a call. The ISUP messages are handled on an exchange by exchange basis, not end-to-end, except, of course, where no transit exchanges are involved in the call. End-to-end ISUP signalling using the SCCP is not used by Telecom. 0.3.4 Although the ITU-T specified MTP allows for a variety of bit rates signalling links connected to Telecom's network use only 64kbit/s. 0.4 Interworking with non-ISUP signalling systems
0.4.1 The retention of Decadic Pulse (DP) and ITU-T version R2 based Multi Frequency Compelled (R2MFC) inter-exchange signalling in parts of Telecom's network will necessitate interworking between these and ISUP signalling for some calls. For some calls this may occur in the POI exchange. 0.4.2 Interworking will also take place in Telecoms network between ISUP and international signalling systems No.5, No.7 TUP and No.7 ISUP (Q.767) at Telecom's international exchanges for international calls. 0.4.3 This document primarily describes the all-ISUP environment. However interworking issues are covered in this way: (1) Where there is an obvious exact equivalent between ISUP and R2MFC or DP (e.g. called party number) this document makes no specific comment on interworking. (2) In other cases, for national calls the mapping to/from R2MFC or DP is shown in the relevant section. (3) Interworking to international signalling systems is in accordance with the relevant ITU-T recommendations. 0.5 ISUP-ISUP interworking at the Telecom POI exchange
0.5.1 Part C of PTC331 describes the structures and meanings of ISUP messages and parameters which are currently used in the Telecom network, and which may be sent to or received from another network at the POI exchange. 0.5.2 In the event that the POI exchange receives ISUP signals from another network which do not comply with those described here, (for example values which are highlighted in this text) it will, in general, take action in accordance with ITU-T Recommendation Q.764 2.9.5 (Receipt of unreasonable signalling information messages); i.e. the exact action will depend on the call state and the affected service. Where a general procedure applies, this is described in the text. Note, however, that the complexity of ISUP signalling means that it has not been possible to test the reaction of Telecom's network to every potential case of unreasonable and unrecognized ISUP signal received
C-7
at the POI exchange. The onus is with the interconnecting network provider to ensure that all ISUP signals sent to the Telecom POI meet the requirements of PTC331. 0.5.3 Note that in some situations the Telecom network may, on receipt from an interconnecting network of signalling information that is not used in the Telecom network and is outside the scope of Part C of PTC331, pass this information to another interconnected network, i.e., the Telecom network does not police the interface. Adherence to the signals defined in this specification is dependent upon the co-operation of all interconnected network operators. 0.6 Changes from Issue 1
The previous issue 1 (1992) of Part C to PTC331 and amendments 1, 2, 3 and 4 were based on Blue Book ITU-T Recommendations Q.763 and Q.764 (1988). This issue is based on the 1997 versions of these ITU-T Recommendations. This has resulted in major change to the layout but these do not represent technical changes to the POI exchange ISUP interface. The only substantive technical changes from the previous issue are: a) Subject to agreement with the interconnected network operator new cause value 22 may be sent by Telecom to indicate release from a changed number subscriber. b) Subject to agreement with the interconnected network operator, forward call indicator parameter, bit M=1 can be used to indicate a reverse charge call, and bit O=1 can be used to indicate that interaction has taken place with the Intelligent Network. c) Subject to agreement with the interconnected network operator, flexibility in passing calling party category values between networks. 1 1.0 1.0.1 General Scope, references, definitions, abbreviations Scope
This Recommendation specifies the formats and codes of the ISDN user part messages and parameters required to support basic bearer services and supplementary services. 1.0.2 References
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. [1] [2] [3] [4] ITU-T Recommendation X.208 (1988), Specification of Abstract Syntax Notation One (ASN.1). ITU-T Recommendation X.209 (1988), Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1). ITU-T Recommendation X.219 (1988), Remote operations: Model, notation, and service definition. ITU-T Recommendation X.229 (1988), Remote operations: Protocol specification.
C-8
[5] [6] [7] [8] [9] [10]
ITU-T Recommendation G.704 (1995), Synchronous frame structures used at 1544, 6312, 2048, 8488 and 44 736 kbit/s hierarchical levels. ITU-T Recommendation Q.931 (1993), ISDN user-network interface layer 3 specification for basic call control. ITU-T Recommendation Q.850 (1993), Use of cause and location in the digital subcriber Signalling System No. 1 and in the Signalling System No. 7 user part. ITU-T Recommendation Q.703 (1993), Signalling link. ITU-T Recommendation Q.704 (1993), Signalling System No. 7 Signalling network functions and messages. ITU-T Recommendation Q.2763 (1995), Signalling System No. 7 B-ISDN User Part (B-ISUP) Format and codes.
[11] ITU-T Recommendation I.530 (03/93), Network interworking between an ISDN and a public switched telephone network (PSTN) [12] [13] [14] [15] [16] 1.0.3 ITU-T Recommendation Q.761 (09/97), Signalling System No. 7 ISDN User Part Functional Description, plus Addendum 1, 05/98. ITU-T Recommendation Q.762 (09/97), Signalling System No. 7 ISDN User Part General Functions of Messages and Signals, plus Addendum 1, 05/98. ITU-T Recommendation Q.763 (09/97), Signalling System No. 7 ISDN User Part Formats and Codes, plus Addendum 1, 05/98. ITU-T Recommendation Q.764 (09/97), Signalling System No. 7 ISDN User Part Signalling Procedures, plus Addendum 1, 05/98. ITU-T Recommendation Q.732.2 (09/99), Stage 3 description for call offering supplementary services using Signalling System No. 7: Call diversion services. Terms and definitions
See ITU-T Recommendation Q.762. 1.0.4 ASN.1 ATP BCD CCBS CCSS CIC CUG DNIC DPC DSS 1 FDM GUG GVNS Abbreviations Abstract Syntax Notation One Access Transport Parameter Binary Coded Decimal Completion of Calls to Busy Subscriber Call Completion Service Set-up Circuit Identification Code Closed User Group Data Network Identification Code Destination Point Code Digital Subscriber Signalling System No. 1 Frequency Division Multiplex GVNS User Group Global Virtual Network Service
This Recommendation uses the following abbreviations:
C-9
IA5 INAP INN ISC ISDN LFB LSB MCID MLPP MNIC NI NI O/E OPC OPSP ROSE ROA SCCP SCF SLS ST TAR TCC TNRN UID
International Alphabet No. 5 Intelligent Network Application Protocol Internal Network Number International Switching Centre Integrated Services Digital Network Look-ahead for Busy (from MLPP Supplementary Service) Least Significant Bit Malicious Call Identification Multi-Level Precedence and Preemption Mobile Network Identification Code Network Identity Number Incomplete Odd/Even Originating Point Code Origination Participation Service Provider Remote Operations Service Element Registered Operating Agency Signalling Connection Control Part Service Control Function Signalling Link Selection End of pulsing signal (Stop Sending) Temporary Alternative Routing Telephony Country Code Termination Network Routing Number User Interactive Dialogue
For further abbreviations, see Recommendation Q.761. 1.0.5 General coding principles
ISDN user part messages are carried on the signalling link by means of message signal units the format of which is described in 2.2/Q.703 [8]. The format of and the codes used in the service information octet are described in 14.2/Q.704 [9]. The service indicator for the ISDN user part is coded 0101 and the Sub Service Field is coded 1000. 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): a) b) c) d) e) f) routing label; circuit identification code; message type code; the mandatory fixed part; the mandatory variable part; the optional part, which may contain fixed length and variable length parameter fields.
PTC 331:2001 C-10 Issue 2 NOTE 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. The Signalling Connection Control Part (SCCP) is not currently used by Telecom to provide services to the ISUP.
Routing label Circuit identification code Message type code Mandatory fixed part Mandatory variable part Optional part
Figure 1 ISDN user part message parts
A description of the various message parts is given in the following subclauses. 1.1 Routing label
The format and codes used for the routing label are described in 2.2/Q.704. For each individual circuit connection, the same routing label must be used for each message that is transmitted for that connection.
NOTE The SLS bits are set to the four least significant bits of the CIC. Telecom POI exchanges operate in accordance with the 1988 (Blue Book) recommendation and do not use this rule.
1.2
Circuit identification code
The format of the Circuit Identification Code (CIC) is shown in Figure 2.

8 7 6 5 4 3 2 Circuit Identification Code (least significant bits) Spare CIC most significant bits 1
Figure 2 Circuit identification field
The allocation of circuit identification codes to individual circuits is in accordance with Appendix 1 of Part C. 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. Allocations for certain applications are defined below: a) 2048 kbit/s digital path 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. 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.
C-11
b) c)
8448 kbit/s digital path Not applicable and not reproduced. Frequency Division Multiplex (FDM) systems in networks using the 2048 kbit/s pulse code modulation standard Not applicable and not reproduced. For a multirate connection type call Not applicable and not reproduced. For the N 64 kbit/s connection types Not applicable and not reproduced. Table 1
Not applicable and not reproduced
d) e)
Table 2
Table 3
1.3
Message type code
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. The allocation with reference to the appropriate descriptive tables in this Recommendation is summarized in Table 4.
C-12
Table 4
Message type Address complete Answer Blocking Blocking acknowledgement Call progress Circuit group blocking Circuit group blocking acknowledgement Circuit group query (national use) Circuit group query response (national use) Circuit group reset Circuit group reset acknowledgement Circuit group unblocking Circuit group unblocking acknowledgement Charge information (national use) Confusion Connect Continuity Continuity check request Facility Facility accepted Facility reject Facility request Forward transfer Identification request Identification response Information (national use) Information request (national use) Initial address Loop back acknowledgement (national use) Loop prevention Network resource management Overload (national use) Pass-along (national use) Release Release complete Reset circuit Resume Rx Only Abbr. ACM ANM BLO BLA CPG CGB CGBA CQM CQR GRS GRA CGU CGUA CRG CFN CON COT CCR FAC FAA FRJ FAR FOT IDR IDS INF INR IAM LPA LOP NRM OLM PAM REL RLC RSC RES Ref. (Table) 21 22 39 39 23 40 40 41 24 41 25 40 40 (Note) 26 27 28 39 45 42 29 42 37 47 48 30 31 32 39 50 46 39 43 33 34 39 38 Code 00000110 00001001 00010011 00010101 00101100 00011000 00011010 00101010 00101011 00010111 00101001 00011001 00011011 00110001 00101111 00000111 00000101 00010001 00110011 00100000 00100001 00011111 00001000 00110110 00110111 00000100 00000011 00000001 00100100 01000000 00110010 00110000 00101000 00001100 00010000 00010010 00001110
C-13
Table 4
Message type Segmentation Subsequent address Suspend Unblocking Unblocking acknowledgement Unequipped CIC (national use) User Part available User Part test User-to-user information Reserved (used in 1984 version) Abbr. SGM SAM SUS UBL UBA UCIC UPA UPT USR Ref. (Table) 49 35 38 39 39 39 44 44 36 Code 00111000 00000010 00001101 00010100 00010110 00101110 00110101 00110100 00101101 00001010 00001011 00001111 00100010 00100011 00100101 00100110 00011101 00011100 00011110 00100111 00111001 to 00111101 Reserved for future extension Note The format of this message is a national matter. All messages shown are originated and received by Telecoms POI exchanges in this implementation, except: Highlighted messages Rx Only = neither originated nor received by Telecom = can be received by Telecom but not originated. 10000000
Reserved (used in 1988 version)
Reserved (used in B-ISUP)
1.4
Formatting principles
Each message consists of a number of PARAMETERS listed and described in clause 3. Each parameter has a NAME which is coded as a single octet (see Table 5). 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. The detailed format is uniquely defined for each message type as described in clause 4. Between parameters there should be no unused (i.e. dummy) octets. A general format diagram is shown in Figure 3.
C-14
1.5
Mandatory fixed part
Those parameters that are mandatory and of fixed length for a particular message type will be contained in the mandatory fixed part. 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. 1.6 Mandatory variable part
Mandatory parameters of variable length will be included in the mandatory variable part. 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 2.3. The number of parameters, and thus the number of pointers, is uniquely defined by the message type. 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 (reflected by the presence of an "end of optional parameter" octet in Tables 21 through 50), but there is no optional part included in this particular message, then 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. 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. If there are no mandatory variable parameters, but optional parameters are possible, the start of optional parameters pointer (coded all "0"s if no optional parameter is present and coded "00000001" if any optional parameter is present) will be included. 1.7 Optional part
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. Unless it is explicitly stated to the contrary within this Recommendation, an optional parameter cannot occur multiple times within one message. Optional parameters may be transmitted in any order although messages originated in Telecom exchanges normally transmit parameters in the order depicted in this document. Each optional parameter will include the parameter name (one octet) and the length indicator (one octet) followed by the parameter contents. 1.8 End of optional parameters octet
If optional parameters are present and after all optional parameters have been sent, an "end of optional parameters" octet containing all zeros will be transmitted. If no optional parameter is present (e.g. for CFN message see Table 26), an "end of optional parameters" octet is not transmitted. 1.9 Order of transmission
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). Unless otherwise indicated, within each octet and subfield the bits are transmitted with the least significant bit first.
C-15
Order of bit transmission 8 7 6 5 4 3 2 1 Order of octet transmission
Routing label Circuit identification code Message type code Mandatory parameter A Mandatory fixed part Mandatory parameter F Pointer to parameter M
Pointer to parameter P Pointer to start of optional part Length indicator of parameter M Parameter M Mandatory variable part
Length indicator of parameter P Parameter P Parameter name = X Length indicator of parameter X Parameter X Optional part Parameter name = Z Length indicator of parameter Z Parameter Z End of optional parameters
T1184880-97
Figure 3 General format overview
1.10
Coding of spare bits
Spare bits are coded 0 unless indicated otherwise. 1.11 National message types and parameters
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. Message type codes in the range 11111111 to 11100000 and parameter name codes in the range 11111111 to 11000001 are reserved exclusively for national use.
C-16
Four such parameters are used in Telecom's network. These are shown in Table 5, below, but are not sent to other networks from Telecom's POI exchange. If other network providers choose to define their own messages and parameters it is recommended that, in order to minimize potential confusion when comparing specifications and during fault handling, they avoid using the codes used in Telecom's network. 1.12 Rules for the allocation of message types codes and parameter name codes
B-ISUP message and parameter codes not used in ISUP should be marked reserved. 1.13 a) Meaning of "spare" codes and "reserved" codes Spare code: A code is indicated in this Recommendation as: spare; spare for international use; or spare for national use.
A code indicated as "spare" or "spare for international use" is a code available for future ITU-T use. A code indicated as "spare for national use" is not available for ITU-T use. b) Reserved code: A code may have been reserved in this Recommendation because of: a previous Recommendation; an intended usage (however, procedures have not been developed); or national use.
A code reserved for a previous Recommendation (e.g. Blue Book) is not available for future use. A code reserved for an intended use (e.g. for future extension) will be specified when the intended procedures are developed. A code reserved for national use is not available for ITU-T use. 2 2.1 Parameter formats and codes Message type codes
The encoding of the message type is shown in Table 4. 2.2 Coding of the length indicator
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. 2.3 Coding of the pointers
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. The pointer value all zeros is used to indicate that, in the case of optional parameters, no optional parameter is present.
C-17
3 3.1
ISDN user part parameter Parameter names
The parameter name codes are given in Table 5 together with references to the subclauses in which they are described. Table 5
Parameter name Access delivery information Access transport Automatic congestion level Backward call indicators Backward GVNS Call diversion information Call diversion treatment indicators Call history information Call offering treatment indicators Call reference (national use) Call transfer number Call transfer reference Called IN number Called party number Calling party number Calling party's category Cause indicators CCSS Charged party identification (national use) Circuit assignment map Circuit group supervision message type Circuit state indicator (national use) Closed user group interlock code Collect call request Conference treatment indicators Connected number Connection request Continuity indicators Reference (subclause) 3.2 3.3 3.4 3.5 3.62 3.6 3.72 3.7 3.74 3.8 3.64 3.65 3.73 3.9 3.10 3.11 3.12 3.63 3.75 3.69 3.13 3.14 3.15 3.81 3.76 3.16 3.17 3.18 Code 00101110 00000011 00100111 00010001 01001101 00110110 01101110 00101101 01110000 00000001 01000101 01000011 01101111 00000100 00001010 00001001 00010010 01001011 01110001 00100101 00010101 00100110 00011010 01111001 01110010 00100001 00001101 00010000
C-18
Table 5 (continued)
Parameter name Correlation id Display information Echo control information End of optional parameters Event information Facility indicator Forward call indicators Forward GVNS Generic digits (national use) Generic notification indicator Generic number Hop counter Information indicators (national use) Information request indicators (national use) Location number Loop prevention indicators MCID request indicators MCID response indicators Message compatibility information MLPP precedence Nature of connection indicators Network management controls Network specific facility (national use) Optional backward call indicators Optional forward call indicators Original called number Origination ISC point code Parameter compatibility information Propagation delay counter Range and status Redirect capability (reserved for national use) Redirect counter (reserved for national use) Redirecting number Redirection information Redirection number Redirection number restriction Remote operations (national use) Reference (subclause) 3.70 3.77 3.19 3.20 3.21 3.22 3.23 3.66 3.24 3.25 3.26 3.80 3.28 3.29 3.30 3.67 3.31 3.32 3.33 3.34 3.35 3.68 3.36 3.37 3.38 3.39 3.40 3.41 3.42 3.43 (Note) (Note) 3.44 3.45 3.46 3.47 3.48 Code 01100101 01110011 00110111 00000000 00100100 00011000 00000111 01001100 11000001 00101100 11000000 00111101 00001111 00001110 00111111 01000100 00111011 00111100 00111000 00111010 00000110 01011011 00101111 00101001 00001000 00101000 00101011 00111001 00110001 00010110 01001110 01110111 00001011 00010011 00001100 01000000 00110010
C-19
Table 5 (concluded)
Parameter name SCF id Service activation Signalling point code (national use) Subsequent number Suspend/Resume indicators Transit network selection (national use) Transmission medium requirement Transmission medium requirement prime Transmission medium used UID action indicators UID capability indicators User service information User service information prime User teleservice information User-to-user indicators User-to-user information Reserved (used in 1984 version, Red Book) Reference (subclause) 3.71 3.49 3.50 3.51 3.52 3.53 3.54 3.55 3.56 3.78 3.79 3.57 3.58 3.59 3.60 3.61 Code 01100110 00110011 00011110 00000101 00100010 00100011 00000010 00111110 00110101 01110100 01110101 00011101 00110000 00110100 00101010 00100000 00010100 00011001 00011011 00011100 00011111 00010111 01000001 01000010 10000000 11000111 11101011 11111011 11111110
Reserved (used in 1988 version, Blue Book) Reserved (used in 1992 version) Reserved for future extension Generic name (used within Telecoms network) Charge number (used within Telecoms network) Inter-Gateway routing (used within Telecoms network) Supplementary line information (used within Telecoms network) Note The format of this parameter is a national matter.
All parameters shown are used in messages originated and received by Telecoms POI exchanges in this implementation, except: Highlighted parameters = not used in messages originated or received by Telecom
The following codes are reserved for use in B-ISUP: 01000110 to 01001010, 01001111 to 01011010, 01011100 to 01100100, 01100111 to 01101101. 3.2 Access delivery information
This section has not been reproduced as this parameter is not implemented.
C-20
3.3
Access transport
3.3.1 This parameter is used to carry signalling information in either direction across the No.7 signalling network between the originating and terminating ISDN subscribers connected to different exchanges. Transit exchanges in Telecom's network do not examine this parameter (other than for call charging purposes) and will pass it on, unchanged. 3.3.2 The format of the information carried in this parameter is identical to that received from the ISDN access. The parameter passes Called party subaddress, Calling party subaddress, Low layer compatibility, High layer compatibility and Progress indicator information elements from the ISDN access. In effect this parameter is used as an envelope to pass access signalling information transparently across the signalling network. Multiple information elements may be included within the Access Transport parameter. The maximum permitted length of this parameter is constrained by the maximum permitted MSU length and its other contents. 3.3.3 Access Transport is an optional parameter which may be used in the following messages: Address Complete (ACM) Answer (ANM) Call Progress (CPG) Connect (CON) Facility (FAC) Identification Response (IDS) Initial Address (IAM) Release (REL) Segmentation (SGM) User to User Information (USR) (ref. 4.2) (ref. 4.3) (ref. 4.4) (ref. 4.8) (ref. 4.30) (ref. 4.33) (ref. 4.13) (ref. 4.14) (ref. 4.34) (ref. 4.17)
However, it is not currently carried by Telecom in the ACM message, and the CON, FAC, IDS, SGM and USR messages are not currently used by Telecom, although the CON message may be received from other networks and carried in the Telecom network. The format of the access transport parameter field is shown in Figure 5.
8 1 . . . n 7 6 5 4 3 2 1
Information element(s)
Figure 5 Access transport parameter field
The information element is coded as described in 4.5/Q.931 [6]. 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. The maximum length of the access transport parameter should only be limited by the message length as the content of the ATP will probably evolve in the future.
C-21
3.4
Automatic congestion level
3.4.1 This parameter is used to pass switching congestion level indications from a transit or terminating exchange back to the preceding exchange. 3.4.2 Receipt of this parameter by a transit or originating exchange will cause that exchange to restrict switched circuit traffic to the congested exchange (from which the message was received) in an effort to reduce the congestion there. At an ISUP-ISUP transit exchange the parameter is then discarded and not passed back to preceding exchanges. 3.4.3 Automatic Congestion Level is an optional parameter which may be used in the following message: Release (REL) 3.4.4 (ref. 4.14) The format of the automatic congestion level parameter field is shown in Figure 6.
8 7 6 5 4 Automatic congestion level 3 2 1
Figure 6 Automatic congestion level parameter field
3.4.5
The following codes are used in the automatic congestion level parameter field: 00000000 00000001 00000010 00000011 to 11111111 Spare; not set by Telecom Congestion level 1 exceeded Congestion level 2 exceeded Spare; not set by Telecom
3.4.6 Telecom exchanges include Congestion Level 1 or Level 2 indication in all call release messages while occupancy of the call processor (controlling the circuit being released) exceeds criteria specified in system data. It is recommended that exchanges interconnected with the Telecom network act in accordance with ITU-T Recommendation Q.764, clause 2.11.2 during conditions of overload. 3.4.7 Receipt of a release message with this parameter causes Telecom exchanges to restrict traffic by application of call gapping to the overloaded exchange at a rate specified in system data. Restriction continues after receipt of the last automatic congestion control parameter for a specified retention period, then reduces to the next level of restriction and finally ceases. Calls with operator, maintenance or priority calling party's categories are not restricted. The action taken by an interconnected network upon receipt of an Automatic congestion level parameter should be in accordance with ITU-T Recommendation Q.764 2.11.1 3.5 Backward call indicators
3.5.1 This parameter is used to pass information relating to the call and the called subscriber back towards the originating exchange (i.e. in the direction from the terminating towards the originating exchange). The information may be used by the receiving exchange for charging, barring, rerouting, mapping to incoming R2MFC or mapping to originating ISDN access. As not all values of this parameter are applicable in other networks, some particular values of Backward Call Indicators
C-22
received from within the Telecom network will be mapped by the Telecom POI exchange to recognized Q.763 values (in accordance with the tables in Appendix 2 of this document) before they are sent to the other network. 3.5.2 Backward Call Indicators is a mandatory fixed length parameter in the following messages: Address Complete (ACM) Connect (CON)
* *
(ref. 4.2) (ref. 4.8)
However, the Connect message is not originated by Telecom. Answer Message (ANM) Call Progress Message (CPG) (ref. 4.3) (ref. 4.4)
It is also an optional parameter which may be included in the following messages:
However, it is not used in these messages by Telecom. The format of the backward call indicators parameter field is shown in Figure 7.
8 H P 7 G O 6 F N 5 E M 4 D L 3 C K 2 B J 1 A I
1 2
Figure 7 Backward call indicators parameter field
The following codes are used in the backward call indicators parameter field: bits BA 00 01 10 11 Charge indicator (Note 1) no indication; set when the call is intercepted by an announcement, operator or IN node, or switched to an outgoing DP route, or when an outgoing R2MFC route receives an A-6 signal no charge; not set by Telecom; passed transparently if received from another network at a POI or from the international network charge; set when the call terminates, or when an outgoing R2MFC route receives B-1, B-6, B-7, B-9 or B-10 spare; not set by Telecom; passed transparently if received from another network at a POI
NOTE 1 The interpretation of these bits depends only on the charging exchange. NOTE 1a Although carried, Telecom does not base its charging on the value of these bits.
C-23
bits DC 00 01
10 11 bits FE 00 01 10 11 bits HG 00 01 10 10 bit I 0 1
Called party's status indicator no indication; set when the call terminates to an ISDN or DDI line, is intercepted by an announcement, operator or IN node, or switched to an outgoing DP route, or when an outgoing R2MFC route receives A-6 signal subscriber free; set when call terminates to a free non-DDI PSTN line, or when outgoing R2MFC route receives B-1, B-6, B-7, B-9 or B-10; may also be received from other networks for calls terminating on some ISDN terminals (ref. ITU-T Q.699 Fig. 5) connect when free (national use); not set by Telecom. Passed transparently if received from another network at a Telecom POI exchange Spare; not set by Telecom. Passed transparently if received from another network at a Telecom POI exchange Called party's category indicator no indication; set when the call is intercepted by an announcement, operator or IN node, or switched to an outgoing DP route, or when an outgoing R2MFC route receives A-6 signal ordinary subscriber; set when call terminates to a line which is neither barred incoming collect nor INWATS terminating category, or when call is switched to an outgoing R2MFC route which receives B-1 or B-6 payphone; used in the Telecom network. Not sent from a Telecom POI to another network. Spare; not set by Telecom End-to-end method indicator (Note 2) no end-to-end method available (only link-by-link method available) ; set for all calls pass-along method available (national use); not set by Telecom; mapped to value 00 if received from another network at a POI SCCP method available; not set by Telecom; mapped to value 00 if received from another network at a POI pass-along and SCCP methods available (national use) ; not set by Telecom; mapped to value 00 if received from another network at a POI Interworking indicator (Note 2) no interworking encountered (Signalling System No. 7 all the way); set when No.7 is used all the way back from the terminating exchange interworking encountered; set in messages returned from transit exchanges where outgoing signalling is not No.7, or when the call is intercepted by an announcement, operator or IN node End-to-end information indicator (Note 2) (national use) no end-to-end information available; set for all calls end-to-end information available, i.e., awaiting transmission; not set by Telecom; mapped to value 0 if received from another network at a POI
bit J 0 1
C-24
bit K 0 1 bit L 0 1 bit M 0 1 bit N 0 1 bits PO 00 01 10 11
ISDN user part indicator (Note 2) ISDN user part not used all the way; set in messages returned from transit exchanges where outgoing signalling is not ISUP, or when the call is intercepted by an announcement, operator or IN node ISDN user part used all the way Holding indicator (national use) holding not requested; set for all calls holding requested; not set by Telecom; mapped to value 0 if received from another network at a POI ISDN access indicator terminating access non-ISDN or not known; also used when the call is intercepted by an announcement, operator or IN node terminating access ISDN and ISUP used all the way Echo control device indicator incoming echo control device not included; set for all calls incoming echo control device included; not set by Telecom; passed transparently if received from another network at a POI SCCP method indicator (Note 2) no indication; set for all calls connectionless method available (national use); not set by Telecom; mapped to value 00 if received from another network at a POI connection oriented method available; not set by Telecom; mapped to value 00 if received from another network at a POI connectionless and connection oriented methods available (national use) ; not set by Telecom; mapped to value 00 if received from another network at a POI
NOTE 2 Bits G-K and O-P constitute the protocol control indicator. NOTE 3 For calls terminating in Telecom's network bits I and K convey identical information because ISUP is the only part of No.7 signalling used for call control. (When I=0, K=1). NOTE 4 The contents of bits I, K and M can be mapped to the originating ISDN access. NOTE 5 Bit I=1 and bit K=0 are returned from an exchange where a call is intercepted by an operator, an announcement or by the Intelligent Network for input of in-band tones, even though ISUP is used all the way.
3.6
Call diversion information
This section has not been reproduced as this parameter is not implemented. 3.7 Call history information
This section has not been reproduced as this parameter is not implemented. 3.8 Call reference (national use)
C-25
3.9
Called party number
3.9.1 This parameter is used to send the called number forward to each succeeding exchange in the call set-up sequence for use in call routing. When this parameter is sent from a Telecom POI it always includes all required digits of the called party number, as the ISUP signalling used is enbloc, not overlap. 3.9.2 Called Party Number is mandatory variable length parameter used in the following message: Initial Address (IAM) (ref. 4.13)
The format of the called party number parameter field is shown in Figure 10.
8 Odd/ even INN Ind. 7 6 5 4 3 2 1
1 2 3 . . n
Nature of address indicator Numbering plan Ind. 2nd address signal Spare 1st address signal
Filler (if necessary)
nth address signal
Figure 10 Called party number parameter field
The following codes are used in the subfields of the called party number parameter field: a) Odd/even indicator 0 1 b) even number of address signals (last octet has no filler) odd number of address signals (last octet has one address signal and one filler) spare; not set by Telecom subscriber number (national use) ; not set by Telecom Unknown (national use); used for all calls (Note 1) national (significant) number; not set by Telecom international number; not set by Telecom network-specific number (national use); not set by Telecom spare; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom
Nature of address indicator 0000000 0000001 0000010 0000011 0000100 0000101 0000110 to 1101111 1110000 to 1111110 1111111
C-26
NOTE 1 - Indicates that the format of the called party number forwarded in the address signal subfields will be by agreement between the network operators, in accordance with Part A section 11.5. NOTE 2 - All values of Nature of Address indicator received from another network at a POI are mapped to 0000010 c) Internal Network Number indicator (INN ind.) 0 1 d) routing to internal network number allowed; set for all calls routing to internal network number not allowed; not set by Telecom; mapped to value 0 if received from another network at a POI spare; not set by Telecom ISDN (Telephony) numbering plan (Recommendation E.164); set for all calls spare; not set by Telecom Data numbering plan (Recommendation X.121) (national use); not set by Telecom Telex numbering plan (Recommendation F.69) (national use); not set by Telecom reserved for national use; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom
Numbering plan indicator 000 001 010 011 100 101 110 111
NOTE All values of Numbering plan indicatore received from another network at a POI are mapped to 001. e) Address signal 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 digit 0 digit 1 digit 2 digit 3 digit 4 digit 5 digit 6 digit 7 digit 8 digit 9 spare ) code 11 ) not set by Telecom; if received from another network, code 12 ) these values will cause the call to be released spare ) spare ) ST; always included after the last digit of called party number used in the Telecom network, to indicate that no subsequent address messages follow the IAM
The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit fields. Telecoms network can support up to 24 digits plus the ST signal in this field. The actual length used will depend on the numbering plan. f) Filler
C-27
In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal. 3.10 Calling party number
3.10.1 This parameter is used to send forward the calling party number for use in charging, malicious call trace printout, display to operators and delivery to customers subscribing to Calling Line Identity Presentation (CLIP) service. Refer to Part A section 11.6 (3) concerning the intended use of this parameter. 3.10.2 Calling Party Number is an optional parameter which may be used in the following messages: Identification Response (IDS) Information (INF) Initial Address (IAM) (ref. 4.33) (ref. 4.11) (ref. 4.13)
However, it is not used in the IDS and INF messages by Telecom. 3.10.3 The method of sending calling party number from a Telecom POI exchange to an interconnected network depends on which of the following options is selected by the other network operator to apply to the interconnect route: OPTION A OPTION B The Telecom POI will always include the full calling party number in the IAM for all calls, where it is available The Telecom POI will always include the first 4 digits of the Calling Party Number in the IAM. In this case, the Calling Party Number Incomplete indicator is set to incomplete and the Address Presentation Indicator is set to Restricted. The Telecom POI will not send a Calling Party Number parameter for any calls.
OPTION C
Refer to Appendix 4 (Figs. 1a to 1f) for associated message handling. 3.10.4 The User-provided, verified and passed calling party number is sufficient for charging purposes and the INR/INF procedure is no longer to be used within the Telecom network. All references to INR and INF have been highlighted in this specification to indicate not supported by Telecom. The format of the calling party number parameter field is shown in Figure 11.
8 Odd/ even NI 7 6 5 4 3 2 1
1 2 3 . . n
Nature of address indicator Numbering plan Ind. 2nd address signal Address presentation Screening restricted indicator 1st address signal
nth address signal
Figure 11 Calling party number parameter field
The following codes are used in the calling party number parameter field.
C-28
a) b)
Odd/even indicator See 3.9.2 a) Nature of address indicator 0000000 0000001 0000010 0000011 0000100 0000101 to 1101111 1110000 to 1111110 1111111 spare; not set by Telecom subscriber number (national use) ; not set by Telecom unknown (national use) ; not set by Telecom national (significant) number (national use) (normally in the format Toll Group Code + Directory Number); set for all national network originated calls where available international number; set for incoming international calls that use ISUP all the way from the international exchange spare; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom complete incomplete; set when a partial calling party number is provided in the following cases: - for calls originated from M party lines; - beyond R2MFC-ISUP interworking point when ONI calling party category is received; - beyond DP-ISUP interworking point when calling party number is generated at the interworking exchange; and - when calling party number is coded '0000' for incoming international calls (when true calling party number is unavailable)
c)
Number Incomplete indicator (NI) 0 1
d) e)
Numbering plan indicator See 3.9.2 d) Address presentation restricted indicator 00 01 presentation allowed (to a terminating customer subscribing to CLIP supplementary service); set except in cases below, and always set beyond MFC or DP interworking point presentation restricted (available to operators and services with special status only); set where originating customer subscribes to CLIR supplementary service, or where originating customer has a special billing number address not available (Note) (national use); not set by Telecom; passed transparently if received spare; not set by Telecom
10 11
NOTE If the parameter is included and the address presentation restricted indicator indicates address not available, octets 3 to n are omitted, the subfields in items a), b), c) and d) are coded with 0's, and the subfield f) is coded with 11.
C-29 NOTE 2 Also refer to Part A, para 11.6.
f)
Screening indicator 00 01 10 11 reserved (Note); not set by Telecom user provided, verified and passed; set to indicate that calling party number is a valid number supplied by the originating ISDN subscriber in setup message reserved (Note); not set by Telecom network provided; set in all other cases to indicate that calling party number is that registered to the originating subscriber line, or for an ONI subscriber, the number entered by the operator
NOTE Code 00 and 10 are reserved for "user provided, not verified" and "user provided, verified and failed" respectively. Codes 00 and 10 are for national use.
g)
Address signal 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 to 1111 digit 0 digit 1 digit 2 digit 3 digit 4 digit 5 digit 6 digit 7 digit 8 digit 9 spare; not set by Telecom code 11 ) not set by Telecom but may be received from another code 12 ) network spare; not set by Telecom
Telecoms network can support up to 24 digits in this field. Interconnecting networks must support at least 15 digits as specified in ITU-T Recommendation E.164. h) Filler See 3.9 f). 3.11 Calling party's category
3.11.1 This parameter is used to send the calling party's category to each succeeding exchange in the call set-up sequence. It is used for charging, routing and barring purposes. In general at a transit exchange the Calling Party Category may change or remain the same, depending on the call type. At a Telecom POI exchange, because not all values of this parameter are applicable in other networks, some values are mapped to applicable values in agreement with the interconnected network operator. 3.11.2 Calling Party's Category is a mandatory fixed length parameter used in the following message. Initial Address (IAM) (ref. 4.13)
C-30
It is also an optional parameter which may be used in the following message: Information (INF) (ref. 4.11) However, it is not used in this message by Telecom. The format of the calling party's category parameter field is shown in Figure 12.
8 7 6 5 4 Calling party's category 3 2 1
Figure 12 Calling party's category parameter field
The following codes, with meanings, equivalent R2MFC signals, and mappings to and from other networks at the Telecom POI exchange shown, are used in the calling party's category parameter field.
C-31
Code
Description
R2MFC Equiv.
Used in Telecom Network
If received at Telecom POI exchange Value mapped to other network1 N.A. N.A. N.A. N.A. N.A. N.A. N.A. Note 2 Note 2 Note 2 Note 2 Note 2 N.A. Note 2 N.A. N.A. 0000 1010 0000 1010 0000 1010 Note 2 0000 1010 N.A. 0000 1010 0000 1010 N.A. Value mapped to Telecom network2 0000 1010 Invalid Invalid Invalid Invalid Invalid Invalid Note 2 Note 2 Note 2 Note 2 Note 2 Invalid Note 2 Invalid Invalid 0000 1010 0000 1010 0000 1010 Note 2 0000 1010 Invalid 0000 1010 0000 1010 Invalid
0000 0000 0000 0001 0000 0010 0000 0011 0000 0100 0000 0101 0000 0110 0000 0111 0000 1000 0000 1001 0000 1010 0000 1011 0000 1100 0000 1101 0000 1110 0000 1111 0001 0000 to 1101 1111 1110 0000 to 1111 0110 1111 0111 1111 1000 1111 1001 1111 1010 1111 1011 1111 1100 1111 1101 1111 1110 1111 1111
calling party's category unknown at this time (national use) operator, language French operator, language English operator, language German operator, language Russian operator, language Spanish (available to Administrations for selection a particular language by mutual agreement) reserved (see Recommendation Q.104) (Note 1) (national use) Operator ordinary calling subscriber calling subscriber with priority data call (voice band data) test call spare payphone spare reserved for national use Used for Telecom network services Operator Number Identification Used for Telecom network services reserved for national use Used for Telecom network services spare
GII-5 GII-1 G11-2 GII-10 GII-3 GII-6 GII-15 GII-14 GII-13 GII-12 GII-11 GII-5 GII-4 -
NO NO NO NO NO NO NO YES YES YES YES YES NO YES NO NO YES YES YES YES YES NO YES YES NO
Note 1 In national networks, code 00001001 may be used to indicate that the calling party is a national operator. Note 2 subject to agreement with the interconnect network operator these values may be either passed transparently or mapped to 0000 1010.
1 2
N.A. = Not Applicable Invalid values received at a POI will cause the call to be released with cause value 21
C-32
3.12
Cause indicators
3.12.1 This parameter is used to convey information in either the forward or backward direction concerning the reason why a call has failed to mature or has been released. When the Cause Indicator included in a REL message sent in the forward direction (i.e. towards the terminating exchange) is received: (1) (2) (3) an ISUP-ISUP transit exchange will pass the parameter on unchanged if it is a recognised value, otherwise it will be changed to the unspecified value for the class. an ISUP-R2MFC or DP transit exchange will convert the cause indicator to a clear forward line signal a terminating exchange will, if the terminating customer is still connected, pass the information in the cause indicator on to the terminating customer via the access signalling or as an inband tone.
When the Cause Indicator included in a REL message sent in the backward direction (i.e. towards the originating exchange) is received: (1) (2) (3) an ISUP-ISUP transit exchange will pass the parameter on, unchanged an ISUP-R2MFC transit exchange will convert the cause indicator into the relevant backward MFC message an originating exchange will, if the originating customer is still connected, pass the information in the cause indicator on to the originating customer via the access signalling or as an inband tone, or action any instruction contained in the received cause value. Confusion (CFN) Facility Reject (FRJ) Release (REL) (ref. 4.7) (ref. 4.10) (ref. 4.14)
3.12.2 Cause Indicators is a mandatory variable length parameter in the following messages:
However, the Facility Reject message is not currently used by Telecom. It is also an optional parameter which may be used in the following messages: Address Complete (ACM) Call Progress (CPG) Release Complete (RLC) (ref. 4.2) (ref. 4.4) (ref. 4.15)
However, it is not generated in the ACM, CPG and RLC messages within the Telecom network but may be passed if received by another network. The format of the cause indicators parameter field is shown in Figure 13.
C-33
8 1 2 3 . . . n ext. ext. 7 Coding standard 6 5 Spare Cause value 4 3 Location 2 1
Diagnostic(s) (if any)
NOTE Octet 3 to 3n may be omitted or repeated, e.g. 3' to 3'n.
Figure 13 Cause indicators parameter field
The codes to be used in the subfields of the cause indicators parameter fields are defined in Recommendation Q.850 [7] and is summarised below. Section number from Recommendation Q.850 is retained to allow easy reference. Q.850/2.2.1 Bit 8 0 1 octet continues through the next octet (e.g. octet 1 to 1a) last octet Extension indicator (ext.)
Q.850/2.2.2 Coding standard Bits 76 00 01 10 11 ITU-T standardized coding, as described below; set for all calls ISO/IEC standard (see Note) ; not set by Telecom national standard (see Note) ; not set by Telecom standard specific to identified location (see Note) ; not set by Telecom
NOTE These other coding standards should be used only when the desired cause value cannot be represented with the ITU-T-standardized coding.
Q.850/2.2.3 Location Bits 4321 0 0 0 0 user (U); set when cause is received from the ISDN Access 0 0 0 1 private network serving the local user (LPN) ; not set by Telecom 0 0 1 0 public network serving the local user (LN); set when cause is initiated at a Telecom exchange served by No. 7 signalling 0 0 1 1 transit network (TN) ; to be sent to Telecom's POI when cause is initiated at a bypass network operator's exchange. Not generated in the Telecom network; carried if received from another network 0 1 0 0 public network serving the remote user (RLN) ; not set by Telecom 0 1 0 1 private network serving the remote user (RPN) ; generated on receipt of LPN from a private network
C-34
0 1 1 1 international network (INTL); set when cause is initiated in the international network 1 0 1 0 network beyond interworking point (BI) ; set when the cause value is based on information received from another signalling system e.g. R2MFC 1 1 0 0 reserved for national use; not set by Telecom 1 1 0 1 reserved for national use; not set by Telecom 1 1 1 0 reserved for national use; not set by Telecom 1 1 1 1 reserved for national use; not set by Telecom All other values are spare; not set by Telecom Q.850/2.2.4 Recommendation Bits 7654321 0 0 0 0 0 0 0 Q.763/Q.931; set for all calls 0 0 0 0 0 1 1 X.21; not set by Telecom 0 0 0 0 1 0 0 X.25; not set by Telecom 0 0 0 0 1 0 1 public land mobile networks, Q.1031/Q.1051 ; not set by Telecom All other values are reserved ; not set by Telecom
NOTE If octet including this field is omitted, Recommendation Q.763/Q.931 is assumed.
Q.850/2.2.5
Cause value (only applicable in the context of Recommendations Q.763 and Q.931)
The cause value is divided into two fields, a class (bits 5 through 7) and a value within the class (bits 1 through 4). 1) The class indicates the general nature of the event. Class (000): normal event Class (001): normal event Class (010): resource unavailable Class (011): service or option not available Class (100): service or option not implemented Class (101): invalid message (e.g. parameter out of range) Class (110): protocol error (e.g. unknown message) Class (111): interworking 2) The cause values are listed in Table 1. Q.850/2.2.6 Diagnostics (only applicable in the context of Recommendations Q.763 and Q.931)
The diagnostics applicable to each cause value are given in Table 1. Diagnostic information is not available for every cause. In those cases in which the diagnostic is a Q.931 information element, the coding of the diagnostic is the same as for the corresponding information element in 4/Q.931.
C-35
Q.850/2.2.6.1 Bit 8: Bits 7-5: Bit 4:
Coding of Condition 1 000 Condition as follows: 0 Network service Provider 1 Network service User
The condition diagnostic is coded as follows:
Bit 3:
Condition as follows: 0 Normal 1 Abnormal
Bits 2-1:
Condition as follows: 00 Unknown 01 Permanent 10 Transient
Q.850/2.2.6.2
Coding of Transit network identity
The diagnostic field contains the entire transit network selection or network specific facilities information element as applicable, including parameter name/information element identifier and length octet. Q.850/2.2.6.3 Bits 8-1: Coding of CCBS indicator 00000000 Spare 00000001 CCBS possible 00000010 CCBS not possible 00000011 to 01111111 10000000 to 11111110 11111111 Reserved for extension
NOTE Not used in Recommendation Q.931.
The CCBS indicator is coded as follows:
Spare
Spare for national use
C-36
TABLE 1/Q.850
Cause information element/parameter

Diagnostics (Note 1) Condition Transit network identify Condition DSCT DSCT DSS 1 DSS 1 DSCT DSCT Condition CCBS Indicator DSCT BT DSCT DSCT B-4 B-4 cfd/clb B-3 cfd cfd ISUP ISUP ISUP ISUP ISUP ISUP B-4 ISUP(NU) Q.931 Q.931 Q.735.3 Q.735.3 2.3/Q.764 Q.732, Q.733.3 Basic call and call diversion services Q.732 Q.931 2.1.4/Q.764 2.9.8.3/Q.764 Q.732 Expiry of waiting ANM timer (T9) Call diversion services Call diversion services B-4 ISUP NUT B-5 ISUP DSCT B-4 ISUP(NU) Q.931 Q.931 Clause 7/Q.35. Not set by Telecom Not set by Telecom DSS1 only DSS1 only MLPP. Not set by Telecom MLPP. Not set by Telecom NUT B-5 ISUP Q.931 Not set by Telecom (Note 2) Tone R2MFC Application Reference Remarks
Cause
Definition
Class Value
No.
000
0001
Unallocated (unassigned) number
000
0010
No route to specified transit network
000
0011
No route to destination
000
0100
Send special information tone
000
0101
Misdialled trunk prefix
000
0110
Channel unacceptable
000
0111
Call awarded and being delivered in an established channel
000
1000
Preemption
000
1001
Preemption circuit reserved for reuse
001
0000
16
Normal call clearing
001
0001
17
User busy
001
0010
18
No user responding
001
0011
19
No answer from user (user alerted)
C-37
Diagnostics (Note 1) DSCT Call rejected condition (NUT) B-2 ISUP Q.931 DSCT B-4 ISUP Q.732 Call diversion services B-4 ISUP (Note 2) Mobile application. Not set by Telecom Tone R2MFC Application Reference Remarks
Cause
Definition
Class Value
No.
001
0100
20
Subscriber absent
001
0101
21
Call rejected
001
0110
22
Number changed. Used by arrangement only. New destination (DSS 1)/ called party number (ISUP) Used to reroute speech and 3.1kHz audio calls to an operator. On a call from another network, the POI will, for speech & 3.1kHz audio calls on agreement with the interconnected network operator, either reroute the call to a Telecom operator or pass transparently; for 64kbit/s calls pass transparently. ISUP ISUP DSS 1 (NUT) DSCT B-4 ISUP B-8 ISUP Q.931 Q.931 Q.931 2.1.1/Q.764 2.1.2/Q.764 2.9.8.3/Q.764 2.2.5/Q.764 Annex A/Q.763 Facility Identification (DSS 1)/ DSCT parameter name (SUP) B-4 ISUP Q.931
001
0111
23
Redirection to new destination
Not set by Telecom Not set by Telecom DSS1 only
001
1001
25
Exchange routing error
001
1010
26
Non-selected user clearing
001
1011
27
Destination out of order
001
1100
28
Invalid number format (address incomplete)
The called party number is not in a valid format or is not complete Not set by Telecom Inability to provide a request signalling capability Q.735.1 Q.737.1 DSS 1 Q.931 CUG UUS DSS1 only
001
1101
29
Facility rejected
001
1110
30
Response to STATUS ENQUIRY

Diagnostics (Note 1) DSCT cfd/clb ISUP 2.1.1/Q.764 2.1.2/Q.764 2.8.1/Q.764 2.8.2/Q.764 2.9.3/Q.764 2.9.6/Q.764 2.9.8.2/Q.764 2.9.8.3/Q.764 2.1.8/Q.764 2.2.4/Q.764 (Note 2) Call failure information indicating the failure of a call due to the lapse of a timeout or a fault not covered by specific causes (examples: expiry of timers Q.764 not covered by specific causes, release of interconnected circuit, etc.) 2.1.6/Q.764 2.9.7/Q.764 Annex A/Q.763 CCBS Indicator DSCT A-4 ISUP Q.931, Q.733.3 Circuit congestion encountered in an exchange. Not set by Telecom B-4 ISUP DSS 1 DSS 1 DSCT DSCT Discarded information element DSCT identifier(s) (Note 4) DSCT B-4 B-4 B-4 ISUP ISUP ISUP Q.931 Q.933 Q.933 Q.931 2.9.9.1/Q.764 Q.931 Temporary trunk block (national use) Not set by Telecom Not set by Telecom DSS1 only DSS1 only Expiry of waiting INF timer (T33) Tone R2MFC Application Reference Remarks
C-38
Cause
Definition
Class Value
No.
001
1111
31
Normal, unspecified
010
0010
34
No circuit/channel available
010
0110
38
Network out of order
DSCT
010
0111
39
Permanent frame mode connection out of service
010
1000
40
Permanent frame mode connection operational
010
1001
41
Temporary failure
010
1010
42
Switching equipment congestion
010
1011
43
Access information discarded
010
1100
44
Requested circuit/channel not available
B-4
DSS 1, ISUP
Q.931
Not set by Telecom
C-39
Diagnostics (Note 1) DSCT DSCT Annex A/Q.763 Condition Facility Identification (DSS 1)/parameter name (ISUP) DSCT NUT Attribute identity Attribute identity DSCT NUT Attribute identity Channel type Facility Identification (DSS 1)/ DSCT parameter name (ISUP) DSCT NUT B-4 B-4 B-5 NUT B-5 B-5 B-4 NUT B-5 NUT B-5 B-5 ISUP DSS 1, ISUP DSS 1, ISUP DSS 1, ISUP DSS 1, ISUP DSS 1, ISUP DSS 1 DSS 1, ISUP DSS 1, ISUP (NU) DSS 1, ISUP DSS 1 Channel identity DSS 1 DSS 1 B-4 ISUP Q.735.1 Q.735.1 Q.931 Q.931 Q.735 Annex A/Q.763 Annex A/Q.763 Inability to provide a requested TMR Q.931 DSS1 only Q.931, Q.737.1 UUS. Not set by Telecom Q.931 Annex A/Q.763 Q.931 Q.931 Q.931 DSS1 only DSS1 only DSS1 only Not set by Telecom Not set by Telecom NUT B-4 DSS 1, ISUP Q.931, Q.735 DSS 1 Q.931 DSS1 only Not set by Telecom A-4 DSS 1, ISUP Q.931 B-4 DSS 1, ISUP Q.735.3 MLPP. Not set by Telecom (Note 2) Tone R2MFC Application Reference Remarks
Cause
Definition
Class Value
No.
010
1110
46
Precedence call blocked
010
1111
47
Resource unavailable, unspecified
011
0001
49
Quality of service unavailable
011
0010
50
Requested facility not subscribed
011
0101
53
Outgoing calls barred within CUG
CUG. Not set by Telecom CUG
011
0111
55
Incoming calls barred within CUG
011
1001
57
Bearer capability not authorized
011
1010
58
Bearer capability not presently available
011
1110
62
Inconsistency in designated outgoing access information and subscriber class
011
1111
63
Service or option not available, unspecified
100
0001
65
Bearer capability not implemented
100
0010
66
Channel type not implemented
100
0101
69
Requested facility not implemented
100
0110
70
Only restricted digital information bearer capability is available
100
1111
79
Service or option not implemented, unspecified
101
0001
81
Invalid call reference value
101
0010
82
Identified channel does not exist
101
0011
83
A suspended call exists, but this call identity does not

Diagnostics (Note 1) DSS 1 DSS 1 DSS 1 NUT Incompatible parameter (DSS 1) User-to-user indicators parameter name ISUP DSCT NUT NUT Information element identifier (Note 4) NUT B-5 B-5 B-5 DSS 1, ISUP(NU) DSS 1, ISUP DSS 1, DSS 1, ISUP B-4 ISUP Q.737.1 Q.735 Q.931 Annex A/Q.763 Q.931 Q.931 2.9.5.2/Q.764 2.9.5.3/Q.764 DSS 1 B-5 DSS 1, ISUP Q.931 2.9.5.2/Q.764 2.9.5.3/Q.764 Annex A/Q.763 DSS 1 DSS 1 Q.931 Q.931 DSS1 only DSS1 only DSS1 only NUT B-5 DSS 1, ISUP Q.931 UUS2 CUG B-5 ISUP, DSS 1 Q.735.1 CUG Q.931 Q.931 DSS1 only DSS1 only Q.931 DSS1 only (Note 2) Tone R2MFC Application Reference Remarks
C-40
Cause
Definition
Class Value
No.
101
0100
84
Call identity in use
101
0101
85
No call suspended
101
0110
86
Call having the requested call identity has been Clearing cause cleared
101
0111
87
User not member of CUG
101
1000
88
Incompatible destination
101
1010
90
Non-existent CUG
101
1011
91
Invalid transit network selection
101
1111
95
Invalid message, unspecified
110
0000
96
Mandatory information element is missing
110
0001
97
Message type non-existent or not implemented Message type
110
0010
98
Message not compatible with call state or message type non-existent or not implemented
110
0011
99
Information element /parameter non-existent or Information element NUT not implemented identifier(s) (DSS 1) (Note 4 and Note 5)/ Parameter names Information element identifier(s) (Note 4) Message type
110
0100
100 Invalid information element contents
110
0101
101 Message not compatible with call state
C-41
Diagnostics (Note 1) Timer number DSCT B-4 DSS 1, ISUP Q.733.4 (Note 2) Terminal portability: expiry of waiting RES (user) timer. Not set by Telecom Expiry of waiting RES (network) timer (incoming international exchange) Not set by Telecom 2.9.5.2/Q.764 2.9.5.3/Q.764 NUT NUT B-5 B-5 DSS 1, ISUP DSS 1, ISUP Annex A/Q.763 Q.735.1 Annex A/Q.763 CUG Not set by Telecom Tone R2MFC Application Reference Remarks
Cause
Definition
Class Value
No.
110
0110
102 Recovery on timer expiry
2.4.3/Q.764
110 Parameter name(s), message name DSCT B-4 ISUP
0111
103 Parameter non-existent or not implemented, passed on
Parameter name(s)
DSCT
B-4
ISUP(NU)
110
1110
110 Message with unrecognized parameter, discarded
110
1111
111 Protocol error, unspecified
111
1111
127 Interworking, unspecified
NOTES
1 Application indicates that the cause value may be carried in DSS 1 and/or ISUP. Causes carried in ISUP which are not marked for national use (NU) are the minimum set of cause values that shall be supported over the international interface.
2 The references included are not exhaustive.
3 deleted 4 Locking and non-locking shift procedures described in 4.5/Q.931 are applied. In principle information element identifiers are ordered in the same order as the information element in the received message.
5 When only locking shift information element is included and no variable length information element identifier follows, it means that the codeset in the locking shift itself is not implemented.
C-42
Q.850/2.2.6.4
Coding of Call rejected diagnostic
The format of the diagnostic field for cause number 21 is as shown in Figure 2 and Table 2. 8 1 ext. 7 6 5 4 3 2 1 Octets x* x+1* etc. (Note 1) x+2* etc. (Note 2)
Rejection reason User specific diagnostic
Condition
IE type NOTES 1
Information element identifier
This octet may be present only if octet x indicates user specific diagnostic.
2 This octet may be present only if octet x indicates information element missing or information element contents are not sufficient. FIGURE 2/Q.850 Coding of diagnostic field for cause number 21
C-43
TABLE 2/Q.850
Coding of diagnostic field for cause number 21

Rejection reason (octet x) Bits 76543 00000 00001 00010 user specific information element missing information element contents are not sufficient
All other values are reserved Condition (octet x) Bits 21 00 01 10 11 unknown permanent transient spare
User specific diagnostic (octet x+1) Coded according to the user specification, subject to the maximum length of the Cause information element. Information element type (octet x+2) Bit 8 0 1 variable length information element fixed length information element
Information element identifier (octet x+2) Bits 7-1 encoded with the information element identifier of the missing or insufficient information element.
Q.850/2.2.6.5
Coding of New destination/Called party number (new)
New destination is formatted as the called party number information element, including information element identifier. Transit network selection may also be included. Q.850/2.2.6.6 Coding of Facility identification/Rejected parameter
The coding of facility identification is network dependent. Q.850/2.2.6.7 Coding of Attribute identity
The coding of the attribute identity diagnostic is shown in Figure 3, Table 3a and Table 3b.
NOTE Not generated by ISUP.
C-44
8 0/1 ext. 0/1 ext. 1 ext. NOTES
1 Octet x x+1 x+2
Attribute number Rejected attribute Available attribute
1 When diagnostics information is provided, octet x and x+1 shall be present. Octet x+2 is optional. 2 Octets x-x+2 may be repeated to report multiple rejected attributes.
3 The extension bit (ext.) when coded 0, indicates that this diagnostic continues to the next octet. FIGURE 3/Q.850 Coding of the diagnostic field for causes number 57, 58 and 65 (Attribute identity)
TABLE 3A/Q.850
Coding of attribute number field for causes number 57, 58 and 65 Attribute number (octet x)
Bits 7654321 0110001 0110010 0110011 0110100 0110101 0110110 0110111 0111000 0111001 No. 1 2 3 4 5 6 7 8 9 Information transfer capability Information transfer mode Information transfer rate Structure Configuration Establishment Symmetry Information transfer rate (dest. orig.) Layer identification
C-45
TABLE 3B/Q.850
Coding of the rejected attribute field for causes number 57, 58 and 65
Rejected attribute (octet x+1) Attribute No. 1. Information transfer capability: Bits 7-6: 00 Bits 5-1: according to Table 4-6/Q.931, octet 3 Information transfer mode Bits 7-6: according to Table 4-6/Q.931, octet 4 Bits 5-1: 00000 Information transfer rate Bits 7-6: 00 Bits 5-1 according to Table 4-6/Q.931, octet 4 Structure (Note 1) Bits 7-5: according to Table 4-6/Q.931, octet 4a Bits 4-1: 0000 Configuration (Note 1) Bits 7-4: 000 Bits 4-3: according to Table 4-6/Q.931, octet 4a Bits 2-1: 00 Establishment (Note 1) Bits 7-3: 00000 Bits 2-1: according to Table 4-6/Q.931, octet 4a Symmetry (Note 1) Bits 7-6: according to Table 4-6/Q.931, octet 4b Bits 5-1: 00000 Information transfer rate (dest. orig.): (Note 1) Bits 7-6: 00 Bits 5-1: according to Table 4-6/Q.931, octet 4b Layer identification: Bits 76 0 1 (layer 1) Bits 5-1 according to Table 4-6/Q.931, octet 5 1 0 (layer 2) Bits 5-1 according to Table 4-6/Q.931, octet 6 1 1 (layer 3) Bits 5-1 according to Table 4-6/Q.931, octet 7 10. Rate Multiplier: Bit 8: 1 Bits 7-1 according to Table 4-6/Q.931, octet 4.1
2.
3.
4.
5.
6.
7.
8.
9.
Available attributes (octet x+2) The same coding as octet x+1 NOTES 1 These values were defined in Recommendation Q.931 (1988). 2 A description of Table 4-6/Q.931 is found in 3.57.
C-46
Q.850/2.2.6.8 Bit 8: Bit 7-5: Bit 4-1: Q.850/2.2.6.9 Q.850/2.2.6.10
Coding of Channel type Extension bit spare according to the Table 4-15/Q.931 octet 3.2, channel type. Coding of Incompatible parameter Coding of Timer number
The channel type is coded as follows:
Incompatible parameter is composed of incompatible information element identifier.

The timer number is coded in IA5 characters, e.g. T308 is coded as "3" "0" "8". The following coding is used in each octet: Bit 8: Bit 7-1: Q.850/2.2.6.11 Spare "0" IA5 character. Coding of Message type
Message type is coded as specified in Table 4 and Table 4-2/Q.931, respectively. Q.850/2.2.6.12 Coding of parameter name
Parameter name is coded as specified in Table 5/Q.763.
3.13
Circuit group supervision message type
3.11.1 This parameter is used in conjunction with circuit group blocking/unblocking messages to indicate the origin of the block/unblocking request. 3.11.2 Circuit Group Supervision Message Type Indicator is a mandatory fixed length parameter used in the following messages. Circuit Group Blocking (CGB) Circuit Group Blocking Acknowledgement (CGBA) Circuit Group Unblocking (CGU) Circuit Group Unblocking Acknowledgement (CGUA) (ref. 4.24) (ref. 4.24) (ref. 4.24) (ref. 4.24)
The format of the circuit group supervision message type parameter field is shown in Figure 14.
8 H 7 G 6 F 5 E 4 D 3 C 2 B 1 A
Figure 14 Circuit group supervision message type parameter field
The following codes are used in the circuit group supervision message type parameter field: bits
C-47
BA 00 01 10 11 bits H-C 3.14
Circuit group supervision message type indicator maintenance oriented; caused by input of circuit blocking command at the exchange hardware failure oriented; caused by transmission system failure reserved for national use (used in 1984 version). not used by Telecom. Mapped to 00 if received spare. not used by Telecom spare not used by Telecom
Circuit state indicator (national use)
This section has not been reproduced as this parameter is not implemented. 3.15 Closed user group interlock code
This section has not been reproduced as this parameter is not implemented. 3.16 Connected number
This section has not been reproduced as this parameter is not implemented. 3.17 Connection request
This section has not been reproduced as this parameter is not implemented. 3.18 Continuity indicators
This section has not been reproduced as this parameter is not implemented. 3.19 Echo control information
This section has not been reproduced as this parameter is not implemented. 3.20 End of optional parameters
3.20.1 Where one or more optional parameters are present in a message the last parameter field of the message is followed by the end of optional parameters indicator, which occupies a one octet field containing all zeros. The last optional parameter field of a message is followed by the end of optional parameters octet (see 1.8). 3.21 Event information
3.21.1 This parameter is used to indicate the type of event which caused a call progress message in the backward direction. An ISUP-ISUP transit exchange will pass the parameter on unchanged. An originating exchange will send the equivalent information to an ISDN calling party via access signalling. 3.21.2 Event Information is mandatory fixed length parameter used in the following message: Call Progress (CPG) (ref. 4.4)
C-48
The format of the event information parameter field is shown in Figure 21.
8 H 7 G 6 F 5 E 4 D 3 C 2 B 1 A
Figure 21 Event information parameter field
The following codes are used in the event indicator parameter field: bits GFEDCBA 0000000 0000001 0000010 0000011 0000100 0000101 0000110 0000111 to 1111111 bit H 0 1 3.22 Event indicator spare ALERTING message received from the ISDN access PROGRESS message received from the ISDN access in-band information or an appropriate pattern is now available, i.e., tones or messages call forwarded on busy (national use) call forwarded on no reply (national use) call forwarded unconditional (national use) spare (Note). Used within the Telecom network for special services; not used at the POI interface.
NOTE Coding of this indicator is frozen; no additional codes can be defined for compatibility.
Event presentation restricted indicator (national use); this field is used to indicate if the event which caused the progress message is to be passed back to the subscriber no indication; set for all calls presentation restricted; not set by Telecom
Facility indicator
This section has not been reproduced as this parameter is not implemented. 3.23 Forward call indicators
3.23.1 This parameter is used to pass information indicating the type of call and some of its basic characteristics to the terminating exchange. It can be used by transit exchanges for routing and by terminating exchanges for barring. On receipt of a particular value of this parameter an ISUP-ISUP transit exchange will, in some circumstances, modify it to indicate call characteristics. 3.23.2 Forward Call Indicators is a mandatory fixed length parameter used in the following message: Initial Address (IAM) (ref. 4.13)
3.23.3 The format of the forward call indicators parameter field is shown in Figure 23.
C-49
8 H P 7 G O 6 F N 5 E M 4 D L 3 C K 2 B J 1 A I
1 2
Figure 23 Forward call indicators parameter field
3.23.4 The following codes are used in the forward call indicators parameter field: bit A 0 1 National/international call indicator call to be treated as a national call; set on all calls originated in the Telecom network, or when the origin is not known call to be treated as an international call; set on the first and subsequent contiguous ISUP stages beyond the international exchange for all incoming international calls
This bit can be set to any value in the country of origin. In the international network this bit is not checked. In the destination country, calls from the international network will have this bit set to 1. bits CB 00 01 10 11 bit D 0 1 End-to-end method indicator (Note) no end-to-end method available (only link-by-link method available); set for all calls pass-along method available (national use); not set by Telecom SCCP method available; not set by Telecom pass-along and SCCP methods available (national use); not set by Telecom Interworking indicator (Note) (Note 2) no interworking encountered (No. 7 signalling all the way) encountered; set on the first and subsequent contiguous No.7 stages beyond the originating exchange to indicate that No.7 signalling has been used all the way interworking encountered; set on first and subsequent No.7 stages following a non-No.7 signalling stage; also set after a call has been intercepted by an operator node End-to-end information indicator (Note) (national use) no end-to-end information available; set for all calls end-to-end information available; i.e., waiting transmission; not set by Telecom ISDN user part indicator (Note) (Note 2) ISDN user part not used all the way; set on first and subsequent contiguous ISUP stages following a non-ISUP signalling stage; also set after a call has been intercepted by an operator node ISDN user part used all the way; set on the first and subsequent contiguous ISUP stages beyond the originating exchange to indicate that ISUP signalling has been used all the way
bit E 0 1 bit F 0 1
C-50
bits HG 00 01 10 11 bit I 0 1 bits KJ 00 01 10 11 bit L bit M 0 1
ISDN user part preference indicator ISDN user part preferred all the way; set on first and subsequent contiguous ISUP stages for all calls from ISDN lines ISDN user part not required all the way; set for all calls from PSTN lines and for all calls beyond a non-ISUP signalling stage; also set after a call has been intercepted by an operator node ISDN user part required all the way; set on first and subsequent contiguous ISUP stages for Wide Area Centrex calls that require ISUP spare; not set by Telecom ISDN access indicator originating access non-ISDN; set for calls from PSTN lines and for all calls beyond a non-ISUP signalling stage; also set after a call has been intercepted by an operator node originating access ISDN; set on first and subsequent contiguous ISUP stages for all calls from ISDN lines SCCP method indicator (Note) no indication; set for all calls connectionless method available (national use) ; not set by Telecom connection oriented method available; not set by Telecom connectionless and connection oriented methods available (national use) ; not set by Telecom Spare; not set by Telecom Reverse charge indicator Not a reverse charge call Reverse charge call. Set for all calls beyond an operator for collect calls. This may be used only by agreement with the interconnect network operator. Otherwise always coded 0 when sent from a Telecom POI to another network. Ignored and converted to value 0 if received from another network. Reserved for national use; Used to provide Telecom network services. Always coded 0 when sent from a Telecom POI to another network. Ignored and converted to value 0 if received from another network. IN indicator Not an IN call IN call. Set for all calls following interaction with the Telecom Intelligent Network This may be used only by agreement with the interconnect network operator.
bit N
bit O 0 1
Reserved for national use; Used to provide Telecom network services. Always coded 0 when sent from a Telecom POI to another network. Ignored and converted to value 0 if received from another network. NOTE Bits B-F and J-K constitute the protocol control indicator.
bit P
C-51
NOTE 2 For calls originating in Telecom's network bits D and F convey identical information because ISUP is the only part of No.7 signalling used for call control. i.e. on first and subsequent links beyond a section of R2MFC or DP signalling bit D = 1 and bit F = 0 3.24 Generic digits (national use)
This section has not been reproduced as this parameter is not implemented. 3.25 Generic notification indicator
This section has not been reproduced as this parameter is not implemented. 3.26 Generic notification indicator
This section has not been reproduced as this parameter is not implemented. 3.27 3.28 Reserved (used in 1992 version) Information indicators (national use)
This section has not been reproduced as this parameter is not implemented. 3.29 Information request indicators (national use)
This section has not been reproduced as this parameter is not implemented. 3.30 Location number
This section has not been reproduced as this parameter is not implemented. 3.31 MCID request indicators
This section has not been reproduced as this parameter is not implemented. 3.32 MCID response indicators
This section has not been reproduced as this parameter is not implemented. 3.33 Message compatibility information
This section has not been reproduced as this parameter is not implemented. 3.34 MLPP precedence
This section has not been reproduced as this parameter is not implemented. 3.35 Nature of connection indicators
3.35.1 This parameter is used to indicate some of the physical characteristics of the inter-exchange traffic circuits used for the call. In the Telecom network its only use is to allow a transit exchange to base routing on whether a preceding stage of the call has used a satellite circuit. 3.35.2 Nature of Connection indicators is a mandatory fixed length parameter used in the following message: Initial Address (IAM) (ref. 4.13)
C-52
The format of the nature of connection indicators parameter field is shown in Figure 36.
8 H 7 G 6 F 5 E 4 D 3 C 2 B 1 A
Figure 36 Nature of connection indicators parameter field The following codes are used in the nature of connection indicators parameter field: bits BA 00 01 10 11 bits DC 00 01 10 11 bit E 0 1 bits F-H Satellite indicator no satellite circuit in the connection one satellite circuit in the connection two satellite circuits in the connection spare; not set by Telecom; mapped to value 10 if received Continuity check indicator continuity check not required; always set continuity check required on this circuit; not set by Telecom continuity check performed on a previous circuit; not set by Telecom spare; not set by Telecom Echo control device indicator outgoing echo control device not included; always set outgoing echo control device included; not set by Telecom; passed transparently if received from another network at a POI Spare; set to value 0 by Telecom
Note 1 - The received value of satellite indicator is incremented by 1 (up to a maximum value of 2) when the outgoing circuit is via satellite. 3.36 Network specific facility (national use)
This section has not been reproduced as this parameter is not implemented. 3.37 Optional backward call indicators
3.37.1 This parameter is used to pass information additional to that in the Backward Call Indicators Parameter (ref 3.5) back to the originating No.7 exchange (i.e. in the direction from the terminating towards the originating exchange). The information may be used by the originating exchange to activate special facilities or may be mapped to the originating ISDN access. On receipt of a particular value of this parameter, an ISUP-ISUP transit exchange will in general pass the parameter on, unchanged. 3.37.2 Optional Backward Call Indicators is an optional parameter which may be used in the following messages (Note: it is normally included only if one or more of bits A, B or H is set to "1"):
C-53
Address Complete (ACM) Answer (ANM) Call Progress (CPG) Connect (CON)
(ref. 4.2) (ref. 4.3) (ref. 4.4) (ref. 4.8)
However, it is not used in the ANM and CON messages by Telecom. Note: it is included in the ACM only in the following circumstances: a) Always, when the terminating line is non-ISDN (bit A=1, bits B, H as applicable). b) Always, when ISUP to non-ISUP interworking has been encountered (bit A=1, bits B, H as applicable). c) When the terminating line is ISDN and the conditions exist for setting any one or more of bits A, B or H to value 1. The format and codes of the optional backward call indicators field is shown in Figure 38.
8 H 7 G 6 F 5 E 4 D 3 C 2 B 1 A
Figure 38 Optional backward call indicators parameter field
The following codes are used in the optional backward call indicators parameter field: bit A 0 1 In-band information indicator no indication; set for calls where Transmission Medium Requirement parameter (ref. 3.54) in the IAM is set to 64kbit/s in-band information or an appropriate pattern is now available; set for calls where Transmission Medium Requirement parameter (ref. 3.54) in the IAM is set to 3.1kHz audio or speech, to indicate that tones or announcements may be returned inband to the calling user The information received in this indicator at the originating exchange will be passed to the ISDN access in an alerting or call progress message. Call diversion may occur indicator no indication; always set call diversion may occur; not set by Telecom Simple segmentation indicator no additional information will be sent; always set additional information will be sent in a segmentation message; not set by Telecom MLPP user indicator no indication; always set MLPP user; not set by Telecom Reserved for national use; set to value 0 by Telecom
Note: bit B 0 1 bit C 0 1 bit D 0 1 bits G-E
C-54
bit H
Reserved for national use; Used in the Telecom network to provide special facilities. Coded "0" if sent from a Telecom POI to another network.
3.38
Optional forward call indicators
This section has not been reproduced as this parameter is not implemented. 3.39 Original called number
3.39.1 This parameter is used in Call Diversion Supplementary service, to carry the identity of the number that was originally called. Refer to Appendix 5 for a description of the ISUP signals used when diverting calls. A terminating exchange receiving this parameter may pass it to the ISDN called party. 3.39.2 The passing of redirecting information, including this parameter, at the POI is subject to agreement and is controlled by configuration data. 3.39.3 Original Called Number is an optional parameter which may be used in the following message: Initial Address (IAM) (ref. 4.13)
The format of the original called number parameter field corresponds to the format shown in Figure 40.
8 Odd/ even Spare 7 6 5 4 3 2 1
1 2 3 . . n
Nature of address indicator Numbering plan ind. 2nd address signal Address presentation Spare restricted indicator 1st address signal
nth address signal
Figure 40 Original called number parameter field
The following codes are used in the subfields of the original called number parameter field: a) Odd/even indicator: see 3.9.2 a).
C-55
b)
Nature of address indicator: 0000000 0000001 0000010 0000011 0000100 0000101 to 1101111 1110000 to 1111110 1111111 spare; not set by Telecom subscriber number (national use) ; not set by Telecom unknown (national use) national (significant) number (national use); (recommended setting) international number; not set by Telecom but passed on if received from another country spare; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom
c) d) e) f) 3.40
Numbering plan indicator: see 3.9.2 d). Address presentation restricted indicator: see 3.10.4 e). Address signal: see 3.10.4 g). Filler: see 3.9.2 f). Origination ISC point code
3.41
Parameter compatibility information
This section has not been reproduced as this parameter is not implemented. 3.42 Propagation delay counter
This section has not been reproduced as this parameter is not implemented. 3.43 Range and status
3.43.1 This parameter is used to indicate the range of circuits, and to identify specific circuits within that range, affected by the message in which the parameter appears. 3.43.2 Range and Status is a mandatory variable length parameter used in the following messages (known as circuit group supervision messages) which are used between exchanges to block and idle groups of traffic circuits: Circuit Group Blocking (CGB) Circuit Group Blocking Acknowledgement (CGBA) Circuit Group Unblocking (CGU) Circuit Group Unblocking Acknowledgement(CGUA) Circuit Group Reset (GRS) Circuit Group Reset Acknowledgement(GRA) (ref. 4.24) (ref. 4.24) (ref. 4.24) (ref. 4.24) (ref. 4.25) (ref. 4.6)
C-56
It is also used in the following messages neither of which is used by Telecom: Circuit Group Query (CGM) Circuit Group Query Response (CQR) (ref. 4.26) (ref. 4.5)
The format of the range and status parameter field is shown in Figure 43.
8 1 2 . . . n 7 6 5 Range Status 4 3 2 1
Figure 43 Range and status parameter field
The following codes are used in the subfields of the range and status parameter field: a) Range A number in pure binary representation ranging from 0 to 255 (1 to 255 for Telecom). The number represented by the range code + 1 indicates the range of circuits affected by the message. The number of circuits affected by a group supervision message is limited to 32 or less. For the group reset messages, a circuit group query message, or a circuit query response message, this requires that the range value be 31 or less. For the group blocking and unblocking messages the range value may be up to 255, but the number of status bits set to 1 must be 32 or less. For the group blocking, unblocking and reset messages, range code 0 is reserved. Range code 0 is exclusively used by the circuit query and circuit query response messages. The range field value of 0 (allowed only in the CQM and CQR messages, which are not used by Telecom) means the message applies only to the circuit identified by the CIC parameter. In this case the status field will not be present. If a range field value of zero or a range value greater than 31 is received, the Telecom network will ignore the group message; no response will be given. b) Status The status subfield contains from 2 to 256 status bits numbered from 0 to 255. Status bit 0 is located in bit position 1 of the first status subfield octet. Other status bits follow in numerical order. The number of relevant status bits in a given status subfield is equal to range + 1. Each status bit is associated with a circuit identification code such that status bit n is associated with circuit identification code m + n, where m is the circuit identification code contained in the message. The status bits are coded as follows: in circuit group blocking (CGB) messages 0 1 no indication; (no action required) blocking; (circuit is to be blocked)
C-57
in circuit group blocking acknowledgement (CGBA) messages 0 1 no indication; (no action taken) blocking acknowledgement; (circuit has been blocked) no indication; (no action required) unblocking; (circuit is to be made idle) no indication; (no action taken) unblocking acknowledgement; (circuit has been released) not blocked for maintenance reasons; (i.e. available for service or blocked for hardware failure reasons) blocked for maintenance reasons; (circuit is to stay blocked); i.e. When a reset message is received for a group of circuits requesting that some circuits already blocked for maintenance reasons be reset (made idle), the Reset Acknowledgement message will advise the exchange originating the reset that these particular circuits must remain blocked.
in circuit group unblocking (CGU) messages 0 1
in circuit group unblocking acknowledgement (CGUA) messages 0 1
in circuit group reset acknowledgement (GRA) messages 0 1
3.44
Redirecting number
3.44.1 This parameter is used in call diversion supplementary service and call rerouting (not used by Telecom) to pass forward the number from which the call was last diverted. Refer to Appendix 5 for a description of the ISUP signals used when diverting calls. 3.44.2 The passing of redirecting information, including this parameter, at the POI is subject to agreement with the interconnect network operator and is controlled by configuration data. 3.44.3 If the POI has been set to pass redirection information, then the Redirecting number parameter must be included for calls that have been redirected one or more times. 3.44.4 If the POI has been set to not pass redirection information, and the Redirecting number parameter is present within Telecoms network, the Calling party number parameter will be set to the contents of the Redirecting number parameter before the call is passed to the POI. 3.44.5 Redirecting Number is an optional parameter which may be used in the following message: Initial Address (IAM) (ref. 4.13)
The format of the redirecting number parameter field corresponds to the format shown in Figure 40. The following codes are used in the subfields of the redirecting number parameter field: a) Odd/even indicator: see 3.9.2 a)
C-58
b)
Nature of address indicator: 0000000 0000001 0000010 0000011 0000100 0000101 to 1101111 1110000 to 1111110 1111111 spare; not set by Telecom subscriber number (national use); not set by Telecom unknown (national use); not set by Telecom national (significant) number (national use); (recommended setting) international number; may be received on incoming international calls spare; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom
c) d) e) f) 3.45
Numbering plan indicator: see 3.9.2 d) Address presentation restricted indicator: see 3.10.4 e) Address signal: see 3.10.4 g) Filler: see 3.9.2 f). Redirection information
3.45.1 This parameter is used to pass information associated with call diversion supplementary service and call rerouting (not used by Telecom) in either the forward or backward direction (not used by Telecom). Refer to Appendix 5 for a description of the ISUP signals used when diverting calls. 3.45.2 The passing of redirecting information, including this parameter, at the POI is subject to agreement with the interconnect network operator and is controlled by configuration data. 3.45.3 Redirection Information is an optional parameter which may be used in the following messages: Initial Address (IAM) Release (REL) (ref. 4.13) (ref. 4.14)
However, it is not used in the REL message by Telecom. The format of the redirection information parameter field is shown in Figure 44.
8 7 6 5 4 3 2 1 1 H G F E D C B A 2 P O N M L K J I Note The parameter may be received without the second octet from an ISUP88 network This is not applicable at the Telecom POI; both octets must be included.
Figure 44 Redirection information parameter field
C-59
The following codes are used in the redirection information parameter field: bits CBA 000 001 010 011 100 101 110 111 bit D bits HGFE 0000 0001 0010 0011 0100 to 1101 1110 1111 bits KJI bit L bits PONM 0000 0001 0010 0011 0100 0101 0110 0111 to 1101 1110 1111 Redirecting indicator no redirection (national use) call rerouted (national use) ; not set by Telecom call rerouted, all redirection information presentation restricted (national use) ; all redirection information presentation; not set by Telecom call diverted call diverted, all redirection information presentation restricted call rerouted, redirection number presentation restricted (national use) ; not set by Telecom call diversion, redirection number presentation restricted (national use) spare; not set by Telecom Spare; set to value 0 by Telecom Original redirection reason unknown/not available user busy (national use) no reply (national use) unconditional (national use) spare; not set by Telecom spare; queue overflow; used by Telecom but not passed to other networks at the POI spare; not set by Telecom Redirection counter. Number of redirections the call has undergone expressed as a binary number between 1 and 5. Reserved for national use Redirecting reason unknown/not available user busy no reply unconditional deflection during alerting; not set by Telecom deflection immediate response; not set by Telecom mobile subscriber not reachable; not set by Telecom spare; not set by Telecom spare; queue overflow; used by Telecom but not passed to other networks at the POI spare; not set by Telecom
C-60
3.46
Redirection number
3.46.1 This parameter is used to pass information associated with call diversion supplementary service and call rerouting in either the forward or backward direction. 3.46.2 The passing of redirecting information, including this parameter, at the POI is subject to agreement with the interconnect network operator and is controlled by configuration data. 3.46.3 Redirection Information is an optional parameter which may be used in the following messages: Address Complete (ACM) Answer (ANM) Call Progress (CPG) Release (REL) (ref. 4.2) (ref. 4.3) (ref. 4.4) (ref. 4.14)
However, it is not used in the REL message by Telecom at the POI. The format of the redirection number parameter field corresponds to the format shown in Figure 10. The following codes are used in the subfields of the redirection number parameter field: a) b) Odd/even indicator: see 3.9.2 a). Nature of address indicator: 0000000 0000001 0000010 0000011 0000100 0000101 to 1101111 1110000 to 1111110 1111111 c) d) e) f) 3.47 spare; not set by Telecom subscriber number (national use); not set by Telecom unknown (national use); normally set by Telecom national (significant) number (national use); not set by Telecom international number; may be received on outgoing international calls spare; not set by Telecom reserved for national use; not set by Telecom spare; not set by Telecom
Internal network number indicator: see 3.9.2 c). Numbering plan indicator: see 3.9.2 d). Address signal: see 3.10.4 g). Filler: see 3.9.2 f). Redirection number restriction
This section has not been reproduced as this parameter is not implemented. 3.48 Remote operations (national use)
This section has not been reproduced as this parameter is not implemented. 3.49 Service activation
C-61
3.50
Signalling point code (national use)
3.50.1 This parameter is sent in either or both directions during call release to identify the exchange (by its signalling point code) which initiated the release procedure. 3.50.2 Signalling Point Code is an optional parameter which may be used in the following message: Release (REL) (ref. 4.14) However, this parameter is included in all release messages sent by the Telecom POI exchange to other networks, and is required to be included in all release messages sent to the Telecom POI exchange by other networks. The format of the signalling point code parameter field is shown in Figure 50.
8 1 2 Spare 7 6 5 4 Signalling point code 3 2 1 LSB
Figure 50 Signalling point code parameter field
3.51
Subsequent number
This section has not been reproduced as this parameter is not implemented. 3.52 a) Suspend/resume indicators the suspension of a call was initiated: i) ii) and b) the resumption of the call was initiated: i) ii) by an ISDN user, or by a PSTN user (set by Telecom but not sent from the Telecom POI to another network), or by an ISDN user, or by the network (not set by Telecom),
3.52.1 This parameter can be used to indicate whether:
iii) by the network (not set by Telecom). 3.52.2 Suspend/Resume indicators is a mandatory fixed length parameter used in the following messages: Suspend (SUS) Resume (RES) (ref. 4.20) (ref. 4.21)
The format of the suspend/resume indicators parameter field is shown in Figure 52.
8 H 7 G 6 F 5 E 4 D 3 C 2 B 1 A
Figure 52 Suspend/resume indicators parameter field
C-62
The following codes are used in the suspend/resume indicators parameter field: bit A 0 1 Suspend/resume indicator ISDN subscriber initiated; always set network initiated; not set by Telecom. If received in a SUS message from another network the call may be released.
bits H-B Spare; set to value 0 by Telecom 3.53 Transit network selection (national use)
This section has not been reproduced as this parameter is not implemented. 3.54 Transmission medium requirement
3.54.1 This parameter is used to indicate the type of transmission bearer capability requested (or implied) by the calling party for the call. 3.54.2 Transmission Medium Requirements Indicators is a mandatory fixed length parameter used in the following message: Initial Address (IAM) (ref. 4.13) The format of the transmission medium requirement parameter field is shown in Figure 54.
8 7 6 5 4 3 Transmission medium requirement (TMR) 2 1
Figure 54 Transmission medium requirement parameter field
The following codes are used in the transmission medium requirement parameter field: 00000000 00000001 00000010 00000011 00000100 00000101 00000110 00000111 00001000 00001001 00001010 00001011 to 00001111 00010000 00010001 00010010 00010011 speech; set for speech calls from ISDN lines only (see ITU-T Recommendation I.530 [11]) spare; not set by Telecom 64 kbit/s unrestricted; set for ISDN unrestricted 64 kbit/s calls 3.1 kHz audio; set for ISDN audio and all PSTN calls (see ITU-T Recommendation I.530) reserved for alternate speech (service 2)/64 kbit/s unrestricted (service 1) ; not set by Telecom reserved for alternate 64 kbit/s unrestricted (service 1)/speech (service 2) ; not set by Telecom 64 kbit/s preferred; not set by Telecom 2 64 kbit/s unrestricted; not set by Telecom 384 kbit/s unrestricted; not set by Telecom 1536 kbit/s unrestricted; not set by Telecom 1920 kbit/s unrestricted; not set by Telecom spare; not set by Telecom 3 64 kbit/s unrestricted; not set by Telecom 4 64 kbit/s unrestricted; not set by Telecom 5 64 kbit/s unrestricted; not set by Telecom spare; not set by Telecom
C-63
00010100 00010101 00010110 00010111 00011000 00011001 00011010 00011011 00011100 00011101 00011110 00011111 00100000 00100001 00100010 00100011 00100100 00100101 00100110 00100111 00101000 00101001 00101010 00101011 to 11111111
7 64 kbit/s unrestricted; not set by Telecom 8 64 kbit/s unrestricted; not set by Telecom 9 64 kbit/s unrestricted; not set by Telecom 10 64 kbit/s unrestricted; not set by Telecom 11 64 kbit/s unrestricted; not set by Telecom 12 64 kbit/s unrestricted; not set by Telecom 13 64 kbit/s unrestricted; not set by Telecom 14 64 kbit/s unrestricted; not set by Telecom 15 64 kbit/s unrestricted; not set by Telecom 16 64 kbit/s unrestricted; not set by Telecom 17 64 kbit/s unrestricted; not set by Telecom 18 64 kbit/s unrestricted; not set by Telecom 19 64 kbit/s unrestricted; not set by Telecom 20 64 kbit/s unrestricted; not set by Telecom 21 64 kbit/s unrestricted; not set by Telecom 22 64 kbit/s unrestricted; not set by Telecom 23 64 kbit/s unrestricted; not set by Telecom spare; not set by Telecom 25 64 kbit/s unrestricted; not set by Telecom 26 64 kbit/s unrestricted; not set by Telecom 27 64 kbit/s unrestricted; not set by Telecom 28 64 kbit/s unrestricted; not set by Telecom 29 64 kbit/s unrestricted; not set by Telecom spare; not set by Telecom
Note If a received value of this parameter is not one of the values set by Telecom the call may be released with cause value 35. 3.55 Transmission medium requirement prime
This section has not been reproduced as this parameter is not implemented. 3.56 Transmission medium used
This section has not been reproduced as this parameter is not implemented. 3.57 User service information
3.57.1 This parameter is used to enable the originating ISDN subscriber to advise the terminating subscriber the transmission protocol to be used. It is also used by some networks that may not be able to support 64kbit/s unrestricted data transmission. At the originating exchange it is coded directly from the Bearer Capability information element in the ISDN access. At the terminating exchange it is mapped to the Bearer Capability information element in the ISDN access. Exchanges in the Telecom network treat this parameter transparently, i.e. they do not use it for routing. 3.57.2 User Service Information is an optional parameter which may be used in the following message: Initial Address (IAM) (ref. 4.13) The format of the user service information parameter field is shown in Figure 55. This format is the same as the Bearer capability information element from Recommendation Q.931 and not all
C-64
capabilities coded here are supported at this time. Refer to Telecom publication TNA 134, 4.5.5 for details. Also note that: (1) (2) (3) (4) Information transfer rates other than 64 kbit/s are not applicable on calls to or from Telecom's POI exchange and another network. Transfer Mode coded "packet mode" is not applicable on calls to or from Telecom's POI exchange and another network. In the Telecom network, calls coded "packet mode" on the originating ISDN access are handled by the Telecom packet network. The User service information parameter shall be present in all calls from ISDN lines where the Forward call indicator sets bit I (ISDN access indicator) to Originating access ISDN. If the User service information parameter is absent in this case, call processing may be undetermined. The User service information parameter shall be absent in all calls from non-ISDN lines where the Forward call indicator sets bit I (ISDN access indicator) to Originating access non-ISDN. If the User service information parameter is present in this case, call processing may be undetermined.
8 ext. ext. ext. ext. ext. 7 6 Coding standard Transfer mode Layer ident. Layer ident. Layer ident. 4 3 2 Information transfer capability Information transfer rate Rate multiplier User information layer 1 protocol User information layer 2 protocol User information layer 3 protocol 5 1
(5)
1 2 2a 3 4 5
NOTE 1 Octet 2a is required if octet 2 indicates multirate (64 kbit/s base rate); otherwise, it shall not be present. NOTE 2 Octets 3, 4, 5 or any combination of these octets may be omitted. Octet 3 may be extended as described in Recommendation Q.931.
Figure 55 User service information parameter field
The codes to be used in the subfields of the user service information parameter field is defined in the Bearer capability information element in Recommendation Q.931. 3.58 User service information prime
This section has not been reproduced as this parameter is not implemented. 3.59 User teleservice information
This section has not been reproduced as this parameter is not implemented. 3.60 User-to-user indicators
C-65
3.61
User-to-user information
3.61.1 This parameter is used to transport information directly from one ISDN user to another. An ISUP-ISUP transit exchange will pass the parameter on, unchanged. 3.61.2 User-to-user Information is an optional parameter which may be used in the following messages: Initial Address (IAM) Answer (ANM) Call Progress (CPG) Connect (CON) Release (REL) Address Complete (ACM) Segmentation (SGM) User to User Information (USR) (ref. 4.13) (ref. 4.3) (ref. 4.4) (ref. 4.8) (ref. 4.14) (ref. 4.2) (ref. 4.34) (ref. 4.17)
It may also be used in the following messages, however Telecom does not do so:
3.61.3 The format of the user-to-user information parameter is shown in Figure 58.
8 1 . . . n 7 6 5 4 3 2 1
User-to-user information
Figure 58 User-to-user information parameter field
3.61.4 The format of the user-to-user information parameter field is coded identically to the protocol discriminator plus user information field described in Recommendation Q.931. The maximum permitted length of this parameter is constrained by the maximum permitted MSU length and its other contents. 3.62 Backward GVNS
This section has not been reproduced as this parameter is not implemented. 3.63 CCSS
This section has not been reproduced as this parameter is not implemented. 3.64 Call transfer number
This section has not been reproduced as this parameter is not implemented. 3.65 Call transfer reference
C-66
3.66
Forward GVNS
This section has not been reproduced as this parameter is not implemented. 3.67 Loop prevention indicators
This section has not been reproduced as this parameter is not implemented. 3.68 Network management controls
This section has not been reproduced as this parameter is not implemented. 3.69 Circuit assignment map
This section has not been reproduced as this parameter is not implemented. 3.70 Correlation id
This section has not been reproduced as this parameter is not implemented. 3.71 SCF id
This section has not been reproduced as this parameter is not implemented. 3.72 Call diversion treatment indicators
This section has not been reproduced as this parameter is not implemented. 3.73 Called IN number
This section has not been reproduced as this parameter is not implemented. 3.74 Call offering treatment indicators
This section has not been reproduced as this parameter is not implemented. 3.75 Charged party identification (national use)
This section has not been reproduced as this parameter is not implemented. 3.76 Conference treatment indicators
This section has not been reproduced as this parameter is not implemented. 3.77 Display information
This section has not been reproduced as this parameter is not implemented. 3.78 UID action indicators
This section has not been reproduced as this parameter is not implemented. 3.79 UID capability indicators
This section has not been reproduced as this parameter is not implemented. 3.80 Hop counter
C-67
3.81
Collect call request
This section has not been reproduced as this parameter is not implemented. 4 4.1 ISDN user part messages and codes General
4.1.1 In Tables 21 to 50, the format and coding of ISDN user part messages are specified. For each message, a list of the relevant parameters is given and for each parameter: a reference to the subclause where the formatting and coding of the parameter content is specified; the type of the parameter. The following types are used in the tables: F = mandatory fixed length parameter; V = mandatory variable length parameter; O = optional parameter of fixed or variable length; the length of the parameter. The value in the table includes: for type F parameters: the length, in octets, of the parameter content; for type V parameters: the length, in octets, of the length indicator and of the parameter content. The minimum and the maximum length are indicated; for type O parameters: the length, in octets, of the parameter name, length indicator and parameter content. For variable length parameters the minimum and maximum length is indicated.
4.1.2 For each message type, type F parameters and the pointers for the type V parameters must be sent in the order specified in these tables. Although optional parameters can be received and handled in any order, messages originating in Telecom's network will always include such parameters in the order depicted in the message formats shown in Tables 21 to 50. 4.1.3 The routing label and circuit identification code fields, which are transmitted ahead of the message type field if required, are not shown. Parameter names, pointers to mandatory variable fields and the optional part, and length indicators appear in the message in accordance with Figure 3 and are not shown explicitly in Tables 21 to 50. 4.2 Address Complete Message
4.2.1 This is a backward message indicating that sufficient information has been received to complete the connection. It also provides information on the progress of the call including some terminating subscriber category information if available. 4.2.2 For calls using ISUP all the way, the ACM is generated at the terminating exchange and sent to the preceding exchange. At each transit exchange in the connection an ACM is sent back when an associated ACM is received from the succeeding exchange. 4.2.3 For calls where an R2MFC link follows an ISUP link the ACM is sent when an A-6, B-1, B-6, B-7, B-9, or B-10 signal is received at the ISUP-R2MFC exchange.
C-68
4.2.4 For calls where a DP link follows an ISUP link the ACM is sent when the IAM has been received at the ISUP-DP exchange. 4.2.5 The format of the ACM is shown in Table 21. Table 21
Message Type: Address complete Parameter Message type Backward call indicators Optional backward call indicators Call reference (national use) Cause indicators User-to-user indicators User-to-user information Access transport Generic notification indicator (Note 1) Transmission medium used Echo control information Access delivery information Redirection number (Note 2) Parameter compatibility information Call diversion information Network specific facility (national use) Remote operations (national use) Service activation Redirection number restriction indicator Conference treatment indicators UID action indicators End of optional parameters NOTE 1 This parameter may be repeated. NOTE 2 Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call. Reference (subclause) 2.1 3.5 3.37 3.8 3.12 3.60 3.61 3.3 3.25 3.56 3.19 3.2 3.46 3.41 3.6 3.36 3.48 3.49 3.47 3.76 3.78 3.20 Type F F O O O O O O O O O O O O O O O O O O O O Length (octets) 1 2 3 7 4-? 3 3-131 3-? 3 3 3 3 5-12 4-? 3 4-? 8-? 3-? 3 3-? 3-? 1
4.3 4.3.1
Answer This is a backward message indicating that the called subscriber has answered.
4.3.2 The ANM is sent in response to the called subscriber answering or in response to receiving an answer signal from the succeeding exchange. 4.3.3 Receipt of the ANM at the originating exchange causes the transmission path for the relevant inter-exchange circuit to be through-connected in the forward direction. It also starts the call charging process (where relevant).
C-69
4.3.4
The format of the ANM is shown in Table 22.
Table 22
Message Type: Answer Parameter Message type Backward call indicators Optional backward call indicators Call reference (national use) User-to-user indicators User-to-user information Connected number (Note 2) Access transport Access delivery information Generic notification indicator (Note 1) Parameter compatibility information Backward GVNS Call history information Generic number (Notes 1 and 2) Transmission medium used Network specific facility (national use) Remote operations (national use) Redirection number (Note 2) Service activation Echo control information Redirection number restriction indicator Display information End of optional parameters NOTE 1 This parameter may be repeated. NOTE 2 Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call. Reference (subclause) 2.1 3.5 3.37 3.8 3.60 3.61 3.16 3.3 3.2 3.25 3.41 3.62 3.7 3.26 3.56 3.36 3.48 3.46 3.49 3.19 3.47 3.77 3.20 Type F O O O O O O O O O O O O O O O O O O O O O O Length (octets) 1 4 3 7 3 3-131 4-? 3-? 3 3 4-? 3-? 4 5-? 3 4-? 8-? 5-12 3-? 3 3 3-? 1
4.4
Call Progress (CPG)
4.4.1 This is a backward message which may be used to pass information on the progress of the call back to the originating ISDN access. 4.4.2 The information sent may be in response to indications received from the terminating ISDN access or in response to actions taken by the switch such as in the case of call forwarding. 4.4.3 The format of the CPG message is shown in Table 23.
C-70
Table 23
Message Type: Call progress Parameter Message type Event information Cause indicators Call reference (national use) Backward call indicators Optional backward call indicators Access transport User-to-user indicators Redirection number (Note 2) User-to-user information Generic notification indicator (Note 1) Network specific facility (national use) Remote operations (national use) Transmission medium used Access delivery information Parameter compatibility Information Call diversion information Service activation Redirection number restriction indicator Call transfer number (Note 2) Echo control information Connected number (Note 2) Backward GVNS Generic number (Notes 1 and 2) Call history information Conference treatment indicators UID action indicators End of optional parameters NOTE 1 This parameter may be repeated. NOTE 2 Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call. Reference (subclause) 2.1 3.21 3.12 3.8 3.5 3.37 3.3 3.60 3.46 3.61 3.25 3.36 3.48 3.56 3.2 3.41 3.6 3.49 3.47 3.64 3.19 3.16 3.62 3.26 3.7 3.76 3.78 3.20 Type F F O O O O O O O O O O O O O O O O O O O O O O O O O O Length (octets) 1 1 4-? 7 4 3 3-? 3 5-12 3-131 3 4-? 8-? 3 3 4-? 3 3-? 3 4-? 3 4-? 3-? 5-? 4 3-? 3-? 1
4.5
Circuit Group Query Response (CQR)
This section has not been reproduced as this message is not implemented.
C-71
4.6
Circuit Group Reset Acknowledgement
4.6.1 This message, in combination with the Circuit Group Reset (GRS) message (refer 4.25 in this part) is used to reset circuits to the idle state following exchange software initialisation at one end of the inter exchange circuits. 4.6.2 The GRA message is sent in response to a GRS message to confirm that circuits are being made idle as requested. 4.6.3 The format of the GRA message is shown in Table 25. Table 25
Message Type: Circuit group reset acknowledgement Parameter Message type Range and status Reference (subclause) 2.1 3.43 Type F V Length (octets) 1 3-34
4.7
Confusion (CFN)
4.7.1 This message is used when it is necessary to advise the preceding exchange that an unrecognisable parameter has been received. 4.7.2 The format of the CFN message is shown in Table 26. Table 26
Message Type: Confusion Parameter Message type Cause indicators End of optional parameters Reference (subclause) 2.1 3.12 3.20 Type F V O Length (octets) 1 3-? 1
4.8
Connect Message (CON)
4.8.1 This is a backward message indicating that sufficient information has been received and that the called subscriber has answered. It serves as both an ACM and an ANM. 4.8.2 Receipt of the CON at the originating exchange causes the transmission path for the relevant inter-exchange circuit to be through-connected in the forward direction. It also starts the call charging process (where relevant). 4.8.3 This message is not originated by Telecom's exchanges, however they are able to receive and interpret it. It will be passed transparently if received from another network (e.g. from the international network). 4.8.4 The format of the CON message is shown in Table 27.
C-72
Table 27
Message Type: Connect Parameter Message type Backward call indicators Optional backward call indicators Backward GVNS Connected number (Note 2) Call reference (national use) User-to-user indicators User-to-user information Access transport Network specific facility (national use) Generic notification indicator (Note 1) Remote operations (national use) Transmission medium used Echo control information Access delivery information Call history information Parameter compatibility information Service activation Generic number (Notes 1 and 2) Redirection number restriction indicator Conference treatment indicators End of optional parameters NOTE 1 This parameter may be repeated. NOTE 2 Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call. Reference (subclause) 2.1 3.5 3.37 3.62 3.16 3.8 3.60 3.61 3.3 3.36 3.25 3.48 3.56 3.19 3.2 3.7 3.41 3.49 3.26 3.47 3.76 3.20 Type F F O O O O O O O O O O O O O O O O O O O O Length (octets) 1 2 3 3-? 4-? 7 3 3-131 3-? 4-? 3 8-? 3 3 3 4 4-? 3-? 5-? 3 3-? 1
4.9
Continuity (COT)
This section has not been reproduced as this message is not implemented. 4.10 Facility Reject (FRJ)
This section has not been reproduced as this message is not implemented. 4.11 Information (INF)
This section has not been reproduced as this message is not implemented. 4.12 Information Request (INR)
C-73
4.13
Initial Address Message (IAM)
4.13.1 This message is the first message sent forward when setting up any call. It is transmitted as soon as the relevant inter-exchange traffic circuit has been selected for the call. 4.13.2 The IAM contains all the information required to route the call to the destination exchange and connect the call to the called party. 4.13.3 Immediately after sending the IAM the originating exchange will through-connect the transmission path for the relevant inter-exchange circuit in the backward direction. 4.13.4 Through-connection of the transmission path in both directions will be completed at transit exchanges immediately after the IAM has been sent. 4.13.5 The format of the IAM is shown in Table 32.
Table 32
Message Type: Initial address Parameter Message type Nature of connection indicators Forward call indicators Calling party's category Transmission medium requirement Called party number (Note 2) Transit network selection (national use) Call reference (national use) Calling party number (Note 2) Optional forward call indicators Redirecting number (Note 2) Redirection information Closed user group interlock code Connection request Original called number (Note 2) User-to-user information Access transport User service information User-to-user indicators Generic number (Notes 1 and 2) Propagation delay counter User service information prime Network specific facility (national use) Generic digit (national use) (Note 1) Origination ISC point code Reference (subclause) 2.1 3.35 3.23 3.11 3.54 3.9 3.53 3.8 3.10 3.38 3.44 3.45 3.15 3.17 3.39 3.61 3.3 3.57 3.60 3.26 3.42 3.58 3.36 3.24 3.40 Type F F F F F V O O O O O O O O O O O O O O O O O O O Length (octets) 1 1 2 1 1 4-16 4-? 7 4-16 3 4-12 3-4 6 7-9 4-12 3-131 3-? 4-13 3 5-? 4 4-13 4-? 4-? 4
C-74
Table 32
Message Type: Initial address Parameter User teleservice information Remote operations (national use) Parameter compatibility information Generic notification indicator (Note 1) Service activation Generic reference (reserved ) MLPP precedence Transmission medium requirement prime Location number (Note 2) Forward GVNS CCSS Network management controls Circuit assignment map Correlation id Call diversion treatment indicators Called IN number (Note 2) Call offering treatment indicators Conference treatment indicators SCF id UID capability indicators Echo control information Hop counter Collect call request End of optional parameters NOTE 1 This parameter may be repeated. NOTE 2 Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call. Reference (subclause) 3.59 3.48 3.41 3.25 3.49 3.27 3.34 3.55 3.30 3.66 3.63 3.68 3.69 3.70 3.72 3.73 3.74 3.76 3.71 3.79 3.19 3.80 3.81 3.20 Type O O O O O O O O O O O O O O O O O O O O O O O O Length (octets) 4-5 8-? 4-? 3 3-? 5-? 8 3 4-? 5-26 3-? 3-? 6-7 3-? 3-? 4-? 3-? 3-? 3-? 3-? 3 3 3 1
4.14
Release (REL)
4.14.1 The Release message can be used as a forward or a backward signal, to indicate that the call is being released from the preceding or succeeding exchange. 4.14.2 The Release message is initiated by one of the following: (1) Calling subscriber goes on hook. (2) Called subscriber goes on hook. (3) Receipt of a REL message from a preceding exchange or a succeeding exchange.
C-75
(4) Receipt of a clear forward signal from a preceding exchange. (5) Receipt of a clear back signal from a succeeding exchange (6) Whenever the No. 7 exchange requires to release the connection. 4.14.3 After sending a REL message the speech connection is released at the exchange but the trunk circuit concerned is held in a blocked state until a Release Complete message (RLC) is received. 4.14.4 The format of the REL message is shown in Table 33. Table 33
Message Type: Release Parameter Message type Cause indicators Redirection information (national use) Redirection number (national use) (Note) Access transport Signalling point code (national use) User-to-user information Automatic congestion level Network specific facility (national use) Access delivery information Parameter compatibility information User-to-user indicators Display information Remote operations (national use) End of optional parameters Reference (subclause) 2.1 3.12 3.45 3.46 3.3 3.50 3.61 3.4 3.36 3.2 3.41 3.60 3.77 3.48 3.20 Type F V O O O O O O O O O O O O O Length (octets) 1 3-? 3-4 5-12 3-? 4 3-131 3 4-? 3 4-? 3 3-? 8-? 1
NOTE Peer-to-peer interworking with an earlier version of ISUP may result in format errors and lead to the release of the call.
4.15
Release Complete (RLC)
4.15.1 This message is always sent to acknowledge receipt of a Release message (REL) and advise that release action is now complete. 4.15.2 The RLC message may be sent in either the forward or backward direction depending on the origin of the REL message. 4.15.3 The format of the RLC message is shown in Table 34.
C-76
Table 34
Message Type: Release complete Parameter Message type Cause indicators End of optional parameters Reference (subclause) 2.1 3.12 3.20 Type F O O Length (octets) 1 5-6 1
4.16
Subsequent Address Message (SAM)
This section has not been reproduced as this message is not implemented. 4.17 User-to-User Information (USR)
This section has not been reproduced as this message is not implemented. 4.18 Delayed Release (DRS)
This message was included in ITU-T Recommendation Q.763 (1988) and was removed in the 1997 version. It is used by Telecom but not implemented by Telecom at the POI. 4.19 Forward Transfer (FOT)
This section has not been reproduced as this message is not implemented. 4.20 Suspend (SUS)
4.20.1 This message is used to indicate a temporary cessation of communication without releasing the call. It can only be accepted during the connective phase of a call. 4.20.2 The SUS message will be sent in response to a suspend indication from the calling or called ISDN access. 4.20.3 On the receipt of a SUS message the exchange will pass a SUS message to the preceding exchange and start a 3 minute timer. At the expiry of the time out period a Release message (cause value = 111) will be generated to release the connection. 4.20.4 The SUS message will not suspend charging in Telecom's network. 4.20.5 If the party initiating the suspend condition re-answers prior to the 3 minute timer expiry a Resume message (ref. 4.21) will be sent back to stop the timers, ensuring the connection is not released. 4.20.6 The format of the SUS message is shown in Table 38. 4.21 Resume (RES)
4.21.1 This message is used to indicate that the connection which has been temporarily disconnected by a Suspend message (ref. 4.20) should now be reconnected. 4.21.2 In the Telecom network the RES message may follow a DRS message (4.18), however, this will not apply to calls to or from another network.
C-77
4.21.3 The receipt of a RES message following a SUS will ensure that the 3 minute timer is stopped to enable the connection to remain held. 4.21.4 The format of the RES message is shown in Table 38. Table 38
Message Type: Resume, Suspend Parameter Message type Suspend/resume indicators Call reference (national use) End of optional parameters Reference (subclause) 2.1 3.52 3.8 3.20 Type F F O O Length (octets) 1 1 7 1
NOTE Parameter compatibility information parameter may be received in the future version.
4.22
Blocking (BLO), Blocking Acknowledgement (BLA), Continuity Check Request (CCR), Loop Back Acknowledge (LPA), Overload (OLM), Reset Circuit (RSC), Unblocking (UBL), Unblocking Acknowledgement (UBA), Unequipped CIC (UCIC)
4.22.1 These messages are all used for maintenance purposes associated with the inter-exchange traffic circuits under the control of ISUP. They all have the same format, as shown in Table 39. 4.22.2 BLO is sent to a neighbouring exchange whenever it is necessary to block a single outgoing circuit from the distant end (e.g. following a maintenance command input). Multiple BLO messages are used to block a group of circuits for maintenance purposes where the circuit group blocking (CGB) message is not used (see 4.24). 4.22.3 BLA is sent in response to a BLO to confirm that the circuit has been busied as requested. 4.22.4 CCR is not used by Telecom. 4.22.5 LPA is used with continuity checking which is not done by Telecom. If it is received from another network the Telecom POI exchange will respond with a Confusion message (CFN) (ref. 4.7). 4.22.6 OLM is sent in response to an IAM by an exchange with call processor occupancy exceeding a specified maximum value; ref Q.764 2.9.9, Temporary Trunk Block Procedure. The preceding exchange (receiving the OLM) will release or reroute the call but will hold the interexchange traffic circuit to the overloaded exchange busy for a period of 2 minutes before allowing it to be reused. This will reduce traffic incoming to the overloaded exchange. 4.22.7 RSC is used to reset a circuit to the idle state in the case where memory associated with a circuit becomes mutilated, including after processor restarts. RSC ensures that both ends revert immediately to the idle state.
C-78
As soon as No.7 link alignment is completed after processor restarts in Telecom's POI exchange, RSC messages are sent (either for all ISUP circuits or only for circuits in the pre-answer state, depending on the level of restart). Circuits are returned to the idle condition on receipt of Release Complete message (RLC) which is sent in response to RSC. The exchange which underwent the restart cannot select an ISUP circuit until the reset procedure is complete (approximately 16 circuits can be reset per second). The remote exchange may use a circuit and send an IAM before it is reset. In this case the IAM is accepted and the call proceeds, whereas if the IAM collides with RSC, IAM is rejected and the RSC is acknowledged by RLC. 4.22.8 UBL is used to release a circuit that has previously been blocked by a BLO message. 4.22.9 UBA is sent in response to a UBL message to confirm that the circuit has been released as requested. 4.22.10 UCIC is sent in response to any message received which has a CIC that is not recognised by the receiving exchange. Receipt of UCIC by a Telecom POI exchange causes the inter-exchange traffic circuit with the specified CIC to be taken out of service, and a maintenance message to be output. Table 39
Message Type: Blocking Blocking acknowledgement Continuity check request Loop back acknowledgement, (national use) Overload, (national use) Reset circuit Unblocking Unblocking acknowledgement Unequipped circuit identification code, (national use) Parameter Message type Reference (subclause) 2.1 Type F Length (octets) 1
4.23
Call Modification Completed (CMC) Call Modification Request (CMR) Call Modification Reject (CMR)
These messages were included in ITU-T Recommendation Q.763 (1988) and were removed in the 1997 version. They are listed here to maintain section numbering consistent with previous versions of PTC331. They are not implemented by Telecom. 4.24 Circuit Group Blocking (CGB), Circuit Group Blocking Acknowledgement (CGBA), Circuit Group Unblocking (CGU), Circuit Group Unblocking Acknowledgement (CGUA)
4.24.1 These messages are all used for management purposes associated with groups of interexchange traffic circuits under the control of ISUP. 4.24.2 They are used to block and idle specific groups of circuits from the distant end of the circuit, e.g., in the case of an inter-exchange transmission system failure it may be necessary to block up to 30 circuits. The actual circuits to be blocked/unblocked are identified in the Range and
C-79
Status parameter and the reason for blocking/unblocking is indicated in the Circuit Group Supervision Message Type Indicator parameter. 4.24.3 The CGB message is used to request the blocking of a number of outgoing circuits due to a transmission failure or a route block maintenance command at the incoming end. 4.24.4 The CGBA message is sent in response to a CGB message to confirm that the circuits have been blocked as requested. 4.24.5 The CGU message is used to request the release of circuits previously blocked by a CGB message. 4.24.6 The CGUA message is sent in response to a CGU message to confirm that the circuits have been released as requested. 4.24.7 Although all Telecom POI exchanges with ISUP signalling capabilities will normally send, receive and respond to this group of messages, in some circumstances blocking of a group of interconnect circuits initiated by maintenance action at the Telecom POI exchange will be done by sending multiple BLO messages (see 4.22) controlling individual circuits to the other network. 4.24.8 Use of Circuit Group Blocking messages at the POIN exchange interface is Telecoms preference. If the interconnected network cannot support Circuit Group Blocking messages Telecom may be able to configure the interface to send only individual Circuit Blocking messages. 4.24.9 All these messages have the same format as shown in Table 40. Table 40
Message Type: Circuit group blocking Circuit group blocking acknowledgement Circuit group unblocking Circuit group unblocking acknowledgement Parameter Message type Circuit group supervision message type Range and status Reference (subclause) 2.1 3.13 3.43 Type F F V Length (octets) 1 1 3-34
4.25
Circuit Group Reset (GRS)
4.25.1 This message, in combination with the Circuit Group Reset Acknowledgement (GRA) message (refer 4.6 in this document) is used to reset circuits to the idle state following exchange software initialisation at one end of the inter exchange circuits. 4.25.2 The GRS message is sent when memory associated with a group of inter-exchange traffic circuits is mutilated or following a processor restart to reset the circuits at the adjacent exchange to idle. 4.25.3 If the GRS message requests the resetting of a circuit made busy by a local maintenance command the circuit will not be reset and the GRA will indicate in the status field that the circuit is still busy.
C-80
4.25.4 Use of GRS/GRA on the POI interface is Telecoms preference. If the interconnected network cannot support GRS/GRA Telecom may be able to configure the interface to send multiple RSC messages instead of GRS by special arrangement. 4.25.5 The format of the GRS message is shown in Table 41. 4.26 Circuit Group Query (CQM)
This section has not been reproduced as this message is not implemented. 4.27 Facility Accepted (FAA) Facility Request (FAR)
This section has not been reproduced as these messages are not implemented. 4.28 Pass Along (PAM)
This section has not been reproduced as this message is not implemented. 4.29 User part test (UPT), User part available (UPA)
This section has not been reproduced as this message is not implemented. 4.30 Facility (FAC)
This section has not been reproduced as this message is not implemented. 4.31 Network resource management (NRM)
This section has not been reproduced as this message is not implemented. 4.32 Identification request (IDR)
This section has not been reproduced as this message is not implemented. 4.33 Identification response (IDS)
This section has not been reproduced as this message is not implemented. 4.34 Segmentation (SGM)
This section has not been reproduced as this message is not implemented. 4.35 Loop prevention (LOP)
C-81
ANNEX A TABLES FOR HANDLING OF UNRECOGNIZED PARAMETER VALUES Reference: see 2.9.5.3/Q.764. Type A exchanges Unrecognized parameter values should be handled as indicated below in Type A exchanges (Type A exchanges as described in 2.9.5.2/Q.764). See also item iii) of 2.9.5.3/Q.764. Required actions: Default Ignore No default Handle as if the default value was received. The value is "don't care"; the received value may be passed on unchanged or reset to zero. Pass to call control.
Table A.1 shows the reaction of a Type A exchange. Table A.1 shows the normal actions unless specific procedural text in Recommendations Q.764 and Q.73x-Series states otherwise. Table A.1 (sheet 1 of 4) Type A exchanges
Reference (subclause) 3.4 3.5 Title Automatic congestion level Backward call indicators Bits BA: Charge ind. Bits DC: Called party status ind. Bits FE: Called party category ind. Bits HG: End-to-end method ind. Bit J: End-to-end information ind. (national use) Bit L: Holding ind. (national use) Bits PO: SCCP method ind. Default: 10 "charge" Default: 00 "no indication" Default: 00 "no indication" Default: 00 "no end-to-end method available" Default: 0 "no end-to-end info available" Default: 0 "holding not requested" Default: 00 "no indication" Discard parameter Action
C-82
Table A.1 (sheet 2 of 4) Type A exchanges

Reference (subclause) 3.9 Title Called party number Nature of address ind. Numbering plan ind. Spare Address signals Filler 3.10 Calling party number Nature of address ind. Number incomplete ind. Numbering plan ind. Presentation restricted ind. Screening ind. Address signals Filler 3.11 3.12 Calling party's category Cause indicators Coding standard Spare Location Cause value 3.13 Circuit group supervision message type indicator Bits BA: Type ind. Bits H-C: Reserved 3.14 Circuit state indicators Maintenance blocking state Spare 3.16 Connected number Nature of address ind. Spare Numbering plan ind. Presentation restricted ind. Screening ind. Address signals Filler 3.18 Continuity indicators Bits H-B: Reserved Ignore Discard parameter Ignore Discard parameter Default: 01 "presentation restricted" Discard parameter No Default Default: 0000 Discard message Ignore Discard message and send confusion with cause 110 Ignore Default: 00 "ITU-T" Ignore International: Default "international network." National: Default Beyond an Interwork. Point" Default: "Unspecified within class xxx" Discard parameter Discard parameter Discard parameter Default: 01 "presentation restricted" Discard parameter No default Default: 0000 Default: 0000 1010 "ordinary subscriber" Send release with cause 28 Send release with cause 28 Ignore Send release with cause 28 (Note) Default: 0000 Action
C-83

Reference (subclause) 3.21 3.22 3.23 Title Event information Bits G-A: Event ind. Facility indicators Forward call indicators Bits CB: End-to-end method ind. Bit E: End-to-end inform ind. (national use) Bits HG: ISUP preference ind. Bits KJ: SCCP method indicator Bit L: Spare Bits P-M: Reserved (national use) 3.28 Information indicators (national use) Bits BA: CgPA response ind. Bit C: Holding ind. Bit D: MCID response ind. Bit E: Spare Bit F: CgPC response ind. Bit G: Charge inform. resp. ind. Bit H: Solicited inf. ind. Bits P-I: Reserved 3.29 3.35 Information request ind. (national use) Bits P-M, L-F, C: Spare/Reserved Nature of connection ind. Bits BA: Satellite ind. Bits DC: Continuity ind. Bits H-F: Reserved 3.37 3.38 Optional backward call indicators Bits E-H: Reserved for national use Optional forward call indicators Bits BA: Closed user group call ind. Spare Bits G-D 3.39 Original called number Nature of address ind. Numbering plan ind. Address present. restr. ind. Address signals Filler spare Discard parameter Discard parameter Default: "Presentation restricted" No default Default: 0000 Ignore Default: 00 "non-CUG call" Ignore Ignore Default: 10 "two satellites in the connection" See Type B exchange Ignore Ignore Default: "CgPA not included" Default: "Hold not provided" Default: "MCID not provided" Ignore Default: "CgPC not included" Default: "Charge inform. not included" Default: "Solicited" Ignore Default: 00 "no end-to-end method available" Default: 0 "no end-to-end info available" Send release with cause 111 Default: 00 "no indication" Ignore Ignore Discard message Discard message Action
C-84

Reference (subclause) 3.43 3.44 Range and status Redirecting number Nature of address ind. Numbering plan ind. Presentation restricted ind. Address signals Filler 3.45 Redirection information Bits C-A: Redirecting ind. Bits H-E: Original redirection reason Bits K-I: Redirection counter Bits P-N: Redirecting reason Bits L, D: Spare/Reserved 3.46 Redirection number Nature of address indicator Numbering plan indicator Address signals Filler 3.51 Subsequent number Bits 1-7: Spare Address signal Filler 3.52 3.53 Suspend/resume indicators Bits H-B: Reserved Transit network selection Type of network identification Network identification plan 3.54 3.57 3.60 Transmission medium requirement User service information User-to-user indicators Bits CB: Service 1 Bits ED: Service 2 Bits GF: Service 3 NOTE Evaluated as far as needed for routing. Default: 00 "no information" Default: 00 "no information" Default: 00 "no information" Release with cause 91 Release with cause 91 Send release with cause 65 No default Ignore Ignore Send release with cause 28 (Note) Default: 0000 discard parameter discard parameter no default default: 0000 Default: "Call diversion, all redirection information presentation restricted" Default: "unknown (not available)" Default: "101" Default: "unknown/not available" Ignore Discard parameter Discard parameter Default: 01 "presentation restricted" No Default Default: 0000 Title Action See Rec. 2.9.3/Q.764, 2.8.2/Q.764 and 2.8.3/Q.764
C-85
Type B exchanges Table A.2 shows the reaction of a Type B exchange. The following definitions are used: Default Ignore Handle as if the default value was received; the default value is sent. The value is "don't care", the received value may be passed on unchanged or reset to zero. Value received passed on unchanged.
No default
Table A.2 shows the normal actions unless specific procedural text in Recommendations Q.764 and Q.73x-Series state otherwise. Table A.2 (sheet 1 of 4) Type B exchanges
Reference (subclause) 3.4 3.5 Title Automatic congestion level Backward call indicator Bits BA: Charge ind. Bits DC: Called party status ind. Bits FE: Called party category ind. Bits HG: End-to-end method ind. Bit J: End-to-end information ind. (national use) Bit L: Holding ind. (national use) Bits PO: SCCP method ind. 3.9 Called party number Nature of address ind. Numbering plan ind. Spare Address signals Filler 3.10 Calling party number Nature of address ind. Number incomplete ind. Numbering plan ind. Presentation restric. ind. Screening ind. Address signals Filler 3.11 Calling party's category No default No default No default No default No default No default Ignore No default Send release with cause 28 Send release with cause 28 Ignore Send release with cause 28 (Note) Default: 0000 No default No default No default No default No default Ignore (international transit) No default (national transit) No default Discard parameter Action
PTC 331:2001 Issue 2 Reference (subclause) 3.12 Cause indicators Coding standard Spare Location Cause value 3.13 Title
C-86
Table A.2 (sheet 2 of 4) Type B exchanges

Action
No default Ignore No default No default
Circuit group supervision message type indicator Bits BA: Type ind. Bits H-C: Reserved Discard message and send confusion with cause 110 Ignore Discard message Ignore No default Ignore No default No default No default No default Ignore Ignore No default Discard message No default No default Send release with cause 111 No default Ignore Ignore
3.14
Circuit state indicators Maintenance blocking state Spare
3.16
Connected number Nature of address ind. Spare Numbering plan ind. Presentation restric. ind. Screening indicator Address signals Filler
3.18 3.21 3.22 3.23
Continuity indicators Bits H-B: Spare Event information Bits G-A: Event ind. Facility indicators Forward call indicators Bits CB: End-to-end method ind. Bit E: End-to-end information ind. (national use) Bits HG: ISUP preference ind. Bits KJ: SCCP method ind. Bit L: Spare Bits P-M: Spare (national use)
C-87
PTC 331:2001 Issue 2 Action

Reference (subclause) 3.28 Title Information indicators (national use) Bits BA: Calling party address resp. ind. Bit C: Hold provided ind. Bit F: Calling party's category resp. ind. Bit G: Charge inform. resp. ind. Bit H: Solicited inform. ind. Bits L-I, E, D: Spare 3.29 3.35 Inform. request indicators (national use) Bits P-M, L-F, C: Spare/reserved Nature of connection indicators Bits BA: Satellite ind. Bits DC: Continuity ind. Bits H-F: Spare 3.37 3.38 Optional backward call indicators Bits H-E: Reserved (national use) Optional forward call indicators Bits BA: Closed user group call ind. Bits O-G: Spare 3.39 Original called number Nature of address indicator Numbering plan indicator Presentation restric. indicator Address signals Filler Spare 3.43 3.44 Range and status Redirecting number Nature of address ind. Numbering plan ind. Presentation restricted ind. Address signals Filler No default No default No default No default Ignore No default No default No default No default Ignore Ignore See 2.9.3/Q.764 and 2.8.2/Q.764 No default Ignore Ignore Default: 10 "two satellites in the connection" Default: 00 "continuity check not required" unless required on the outgoing circuit Ignore Ignore No default No default No default No default Default: 0 "solicited" Ignore
PTC 331:2001 Issue 2 Reference (subclause) 3.45 Title Redirection information Bits C-A: Redirecting indicator
C-88

Action
No default No default No default No default Ignore No default No default No default Ignore Ignore Send release with cause 28 (Note) Default: 0000 Ignore Release with cause 91 Release with cause 91 Send release with cause 65 No default
Bits H-E: Original redirection reason Bits K-I: Redirection counter Bits P-N: Redirecting reason Bits L, D: Spare 3.46 Redirection number Nature of address indicator Numbering plan indicator Address signals Filler 3.51 Subsequent number Bits 1-7: Spare Address signal Filler 3.52 3.53 Suspend/resume indicators Bits H-B: Spare Transit network selection Type of network identification Network identification plan 3.54 3.57 3.60 Transmission medium requirement User service information User-to-user indicators Bit A: Type Bits CB: Service 1 Bits ED: Service 2 Bits GF: Service 3 NOTE Evaluated as far as needed for routing.
Default: 00 "no information" Default: 00 "no information" Default: 00 "no information"
ANNEX B GENERAL DESCRIPTION OF COMPONENT ENCODING RULES This annex is not reproduced as the Remote operations parameter is not implemented.
C-89
APPENDIX 1 CIRCUIT IDENTIFICATION CODE (CIC) NUMBERING
Relationship between ISUP Circuit Identification Code (CIC) and the channel-timeslot number in the inter-exchange transmission system.
Sys 1 Channel 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Channel 6 Channel 7 Channel 8 Channel 9 Channel 10 Channel 11 Channel 12 Channel 13 Channel 14 Channel 15 Channel 16 Channel 17 Channel 18 Channel 19 Channel 20 Channel 21 Channel 22 Channel 23 Channel 24 Channel 25 Channel 26 Channel 27 Channel 28 Channel 29 Channel 30 Channel 31 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Sys 2 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Sys 3 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 Sys 4 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 Sys 5 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 Sys 6 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 Sys 7 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 Sys 8 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 Sys 9 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 Sys 10 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 Sys 11 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 Sys 12 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 Sys 13 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 Sys 14 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 Sys 15 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479
Sys 16 Channel 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Channel 6 Channel 7 Channel 8 Channel 9 Channel 10 Channel 11 Channel 12 Channel 13 Channel 14 Channel 15 Channel 16 Channel 17 Channel 18 Channel 19 Channel 20 Channel 21 Channel 22 Channel 23 Channel 24 Channel 25 Channel 26 Channel 27 Channel 28 Channel 29 Channel 30 Channel 31 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511
Sys 17 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543
Sys 18 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575
Sys 19 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607
Sys 20 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639
Sys 21 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671
Sys 22 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703
Sys 23 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735
Sys 24 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767
Sys 25 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799
Sys 26 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831
Sys 27 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863
Sys 28 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895
Sys 29 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927
Sys 30 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959
C-90
Sys 47 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503
Sys 48 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535
Sys 49 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567
Sys 50 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599
Sys 51 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631
Sys 52 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663
Sys 53 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695
Sys 54 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727
Sys 55 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759
Sys 56 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791
Sys 57 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823
Sys 58 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855
Sys 59 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887
Sys 60 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919
C-91
Sys 77 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463
Sys 78 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495
Sys 79 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527
Sys 80 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559
Sys 81 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591
Sys 82 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623
Sys 83 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655
Sys 84 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687
Sys 85 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719
Sys 86 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751
Sys 87 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783
Sys 88 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815
Sys 89 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847
Sys 90 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879
C-92
Sys 91 Channel 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Channel 6 Channel 7 Channel 8 Channel 9 Channel 10 Channel 11 Channel 12 Channel 13 Channel 14 Channel 15 Channel 16 Channel 17 Channel 18 Channel 19 Channel 20 Channel 21 Channel 22 Channel 23 Channel 24 Channel 25 Channel 26 Channel 27 Channel 28 Channel 29 Channel 30 Channel 31 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 Sys 92 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 Sys 93 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 Sys 94 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 Sys 95 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 Sys 96 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 Sys 97 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 Sys 98 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 Sys 99 Sys 100 Sys 101 Sys 102 Sys 103 Sys 104 Sys 105 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359
Sys 106 Sys 107 Sys 108 Sys 109 Sys 110 Sys 111 Sys 112 Sys 113 Sys 114 Sys 115 Sys 116 Sys 117 Sys 118 Sys 119 Sys 120 Channel 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Channel 6 Channel 7 Channel 8 Channel 9 Channel 10 Channel 11 Channel 12 Channel 13 Channel 14 Channel 15 Channel 16 Channel 17 Channel 18 Channel 19 Channel 20 Channel 21 Channel 22 Channel 23 Channel 24 Channel 25 Channel 26 Channel 27 Channel 28 Channel 29 Channel 30 Channel 31 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839
C-93
Sys 121 Sys 122 Sys 123 Sys 124 Sys 125 Sys 126 Sys 127 Sys 128 Sys 129 Sys 130 Sys 131 Sys 132 Sys 133 Sys 134 Sys 135 Channel 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Channel 6 Channel 7 Channel 8 Channel 9 Channel 10 Channel 11 Channel 12 Channel 13 Channel 14 Channel 15 Channel 16 Channel 17 Channel 18 Channel 19 Channel 20 Channel 21 Channel 22 Channel 23 Channel 24 Channel 25 Channel 26 Channel 27 Channel 28 Channel 29 Channel 30 Channel 31 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319
C-94
APPENDIX 2 SIGNALLING INTERWORKING BACKWARD CALL INDICATORS
Examples of Mapping of ISUP Backward Call Indicators parameter (ref. 3.4) and Optional Backward Call Indicators parameter (ref. 3.24) at the Telecom POI exchange, for calls to the Telecom network. Only bits used in the Telecom network are shown. Note that the examples here are not exhaustive. Other combinations of codings may apply, particularly in cases where calls transit the Telecom network to other national or international networks. Example 1. Call interworks with R2MFC or DP at or beyond the Telecom POI exchange
network boundary other network Telecom network ISUP POI direction of ACM carrying Backward Call Indicators direction of ACM carrying Backward Call Indicators TX direction of backward R2MFC signals R2MFC / DP
direction of call setup
Opt. Bwd Call Ind. (bit) HBA 0X1 0X1 0X1 0X1 0X1 0X1 M 0 0 0 0 0 0 Opt. Bwd. Call Ind. (bit) BA 10 10 10 10 10 00 HBA 1X1 0X1 0X1 0X1 1X1 0X1 M 0 0 0 0 0 0
If applicable
R2MFC Backward Signal (or DP route) BA 10 10 10 10 10 00 signal B-1 B-6 B-7 B-9 B-10 A6 or DP
Backward Call Indicator (bit)
K 0 0 0 0 0 0
I 1 1 1 1 1 1
FE 01 01 01 01 01 00
DC 01 01 01 01 01 00
K 0 0 0 0 0 0
I 1 1 1 1 1 1
FE 01 01 11 10 11 00
DC 01 01 01 01 01 00
X = 0 or 1
X = 0 or 1
C-95
Example 2. Call terminates in the Telecom network without interworking with R2MFC or DP at or beyond the Telecom POI exchange
network boundary other network Telecom network ISUP POI direction of ACM carrying Backward Call Indicators direction of ACM carrying Backward Call Indicators LX subscriber terminating exchange
direction of call setup
Opt. Bwd Call Ind. (bit) HBA M Opt. Bwd. Call Ind. (bit) BA HBA M
If applicable
FE
DC
FE
DC
BA
Terminating Line
0XX
01
00
10
XXX
X1
00
10
ISDN
0XX
X1
00
10
XXX
X1
00
10
PSTN (DDI)
0X1 0X1 X = 0 or 1
0 0
1 1
0 0
01 01
01 01
10 10
XX1 XX1 X = 0 or 1
0 0
1 1
0 0
01 1X
01 01
10 10
PSTN (non-DDI)
C-96
APPENDIX 3 RECOMMENDATION Q.764 SIGNALLING PROCEDURES
This appendix details only the exceptions and clarifications to the Common Channel Signalling System No.7 specifications adopted for Telecom network based on ITU-T Recommendation Q.764 (09/97) as applicable in the Telecom network, including the POI exchange, for purposes of interconnecting to other networks. Where no reference is given the procedures specified in Q.764 apply.
C-97 COMMENT ON REQUIREMENTS OF NEW NETWORK NODE NOTE: The standard ITU procedures as described in Q.764 apply to all paragraphs not listed in this table All references to actions specific to the international exchange (eg. 2.1.10 Forward transfer message) are not applicable to POI exchanges within the Telecom national network Normally the standard option of completing the transmission path in the forward direction for all call types at OLE only on receipt of ANM applies. In addition, Telecom will apply the specified alternative option of completing the transmission path in the forward direction for selected TMR=speech & 3.1kHz audio calls at OLE when sending the IAM (for calls that require pre-answer DTMF interworking eg. for PIN entry). NOTE: May later be replaced by UID procedures specified in Q.1600. 2.1.2 Not applicable as Telecom NZ uses only en bloc operation for ISUP
ISUP BASIC CALL PROCEDURE throughout
Reference (Q.764 09/97)
International Exchange
Successful call setup
2.1.1.1 d)
Forward address signalling en bloc operation
Actions at originating exchange
Forward address signalling overlap operation 2.1.4.9 Access delivery indication is not supported by Telecom NZ
ACM or CON message 2.1.6 2.1.8 2.1.12 2.1.13 Information messages are not supported by Telecom NZ Continuity checking is not performed within the Telecom NZ national network Segmentation is not used in the Telecom NZ network Although supported in Telecom NZ national network exchanges N x 64kbit/s connection types are not currently used by Telecom NZ
Access Delivery Indication
INF messages
Continuity check
Simple segmentation
N x 64kbit/s connection type
PTC 331:2001 Issue 2 COMMENT ON REQUIREMENTS OF NEW NETWORK NODE NOTE: The standard ITU procedures as described in Q.764 apply to all paragraphs not listed in this table Standard. Telecoms network applies special handling for REL (CV34, 42) Note that symmetrical release procedures apply both to ISDN and PSTN originated and terminated calls (ie. on-hook by a called PSTN party causes REL to be sent) SUS (network) not supported in the Telecom network. Receipt of on-hook indication from a normal analogue (PSTN) called party at the destination node causes REL message (not SUS message) to be sent. Receipt of an off-hook indication (after on-hook) from a normal analogue (PSTN) called party at the destination node causes sending of dial tone (to enable a new call) and not RES message. Fallback is not used is not used in the Telecom NZ network Propagation delay determination is not used in the Telecom NZ network Echo control signalling procedures are not currently used in the Telecom NZ national network. Any echo control equipment is fixed for given circuits; its presence is not signalled via ISUP, nor is its activation controlled by ISUP Telecom NZ network does not support this method of remote unblocking (also ref Q.784 1.3.2.4 Circuit group query is not used in the Telecom NZ network Both Selection Methods 1 and 2 are available, selectable by route data. Telecom prefers Method 2 on POI interfaces. TTB is the primary ISUP flow control mechanism used in the Telecom network and on the POI interface. Reference (Q.764 09/97) 2.2.3 2.3 2.4.1 a)
C-98
ISUP BASIC CALL PROCEDURE
Unsuccessful call setup
Actions at controlling exchange
Normal call release
Suspend
Resume
2.4.2
Fallback 2.6 2.7
2.5
Propagation delay determination
Echo control signalling procedures
Network Features 2.8.3 2.9.1 2.9.9
2.8.2.3 xiv)
Abnormal blocking
Network Features
Circuit group query
Abnormal conditions
Dual seizure
Temporary Trunk Block (TTB) (national use)
C-99 COMMENT ON REQUIREMENTS OF NEW NETWORK NODE NOTE: The standard ITU procedures as described in Q.764 apply to all paragraphs not listed in this table ACC is the secondary ISUP flow control mechanism used in the Telecom network and on the POI interface with trigger points generally set at higher levels of congestion than for initiation of TTB (2.9.9). Inter-exchange calls in progress are not released by a signalling outage User part test and user part available messages are not supported 2.14 2.15 2.16 2.17 2.18 Not used by Telecom Telecom NZ network currently operates a proprietary version of this facility (using FCI bit M=1 to mark a collect call). In future the ITU facility may be introduced. Inter-exchange calls in progress are not released by receipt of MTP pause Standard as segmentation is not supported in the Telecom NZ network The exchange of TAR indications in ISUP is not used in the Telecom NZ network
ISUP BASIC CALL PROCEDURE 2.11
Reference (Q.764 09/97)
Automatic congestion control (ACC)
ISUP availability control
2.13.2
Procedures
MTP Pause/Resume
Overlength messages
Temporary alternative routing (TAR)
Hop counter procedure
Collect call request (CCR)
C-100
APPENDIX 4 SAMPLE MESSAGE SEQUENCES
The sample message sequences provided in issue 1 of this document have not been included. A paper version can be supplied on request.
C-101
APPENDIX 5 SUPPORT OF SUPPLEMENTARY SERVICES This appendix identifies the supplementary services, as listed in ITU-T Recommendation Q.730, supported at the POI. Support at the POI for interconnection Yes (no ISUP impact) N/A (no ISUP impact) Yes Yes No No No Yes N/A See section on Call Forwarding Procedures below See section on Call Forwarding Procedures below See section on Call Forwarding Procedures below Yes N/A (no ISUP impact) Yes, but call handled as a new call using basic call control N/A Yes but notification to calling user not sent Yes No Yes
ITU-T
Description
Number identification supplementary services Q.731.1 Direct-Dialling-In (DDI) Q.731.2 Q.731.3 Q.731.4 Q.731.5 Q.731.6 Q.731.7 Q.731.8 Q.732.1 Q.732.2 Q.732.3 Q.732.4 Q.732.5 Q.732.6 Q.732.7 Q.732.8 Q.733.1 Q.733.2 Q.733.3 Q.733.4 Reserved for Multiple Subscriber Number (MSN) Calling Line Identification Presentation (CLIP) Calling Line Identification Restriction (CLIR) Connected Line Identification Presentation (COLP) Connected Line Identification Restriction (COLR) Malicious Call Identification (MCID) Sub-addressing (SUB) Reserved for Call Transfer (CT) Call Forwarding Busy (CFB) Call Forwarding No Reply (CFNR) Call Forwarding Unconditional (CFU) Call Deflection (CD) Reserved for Line Hunting (LH) Explicit Call Transfer (ECT) Reserved for Single Step Call Transfer (SCT) Call Waiting (CW) Call Hold (HOLD) Completion of Calls to Busy Subscribers (CCBS) Terminal Portability (TP)
Call offering supplementary services
Call completion supplementary services
C-102
ITU-T
Description
Support at the POI for interconnection Yes, but call handled as a new call using basic call control Yes, but call handled as a new call using basic call control No N/A No N/A N/A No SCCP not supported at the POI Interface N/A No Service 1 implicit only
Multiparty supplementary services Q.734.1 Q.734.2 Conference Calling (CONF) Three-Party Service (3PTY)
Community of interest supplementary services Q.735.1 Q.735.2 Q.735.3 Q.735.4 Q.735.5 Q.735.6 Q.736.1 Q.736.2 Q.736.3 Q.737.1 Closed User Group (CUG) Reserved for Private Numbering Plan (PNP) Multi-Level Precedence and Preemption (MLPP) Reserved Reserved Global Virtual Network Service (GVNS) International Telecommunication Charge Card (ITCC) Reserved for Advice of Charge (AOC) Reverse Charge (REV) User-to-User Signalling (UUS)
Charging supplementary services
Additional information transfer supplementary service
C-103
Call Forwarding (CALL DIVERSION) Procedures Explanation of ISUP parameters associated with multi-hop Call Forwarding using ISUP all the way. Party A calls party B; B is diverted to C; C is diverted to D; D is diverted to E; E is diverted to F.
Originating Exchange A LX Hop 1 IAM ACM CPG1 B LX Hop 2 C LX Hop 3 D LX Hop 4 E LX Hop 5 F LX
Standard Procedure
CPG2
IAM ACM CPG2
CPG3
CPG3
IAM ACM CPG3
CPG4 RBT RBT
CPG4 RBT
CPG4 RBT
IAM ACM CPG4
IAM ACM RBT
RBT
Ringing 2
Relevant IAM parameters

Called Party Number Calling Party Number Calling Party Category Redirecting Number Original Called Number Redirection Information: - Redirecting Indicator Original Redir. Reason NOTE 5 Redirection Counter NOTE 3 Redirecting Reason B A A C A B B (NOTE1) B V W 1 (NOTE 6) W D A C C B V' W 2 W' W= or or or E A D D B V'' W 3 W'' F A E E B V''' W 4 W'''
V = call forwarded or call forwarded all redirection info presentation restricted or call forwarded redirection number presentation restricted NOTE5
unconditional user busy no reply unknown/not available
Relevant ACM parameter

Optional Backward Call Ind Z (CPG1) Y C Z' (CPG2) Y' D Z= Z'' (CPG3) Y" E Call forwarding may occur (only in the case that called party has call diversion on no reply service) Z''' (CPG4)
Relevant CPG parameters

Event Information Redirection Number Y = Call forwarded on busy or Call forwarded on No Reply or Call forwarded Unconditionally
C-104
Note 1: Redirecting number is included at the first forwarding, in accordance with the ITU-T 03/93 and subsequent procedures. Note 2: An alternative procedure which will occur for some forwarded calls will be for each forwarding exchange to return a CPG as the first backward message, and then for the final (nonforwarding) destination exchange to to send the ACM, to the preceeding exchange. The ACM will then be transited back to the originating exchange. This procedure is not included in the ITU-T 03/93 recommendations, however, it is still used in parts of the Telecom network and possibly some interconnected networks.
Originating Exchange A LX Hop 1 IAM CPG1 CPG2 CPG3 CPG4 ACM RBT RBT B LX Hop 2 C LX Hop 3 D LX Hop 4 E LX Hop 5 F LX
Alternative Procedure
IAM CPG2 CPG3 CPG4 ACM RBT
IAM CPG3 CPG4 ACM
IAM CPG4 ACM
IAM ACM
RBT
RBT
RBT
Ringing 2
Thus for some forwarded calls, the originating exchange may receive one or more CPG messages before an ACM. For multiple forwardings a mixture of the standard procedure and the alternative procedure may occur. The contents of parameters in the IAM will be the same as for the standard procedure. Note 3: When the counter reaches 5 and another diverting line is reached, a Telecom exchange will release the call with:cause value 17 (if diverting line has Call Forwarding on Busy) cause value 18 (if diverting line has Call Forwarding unconditional) cause value 19 (after ringing time out if diverting line has Call Forwarding on No Reply). Note 4: ITU-T 03/93 recommendations introduced a new ISUP parameter: redirection number restriction sent in the backward direction for use with call forwarding services. The Telecom network does not currently support this parameter. It therefore is not to be sent on the PTC331 interface. Note 5: ITU-T 03/93 and subsequent recommendations have marked these codings of the redirection information parameter as national use, however, they are still set within the Telecom network and possibly in interconnected networks and may therefore be sent on the PTC331 interface. Note 6: The 1988 recommendation option of not sending the counter with the first forwarding is not accepted by the Telecom network. The Redirection information parameter must always include the counter. -end of PTC331-

Telephone Network Interconnection Using. ITU-T No. 7 Signalling PART C ISUP Specification

Uploaded by

Copyright:

Available Formats

Telephone Network Interconnection Using. ITU-T No. 7 Signalling PART C ISUP Specification

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Telephone Network Interconnection Using. ITU-T No. 7 Signalling PART C ISUP Specification

Uploaded by

Copyright:

Available Formats

Specification PTC 331 Telephone Network Interconnection using ITU-T No.

7 Signalling PART C ISUP SPECIFICATION

Issue 2: March 2001

PTC 331:2001 Issue 2

(This page intentionally blank)

PTC 331:2001 Issue 2

CONTENTS Section Title Page C- .

Parameter formats and codes

ISDN user part parameter

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

ISDN user part messages and codes

PTC 331:2001 Issue 2

Annex A Annex B Appendix 1 Appendix 2 Appendix 3 Appendix 4 Appendix 5

Call Forwarding (CALL DIVERSION) Procedures

PTC 331:2001 Issue 2

The meaning of the different typefaces is illustrated below.

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

[5] [6] [7] [8] [9] [10]

This Recommendation uses the following abbreviations:

PTC 331:2001 Issue 2

Figure 1 ISDN user part message parts

Circuit identification code

The format of the Circuit Identification Code (CIC) is shown in Figure 2.

Figure 2 Circuit identification field

PTC 331:2001 Issue 2

Message type code

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

Reserved (used in 1988 version)

Reserved (used in B-ISUP)

PTC 331:2001 Issue 2

Mandatory fixed part

PTC 331:2001 Issue 2

Figure 3 General format overview

Coding of spare bits

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

ISDN user part parameter Parameter names

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

PTC 331:2001 Issue 2

Figure 5 Access transport parameter field

PTC 331:2001 Issue 2

Automatic congestion level

Figure 6 Automatic congestion level parameter field

PTC 331:2001 Issue 2

(ref. 4.2) (ref. 4.8)

It is also an optional parameter which may be included in the following messages:

Figure 7 Backward call indicators parameter field

PTC 331:2001 Issue 2

10 11 bits FE 00 01 10 11 bits HG 00 01 10 10 bit I 0 1

PTC 331:2001 Issue 2

bit K 0 1 bit L 0 1 bit M 0 1 bit N 0 1 bits PO 00 01 10 11

Call diversion information

PTC 331:2001 Issue 2

Called party number

Filler (if necessary)