1 Scope
1.1 Relation to other ITU-T H.248 related NAT traversal mechanisms
2 References
3 Definitions
3.1 Terms defined elsewhere
3.2 Terms defined in this Recommendation
4 Abbreviations and acronyms
5 Conventions
6 Toolkit usage
6.1 ITU-T H.248.50 usage in different network
models
6.2 Overview of toolkit NAT traversal techniques
6.3 ITU-T H.248 call/bearer separation, connection model and IP
addresses for ephemeral terminations
6.4 Specific SDP information elements
6.5 Overview of NAT traversal support mechanisms (by ITU-T H.248
entities)
7 STUN and TURN support
7.1 STUN base package
7.2 MG STUN client package
7.3 MG TURN client package
7.4 MGC STUN client package
7.5 STUN information package
8 ICE support
8.1 MG act-as STUN server package
8.2 Originate STUN continuity check package
8.3 STUN consent freshness package
9 Keep-alive and pinhole support
9.1 MGC-originated STUN request package
9.2 Keep alive request package
10 Package-independent NAT-T procedures
10.1 Support for MG terminated STUN-based connectivity checks
Appendix I – Example signalling scenarios for package-independent NAT-T
procedures
I.1 Example #1: ICE/STUN support by ITU-T H.248 IP access gateways
Appendix II – ICE for TCP
II.1 Introduction
II.2 MG bearer interface: protocol stack
II.2 Bearer establishment
II.3 TCP address candidates
Appendix III – ICE mode support by gateway-embedded ICE agents
III.1 Background
III.2 Main differences between ICE-full and ICE-lite
Appendix IV – ICE extensions: "Trickle ICE"
IV.1 Introduction
IV.2 Impact of trickle ICE on ITU-T H.248.50-defined packages
IV.3 Example signalling flows for trickle ICE
IV.4 Summary
Appendix V – ICE multihomed and IPv4/IPv6 dual stack fairness
V.1 Introduction
V.2 Impact on ITU-T H.248 gateways with ICE support?
Appendix VI – ICE restarts
VI.1 Introduction
VI.2 ICE restart procedures
VI.2 Impact on ITU-T H.248 gateways with ICE support?
Bibliography