SIST-TS TS 101 883 V1.1.1:2004

• Abstract:

  This work item will deliver a mapping of the reference points C1.C2.C3.SC2, R1, R2 in WI2003 to the H.323 protocol suite.

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2004
• Due Date: 01-Apr-2004
• Completion Date: 01-Apr-2004
• Ref Project: ETSI TS 101 883 V1.1.1 (2002-04) - Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Technology Mapping; Implementation of TIPHON architecture using H.323

SIST-TS TS 101 883 V1.1.1:2004 is the Slovenian adoption of ETSI TS 101 883 V1.1.1 for Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3. It specifies how the H.323 protocol suite is used to implement the TIPHON architecture, including the registration, bearer control and call control mappings needed for IP telephony and SCN interworking.

What does SIST-TS TS 101 883 V1.1.1:2004 specify?

SIST-TS TS 101 883 V1.1.1:2004 specifies the H.323-based mapping for TIPHON Release 3. It covers terminals, gateways, gatekeepers and the IP-network entities needed to support the TIPHON Release 3 architecture.

The document ties H.323 to the TIPHON functional architecture defined in TS 101 314 and to the primitives, information elements and behaviours defined in TS 101 882. It focuses on the Registration meta-protocol, the Bearer Control meta-protocol and the Call Control meta-protocol.

The scope includes two registration scenarios - “User at home” and “Roaming user” - and the call flows needed for IP-to-IP and IP-to-SCN use cases. The location of the Registration point of Attachment (RpoA) may use DHCP, but that locating step is outside the document’s scope.

Annex structure

Annex	What it covers
Annex A	Informative message flows for basic call establishment, with scenarios 0 to 3
Annex B	Normative H.323 protocol profile for H.225.0, RAS, Q.931/Q.932 and H.245 usage
Annex C	Normative mapping of service capabilities from TS 101 878
Annex D	Void
Annex E	Normative mapping of TIPHON M-PDUs to H.225.0 messages and parameters
Annex F	Informative example of H.323 implementation used by VISIONng
Annex G	Void
Annex H	Void
Annex I	Informative proposed changes to ITU-T Recommendation H.323
Annex J	Informative bibliography

What are the key requirements of SIST-TS TS 101 883 V1.1.1:2004?

SIST-TS TS 101 883 V1.1.1:2004 sets out the behaviour of H.323 terminals, gatekeepers and gateways for registration, call setup, release and user identity handling. In practice, it tells implementers which H.323 messages to exchange, which fields to include, and how to behave when a call crosses home, serving, intermediate and SCN boundaries.

Clause 4 - mapping H.323 into the TIPHON architecture

Clause 4 maps the H.323 terminal, gatekeeper, gateway, Media Gateway Controller (MGC), Signalling Gateway (SG) and Media Gateway (MGW) into TIPHON functional groups. It also notes that reference point R2 is internal to the network functional group.

For implementers, this means the document is not just about message syntax - it assigns each H.323 entity a role in the TIPHON architecture. That matters when designing which box performs registration, proxying, call control or SCN interworking.

Clause 5 - registration and unregistration

Clause 5 defines how H.323 registration works for “User at home” and “Roaming user” cases. It requires automatic gatekeeper discovery support, unless a gatekeeper address is manually configured, and it describes the GRQ, GCF, RRQ, RCF, URQ, UCF and URJ flows.

The H.323 terminal’s RRQ handling is constrained so that some fields intended for direct-routed call handling or gateway-only functions are not used. The gatekeeper validates user identity against the user profile, authenticates the user, returns the valid terminalAlias list, and provides preGrantedARQ information.

This matters because the home network gatekeeper decides which user identities are valid for the registration and which call permissions are pre-granted. The serving and intermediate network gatekeepers forward registration information, preserve the relevant addresses, and release resources when the registration is rejected or completed.

Clause 5.3 lets any of the involved parties cancel a registration with URQ. If the URQ has no endpointAlias, it means cancel all user identities linked to that registration, which is important for partial versus full deregistration handling.

Clause 5.4 describes Lightweight RRQ. That is the mechanism used to revoke or refresh the time a user remains attached to a service, so implementers need to support timed attachment control as part of the service lifecycle.

Clause 6 - call connectivity and signalling behaviour

Clause 6 maps H.225.0 / Q.931 call signalling to the Call Control meta-protocol. It requires a gatekeeper-routed call model, keeps the call-signalling channel open for the duration of the call, and supports fast connect and H.245 encapsulation within H.225.0.

The clause also defines robust error handling. Optional invalid elements are ignored, while mandatory invalid elements are either treated as defaulted or rejected, depending on whether a default exists. In practice, this tells implementations how to react to malformed or out-of-context call messages without breaking interoperability.

Clause 6 distinguishes the roles of originating terminal, serving network, intermediate network, home network, originating gateway, terminating gateway and terminating terminal functional groups. The serving and intermediate network gatekeepers act as H.323 proxies and may apply policy controls, including QoS-related handling and firewall interaction, although those external interactions are outside the document.

For call setup, the document supports both en-bloc and overlap sending. That is important because some networks pass the full number at once, while others need additional digits before the destination can be determined.

For SCN interworking, the originating and terminating gateway behaviours prevent protocol-breaking information from being sent across the IP/SCN boundary. The gateway can return SETUP ACKNOWLEDGE, forward INFORMATION messages, and use timer-based decisions when digit collection is still incomplete.

Clauses 7 and 8 - carrier selection and calling user identity

Clause 7 covers carrier selection by prefixing the called party number. This means the user or the home network service provider can indicate the chosen carrier as part of the dialled number format.

Clause 8 covers calling user identity. The terminal may include a calling party number or sourceAddress in SETUP, while gatekeepers in serving or intermediate networks must not alter those identity fields. The home network gatekeeper may screen the identity and, if needed, replace it with a default identity or apply presentation restrictions.

Annexes B and E - profile and message mapping

Annex B fixes the H.323 profile used by this specification. It shows which H.225.0, RAS, Q.931/Q.932 and H.245 fields are used for TIPHON Release 3, and which message elements are mandatory, optional or forbidden for the relevant H.323 versions and reference points.

Annex E maps the TIPHON M-PDUs to H.225.0 messages and parameters. That is the practical bridge between the TIPHON functional model and the concrete H.323 protocol messages used on the wire.

What terms does SIST-TS TS 101 883 V1.1.1:2004 define?

SIST-TS TS 101 883 V1.1.1:2004 defines the terms it uses so that registration and call-control roles are unambiguous. The most useful ones for implementers are:

• GateKeeper (GK) - An H.323 network entity that translates addresses and controls access for terminals, gateways and MCUs, and may also manage bandwidth and locate gateways.
• H.323 terminal - An endpoint that provides audio, and optionally video and data, for point-to-point or multipoint conferencing in packet-based networks.
• Gateway - An endpoint that provides real-time, two-way communication between an IP-based network and a Switched Circuit Network (SCN).
• Switched Circuit Network (SCN) - A circuit-switched telecommunications network such as PSTN, ISDN or GSM used for voice calls.
• Service point of Attachment (SpoA) - The point where a user attaches to a service application after the single sign-on procedure.
• Registration point of Attachment (RpoA) - The point the user locates first in the registration process.
• User at home - A scenario in which the user communicates directly with its gatekeeper without intermediate networks.
• VoIP - Voiceover IP, used here for telephony services supported on a managed IP network.

Who uses SIST-TS TS 101 883 V1.1.1:2004?

SIST-TS TS 101 883 V1.1.1:2004 is used by engineers and architects implementing H.323-based TIPHON services, especially where IP telephony must interwork with SCN networks. It is also relevant to gateway, gatekeeper and terminal vendors who need consistent registration and call-control behaviour.

Quality teams and test labs use it to verify message content, procedure sequencing and interworking behaviour against the normative profile in Annex B and the mappings in Annex E. Service providers and network operators use it when defining roaming, home-network and serving-network handling for VoIP service access.

Which standards are used with SIST-TS TS 101 883 V1.1.1:2004?

SIST-TS TS 101 883 V1.1.1:2004 relies on a set of TIPHON and ITU-T documents that define the architecture, service capabilities and protocol base:

• ITU-T Recommendation E.164 - provides the international numbering plan used for called numbers.
• ETSI TR 101 311 - defines the transport-plane requirements for TIPHON Release 3.
• ETSI TR 101 300 - gives the technical-issues background used in the TIPHON work.
• ETSI TS 101 878 - defines the service capabilities for a simple call.
• ETSI TS 101 314 - defines the abstract architecture and reference points.
• ITU-T Recommendation H.323 - provides the base packet-based multimedia communications system that this specification profiles.
• ETSI TR 101 301 - defines TIPHON Release 3 at a release level.
• ETSI TR 102 008 - provides terms and definitions for the TIPHON programme.
• ETSI TS 101 890 (all parts) - provides the TIPHON profile for ITU-T H.245.
• ETSI TS 101 804 (all parts) - provides the H.225 conformance test specification.
• ITU-T Recommendation I.112 - supplies ISDN vocabulary used in the terminology.
• ITU-T Recommendation H.235 - covers security and encryption for H.323 and H.245-based multimedia terminals.

The body of the document also uses H.225.0, H.245 and Q.931/Q.932 for concrete signalling behaviour, and Annex B and Annex E show how those protocols are constrained for TIPHON Release 3.

What does the SIST-TS TS 101 883 V1.1.1:2004 document contain?

SIST-TS TS 101 883 V1.1.1:2004 contains procedural text, message-flow figures and protocol-profile tables rather than a product specification. It includes registration procedures, call establishment and release behaviour, carrier selection, and calling-user-identity handling.

Annex A provides worked message-flow examples for four basic call-establishment scenarios, including user-at-home and roaming-user cases. Annex B contains the detailed H.323 profile tables for RAS, Q.931/Q.932 and H.245 usage, which is the section most directly used for implementation and interoperability testing.

Annex C links TIPHON service capabilities to the clauses in this document, and Annex E maps TIPHON M-PDUs to H.225.0 messages and parameters. Together, these annexes are the main reference material for design verification, protocol conformance and interoperability work.

SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Tehnologija preslikave - Implementacija arhitekture TIPHON z uporabo
H.323
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Technology Mapping; Implementation of TIPHON architecture using H.323
Ta slovenski standard je istoveten z: TS 101 883 Version 1.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3;
Technology Mapping;
Implementation of TIPHON architecture using H.323

2 ETSI TS 101 883 V1.1.1 (2002-04)
Reference
DTS/TIPHON-03017
Keywords
architecture, configuration, internet, IP, network,
protocol, telephony, VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:[phone] Fax:[phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
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 2002.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 101 883 V1.1.1 (2002-04)
Contents
Intellectual Property Rights.8
Foreword.8
Introduction .8
1 Scope .10
2 References .11
3 Definitions and abbreviations.12
3.1 Definitions.12
3.2 Abbreviations .18
4 Implementation in the TIPHON functional architecture .19
5 Registration .20
5.1 Gatekeeper discovery .21
5.1.1 Procedures in the H.323 terminal.22
5.1.1.1 Normal procedures.22
5.1.1.2 Exceptional procedures .23
5.1.2 Procedures in the gatekeeper .23
5.1.3 Procedures in the gatekeeper in the home network.23
5.1.3.1 Normal procedures.24
5.1.3.2 Exceptional procedures .24
5.1.4 Procedures in the gatekeeper in the serving network.24
5.1.4.1 Normal procedures.24
5.1.4.2 Exceptional procedures .25
5.1.5 Procedures in the gatekeeper in the intermediate network.25
5.1.5.1 Normal procedures.25
5.1.5.2 Exceptional procedures .26
5.2 Endpoint registration .26
5.2.1 Procedures in the H.323 terminal.27
5.2.1.1 Normal procedures.27
5.2.1.2 Exceptional procedures .28
5.2.2 Procedures in the gatekeeper .29
5.2.2.1 Gatekeeper in the home network.29
5.2.2.1.1 Normal procedure.30
5.2.2.1.2 Exceptional procedures.30
5.2.2.2 Gatekeeper in the serving network.30
5.2.2.2.1 Normal procedures .31
5.2.2.2.2 Exceptional procedures.31
5.2.2.3 Procedures in the intermediate network .32
5.2.2.3.1 Normal procedures .32
5.2.2.3.2 Exceptional procedures.33
5.3 Cancelling the registration.33
5.3.1 Procedures in the H.323 terminal.34
5.3.1.1 URQ message sent by the H.323 terminal .34
5.3.1.1.1 Normal case.34
5.3.1.1.2 Exceptional case .34
5.3.1.2 URQ message received from the network.35
5.3.2 Gatekeeper in the home network .35
5.3.2.1 URQ message sent by the gatekeeper in the home network.35
5.3.2.1.1 Normal procedure.35
5.3.2.1.2 Exceptional procedure .35
5.3.2.2 URQ message received from the H.323 terminal, from the gatekeeper in the serving network or
from gatekeepers in intermediate networks.36
5.3.3 Gatekeeper the serving network.36
5.3.3.1 URQ message initiated by the H.323 terminal.36
5.3.3.1.1 Normal procedures .36
ETSI
4 ETSI TS 101 883 V1.1.1 (2002-04)
5.3.3.1.2 Exceptional procedures.36
5.3.3.2 URQ message initiated by the home network or an intermediate network .37
5.3.3.2.1 Normal procedure.37
5.3.3.2.2 Exceptional procedure .37
5.3.3.3 URQ message initiated by the gatekeeper in the serving network .37
5.3.3.3.1 Normal procedure.37
5.3.3.3.2 Exceptional procedure .37
5.3.4 Gatekeeper the intermediate network .38
5.3.4.1 URQ message initiated by the H.323 terminal or the serving network .38
5.3.4.1.1 Normal procedure.38
5.3.4.1.2 Exceptional procedures.38
5.3.4.2 URQ message initiated by the home network or the serving network .38
5.3.4.2.1 Normal procedure.38
5.3.4.2.2 Exceptional procedure .39
5.3.4.3 URQ message initiated by a gatekeeper in the intermediate network .39
5.3.4.3.1 Normal procedure.39
5.3.4.3.2 Exceptional procedure .39
5.4 Use of Lightweight RRQ.39
5.4.1 Procedures in the H.323 terminal.40
5.4.2 Gatekeeper in the home network .40
5.4.2.1 Normal procedure .40
5.4.2.2 Exceptional procedure.40
5.4.3 Gatekeeper in the serving network .40
5.4.3.1 Normal procedure .40
5.4.3.2 Exceptional behaviour.41
5.4.4 Gatekeeper in the intermediate network .41
5.4.4.1 Normal procedure .41
5.4.4.2 Exceptional behaviour.41
6 Call connectivity .42
6.1 General behaviour .42
6.1.1 Error handling.42
6.1.2 Timers.43
6.2 Originating terminal functional group.43
6.2.1 Call establishment.44
6.2.1.1 En-bloc Procedure.44
6.2.1.2 Overlap sending .44
6.2.2 Active phase.44
6.2.3 Call release.44
6.2.4 Exceptional behaviour .44
6.3 Serving and intermediate network functional group for the calling party .45
6.3.1 Call establishment.45
6.3.2 Active phase.46
6.3.3 Call release.46
6.3.4 Exceptional behaviour .46
6.4 Home network functional group for the calling party .46
6.4.1 Call establishment.47
6.4.1.1 En-bloc procedure .47
6.4.1.2 Overlap procedure.47
6.4.2 Active phase.48
6.4.3 Call release.48
6.4.4 Exceptional procedures.48
6.5 Originating gateway functional group.48
6.5.1 Call establishment.48
6.5.1.1 En-bloc procedure .49
6.5.1.2 Overlap procedure.49
6.5.1.2.1 In the gateway .49
6.5.1.2.2 In the gatekeeper.50
6.5.2 Active phase.50
6.5.3 Call release.50
6.6 Intermediate network functional group .50
6.6.1 Call establishment.51
ETSI
5 ETSI TS 101 883 V1.1.1 (2002-04)
6.6.2 Active phase.51
6.6.3 Call Release .52
6.6.4 Exceptional behaviour .52
6.7 Home network functional group for the called party.52
6.7.1 Call Establishment .52
6.7.1.1 Void.53
6.7.1.2 En-bloc procedure .53
6.7.1.3 Overlap procedures .53
6.7.1.3.1 Normal behaviour.53
6.7.1.3.2 Exceptional behaviour .54
6.7.1.4 Void.54
6.7.1.5 Ring tone control.54
6.7.2 Active Phase .54
6.7.3 Call release.54
6.8 Serving network and intermediate network functional group for the called party .54
6.8.1 Call establishment.55
6.8.2 Active phase.55
6.8.3 Call release.55
6.8.4 Exceptional behaviour .55
6.9 Terminating terminal functional group.55
6.9.1 Call establishment.56
6.9.2 Active phase.56
6.9.3 Call release.56
6.10 Terminating gateway functional group.56
6.10.1 Call establishment.56
6.10.1.1 En-bloc procedure .57
6.10.1.2 Overlap.57
6.10.1.2.1 Actions by the gatekeeper.57
6.10.1.2.2 Actions by the gateway .58
6.10.1.3 Support of in-band information sent by the SCN.58
6.10.2 Active phase.58
6.10.3 Call release.58
7 Carrier selection .59
8 Calling user identity .59
8.1 Procedures in the H.323 terminal .59
8.2 Procedures in the gatekeeper.59
8.3 Procedures in the gateway.60
Annex A (informative): Message flows for basic call establishment.61
A.0 Message flow assumptions/pre-conditions.61
A.1 Scenario 0.61
A.1.1 User at home.62
A.1.2 Roaming user.62
A.2 Scenario 1.63
A.2.1 User at home.63
A.2.2 Roaming user.64
A.3 Scenario 2.64
A.3.1 User at home.65
A.3.2 Roaming user.66
A.4 Scenario 3.67
Annex B (normative): H.323 protocol profile.68
B.1 H.225.0.69
B.1.1 H323-UU-PDU.69
B.1.2 RAS messages and parameters.69
B.1.2.1 Gatekeeper discovery procedures .69
B.1.2.1.1 Gatekeeper ReQuest (GRQ).70
ETSI
6 ETSI TS 101 883 V1.1.1 (2002-04)
B.1.2.1.2 Gatekeeper ConFirm (GCF).70
B.1.2.1.3 Gatekeeper ReJect (GRJ) .71
B.1.2.2 Registration request procedure .71
B.1.2.2.1 Register Request (RRQ).72
B.1.2.2.2 Register ConFirm (RCF).73
B.1.2.2.3 Register ReJect (RRJ) .74
B.1.2.3 Unregistration Registration request procedure.74
B.1.2.3.1 UnregisterRequest (URQ).74
B.1.2.3.2 UnregisterConfirm (UCF).74
B.1.2.3.3 UnregisterReject (URJ).75
B.1.2.4 Request In Progress (RIP).75
B.1.2.5 Admission ReQuest procedures (ARQ).75
B.1.2.6 Information Request procedures .75
B.1.2.7 Location request procedures .75
B.1.3 Q.931/Q.932 messages and parameters.76
B.1.3.1 Alerting message .77
B.1.3.2 Call Proceeding.78
B.1.3.3 Connect message .79
B.1.3.4 Facility .80
B.1.3.5 Information .81
B.1.3.6 Progress .82
B.1.3.7 Release Complete .83
B.1.3.8 Setup .84
B.1.3.9 Setup Acknowledge .85
B.2 H.245.86
B.2.1 Terminal Capability Set message .86
B.2.1.1 Terminal Capability Set .86
B.2.1.2 Terminal Capability Set Acknowledge .86
B.2.1.3 Terminal Capability Set Reject.86
B.2.2 Void.86
B.2.3 Logical Channel signalling messages.86
B.2.3.1 Open Logical Channel .86
B.2.3.2 Open Logical Channel Acknowledge .86
B.2.3.3 Open Logical Channel Reject .87
B.2.3.4 Open Logical Channel Confirm.87
B.2.3.5 Close Logical Channel.87
B.2.3.6 Close Logical Channel Acknowledge.87
B.2.4 Request mode messages .87
B.2.4.1 Request mode.87
B.2.4.2 Request Mode Ack.87
B.2.4.3 Request Mode Reject.87
Annex C (normative): Service Capabilities.88
Annex D: Void .89
Annex E (normative): H.323 implementation of TIPHON functional architecture .90
E.1 Mapping of M-PDU .90
E.1.1 Registration .90
E.1.1a Registration meta-protocol .90
E.1.1.1 U_SpoAServiceAttachRequest.90
E.1.1.2 D_SpoAServiceAttachReject.91
E.1.1.3 D_SpoAServiceAttachResponse.92
E.1.2 Call control M-PDUs.93
E.1.2.1 CallRequest (SETUP).93
E.1.2.1.1 U_CallRequest .93
E.1.2.1.2 D_CallRequest .94
E.1.2.1.3 NW_CallRequest .95
E.1.2.2 CallReport (SETUP ACKNOWLEDGE) .96
E.1.2.3 CCAditionalDigits (INFORMATION).96
E.1.2.4 CallReport (CALL PROCEEDING).96
ETSI
7 ETSI TS 101 883 V1.1.1 (2002-04)
E.1.2.5 CallReport (PROGRESS) .96
E.1.2.6 CallReport (ALERTING) .97
E.1.2.7 CallConnect (CONNECT).97
E.1.3 Bearer control M-PDUs.98
E.1.3.1 BearerRequest (SETUP).98
E.1.3.2 BearerConnect (CALL PROCEEDING, FACILITY, PROGRESS, ALERTING and/or CONNECT) .99
Annex F (informative): H.323 Implementation used by VISIONng.100
F.1 Introduction .100
Annex G: Void .102
Annex H: Void .103
Annex I (informative): Proposed changes to ITU-T Recommendation H.323.104
Annex J (informative): Bibliography.105
History .106
ETSI
8 ETSI TS 101 883 V1.1.1 (2002-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON).
Introduction
The approach being taken to standardization in TIPHON represents a departure from that used in the past for PSTN,
ISDN and GSM. Its aim is to allow much greater scope for competition through innovation in the design of equipment
and services. Its aim is also to provide adequate standardization to facilitate the operation of services across
interconnected networks, even networks that use different technologies. The present document presents the initial core
set of Service Capabilities envisaged to be required to enable service providers to offer services on TIPHON networks
that may safely interwork with existing PSTN services while enabling more advanced services to be subsequently
developed.
ETSI
9 ETSI TS 101 883 V1.1.1 (2002-04)
Figure 1 shows the relationship of the present document with other TIPHON Release 3 deliverables.
TR 101 301
Release 3: Scope & Definition
TR 102 008
Definition of Terms
Transport Plane
Service Capabilities
TR 101 311 TS 101 878
Architecture & Reference
TS 101 314
configurations
Protocol
Implementer’s
TS 101 882 TS 101 315
Framework
guide
TS 101 885
TS 101 883 TS 101 884
H.323 profile SIP profile H.248 profile
TS 101 890 TS 102 027 TS 101 889 TS 101 804
SIP PICS H.248PICS
H.245 H.225
PICS,ATS,PIXIT TS, ATS, PIXIT
Figure 1: Relationship with other TIPHON Release 3 documents
• TR 101 311 [2] provides the requirements on the transport plane;
• TS 101 878 [6] defines service capabilities that are used in the TIPHON Release 3 for a simple call;
• TS 101 882 provides the Protocol Framework based on the TIPHON Release 3 architecture to implement the
simple call service capabilities as defined in the present document;
• TS 101 315 [17] is an implementer's guide that shows how to use of the meta-protocol to realize the capabilities
as defined in TS 101 878 [6];
• TS 101 883 (the present document) provides the protocol mappings for the ITU-T H-323 profile;
• TS 101 884 provides the protocol mappings for the SIP profile;
• TS 101 885 [14] provides the protocol mappings for the ITU-T H-248 profile; and
• TS 101 314 [8] provides the architecture and reference configurations for TIPHON Release 3.
ETSI
SCN plane
10 ETSI TS 101 883 V1.1.1 (2002-04)
1 Scope
The present document describes how the H.323 protocol suite can be used to implement the architecture, defined in
TS 101 314 [8] and the primitives, information elements and behaviours, defined in TS 101 882.
The present document defines the mapping of the following meta-protocols:
• the Registration meta-protocol;
• the Bearer Control meta-protocol; and
• the Call Control meta-protocol.
The document is applicable to equipment performing the roles of terminal, gateway, gatekeeper and also to entities
within the IP network that are necessary to support TIPHON Release 3.
The H.323 profile contained in the present document was derived by examination of:
• ITU-T Recommendation H.323 [10] and associated suite of protocols:
- H.225.0 (RAS and Q.931); and
- H.2
...