SIST ETS 300 192 E1:2005
(Main)Private Telecommunication Network (PTN); Signalling protocol at the S-reference point; Circuit mode basic services
Private Telecommunication Network (PTN); Signalling protocol at the S-reference point; Circuit mode basic services
Stage 3 for basic call at S ref pt. See ENV41004 for definition of S ref pt. & 41005 for defn of stage 3.
Zasebno omrežje z integriranimi storitvami (PISN) - Signalizacijski protokol na referenčni točki S - Vodovne osnovne storitve
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 192 E1:2005
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL 3,61 6LJQDOL]DFLMVNLSURWRNROQD
UHIHUHQþQLWRþNL69RGRYQHRVQRYQHVWRULWYH
Private Telecommunication Network (PTN); Signalling protocol at the S-reference point;
Circuit mode basic services
Ta slovenski standard je istoveten z: ETS 300 192 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST ETS 300 192 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 192 E1:2005
---------------------- Page: 2 ----------------------
SIST ETS 300 192 E1:2005
EUROPEAN ETS 300 192
TELECOMMUNICATION December 1992
STANDARD
Source: ETSI TC-ECMA Reference: DE/ECMA-106
ICS: 33.080
PTN, SSIG-BC
Key words:
Private Telecommunications Network (PTN)
Signalling protocol at the S-reference point
Circuit mode basic services
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1992. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
SIST ETS 300 192 E1:2005
Page 2
ETS 300 192: 1992
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI
Editing and Committee Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST ETS 300 192 E1:2005
Page 3
ETS 300 192: 1992
Table of Contents
Foreword 7
1 Scope 9
2 Conformance 9
3 References 9
4 Definitions 9
4.1 Basic Call 9
4.2 Incoming Call 9
4.3 Outgoing Call 10
4.4 User and Network 10
5 Acronyms 10
6 General principles 10
6.1 Protocol model 10
6.2 Services provided to Call Control 11
6.3 Services required of the Data Link Layer 11
6.3.1 Acknowledged information transfer services 11
6.3.2 Unacknowledged information transfer services 12
6.4 Protocol Control states 12
6.4.1 States for circuit mode Call Control 12
6.4.2 States for Layer management 12
6.5 Message segmentation and reassembly functions 12
6.5.1 Null (0) 13
6.5.2 Receiving segmented message (1) 13
7 General procedures 13
7.1 Use of the services of Layer 2 13
7.1.1 Establishment of a Data Link connection 13
7.1.2 Transfer of data 14
7.2 Message segmentation procedures 14
7.3 Handling of protocol error conditions 14
7.3.1 Addition to requirements of subclause 5.8.6.1 of ETS 300 102-1 14
7.3.2 Addition to requirements of subclause 5.8.6.2 of ETS 300 102-1 15
7.3.3 Modification to subclause 5.8.7.1, second paragraph, of ETS 300 102-1 15
7.3.4 Replacement for items a, b and c of subclause 5.8.7.1 of ETS 300 102-1 15
7.3.5 Addition to requirements of subclause 5.8.7.2 of ETS 300 102-1 15
7.3.6 Modification to subclause 5.8.7.2, first paragraph, of ETS 300 102-1 15
7.3.7 Modification to subclause 5.8.7.2, second paragraph, of ETS 300 102-1 15
7.4 Handling of configuration errors 15
7.5 Status and status enquiry procedures 16
7.5.1 Modifications to subclause 5.8.10 of ETS 300 102-1 16
7.5.2 Modifications to subclause 5.8.11 of ETS 300 102-1 16
8 Procedures for circuit mode call control 16
8.1 Call establishment at the originating interface 16
8.1.1 Addition to subclause 5.1.1 of ETS 300 102-1 16
---------------------- Page: 5 ----------------------
SIST ETS 300 192 E1:2005
Page 4
ETS 300 192: 1992
8.1.2 Modification to the "ETSI Requirement" concerning en-bloc sending in subclause
5.1.1 of ETS 300 102-1 16
8.1.3 Modification to the "ETSI Requirement" concerning the tone option in subclause
5.1.3 of ETS 300 102-1 17
8.1.4 Clarification of subclause 5.1.5 of ETS 300 102-1 17
8.1.5 Modification to subclause 5.1.6 of ETS 300 102-1 17
8.1.6 Modification to the "ETSI Requirement" concerning the sending of the alerting
message in subclause 5.1.7 of ETS 300 102-1 17
8.1.7 Modification to the "ETSI Requirement" concerning the receipt of the alerting
message in subclause 5.1.7 of ETS 300 102-1 17
8.1.8 Addition to subclause 5.1.8 of ETS 300 102-1 17
8.1.9 Non-applicability of transit network selection 17
8.2 Call Establishment at the destination interface 18
8.2.1 Addition to subclause 5.2.1 of ETS 300 102-1 18
8.2.2 Change to case 4 of subclause 5.2.3.1 of ETS 300 102-1 18
8.2.3 Change to case b of subclause 5.2.3.2 of ETS 300 102-1 18
8.2.4 Non-applicability of overlap receiving procedure 18
8.2.5 Replacement of the first paragraph of 5.2.5.2 of ETS 300 102-1 18
8.2.6 Modification to the "ETSI Requirement" concerning progress description value No.
1 18
8.2.7 Addition to subclause 5.2.8 of ETS 300 102-1 18
8.3 Call clearing 18
8.3.1 Replacement of item b of subclause 5.3.2 of ETS 300 102-1 18
8.3.2 Non applicability of item c of subclause 5.3.2 of ETS 300 102-1 19
8.3.3 Modification to subclause 5.3.3 of ETS 300 102-1 19
8.3.4 Modification to subclause 5.3.4.1 of ETS 300 102-1 19
8.3.5 Modification to subclause 5.3.4.2 of ETS 300 102-1 19
8.4 In-band tones and announcements 19
8.5 Call collisions 19
8.6 Suspend and Resume procedures 19
8.7 TE side and PTN side SDL diagrams (informative) 19
9 Procedures for layer management 19
9.1 Restart procedures 19
10 List of system parameters 19
11 Functional definition and content of messages 20
11.1 Messages for general procedures 21
11.1.1 STATUS 21
11.1.2 STATUS EQUIRY 21
11.2 Messages for circuit mode Call Control 21
11.2.1 ALERTING 21
11.2.2 CALL PROCEEDING 21
11.2.3 CONNECT 21
11.2.4 CONNECT ACKNOWLEDGE 22
11.2.5 DISCONNECT 22
11.2.6 INFORMATION 22
11.2.7 PROGRESS 22
11.2.8 RELEASE 22
11.2.9 RELEASE COMPLETE 22
11.2.10 RESUME 22
---------------------- Page: 6 ----------------------
SIST ETS 300 192 E1:2005
Page 5
ETS 300 192: 1992
11.2.11 RESUME ACKNOWLEDGE 22
11.2.12 RESUME REJECT 22
11.2.13 SETUP 23
11.2.14 SETUP ACKNOWLEDGE 23
11.2.15 SUSPEND 23
11.2.16 SUSPEND ACKNOWLEDGE 23
11.2.17 SUSPEND REJECT 23
11.3 Messages for Layer Management 23
11.3.1 RESTART 23
11.3.2 RESTART ACKNOWLEDGE 23
12 General message format and coding of information elements 23
12.1 Overview 24
12.2 Protocol discriminator 24
12.3 Call reference 24
12.4 Message type 24
12.5 Other information elements (Codeset 0) 24
12.5.1 Coding rules 24
12.5.2 Extensions of codesets 25
12.5.3 Locking shift procedure 25
12.5.4 Non-locking shift procedure 26
12.5.5 Bearer capability 26
12.5.6 Call identity 26
12.5.7 Call state 26
12.5.8 Called party number 26
12.5.9 Called party subaddress 26
12.5.10 Calling party number 26
12.5.11 Calling party subaddress 27
12.5.12 Cause 27
12.5.13 Channel identification 27
12.5.14 Connected number 27
12.5.15 Connected subaddress 27
12.5.16 Date / time 28
12.5.17 Display 28
12.5.18 High layer compatibility (Layers 4 - 7) 28
12.5.19 Low layer compatibility (Layers 1 - 3) 28
12.5.20 Progress indicator 28
12.5.21 Restart indicator 28
12.5.22 Segmented message 28
12.5.23 Sending complete 29
12.6 Information elements of codeset 5 29
12.6.1 Party category 29
Annex A (informative): Use of progress indicators 30
Annex B (informative): Use of cause values 31
B.1 Definition of cause values 31
B.2 Use of causes for busy conditions 31
Annex C (informative): Examples of message sequences 32
---------------------- Page: 7 ----------------------
SIST ETS 300 192 E1:2005
Page 6
ETS 300 192: 1992
C.1 En-bloc sending 32
C.1.1 Successful call setup 32
C.1.2 Unsuccessful call setup 32
C.2 Overlap sending 33
C.2.1 Successful call setup 33
C.2.2 Unsuccessful call setup 33
C.3 Call clearing 34
Annex D (informative): Manufacturer specific information 35
Annex E (informative): Bibliography 36
Annex F (informative): Terminal interchangeability 37
History 38
---------------------- Page: 8 ----------------------
SIST ETS 300 192 E1:2005
Page 7
ETS 300 192: 1992
Foreword
This European Telecommunication Standard (ETS) has been produced by the European Computer Manufacturers
Association (ECMA) on behalf of its members and those of the European Telecommunications Standards Institute
(ETSI).
This ETS defines the signalling protocol for use at the S-reference point in support of basic circuit mode services. It is
intended to be supported by a suitable layer 2 protocol, e.g. ETS 300 169, in the D-channel of a basic access interface
or a primary rate access interface.
The protocol defined in this ETS is based upon that specified in ETS 300 102-1. ETS 300 102-1 is applicable to
interfaces to public ISDNs at the T reference point, or at coincident S and T reference points if there is no NT2
function. This ETS references many of the Clauses of ETS 300 102-1 to avoid reproducing large quantities of text.
Some of the options in ETS 300 102-1 are not applicable to interfaces at the S reference point, and therefore are
excluded by this standard. On the other hand, certain additions have been identified as being required at the S
reference point. However, the major part of the protocol is identical with that specified in ETS 300 102-1, enabling
TEs to be designed which are compatible with both PTNs and public ISDNs and can therefore be connected to either.
This ETS refers to ETS 300 102-2 for the description of the protocol in SDL form.
This ETS was produced by ECMA using the ECMA guidelines for the production of standards and using the ECMA
stylesheet. In order to avoid undue delays in the publication of this ETS it has been agreed that this ETS will not be
converted to the ETSI stylesheet.
---------------------- Page: 9 ----------------------
SIST ETS 300 192 E1:2005
Page 8
ETS 300 192: 1992
Blank page
---------------------- Page: 10 ----------------------
SIST ETS 300 192 E1:2005
Page 9
ETS 300 192: 1992
1 Scope
This standard defines the Layer 3 protocol for signalling for the support of circuit-mode bearer services (used
either on their own or in support of teleservices) at an interface at the S reference point between a Terminal
Equipment (TE) and a Private Telecommunication Network (PTN). The S reference point is defined in ENV
41004.
This standard is based upon ETS 300 102-1, which defines the equivalent protocol for the T and coincident T
and S reference points between a user and a public ISDN. Many of the Clauses of ETS 300 102-1 are
incorporated by reference. Any reference in the text of ETS 300 102-1 to Annex D of that document are not
applicable to this standard. Annex F contains information on terminal interchangeability between PTNs and
public ISDNs.
This standard is applicable to basic and primary rate accesses of PTNXs and to TEs that are intended for
connection to such accesses.
The conveyance of non-standardized (e.g. manufacturer-specific) information in messages is outside the scope
of this standard. Annex D discusses ways in which this can be achieved.
2 Conformance
In order to conform to this standard, a PTNX shall satisfy the PTN requirements and a TE shall satisfy the TE
requirements contained in Clauses 7, 8, 9, 10, 11 and 12 of this standard.
3 References
ETS-300 102-1 Integrated Services Digital Network (ISDN); User-network interface layer 3,
Specifications for basic call control (1990).
I-ETS 300 169 Private Telecommunication Network (PTN); Signalling at the S-reference
point, Data link layer protocol (1992).
ETS 300 171 Private Telecommunication Network (PTN); Specification, functional
models and information flows, Control aspects of circuit mode basic services
(1992).
ETS 300 189 Private Telecommunication Network (PTN); Addressing (1992).
CCITT Recommendation I.112 "Blue Book", 1988 - Vocabulary of Terms for ISDNs.
ENV 41004 Reference Configurations for Calls through Exchanges of Private
Telecommunication Networks.
ENV 41005 Method for the Specification of Basic and Supplementary Services of Private
Telecommunication Networks.
ENV 41007 Definition of Terms in Private Telecommunication Networks.
4 Definitions
For the purpose of this standard the terminology defined in ENV 41007 and CCITT Recommendation I.112
applies. If there is conflict, the definitions in ENV 41007 shall take precedence. In addition the following
definitions apply.
4.1 Basic Call
A single invocation of a basic service according to ETS 300 171.
4.2 Incoming Call
A call presented to the TE by the PTN.
---------------------- Page: 11 ----------------------
SIST ETS 300 192 E1:2005
Page 10
ETS 300 192: 1992
4.3 Outgoing Call
A call presented to the PTN by the TE.
4.4 User and Network
Throughout this standard, reference is made to Clauses in ETS 300 102-1. When applying a Clause in
ETS-300 102-1 to the TE-PTN interface, the term user shall be interpreted as TE, and the term network
shall be interpreted as PTN.
5 Acronyms
CLIP Calling Line Identification Presentation
COLP Connected Line Identification Presentation
ISDN Integrated Services Digital Network
MSI Manufacturer Specific Information
PTN Private Telecommunication Network
PTNX Private Telecommunication Network eXchange
SAP Service Access Point
TE Terminal Equipment
6 General principles
This standard specifies the signalling procedures for establishing, maintaining and clearing a basic circuit-
switched call at a PTN user access. These signalling procedures are defined in terms of messages exchanged
over a data link connection on the D-channel of a basic or primary rate interface structure. The result of
successful basic call establishment is a connection for the purpose of user information transfer. This
connection uses a B-channel of a basic or primary rate interface structure.
Throughout this standard, the term B-channel is used to indicate any channel other than the D-channel.
The basic call signalling procedures specified in this standard apply to circuit mode bearer services, used
either on their own or in support of teleservices.
In addition, this standard includes signalling procedures for layer management, including restart.
6.1 Protocol model
Figure 1 shows the relationship, within the Control Plane, between the layer 3 protocol at the S reference
point, the protocol entities in the TE and PTN, and the adjacent layers.
---------------------- Page: 12 ----------------------
SIST ETS 300 192 E1:2005
Page 11
ETS 300 192: 1992
TE PTN
CALL CALL
CONTROL CONTROL
LAYER 3
PROTOCOL PROTOCOL
CONTROL CONTROL
PROTOCOL
LAYER 2 SERVICE
ACCESS POINT
LAYER 2 LAYER 2
LAYER 1
LAYER 1
TE-PTN
INTERFACE
Figure 1 - Protocol model
The Protocol Control entity provides services to Call Control. Call Control corresponds to the functional
entities identified for the basic call at Stage 2 (see ETS 300 171), i.e., the Call Control functional entity
within the PTN (PTNX) and the Call Control Agent functional entity within the TE. Primitives exchanged
across the boundary between Call Control and Protocol Control correspond to the information flows
exchanged between the Call Control and Call Control Agent functional entities, as identified at Stage 2.
Protocol Control provides the mapping between these primitives and the messages transferred across the
TE-PTN interface.
In order to transfer messages, Protocol Control uses the services of the Data Link Layer, as available at the
Data Link Layer Service Access Point (SAP). The Data Link Layer in turn uses the services of the Physical
Layer.
6.2 Services provided to Call Control
Protocol Control provides services to Call Control whereby Call Control can send information flows to and
receive information flows from the peer Call Control. A primitive from Call Control to Protocol Control of
type "request" or "response" normally results in the associated information flow being presented to the peer
Call Control as a primitive of type "indication" or "confirmation" respectively.
PTN side primitives are as listed in subclause 5.3 of ETS 300 102-2. TE side primitives are as listed in
subclause 6.3 of ETS 300 102-2.
Note 1:
These primitive names differ from the information flow names specified at Stage 2 in ETS 300 171.
6.3 Services required of the Data Link Layer
Services provided by the Data Link Layer and the associated primitives are defined in I-ETS 300 169.
Protocol Control uses the following services:
6.3.1 Acknowledged information transfer services
- Data Transfer, using the DL-DATA-REQUEST/INDICATION primitives;
- Establishment of Multiple Frame Operation, using the DL-ESTABLISH-REQUEST/INDICATION/-
CONFIRM primitives;
---------------------- Page: 13 ----------------------
SIST ETS 300 192 E1:2005
Page 12
ETS 300 192: 1992
- Termination of Multiple Frame Operation, using the DL-RELEASE-REQUEST/INDICATION/-
CONFIRM primitives.
6.3.2 Unacknowledged information transfer services
- Data Transfer, using the DL-UNIT-DATA-REQUEST/INDICATION primitives.
6.4 Protocol Control states
Protocol Control procedures for calls and layer management are specified in terms of:
- messages which are transferred across the TE-PTN interface;
- the primitives to and from Call Control at the TE side and the PTN side of the TE-PTN interface;
- the information processing and actions that take place within Protocol Control at the TE side and the
PTN side of the TE-PTN interface; and
- the states that can exist within Protocol Control at the TE side and the PTN side of the TE-PTN
interface.
State machines are deemed to exist for each circuit mode call. A further state machine is deemed to exist
for layer management, covering restart procedures.
6.4.1 States for circuit mode Call Control
The call states defined in subclause 2.1.1 of ETS 300 102-1 for the user side of the user-network
interface apply also to the TE side of the TE-PTN interface.
Note 2:
If the TE does not support the optional suspend and resume procedures of subclause 8.6, states U15 and
U17 will never be entered.
The call states defined in subclause 2.1.2 of ETS 300 102-1 for the network side of the user-network
interface apply also to the PTN side of the TE-PTN interface.
Note 3:
If the PTN does not support the optional suspend and resume procedures of subclause 8.6, states N15
and N17 will never be entered.
6.4.2 States for Layer management
The states defined in subclause 2.4.1 of ETS 300 102-1 for use in association with the global call
reference at the user side of the user-network interface apply also to the TE side of the TE-PTN
interface.
The states defined in subclause 2.4.2 of ETS 300 102-1 for use in association with the global call
reference at the network side of the user-network interface apply also to the PTN side of the TE-PTN
interface.
6.5 Message segmentation and reassembly functions
Message segmentation and reassembly functions are employed where the size of a message exceeds the
maximum size of the Data Link Layer information field size. The architectural relationship of
segmentation and reassembly functions to other Protocol Control functions is shown in figure 2.
---------------------- Page: 14 ----------------------
SIST ETS 300 192 E1:2005
Page 13
ETS 300 192: 1992
CALL CONTROL
OTHER FUNCTIONS
PROTOCOL
SEGMENTATION
CONTROL
AND REASSEMBLY
FUNCTIONS
PROTOCOL
DISCRIMINATOR
FILTER
DATA LINK LAYER
Figure 2 - Logical architecture of Protocol Control showing segmentation and reassembly functions
Segmentation and reassembly, where provided, effectively constitutes a lower sub-layer of Protocol
Control. The only function of Protocol Control which lies below the segmentation and reassembly functions
is the filtering out of messages containing a protocol discriminator which is not in accordance with that
specified.
The primitives across the boundary between segmentation and reassembly functions and other functions are
the same as those between the Data Link Layer and Protocol Control. The segmentation functions act upon
DL-DATA-REQUEST primitives by converting, where necessary, a single primitive into two or more
primitives before passing to the Data Link Layer. The reassembly functions act upon DL-
DATA-INDICATION primitives from the Data Link Layer by converting, where necessary, two or more
primitives into a single primitive for passing up to the other functions of Protocol Control. Other primitives
to and from the Data Link Layer are not affected by the segmentation and reassembly functions.
Message segmentation and reassembly procedures are each specified in terms of a state machine. Message
segmentation uses a single state, Null (0). Message reassembly uses two states, as listed below.
6.5.1 Null (0)
No message is being reassembled.
6.5.2 Receiving segmented message (1)
One or more segments of a segmented message have been received and one or more further segments are
awaited.
7 General procedures
7.1 Use of the services of Layer 2
7.1.1 Establishment of a Data Link connection
Before the procedures for call control, layer management or any of the general procedures in subclauses
7.2 to 7.4 can be performed, a Data Link connection must be established between the PTN and the TE.
---------------------- Page: 15 ----------------------
SIST ETS 300 192 E1:2005
Page 14
ETS 300 192: 1992
The exception is the sending of a SETUP message by the PTN using the unacknowledged information
transfer service of the Data Link Layer.
If a Data Link connection has not already been established, Protocol Control can request establishment
by sending a DL-ESTABLISH-REQUEST primitive to the Data Link Layer. Receipt of a DL-
ESTABLISH-CONFIRMATION primitive or a DL-ESTABLISH-INDICATION primitive from the Data
Link Layer indicates that a Data Link connection has been established.
7.1.2 Transfer of data
If a multi-point configuration exists at an interface, or if the PTN does not know whether the
configuration is multi-point or point-to-point, a SETUP message sent by the PTN shall use the
unacknowledged data transfer service (broadcast Data Link) of the Data Link Layer. A message (or
message segment) shall be transmitted by including it within a DL-UNIT-DATA-REQUEST primitive to
the Data Link Layer. A received message (or message segment) will appear included with a DL-UNIT-
DATA-INDICATION primitive from the Data Link Layer.
All other messages shall use the acknowledged data transfer service of the Data Link Layer (point-to-
point Data Link). A message (or message segment) shall be transmitted by including it with a DL-
DATA-REQUEST primitive to the Data Link Layer. A received message (or message segment) will
appear included within a DL-DATA-INDICATION primitive from the Data Link Layer.
Note 4:
Before a TE can respond to a SETUP message delivered using the unacknowledged data transfer service,
it must establish a Data Link connection according to the procedures of subclause 7.1.1, unless a Data
Link connection already exists between the PTN and that TE.
7.2 Message segmentation procedures
This subclause specifies message segmentation and reassembly procedures for messages whose length
exceeds the maximum size of the Data Link Layer information field. The maximum Data Link Layer
information field size is defined in ETS 300 169 (parameter N201).
A PTN or a TE shall conform to the message segmentation procedures if it is capable of transmitting a
message which exceeds the maximum size of the Data Link Layer information field. Segmentation
procedures shall not be applied to messages which do not exceed the maximum size of the Data Link Layer
information field.
A PTN or a TE which claims conformance to this standard shall declare the maximum size of message
which it is able to receive. The declared maximum size shall not be less than 260 octets. If the maximum
size of the Data Link Layer information field is less than the declared maximum size of message which can
be received, the PTN or TE shall conform to the message reassembly procedures.
The message segmentation and reassembly procedures of Annex K of ETS 300 102-1 shall apply except the
requirement in Clause K.1.
If a segmented message is received by a PTN or TE which does not support reassembly procedures, the
procedures specified in subclause 5.8.4 of ETS 300 102-1 for message type errors shall apply to each
received segment.
7.3 Handling of protocol error conditions
The requirements of subclauses 5.8.1 to 5.8.9 of ETS 300 102-1 shall apply with the following
clarifications and additions.
7.3.1 Addition to requirements of subclause 5.8.6.1 of ETS 300 102-1
When a RELEASE message which contains no Cause information element is received as a first clearing
message, the actions to be taken shall be the same as if a RELEASE message with Cause No. 31 "normal,
---------------------- Page: 16 ----------------------
SIST ETS 300 192 E1:2005
Page 15
ETS 300 192: 1992
unspecified" had been received, except that if a RELEASE COMPLETE message is sent, it shall contain
Cause No. 96 "mandatory information element is missing".
7.3.2 Addition to requirements of subclause 5.8.6.2 of ETS 300 102-1
When a RELEASE message with invalid content of the Cause information element is received as a first
clearing message, the actions to be taken shall be the same as if a RELEASE message with Cause No. 31
"normal, unspecified" had been received, except that if a RELEASE COMPLETE message is sent, it
shall contain Cause No. 100 "invalid information element contents".
7.3.3 Modification to subclause 5.8.7.1, second paragraph, of ETS 300 102-1
When the unrecognised information element occurs in a message other than DISCONNECT, RELEASE,
or RELEASE COMPLETE the STATUS message, if sent, shall indicate the call state that the receiving
entity enters after processing the message in which the unrecognised information element was received.
7.3.4 Replacement for items a, b and c of subclause 5.8.7.1 of ETS 300 102-1
a) When a DISCONNECT message is received which has one or more unrecognized information
elements, the actions taken shall be the same as if a DISCONNECT message had been
received without these unrecognized information elements with the exception that the
RELEASE message returned shall contain Cause No. 99 "information element non-existent".
It is recommended to provide Cause No. 99 with diagnostics, although the inclusion of
diagnostics is optional.
b) When a RELEASE message is received which has one or more unrecognized information
elements, the actions taken shall be the same as if a RELEASE message had been received
without these unrecognized information elements with the exception that the RELEASE
COMPLETE message returned shall contain Cause No. 99 "information element non-
existent". It is recommended to provide Cause No. 99 with diagnostics, although the inclusion
of diagnostics is optional.
c) When a RELEASE COMPLETE message is received which has one or more unrecognized
information elements, the actions taken shall be the same as if a RELEASE COMPLETE
message without these unrecognized information elements had been received.
7.3.5 Addition to requirements of subclause 5.8.7.2 of ETS 300 102-1
If a DISCONNECT, RELEASE or RELEASE COMPLETE message is received which has one or more
non-mandatory information elements with invalid contents, normal call clearing shall apply. The
RELEASE and RELEASE COMPLETE messages returned shall contain Cause No. 100 "invalid
information element contents". It is recommended to provide Cause No. 100 with diagnostics, although
the inclusion of diagnostics is optional.
7.3.6 Modification to subclause 5.8.7.2, first paragraph, of ETS 300 102-1
When the information element with content error occurs in a message other than DISCONNECT,
RELEASE, or RELEASE COMPLETE the STATUS message, if sent, shall indicate the call state that the
receiving entity enters after processing the message in which the information element with content error
was received.
7.3.7 Modification to subclause 5.8.7.2, second paragraph, of ETS 300 102-1
Access information elements with a length exceeding the maximum length shall be treated as having
content error, i.e. they shall not be truncated and processed.
7.4 Handling of configuration errors
In point-to-multipoint configurations at the TE-PTN interface, the PTN capability may be limited by
manufacturer declaration. This means that the PTN may accept only a limited number of positive responses
---------------------- Page: 17 ----------------------
SIST ETS 300 192 E1:2005
Page 16
ETS 300 192: 1992
to a SETUP message which was delivered using the broadcast data link. If the number of positively
responding TEs, as defined by the data link on which an initial responding message (i.e., CALL
PROCEEDING, ALERTING or CONNECT) is received, reaches the limit, any additional positive response
shall be rejected. Depending on implementation, the PTN shall either send a RELEASE COMPLETE
message containing Cause No. 47 "Resource unavailable, unspecified" or initiate normal call clearing using
the same Cause number.
Note 5:
It is the user's responsibility to configure a basic access in accordance with the particular PTN's limitation.
7.5 Status and status enquiry procedures
The requirements of subclauses 5.8.10 to 5.8.11 of ETS 300 102-1 shall apply with the following
amendments.
7.5.1 Modifications to subclause 5.8.10 of ETS 300 102-1
The requirements of the paragraph beginning with "The sending or receipt of the STATUS ENQUIRY
message." shall be modified as follows.
A STATUS message containing Cause No. 97 shall not be treated as a response to the STATUS
ENQUIRY message.
7.5.2 Modifications to subclause 5.8.11 of ETS 300 102-1
The requirements of the paragraph beginning with "A STATUS message may be received." and the
paragraph beginning with "In this case the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.