1
Scope
2
References
2.1 Normative references
2.2 Normative references
3
Definitions
4
Abbreviations
5
General
5.1 Master-slave determination
5.2 Capability exchange
5.3 Logical channel signalling
procedures
5.4 Receive terminal close logical
channel request
5.5 H.223 multiplex table entry
modification
5.6 Audiovisual and data mode request
5.7 Round-trip delay determination
5.8 Maintenance loops
5.9 Commands and indications
Annex A – Messages: Syntax
Annex B – Messages: Semantic definitions
B.1 Master-Slave Determination messages
B.2 Terminal capability messages
B.3 Logical channel signalling messages
B.4 Multiplex Table signalling messages
B.5 Request Multiplex Table signalling
messages
B.6 Request Mode messages
B.7 Round-trip Delay messages
B.8 Maintenance Loop messages
B.9 Communication Mode Messages
B.10 Conference Request and Response
Messages
B.11 Multilink Messages
B.12 Logical Channel Bit rate Change Messages
B.13 Commands
B.14 Indications
B.15 Generic messages
Annex C – Procedures
C.1 Introduction
C.2 Master-slave determination
procedures
C.3 Capability exchange procedures
C.4
Unidirectional Logical Channel signalling procedures
C.5 Bidirectional Logical Channel
signalling procedures
C.6 Close Logical Channel procedures
C.7 H.223 Multiplex Table Procedures
C.8 Request Multiplex Entry procedures
C.9 Mode Request procedures
C.10 Round-trip delay procedures
C.11 Maintenance Loop procedures
Annex D – Object identifier assignments
Annex E – ISO/IEC 14496-2 Capability Definitions
Annex F – Logical Channel Bit-Rate Management Capability Definitions
Annex G – ISO/IEC 14496-1 Capability Definitions
G.1 Capability Identifier
G.2 Capability parameters used for
capability negotiations and logical channel signalling
G.3 Capability parameters used for
logical channel signalling only
Annex H – ISO/IEC 14496-3 Capability Definitions
Annex I – GSM Adaptive Multi-Rate Capability Definitions
I.1 Definition
of mode signalling and bit stuffing to achieve octet alignment
Annex J – TDMA ACELP voice codec definitions
Annex K – TDMA US1 voice codec definitions
Annex L – CDMA EVRC Voice Codec Definitions
Annex M – ISO/IEC 13818-7 and ITU-R BS.1196 Definitions
Annex N – RFC 3389 – RTP Payload for Comfort Noise
Annex O – L16 Capability Identifier
Annex P – Bounded audio stream capability
Annex Q – Generic Capability for Nx64K Circuit Relay over IP
Q.1 Introduction
Q.2 Description
Appendix I – Overview of ASN.1 syntax
I.1 Introduction
to ASN.1
I.2 Basic ASN.1
data types
I.3 Aggregate
data types
I.4 Object
identifier type
Appendix II – Examples of H.245 procedures
II.1 Introduction
II.2 Master-slave Determination
Signalling Entity
II.3 Capability Exchange Signalling
Entity
II.4 Logical Channel Signalling Entity
II.5 Close Logical Channel Signalling
Entity
II.6 Multiplex Table Signalling Entity
II.7 Mode Request Signalling Entity
II.8 Round-trip Delay Signalling Entity
II.9 Bidirectional Logical Channel
Signalling Entity
Appendix III – Summary of procedure timers and counters
III.1 Timers
III.2 Counters
Appendix IV – H.245 extension procedure
Appendix V – The replacementFor procedure
Appendix VI – Examples of H.263 Capability Structure Settings
VI.1 Examples of Enhancement Layer H.245
parameter setting
VI.2 Examples of video back channel H.245
parameter setting
Appendix VII – Procedure and template for defining new capabilities with
H.245 generic capabilities
VII.1 Procedure
VII.2 Template
VII.3 Example Template – H.261
Appendix VIII – List of generic capabilities and generic messages defined
in Recommendations/Standards other than this Recommendation
Appendix IX – ASN.1 usage in this Recommendation
IX.1 Tagging
IX.2 Types
IX.3 Constraints and Ranges
IX.4 Extensibility
Appendix X – Resolution of unidirectional and bidirectional conflict
scenarios
X.1 Both
terminals use bidirectional OLC
X.2 Master proposes bidirectional OLC
and slave proposes unidirectional OLC
X.3 Master proposes unidirectional OLC
and slave proposes bidirectional OLC
X.4 Master proposes bidirectional OLC
with nullData and slave proposes unidirectional OLC
X.5 Both terminals propose bidirectional
OLC with nullData