1
Scope
2 References
3 Definitions
4 Abbreviations and acronyms
5 Network conditions
5.1 Introduction
5.2 Constitution of a
control association
5.3 IP-based H.248 transport
5.4 Relation between the
address of an H.248 entity and an H.248 message identifier
5.5 MG database for MGC entries
5.6 Dedicated network
applications
6 Procedures for IP-based H.248
control associations
6.1 Starting point
6.2 Control association
establishment
6.3 Control association
refreshment
7 Procedures for non-IP-based
H.248 control associations
8 H.248 control association:
summary of scenarios with usage of ServiceChangeMgcID parameter
8.1 Case a): Restart
request (Initial registration)
8.2 Case b): Handoff
request
8.3 Case c): Failover
request
8.4 Case d): Disconnected H.248 control association renewal request
8.5 Case e): Forced H.248 control association closure request
8.6 Case f): Graceful H.248 control association release request
9 H.248 control association:
impact of protocol version changes and/or profile changes on established
control associations
10 H.248 control association:
Impact of transport mode changes
10.1 Situation of transport mode changes
10.2 Impact on established
control associations
10.3 Relation between
profile and transport modes
10.4 Indication of
transport mode
11 H.248 control association:
registration of multi-mode transport capable media
gateways
11.1 Variant A: single-mode transport capable MGC
11.2 Variant B: multi-mode
transport capable MGC, prepared to serve all transport modes
11.3 Variant C: multi-mode
transport capable MGC, not prepared to serve all transport modes
12 H.248 control association:
policing of incoming H.248 messages
12.1 Overview
12.2 Principal filter
stages
12.3 MID Policing: filter
rules, dependent on MID format and provisioned information