`
`ITU-T
`
`TELECOMMUNICATION
`STANDARDIZATION SECTOR
`OF ITU
`
`H.323
`
`(06/2003)
`
`SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
`
`Infrastructure of audiovisual services — Systems and
`terminal equipment for audiovisual services
`
`Packet-based multimedia communications
`
`systems
`
`ITU-T Recommendation H.323
`
`Ms___Biscotti__oo73oa1
`
`Petitioner Microsoft - Ex. 1026, Cover 1
`
`
`
`ITU-T H-SERIES RECOIVHVIENDATIONS
`AUDIOVISUAL A‘ID MULTIMEDIA SYSTEMS
`
`CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS
`INFRASTRUCTURE OF AUDIOVISUAL SERVICES
`General
`
`Transmission multiplexing and synchronization
`Systems aspects
`Communication procedures
`Coding of moving video
`Related systems aspects
`[I
`1:
`ii:
`::
`.5!35t¢‘3‘.3 #11161 :t°;1'l31:i1!?11 ¢Fl“iP1.‘1C"1if01‘:311di0Yi$1!i11 S¢1TYi¢¢S:
`Directory services architecture for audiovisual and multimedia services
`Quality of service architecture for audiovisual and multimedia services
`Supplementary services for multimedia
`MOBILITY AND COLLABORATION PROCEDURES
`
`e Ti
`
`I
`
`Overview of Mobility and Collaboration, definitions, protocols and procedures
`Mobility for II-Series multimedia systems and services
`Mobile multimedia collaboration applications and services
`Security for mobile multimedia systems and services
`Security for mobile multimedia collaboration applications and services
`Mobility interworking procedures
`Mobile multimedia collaboration inter-working procedures
`BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES
`Broadband multimedia services over VDSL
`
`Furfltrllzer details, please refer to [he list ofITU-T Rec'urrm1emI'ut1'uns.
`
`MS_Biscotti_0073082
`
`Petitioner Microsoft - Ex. 1026, Cover 2
`
`
`
`ITU-T Recommendation H.323
`
`Packet-based multimedia communications systems
`
`Summary
`
`provide multimedia
`that
`entities
`other
`and
`terminals
`describes
`This Recommendation
`communications services over Packet—Based Networks (PBN) which may not provide a guaranteed
`Quality of Service. H.323 entities may provide real-time audio, video and/or data communications.
`Support for audio is mandatory, while data and video are optional, but if supported, the ability to use
`a specified common mode of operation is required, so that all terminals supporting that media type
`can inteivvork.
`
`The pa.cket—based network over which H.323 entities communicate may be a point—to—point
`connection, a single network segment, or an internetwork having multiple segments with complex
`topologies.
`
`H.323 entities may be used in point-to-point, multipoint, or broadcast (as described in lTU-T
`Rec. H.332) configurations. They may interwork with H.310 terminals on B-ISDN, H.320 terminals
`on N—ISDN, H.321 terminals on B—lSDN, H.322 terminals on Guaranteed Quality of Service LANs,
`H.324 terminals on GSTN and wireless networks, V.70 terminals on GSTN, and voice terminals on
`GSTN or ISDN through the use of Gateways.
`
`H.323 entities may be integrated into personal computers or implemented in stand—alone devices
`such as videotelephones.
`
`Note that the title of H.323 (1996) was "Visual telephone systems and equipment for local area
`networks which provide a non-guaranteed quality of service". The title changed in Version 2 to be
`consistent with its expanded scope.
`
`Products claiming compliance with Version 1 of H323 shall comply with all of the mandatory
`requirements of H.323 (1996) which references ITU-T Recs H.225.0 (1996) and H.245 (1997).
`Version 1 products shall be identified by H.225.0 messages containing a protocolldentifier = {itu-t
`(0)
`recommendation (0) h (8) 2250 version (0)
`1}
`and H.245 messages
`containing a
`protocolldentifier = ’itu—t (0) recommendation (0) h (8) 245 version (0) 2}.
`
`Products claiming compliance with Version 2 of H.323 shall comply with all of the mandatory
`requirements of this Recommendation, H.323 (1998), which references ITU-T Recs H.225.0 (1998)
`and H.245 (1998 or later). Version 2 products shall be identified by H.225.0 messages containing a
`protocolldentifier : {itu-t (0) recommendation (0) h (8) 2250 version (0) 2} and H.245 messages
`containing a protocolldentifier : {itu-t (0) recommendation (0) h (8) 245 version (0) X}, where "x"
`is 3 or higher.
`
`Products claiming compliance with Version 3 of H323 shall comply with all of the mandatory
`requirements of this Recommendation, H.323 (1999), which references ITU-T Recs H.225.0 (1999)
`and H.245 (1999 or later). Version 3 products shall be identified by H.225 0 messages containing a
`protocolldentifier = {itu-t (0) recommendation (0) h (8) 2250 version (0) 3} and H.245 messages
`containing a protocolldentifier = {itu-t (0) recommendation (0) h (8) 245 version (0) X}, where "X"
`is 5 or higher.
`
`Products claiming compliance with Version 4 of H323 shall comply with all of the mandatory
`requirements of this Recommendation, H.323 (2000), which references ITU-T Recs H.225.0 (2000)
`and H.245 (2000 or later). Version 4 products shall be identified by H.225.0 messages containing a
`protocolldentifier = {itu-t(0)reco1n1nendation (0) h (8) 2250 version (0,) 4} and H.245 messages
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073083
`
`Petitioner Microsoft - Ex. 1026, p. i
`
`
`
`containing a protocolldentifier = {itu-t (0) recommendation (0) h (8) 245 Version (0) X}, where "X"
`is 7 or higher.
`
`Products claiming compliance with Version 5 of H.323 shall comply with all of the mandatory
`requirements of this Recommendation, H.323 (2003), which references ITU-T Recs H.225.0 (2003)
`and H.245 (02/2003 or later). Version 5 products shall be identified by H2250 messages containing
`a protocolldentifier = {itu—t (0) recommendation (0) h (8) 2250 Version (0) 5} and H.245 messages
`containing a protocolldentifier = {itu—t (0) recommendation (0) h (8) 245 version (0) x}, where "x"
`is 9 or higher.
`
`Products claiming compliance with Version 6 of H323 shall comply with all of the mandatory
`requirements of this Recommendation, H.323 (2006), which references ITU-T Recs H.225.0 (2006)
`and H.245 (O5/2006 or later), Version 6 products shall be identified by H2250 messages containing
`a protocolldentifier = {itu—t (0) recommendation (0) h (8) 2250 version (0) 6} and H.245 messages
`containing a protocolldentifier = {itu-t (0) recommendation (0) h (8) 245 version (0) x}, where "x"
`is 13 or higher.
`
`This Version of ITU-T Rec. H.323 integrates the changes approved in Amendment
`"Revised Annex D" and Amendment 2 (01/2005) "New Annex M4".
`
`1 (01/2005)
`
`Source
`
`1TL—T Recommendation H.323 was approved on 13 June 2006 by lTU—T Study Group 16
`(2005-2008) under the ITU-T Recommendation A8 procedure.
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073084
`
`Petitioner Microsoft - Ex. 1026, p. ii
`
`
`
`FOREWORD
`
`The lntemational Telecommunication Union (ITU) is the United Nations specialized agency in the field of
`telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of
`ITU.
`ITU-T is
`responsible
`for
`studying technical, operating and tariff questions
`and issuing
`Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
`
`The World Telecommunication Standardization Assembly (WTSA), which meets every four years,
`establishes the topics for study by the ITU-T study groups which, in turn. produce Recommendations on
`these topics‘
`
`The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
`
`In some areas of infonnation technology which fall within ITU-T's purview, the necessary standards are
`prepared on a collaborative basis with ISO and IEC.
`
`NOTE
`
`the expression "Administration" is used for conciseness to indicate both a
`In this Recommendation,
`telecommunication administration and a recognized operating agency.
`
`Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain
`mandatory provisions
`(to ensure c_g_
`interoperability or applicability) and compliance with the
`Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some
`other obligatory language such as "must" and the negative equivalents are used to express requirements. The
`use of such words does not suggest that compliance with the Recommendation is required of any party.
`
`INTELLECTUAL PROPERTY RIGHTS
`
`ITU draws attention to the possibility that the practice or implementation of this Recommendation may
`involve the Lise of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,
`validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others
`outside of the Recommendation development process.
`
`As of the date of approval of this Rccommcndation, ITU had received notice of intellectual property,
`protected by patents, which may be required to implement this Recommendation. However, implementors
`are cautioned that this may not represent the latest information and are therefore strongly urged to consult the
`TSB pate11t database.
`
`All rights reserved. No part of this publication may be reproduced, by any means whatsoever,
`without the prior written permission of ITU.
`
`© ITU 2007
`
`ITU-T Rec. H.323 (06/2006)
`
`iii
`
`MS_Biscotti_0073085
`
`Petitioner Microsoft - Ex. 1026, p. iii
`
`
`
`Page
`
`1
`2
`
`10
`14
`
`l4
`
`CONTENTS
`
`Scope .......................................................................................................................... ..
`References ................................................................................................................... ..
`
`Definitions .................................................................................................................. ..
`
`Symbols and abbreviations ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,
`Conventions........
`..
`
`System description ................................................................................................... ..
`6.1
`Information streams ...................................................................................... ..
`
`6.2
`
`63
`
`6.4
`
`6.5
`
`6.6
`
`6.7
`
`6. 8
`
`69
`
`Terminal characteristics ................................................................................ ..
`
`Gateway characteristics ............................................................................. ..
`
`Gatekeeper characteristics ............................................................................ ..
`
`Multipoint controller characteristics ........................................................... ..
`
`Multipoint processor characteristics ............................................................. ..
`
`Multipoint control unit characteristics .......................................................... ..
`
`Multipoint capability .................................................................................... ..
`
`Models for supplementary services .............................................................. ..
`
`Call signalling ............................................................................................................. ..
`7.1
`Addresses .................................................................................................. ..
`
`7.2
`
`7.3
`7.4
`
`7.5
`
`7.6
`
`7.7
`7.8
`
`7.9
`
`Registration, Admission and Status (RAS) channel ..................................... ..
`
`Call signalling channel ................................................................................. ..
`Call reference value ...................................................................................... ..
`
`Call ID .......................................................................................................... ..
`
`Conference ID and conference goal ............................................................. ..
`
`Endpoint call capacity .................................................................................. ..
`Caller identification services ........................................................................ ..
`
`Generic extensible framework ..................................................................... ..
`
`Call signalling procedures .......................................................................................... ..
`
`8.1
`
`8 2
`8.3
`
`8.4
`
`8.5
`
`8.6
`
`Phase A — Call setup ..................................................................................... ..
`
`Phase B — Initial communication and capa.hility exchange
`Phase C — Establishment of audiovisual communication ............................ ..
`
`Phase D — Call services ................................................................................ ..
`
`Phase 1: — Call termination ........................................................................... ..
`
`Protocol failure handling .............................................................................. ..
`
`lnteroperation with other tenninal types .................................................................... ..
`
`9.1
`
`9.2
`
`9.3
`
`9.4
`
`Speech—only terminals ................................................................................ ..
`
`Visual telephone terminals over the ISDN (ITU-T Rec. H.320) .................. ..
`
`Visual telephone terminals over GSTN (ITU-T Rec. H.324) ...................... ..
`
`Visual telephone terminals over mobile radio (Annex C/H.324, a.l<.a.
`"H.324/M") ............................................................................................... ..
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073086
`
`Petitioner Microsoft - Ex. 1026, p. iv
`
`
`
`Page
`
`127
`
`128
`
`128
`
`128
`
`128
`
`129
`
`129
`
`129
`
`129
`
`132
`
`9.5
`
`9.6
`
`9.7
`
`9.8
`
`99
`
`Visual telephone terminals over ATM (H.321 and H.310 RAST) ............... ..
`
`Visual telephone terminals over guaranteed quality of service LANs
`(ITU-T Rec. 1-1.322) ...................................................................................... ..
`
`Simultaneous voice and data terminals over GSTN (ITU-T Rec. V 70) ...... ..
`
`T. 120 terminals on the packet—based network .............................................. ..
`
`Gateway for H.323 media transport over ATM ........................................... ..
`
`Optional enhancements ............................................................................................. ..
`
`10. 1
`
`10.2
`
`103
`
`10.4
`
`Encryption .................................................................................................... ..
`
`Multipoint operation ..................................................................................... ..
`
`Call Linkage in H.323 .................................................................................. ..
`
`Tunnelling of non—H.323 signalling messages ............................................. ..
`
`105
`
`Use of RTP payload for DTNTF digits, telephony tones and telephony
`signals ........................................................................................................... ..
`Maintenance ................................................................................................................ ..
`
`1 1
`
`11.1
`
`1 1.2
`
`Loopbacks for maintenance purposes .......................................................... ..
`
`Monitoring methods ................................................................................... ..
`
`Annex A — H.245 messages used by H.323 endpoints .......................................................... ..
`
`Annex B — Procedures for layered video codecs ................................................................... ..
`
`B.l
`B .2
`
`B3
`B.4
`
`B.5
`
`B.6
`
`B.7
`
`Scope ............................................................................................................ ..
`Introduction .................................................................................................. ..
`
`..
`Scalabilitymethods...........
`Call establishment ........................................................................................ ..
`
`Use of RTP sessions and codec layers ......................................................... ..
`
`Possible layering models .............................................................................. ..
`
`Impact on multipoint conferences ................................................................ ..
`
`Use ofnetwork QoS for layered Video streams...... .
`R 8
`Annex C — H.323 on ATM .................................................................................................... ..
`
`C. 1
`
`C.2
`C.3
`
`C.4
`
`Introduction .................................................................................................. ..
`
`Scope ............................................................................................................ ..
`Architecture .................................................................................................. ..
`
`Protocol section ............................................................................................ ..
`
`Annex D — Real—time facsimile over H.323 systems ............................................................. ..
`D. 1
`Introduction .................................................................................................. ..
`
`D2
`
`D3
`
`D.4
`
`D.5
`
`D.6
`
`D.7
`
`Scope ............................................................................................................ ..
`
`Procedures for opening channels to send T38 packets ................................ ..
`
`Non-fast connect procedures ........................................................................ ..
`
`Replacing an existing audio stream with a T3 8 fax stream ......................... ..
`
`Usage of the maxBitRate/bandWidth in messages ....................................... ..
`
`Interactions with gateways and T38/Annex B devices ................................ ..
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073087
`
`Petitioner Microsoft - Ex. 1026, p. v
`
`
`
`Annex E — Framework and wire—protocol for multiplexed call signalling transport ............. ..
`
`E.l
`
`E2
`
`Scope ........................................................................................................... .4
`
`H.225.0 call signalling over Annex E .......................................................... ..
`
`Annex F — Simple endpoint types .......................................................................................... ..
`13.1
`Introduction .............................................................................................. .4
`
`F2
`
`F.3
`F.4
`
`F.5
`
`F6
`
`F.7
`
`F .8
`
`F9
`
`S oecification conventions ............................................................................. .4
`
`Scope ............................................................................................................ ..
`l\ormative references.................................................................................... ..
`
`Abbreviations ............................................................................................... 44
`
`S'mple (Audio) Endpoint Type — System functionality overview ............... ..
`
`P‘ocedures for Simple Endpoint Types ...................................................... .4
`
`Security extensions ....................................................................................... ..
`
`Irteroperability considerations ..................................................................... ..
`
`Implementation notes (Informative) ............................................................. ..
`F.10
`Annex G — Text conversation and Text SET ......................................................................... ..
`
`G4 1
`
`G2
`G.3
`
`G.4
`
`G_5
`
`G6
`
`G.7
`G8
`
`G.9
`
`Introduction .............................................................................................. .4
`
`Scope ............................................................................................................ ..
`References .................................................................................................... ..
`
`Definitions .................................................................................................... ..
`
`Capability Advertisement for Text in H.323 ................................................ ..
`
`Procedures for opening channels for T.l40 text conversation . ................... 44
`
`Framing and buffering ofT.l40 data ........................................................... ..
`Interaction with text conversation facilities in other devices ....................... ..
`
`Multipoint considerations ............................................................................. ..
`
`G, 10
`
`Text SET: Text Conversation Simple Endpoint Type ,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,
`
`Annex I — Security for Annex F ............................................................................................. ..
`J. l
`Introduction ............................................................................................... 44
`
`I42
`
`J.3
`J .4
`
`J.5
`
`I46
`
`Specification conventions .......................................................................... .4
`
`Scope ............................................................................................................ ..
`Abbreviations ............................................................................................... .4
`
`Normative references.................................................................................... ..
`
`Secure Audio Simple Endpoint Type (SASET) .......................................... .4
`
`Annex K — I-ITTP—based service control transport channel ................................................... 44
`K. I
`Introduction .................................................................................................. .4
`
`K42
`
`K3
`
`K4
`K. 5
`
`Service control in H.323 ............................................................................. 44
`
`Usage ofHTTP ............................................................................................. .4
`
`Example scenarios ........................................................................................ ..
`References ................................................................................................ .4
`
`Page
`
`165
`
`165
`
`177
`
`180
`1 80
`
`181
`
`181
`182
`
`182
`
`182
`
`183
`
`190
`
`190
`
`190
`193
`
`193
`
`194
`194
`
`194
`
`195
`
`197
`
`198
`I98
`
`199
`
`201
`
`202
`202
`
`203
`
`203
`203
`
`204
`
`204
`
`206
`206
`
`207
`
`209
`
`211
`215
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073088
`
`Petitioner Microsoft - Ex. 1026, p. vi
`
`
`
`Page
`
`216
`
`216
`218
`
`219
`
`221
`
`221
`
`221
`221
`
`221
`
`223
`
`223
`
`223
`
`223
`223
`
`Annex L — Stimulus control protocol ..................................................................................... .1
`
`L.l
`L.2
`
`L.3
`
`L.4
`
`Scope ......................................................................................................... 11
`Introduction .................................................................................................. ..
`
`Stimulus framework ..................................................................................... ..
`
`References .................................................................................................... .1
`
`Annex \/11 — Tunnelling of signalling protocols (QSIG) in H.323 ....................................... .1
`
`V11.1
`
`Scope ............................................................................................................ .1
`Normative references.................................................................................... .1
`
`Endpoint procedures ................................................................................... 11
`
`Tunnelling of QSIG connection—oriented call—independent signalling ........ ..
`
`Gatekeeper procedures .............................................................................. .1
`
`Annex V12 — Tunnelling of signalling protocols (ISUP) in H.323 ........................................ ..
`
`Scope ............................................................................................................ .1
`\/12.1
`V122 Normative references.................................................................................... .1
`
`V123
`
`V124
`
`Endpoint procedures ..................................................................................... ..
`
`Gatekeeper procedures .............................................................................. .1
`
`Annex V13 — Tunnelling ofDSSl through H.323 .................................................................. 11
`
`V13 .1
`
`Scope ............................................................................................................ ..
`Normative references.................................................................................... .1
`
`Endpoint procedures ..................................................................................... .1
`
`Tunnelling of bearer-independent DSSl signalling .................................... .1
`
`Gatekeeper procedures .............................................................................. .1
`
`Annex V14 — Tunnelling of narrow—band signalling syntax (N SS) for H.323 ....................... ..
`
`V14.l
`
`Scope ............................................................................................................ ..
`References .................................................................................................... .
`.
`
`H.22510 Endpoint procedures ....................................................................... .1
`
`Gatekeeper procedures ................................................................................. .1
`
`RAS procedures for direct—routed calls ........................................................ ..
`
`Annex 0 — Usage of URLs and DNS .................................................................................... ..
`
`011
`0.2
`
`0.3
`
`0.4
`
`0.5
`0.6
`
`0.7
`
`0.8
`
`0.9
`
`Scope ............................................................................................................ 11
`Normative references.................................................................................... .
`.
`
`Informative references .................................................................................. .1
`
`H.323 URL ................................................................................................... .1
`
`Encoding ofH.323 URL in H.323 messages _______________________________________________ _.
`Non—H.323 URLs and URIs within the context of H.323 ............................ ..
`
`11.323 URL parameters ................................................................................. ..
`
`Usage ofthe H.323 URL .............................................................................. .1
`
`Resolving an H.323 URL to IP Address using DNS .................................... .1
`
`0.10
`
`Using DNS SRV Resource Records ............................................................. ..
`
`ITU-T Rec. H.323 (06/2006)
`
`MS_Biscotti_0073089
`
`Petitioner Microsoft - Ex. 1026, p. vii
`
`
`
`Annex F — Transfer of modem signals over H.323 ................................................................ .4
`
`P1
`P.2
`
`P3
`
`P.4
`
`P. 5
`
`R6
`P7
`
`R8
`
`Scope ......................................................................................................... ..
`References .................................................................................................... ..
`
`Definitions .................................................................................................... ..
`
`Abbreviations ............................................................................................... IA
`
`Introduction .............................................................................................. ..
`
`Capability advertisement .............................................................................. ..
`Call establishment ........................................................................................ ..
`
`Logical channel signalling ............................................................................ IA
`
`Annex Q — Far—end camera control and H.281/H.224 ........................................................... ..
`
`Q. l
`
`Q2
`
`Q.3
`
`Q.4
`
`Scope .......................................................................................................... ..
`
`References .................................................................................................... DA
`
`Introduction .................................................................................................. U4
`
`Far—end camera control protocol .................................................................. ..
`
`RTP header information ............................................................................... ..
`Q_5
`Annex R — Robustness methods for H.323 entities ............................................................. ..
`
`R.l
`R2
`
`R.3
`
`R.4
`
`R5
`
`R.6
`
`R.7
`
`R.8
`
`R9
`
`R.10
`
`R.l 1
`
`R. 12
`
`R. 13
`
`Introduction and scope ................................................................................. ..
`Normative references.................................................................................... IA
`
`Definitions .................................................................................................... U4
`
`Abbreviations ............................................................................................... ..
`
`Overview of the two methods ..................................................................... ..
`
`Common mechanisms .................................................................................. ..
`
`Method A: State recovery from neighbours ................................................. ..
`
`Method B: State recovery from a shared repository ..................................... IA
`
`Interworking between robustness methods ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,
`
`Procedures for recovery ................................................................................ ..
`
`GenericData usage ........................................................................................ U4
`
`Informative Note I: Background on robustness methods ............................ IA
`
`Informative Note 2: Call state sharing between an entity and its backup
`peer ............................................................................................................... ..
`
`Appendix I — Sample MC to terminal communication mode command .............................. #4
`
`I.l
`
`I.2
`
`I.3
`
`I.4
`
`Sample conference Scenario A ..................................................................... ..
`
`CommunicationModeTable sent to all endpoints ......................................... ..
`
`Sample conference Scenario B ..................................................................... ..
`
`CommunicationModeTable sent to all endpoints ......................................... ..
`
`Appendix II — Transport level resource reservation procedures ............................................ .4
`ll. 1
`Introduction .................................................................................................. U4
`
`II2
`
`II3
`
`QoS support for H.323 ................................................................................. ..
`
`RSVP background ........................................................................................ ..
`
`viii
`
`ITU-T Rec. H.323 (06/2006)
`
`Page
`
`239
`
`239
`23 9
`
`23 9
`
`240
`
`240
`
`241
`241
`
`241
`
`U1-I3-IA-IA
`
`2--
`
`24
`
`24
`
`2--
`‘F’
`
`l\)l\)l\)
`
`[0—l\
`
`.J3-l\J:.0000\}\]O‘\O\O\U!
`
`l\)—l\
`
`MS_Biscotti_0073090
`
`Petitioner Microsoft - Ex. 1026, p. viii
`
`
`
`114
`
`115
`
`11.6
`
`11.7
`
`11.8
`
`The H.245 capability exchange phase ........................................................ ..
`
`Open logical channel and setting up reservations ....................................... ..
`
`Close logical channel and tearing down reservations................................... ..
`
`Resource reservation for multicast 1-1.323 logical channels ......................... ..
`
`Synchronized RSVP ..................................................................................... ..
`
`Appendix 111- Gatekeeper—based user location ..................................................................... ..
`111.1
`lntroducti on .................................................................................................. ..
`
`111.2
`
`Signalling ................................................................................................... ..
`
`Appendix IV — Signalling prioritized alternative logical channels in H.245 ......................... ..
`IV. 1
`Introduction .................................................................................................. ..
`
`1V.2
`
`Signalling .................................................................................................. ..
`
`Appendix V — Use of E164 and ISOHEC 11571 numbering plans _____________________________________ _.
`
`V. 1
`V.2
`
`V.3
`
`E. 164 numbering plan .................................................................................. ..
`Private network number ............................................................................... ..
`
`H.323 version