Professional Documents
Culture Documents
Rapporteur
TITLE:
__________________
This is the full text of the Recommendation that appears in GEN 7 : Liaison statement:
Request for comments on G.799.1 support of modem over IP
ABSTRACT:
This contribution constitutes a revision of draft Recommendation G.799.1, Functionality and
Interface Specifications for GSTN Transport Network Equipment for Interconnecting GSTN
and IP Networks, incorporating the changes that were agreed to at meeting.
1. Introduction:
Question 7 of Study Group 15 has been created to produce a new Recommendation on the
functionality and interface specifications for GSTN transport network equipment for
interconnecting GSTN and IP networks.
Currently there is no globally recognised equipment standard defining the functionality or interface
characteristics of Network-Network Interfaces designed for connection GSTN and IP based
networks. Not only does this jeopardize the voice quality that results from such interconnection, but
also it unnecessarily complicates the network operators task of selecting and configuring such
equipment.
This document constitutes a draft Recommendation that addresses the various functionality, interface and
interworking aspects of this equipment.
* Contact:
Jerry Skene
Tellabs, OY (Finland)
Tel:
+1 703 724-7302
Fax:
+1 703 724-7202
E-mail: jerry.skene@ties.itu.int
Attention: This is not a publication made available to the public, but an internal ITU-T Document intended only for use by the
Member States of the ITU, by ITU-T Sector Members and Associates, and their respective staff and collaborators in their ITU
related work. It shall not be made available to, and used by, any other persons or entities without the prior written consent of the
ITU-T.
ITU-T\SG_DOC\SG16\FEB02\GEN\GEN-021.DOC
Recommendation G.799.1
Summary
Voice and voice-band traffic in international networks has traditionally been transported by circuit
switched systems and equipment. With the advent of the networks optimized for the transport of
Internet Protocol (IP), and as a result of its considerable growth and pervasive nature, more and
more voice traffic is expected to be carried over IP networks.
Given that voice and voice-band services remain a significant part of telecommunications, there is a
need to ensure a high quality of service for voice carried in part or wholly via IP. This
Recommendation defines interfaces and functionality for equipment that interconnect GSTN and
networks optimized for the transport of IP, such that they will provide the degree of voice quality
and interoperability required.
Introduction and Background
Keywords
Gateway, IP gateway, TDM-IP gateway, signalling interface, bearer interface, voice gateway, Voice
Over IP, internet protocol, internet gateway, end-to-end transmission performance, fax over IP,
media gateway, media gateway controller, TDM, VoIP, voice quality, quality of service, echo
canceller, speech coding, TIGIN.
Scope
This Recommendation covers the requirements of equipment that interconnects GSTN networks and
networks optimized for the transport of IP. Such equipment is referred to in this document as a
TIGIN gateway. The Recommendation describes functionality, transport interfaces, coding
protocols, signalling interfaces, and OA&M interfaces of these devices. Support is provided for calls
from IP to GSTN, GSTN to IP, IP to IP and GSTN to GSTN. While such TIGIN gateways may
support multimedia traffic and Remote Access Server (RAS) functionality, this Recommendation
covers only voice, and voice-band data, facsimile, narrowband digital data, address and signalling
tones. traffic requirements. Support of other media such as digital data and video are left for further
study. In this sense, a TIGIN gateway is a subset of a Media Gateway.
This Recommendation does not define any new protocols or network architectures, but rather refers
to existing protocols and architectures. It also does not specify a level of performance, as this will be
covered by other Recommendations referenced by this document. Operation and management
procedures are outside the scope of this Recommendation.
TIGIN Gateways are assumed to support bulk interconnection between GSTN and IP networks, and
are not intended to connect directly to Simple Endpoint Type devices. They are considered to be a
trunking and not an access gateway. Support of ATM on the GSTN interface is not specifically
defined in this release.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
References
Normative 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.
ITU-T Recommendation E.370 (10/00) Service principles when public circuit switched
international telecommunication networks interwork with IP-based networks
ITU-T Recommendation G.704 (10/98) Synchronous frame structures used at 1544, 6312,
2048, 8488 and 44,736 kbits/s hierarchical levels
ITU-T Recommendation G.707 (10/00), Network Node Interface for the Synchronous
Digital Hierarchy (SDH)
ITU-T Recommendation G.711 Appendix II, (02/2000), A comfort noise payload definition
for ITU-T G.711 use in packet-based multimedia communication systems
ITU-T Recommendation G.723.1 (03/96), Dual rate speech coder for multimedia
communications transmitting at 5.3 and 6.3 kbit/s
ITU-T Recommendation G.726 (12/90) - 40, 32, 24, 16 kbit/s Adaptive Differential Pulse
Code Modulation (ADPCM)
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
ITU-T Recommendation G.729 (03/96) - Coding of speech at 8 kbit/s using conjugatestructure algebraic-code-excited linear-prediction
ITU-T Recommendation G.957 (06/99) - Optical interfaces for equipments and systems
relating to the synchronous digital hierarchy
ITU-T Recommendation H.225.0 (11/00) - Call signalling protocols and media stream
packetization for packet-based multimedia communication systems
CCITT Recommendation I.233.1 (1991), Frame mode bearer services: ISDN frame
relaying bearer service.
ITU-T Recommendation I.363.2 (11/00) - B-ISDN ATM Adaptation Layer (AAL) type 2
specification
ITU-T Recommendation Q.2 (11/88) - Signal receivers for automatic and semi-automatic
working, used for manual working
ITU-T Recommendation Q.115 (12/99) - Logic for the control of echo control devices
IEEE Standard 802-1990 - IEEE Standards for Local and Metropolitan Area Networks:
Overview and Architecture.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
IETF RFC 1332 (05/92), The PPP Internet Protocol Control Protocol, (Proposed Standard)
IETF RFC 1661 (07/94) The Point-to-Point Protocol (PPP) (Standard)
IETF RFC 1812 (06/95), Requirements for IP Version 4 Routers, June 1995 (Proposed
Standard)
IETF RFC 1889 (01/96), RTP: A Transport Protocol for Real-Time Applications (Proposed
Standard)
IETF RFC 2131 (03/97), Dynamic Host Configuration Protocol, (Draft Standard)
IETF RFC 2225 (04/98), Classical IP and ARP over ATM, (Proposed Standard)
IETF RFC 2427 (09/88) Multiprotocol Interconnect over Frame Relay (Standard)
IETF RFC 2684 (09/99), Multiprotocol Encapsulation over ATM Adaption Layer 5,
(Proposed Standard)
IETF RFC 2719 (10/99), Framework Architecture for Signalling Transport, (Informational)
IETF RFC 2833 (05/00), RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals, (Proposed Standard)
1.2
Informative References
1.3
For terms and definitions not appearing in this section, see Recommendation G.701 (03/93),
Vocabulary of Digital Transmission and Multiplexing and Pulse Code Modulation (PCM) Terms.
general switched telephone network (GSTN):
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
This network includes ATM, PSTN, ISDN, wireless networks and private networks.
media gateway (MG):
The media gateway converts media provided in one type of network to the format required in
another type of network. For example, a MG could terminate bearer channels from a switched
circuit network (e.g., DS0s) and media streams from a packet network (e.g., RTP streams in an IP
network). This gateway may be capable of processing audio, video and T.120 alone or in any
combination, and will be capable of full duplex media translations. The MG may also play
audio/video messages and performs other IVR functions, or may perform media conferencing. For
the purpose of this Recommendation, the term media gateway refers to a voice gateway.
media gateway controller (MGC):
Controls the parts of the call state that pertain to connection control for media channels in a media
gateway
simple endpoint type devices (SET):
See H.323 Annex F.
TIGIN Gateway
A voice gateway complying with this Recommendation
voice gateway (VG):
A voice gateway is a subset of a media gateway that deals with voice and voiceband traffic only, and
not data or video traffic.
1.4
Abbreviations
Discontinuous Transmission
IP
Internet Protocol
ITU
MG
Media Gateway
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
MGC
PCC
PCM
PPP
SCN
SDH
SET
TDM
TFO
UDP
VBD
Voiceband Data
VoIP
Voice over IP
In practice, a TIGIN gateway may be composed of multiple pieces of equipment, each with
specialized functions, such as signalling interfaces, voice compression/decompression, packetization,
etc. Figure 1 illustrates some of the functions performed in a gateway. This Recommendation does
not specify how these functions are to be performed, nor does it specify the specific
interconnections, which may be implemented between functions. It is recognized that the functions
of a media gateway controller (MGC) may be combined with those of a TIGIN gateway in the same
physical device. In this situation, certain interfaces described in this Recommendation may not be
present. This Recommendation does not cover the requirements of such a controller.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
note 1
Call Control
note 4
TDM
Bearer
Interface
note 4
TDM
Signalling
Interface
note 4
Q.55 Signalling
Interface
note 1
Bearer Control
note 1
Network Management
System
Synchronization
Time Division
Multiplexed
Network
Interface
Signal
Processing
Functions
TDM Signalling
Interface
note 2
Q.55 Echo
Canceller control
Interface
note 3
P
a
c
k
e
t
i
z
e
r
Internet
Protocol
Interface
IP Bearer
Interface
note 1
Switching Function
note 1: these may or may not share the same external interface
note 2: optional. Only required when inband signalling on TDM interface is supported.
note 3: optional
note 4: these may or may not share the same external interface
Each of the elements included in the above block diagram is described in detail in the following
sections.
3
Interfaces
The overall relationship between the TIGIN gateway and other devices and protocols in the network
is illustrated in figure 2.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
SS7
GSTN
TDM
Network
H.323
Gateway
Signalling
transport over IP
See section 3.3.2
TIGIN
GATEWAY
(G.799.1)
Functionality
(see section 4)
Network
Optimized for
Internet
Protocol
IP Bearer Interface
(see section 3.1)
Figure 2/G.799.1 Relationship between TIGIN gateway and other IP-related standards
3.1
IP Bearer Interfaces
The IP interface block in the block diagram in Figure 1 provides the transmission facility interface for
the network element to the IP network. It terminates all the lower layers and much or all of the
upper layers of the incoming signal from the IP network. It also performs alarm detection and
performance monitoring of the interface layers. It then sends the data to the Packetizer block for
further processing. It performs the inverse function in the transmitting direction towards the IP
network.
The layers of the IP bearer interface should conform to at least one of the interface types from the
following section. Voice and voiceband data and higher layers on this interface should conform to
that specified in H.323. Higher layer protocols may include any of the following: TRP, UDP, and
RTCP. Facsimile traffic may use ITU-T Recommendation T.38.
Figure 3.1 shows layers of TIGIN IP bearer interface model.
Application Transparent Voice
Upper
Layers
Transport
Layer
Tones
RTP
FAX TIGIN
Control
Management
Signalling
System No.
7 Transport
T.38
SNMP/TMN
M2UA*
H.248/MGCP
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
SCTP
06.10.15
10
IP Layer
IP (Internet Protocol)
Lower
Layers
* Editors Note: This depends upon the results of a liaison sent to SG11 and IETF.
Figure 3 shows only a basic stack. Additional function for Quality of Service (QoS), security, header
compression, etc. may be added.
3.1.1 Lower Layers
This Recommendation does not restrict using of any lower layer protocol intended for IP packet
transmission and approved by an internationally recognized standards body.
Lower layer interface performs link protection, alarm detection and performance monitoring of the
interface layers as define in appropriate standards.
3.1.2 IP Layer
IP protocol should conform to IETF RFC 791, RFC 950, RFC 919 and RFC 920.
Support of MPLS is for further study.
Support of IP V6 is for further study.
IP network topology, IP packet distribution and routing protocols are not the subject of this
Recommendation.
3.1.3 Transport Layer
UDP protocol is used as transport layer protocol and it should conform to IETF RFC 768.
SCTP protocol is used for transport PSTN signalling messages over IP networks and it should
conform to IETF RFC 2960.
TCP protocol (RFC 793) may be optionally used for non time critical applications.
3.1.4 Upper Layers
RTP protocol is used for transparent signal transmission and for voice and tones transmission as
IETF RFC 1889 describes. IETF RFC 1889 also defines RTCP (Real Time Control Protocol) as a
companion control protocol for RTP.
A TIGIN gateway should support both transparent G.711 and T.38 fax protocol for fax transmission.
Other types of application interfaces are described later in this section.
3.1.5 Layer 3
Layer 3 protocols may include any of the following:
DHCP - IETF RFC 2131
IP V4 Router - IETF RFC 1812
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
11
Support of IP V6 (IETF RFC 2472 - IP Version 6 over PPP ) is for further study.
3.1.6 Layer 2
Layer 2 protocols may include any of the following:
PPP (x.ip)
Frame Relay I.233ATM I.363.1, I.363.2, I.363.5
IP over PPP, as per IETF - RFC 1661
IP over Frame Relay, as per IETF -
RFC 2427
IP over ATMIP over PPP over SDH, as per IETF - RFC 2615
3.1.7 Layer 1
Layer 1 protocols may include any of the following:
G.704, G.707, G.703, G.957, ISO/IEC 8802-3, ISO/IEC 8802-1
3.2
The TDM interface block in the block diagram in Figure 1 provides the transmission facility interface
for the network element to the GSTN network. The physical layer of the TDM bearer interface
should consist of at least one of the interface types in the table below. Voice and voiceband coding
on this interface should conform to G. 711. Mechanisms for tandem coder avoidance are for further
study.
Layer 1 G.704, G.707, G.703, G.806, G.957
3.3
Establish, modify, and release connections within the TIGIN, including originating and
terminating addresses (e.g. TDM-TDM, TDM-IP)
Continuity Check
Transfer of certain GSTN Signalling information for MF and CAS based protocols carried on
the TDM link
PCC allows the MGC to specify the internal TIGIN resources required in the connection path (Echo
control, DTMF detection, Modem/Fax detection, etc.). It also allows for the setting of per call
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
12
features and parameters required based on call type and interoperability needs. . These parameters
may include some or all of the followingsuch as:
Real time call processing event notification, including the control of echo cancellers
Selection of and/or negotiation of codec (e.g. G.711, G.723.1, G.729). Selection of different
codecs on the GSTN and IP interfaces implies performing a transcoding function (e.g., G.711
to G.729). It is recommended that ITU-T Recommendation H.245 be used for codec
negotiation.
Mechanisms for supporting the above features are for further study. Selection of these
mechanisms will affect voice quality. See sections 4.1, 4.2 & 4.3 for more information on this
topic.
Upon completion of a call, as specified in H.248 PCC protocols, TIGIN should be capable of
supplying, upon request, statistics related to the call, for example:
Packet loss
Mechanisms for supporting the above features are for further study. Selection of these mechanisms
will affect voice quality. See sections 4.1, 4.2 & 4.3 for more information on this topic.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
13
The upper layer protocol used should conform to one of the following:
H.248
Note: If H.248 is not used, then certain gateway capability such as NLP control of integrated echo
cancellers may not be available.
. Lower layer protocols should conform to one of those listed in sections 3.1.1, 3.1.2, or 3.1.3. Use
of the MGCP protocol on this interface is for further study.
Examples of protocols that may be used on this interface include:
IEEE Std 802-1990, IEEE Standards for Local and Metropolitan Area Networks: Overview
and Architecture
1 Gbps Ethernet
TCP or UDP/IP
The PCC interface may share the same circuit as the IP bearer interface.
3.3.2 Signalling over IP
A framework architecture for signalling transport over IP networks may be found in IETF RFC2719.
3.3.2.1 Out-of-band signalling
As described in H.248, TIGIN interfaces to the Signalling Gateway through the Media Gateway
Controller (which is referred in H.248 as the Call Agent). As a consequence, the Media Gateway
Controller implements the "signalling" layers of the H.323 standard, and presents itself as an "H.323
Gatekeeper" or as one or more "H.323 Endpoints" to the H.323 systems.
Signalling exchanges with the Media Gateway Controller are done through H.225/RAS and
H.225/Q.931.
Possible negotiation of logical channels and transmission parameters with the Media Gateway
Controller are done through H.245.
3.3.2.2 In-band signalling
There are some applications that require support for in-band signalling:
Internet telephony gateway that detects the DTMF signals on the incoming circuits and sends
the appropriate digits as RTP payload (see IETF RFC-2833)
Internet end system such as an "Internet phone" can emulate DTMF functionality without
generating precise tone pairs and without imposing the burden of tone recognition on the
receiver
When the coder used destroys the in-band signalling information (like G.723.1)
In such cases, the support for in-band signalling will be done in accordance with IETF RFC-2833.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
14
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
15
If SS7 A link is used, then signalling on the TDM bearer interface is not used.
Support of the following and other signalling types is for further study:
SS7 Signalling
Q.931
R1 Q.2
R2 Q.400
V 5.2 (G.965)
3.5
Management Interface
Both TMN and SNMP management interfaces are for further study.
4
4.1
TIGIN Functionality
Signal Processing Functions
The network element supports voice-related features as described in this section. Some or all of the
voice feature functions listed in this section may be utilized during a call. The PCC message specifies
which functions should be used on a call.
As an example, silence suppression and comfort noise generation may be requested on a call that
uses G.711 coding. The network element in that case would take the GSTN data, interpret it as
G.711 coding and generate packets to the IP network using G.711 coding only if it detects speech
activity. In the reverse direction, it would receive packets from the IP network, interpret them as
G.711 encoded PCM, convert the packets into a synchronous (TDM) stream and send it to the
GSTN network. During the time packets are not received it would generate comfort noise G.711
PCM values and send it to the GSTN network.
In addition, other signal processing features supported by the network element could include the
following:
Signal processing functions may affect voice quality. See sections 3.3.1 & 4.3 for more information
on this topic.
4.1.1 Echo Control
In compliance with ITU-T Recommendation G.177, Transmission Planning for voiceband services
over hybrid internet/PSTN connections, a voice-over-IP connection traversing a hybrid is required to
include a G.168 compliant echo canceller. Since the echo canceller needs to have a constant delay for
its echo path, it should be placed so that the echo path is on the TDM side of the interface that
includes the hybrid. Issues that need to be addressed are:
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
16
Tail Capacity
Network Operators and Service Providers should ensure that echo cancellation is applied in the most
appropriate location for the specific configuration. The echo canceller should be associated with the
TIGIN gateway in one of three possible configurations, as outlined in the following sections.
It should be reinforced that all voice connections involving GSTN to IP interworking involving a
hybrid require echo cancellation and the Network Operator or Service Provided choosing to utilize
either configuration B or C below should ensure that an echo canceller is provisioned on the TDM
bearer side of the hybrid Internet/ GSTN connection.
4.1.1.1 TIGIN Internal Echo Control Configuration A
In this configuration the echo canceller is integrated into the TIGIN gateway itself as shown in
Figure 3. With this configuration, H.248 messages conveying are generated by the Q.115 echo
control logic in the MGC and are sent to the TIGIN gateway. The TIGIN gateway then directly
controls the internal echo canceller function in accordance with the messages received. For this
configuration, the echo canceller function within the TIGIN gateway is required and the Q.55/Q.52
process is optional but not used.
SS7
MEDIA
GATEWAY
CONTROLLER
(MGC)
SIGNALLING
GATEWAY
GSTN
TDM
Network
TDM bearer
Echo
Echo
canceller
function
TIGIN
GATEWAY
(G.799.1)
IP Network
IP bearer
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
17
section 4.1.1.2.1. For this configuration, the echo canceller function within the TIGIN gateway is
optional but not used, and the Q.55 process is mandatory.
SS7
MEDIA
GATEWAY
CONTROLLER
(MGC)
SIGNALLING
GATEWAY
GSTN
TDM
Network
Echo
H.248,
MGCP (optional)
TDM bearer
TIGIN
Associated
Echo
canceller
Q.55
process
TIGIN
GATEWAY
(G.799.1)
IP Network
IP bearer
Q.55 control
protocol
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
18
SIGNALLING
GATEWAY
SS7
Q.115 echo
control logic
Echo canceller
association
H.248,
MGCP (optional)
TDM bearer
GSTN
TDM
Network
Q.55 (or
other)
control
process
MEDIA
GATEWAY
CONTROLLER
(MGC)
[Q.115 echo control logic]
GSTN switch
Associated
Echo
Canceller
TIGIN
GATEWAY
(G.799.1)
Echo
Q.55 (or other)
control protocol
IP Network
IP bearer
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
19
TIGIN gateway, if any is present, as in this particular case one has already been provisioned in the
GSTN.
SS7
SIGNALLING
GATEWAY
MEDIA
GATEWAY
CONTROLLER
(MGC)
[Q.115 echo control logic]
Q.115 echo
control logic
H.248,
MGCP
GSTN
TDM
Network
Q.55 (or
other)
control
process
Echo
Canceller
Echo
TIGIN
GATEWAY
(G.799.1)
IP Network
IP bearer
TDM bearer
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
20
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
21
Voice signals.
Speech Detector
Voiceband (VBD) Detectors (e.g.: V.34 detector, V.32 detector, Facsimile detector, etc.).
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
22
VBD Detectors
Voice
VBD
New Call Detectors
or
Speech Detector
or
End of VBD Detectors
4.2
Voiceband Quality
See section 4.1.3 for handling of silence suppression and comfort noise generation. ITU-T
Recommendation G.177 should be followed to ensure adequate end-to-end speech quality.
Definitions of categories of voice transmission quality may be found in ITU-T Recommendation
G.109.
4.2.1 Tandem Free Operation
It is highly recommended that a single codec pair be used end to end.
High quality speech codecs operating at low to medium rates (4 to 16 kbps) have been a primary
factor in making packet voice networks, including VoIP and Wireless networks practical. As different
packet networks will be interfaced with one another, the tandeming of speech codecs will be very
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
23
common in the near future. Tandem speech codecs may degrade speech quality considerably. As a
result, many tandem free operation (TFO) standards have been developed under different standard
organizations to avoid additional speech coding and decoding in a communication link. The TFO
standards were based on the same approach and were originally intended for Wireless services.
However, TFO standards are also applicable to any packetized networks including IP networks.
To avoid tandeming speech codecs and improve speech quality, a G.799.1 gateway should support
the TFO protocol as defined in the following standards:
3GPP2 A.S0004-0.1, 3GPP2 Tandem Free Operation Specification, Version 1.0.0,
and
3G TS 28.062, Inband Tandem Free Operation (TFO) of Speech Codes; Stage 3 Service
Description
When G.799.1 gateways interconnect mobile networks using the first of these standards at one end
and the second at the other end, interworking of the two TFO techniques is necessary. To provide
high quality digitized voice services through seamless interworking across different networks, there
is a need to consolidate these different TFO standards. This is a subject for further study.
4.2.2 Packet size selection
The choice of packet size is a trade-off between transport efficiency, quality and delay. The delay
associated with codec processing and packetization should be kept as short as possible. Gateways
should adhere to ITU-T Recommendation G.177 in this regard. When multiple frames of a speech
codec are allocated to the same packet, packet loss concealment techniques become less effective
and as a result may possibly lower end-to-end speech quality when packet loss is encountered.Packet
size should be an integer multiple ofmatched to the codec frame length. To accomplish this objective
when G.729 or G.729A is used, two frames per packet should be considered as the maximum packet
size. Similarly, G.711 may be used with packet sizes of 10 ms (80 frames) or 20 ms (160 frames) to
achieve this objective. Finally, when G.723.1 is used, only one frame should be included in each
packet. The 7.5 ms look-ahead and the 30 ms frame size of G.723.1 results in a combined voice
buffering and processing delay of between 37.5 ms and 67.5 ms (depending on the computational
power available), thus contributing to difficulty of interactive communications.
The 30 ms frame size of G.723.1 results in voice collection and coding delay of at least 60 ms,
contributing to difficulty of interactive communications.
4.3
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
24
4.4
Switching
The TIGIN Gateway shall provide the ability to switch calls in the direction of the PSTN and in the
direction of the IP network. Switch control based on general call control and allows establish,
modify and release connection within the TIGIN.
Some details on methods of switching, and a discussion on switching philosophy are included in
MSF-ARCH-001.00-FINAL IA Multiservice Switching Forum Implementation Agreement of the
Multiservice Switching Forum.
Editors Note: The above reference document may become normative text depending on Q7s
conclusions on this issue following discussion on the Q7 discussion board and/or an interim
meeting.
This item is for further study.
4.5
Conference Bridging
A TIGIN gateway requires a clock recovery circuit that would allow it to generate a precise local
clock and keep this clock synchronised to a remote TDM clock. A synchronisation mechanism
improves the quality of voice at the reception and it is vital for the transport of data through RTP
trunking.
Timing information may be transported between two Circuit Switch domains:
over the IP network (using the timestamp mechanism provided by the RTP encapsulation)
other methods (e.g. those used for hierarchical timing distribution in SDH networks as
specified in G.813, "Timing characteristics of SDH equipment slave clocks (SEC) ")
For interoperability reasons, TIGIN implementations which use methods for synchronising the local
TDM clock based on timing information transported over the IP networks, should be based on
information made available by the approved protocols rather then using proprietary schemes. Such
information, for example, is the RTP timestamp (see RFC 1889). Methods of determining the
resolution of the timestamp are for future study.
Similar to the case of hierarchical master-slave SCN synchronisation methods, it is recommended
that a primary and a secondary synchronisation reference input be provided to each clock (e.g. two
independent sources of IP/UDP/RTP packets that could be used for extracting timing information).
The remainder of this section is for information purposes only:
As described in IETF RFC-1889 the randomly initialised RTP timestamp is a 32-bit field that must be
updated such that it reflects the sampling instance of the first octet in the RTP data packet.
Consequently, there is a direct relation between the rate of the TDM clock at the sending TIGIN and
the rate of the RTP packets being filled up, sent over the IP network, and, the rate of their arrival at
the receiving TIGIN. At the receive end, the arrival of an RTP packet could be timestamped based on
the TDM clock of the Circuit Switch domain interfacing to the local (receiving) TIGIN.
The difference between the packet arrival times and the difference between RTP packet timestamps
could be algorithmically processed to extract information for adjusting the local TDM clock- see
IETF RFC-2833-RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
25
4.7
Management System
The Management System Interface performs the functions to administer the system on a non-real
time (non per-call) basis with respect to the following subsections. Further details for each of the
management functions outlined in the following sub-sections are included in the general (e.g., ITU-T
M.3100) and technology specific (e.g., ITU-T G.784, IETF RFC 2579) recommendations.
Support of TMN and SNMP management systems are for further study.
4.7.1 Configuration Management
For further study. Issues to be considered include the management of:
IP interface features
Packetizer options such packet loss mitigation scheme, which are not needed to be controlled on
a per call basis.
clock recovery
Equipment faults
Congestion control
Traffic management
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
26
TIGIN Gateway
TDM
IP
Test Access Port
(TDM and/or IP)
Figure 8.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
27
Gateway Functions
TDM
IP
TDM / IP
Gateway Functions
TDM
IP
TDM / IP
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
28
In the case of SS7 signalling arrangements, the signalling to set up calls is done via the H.248 path to
the MGC.
The functions provided by the management system should not overlap with those provided by per
call control.
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
29
(1)
GSTN - TIGIN
signalling
GSTN
Terminal.
GSTN
Terminal.
(2)
GSTN
TIGIN
Gateway
(G.7991.)
IP
Network
to TIGIN
signalling
Network
Optimized
for
Transport
of Internet
Protocol
H.323
Terminal
H.323
Terminal
(3)
(4)
Bearer Interface
signalling
Figure I1: Location of TIGIN and possible connection types of interest in this
Recommendation. Four connection types are shown. See text for details.
The terminals attached to the Internet are assumed to have H.323 functionality from the point of
view of voice and voice-band data transmission. These terminals may be connected to the IP network
via a direct connection (e.g., Ethernet, Token Ring, etc.) or a dial-up connection (e.g., modem and
PPP link). The IP and GSTN sections are interconnected through a GSTN/IP gateway, called a
TIGIN. For convenience, this gateway is designated with a single box in Figure I1.
The specific functions of the gateway will depend on whether the direction of transmission is from
the IP Network to the GSTN or vice versa. In particular, the functions in the gateway include (but
are not limited to):
Call originating on the IP Network and terminating on GSTN
Speech decoder (including error concealment, comfort noise, silence insertion, etc.)
Echo cancellation
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
30
Echo cancellation
Four connection arrangements are considered in this Recommendation, each of which is shown in
Figure I1. They are:
1. GSTN Terminal H.323 Terminal (GSTN Terminal GSTN TIGIN IP Network
H.323 Terminal)
2. H.323 Terminal GSTN Terminal (H.323 Terminal IP Network TIGIN GSTN
GSTN Terminal)
3. H.323 Terminal H.323 Terminal (H.323 Terminal IP Network TIGIN IP Network
H.323 Terminal)
4. GSTN Terminal GSTN Terminal (GSTN Terminal GSTN TIGIN GSTN GSTN
Terminal)
Each of these four connection arrangements requires the use of one gateway. Hence, connections
that are purely GSTN-based or are strictly H.323-to-H.323 using only the Internet are not the
subject of this Recommendation. Situations in which multiple or tandem gateways are used are
covered by combinations of connections 1 through 4 (e.g. a combination of 1 & 2 would be GSTN
Terminal GSTN TIGIN #1 IP Network TIGIN #2 GSTN GSTN Terminal). More
complex arrangements may be envisaged but it is not considered necessary to describe them in detail
as they can be made up of these above cases.
Appendix II. Performance / Interworking
Performance / interworking issues include:
a. Ability to vary the packet size on a per call basis
Voice samples are accumulated and buffered into a packet, and a packet is sent when it
becomes full. The size of the packet can be controlled by PCC messages, but the network
must ensure that they are the same on both ends of a connection. In addition, the capability
to vary the packet size on a per call basis must be supported by the PCC protocol, and is
outside the scope of this of document.
b. Silence suppression / Comfort noise generation when used in conjunction with codecs that do
not describe them.
c. Real time control protocol (RTCP)
d. Packet loss mitigation scheme
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
31
GSTN Terminal
General Switched
Telephone Network
TIGIN Gateway
(G.799.1)
H.323 Terminal
IP Network
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
32
Network optimized
for transport of
internet protocol
TIGIN
Gateway
(G.799.1)
TIGIN
Gateway
(G.799.1)
GSTN Terminal
GSTN Terminal
General Switched
Telephone Network
General Switched
Telephone Network
or
General Switched
Telephone Network
TIGIN
Gateway
(G.799.1)
TIGIN
Gateway
(G.799.1)
H.323 Terminal
H.323 Terminal
Network optimized
for transport of
internet protocol
Network optimized
for transport of
internet protocol
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15
33
Interoffice
Transmission
IP Router/Switch
Multiplex
Multiplex
Telephony
Switch
/var/www/apps/conversion/tmp/scratch_4/288934581.doc
06.10.15