ITU-T H.323 System Implementers Guide
INTERNATIONAL TELECOMMUNICATION UNIONITU-TH.323 SystemImplementers GuideTELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(30 May 2003)SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services – CommunicationproceduresImplementors Guide for Recommendations ofthe H.323 System:H.323, H.225.0, H.245, H.246, H.283, H.235, H.341,H.450 Series, H.460 Series, and H.500 SeriesAttention: This is not a publication made available to the public, but an internal ITU-T Document intended only for use by theMember States of the ITU, by ITU-T Sector Members and Associates, and their respective staff and collaborators in their ITUrelated work. It shall not be made available to, and used by, any other persons or entities without the prior written consent of theITU-T.
SummaryThis document is a compilation of reported defects identified in the versions of ITU-TRecommendation H.323 and its related Recommendations currently in force. It must be read inconjunction with the Recommendations to serve as an additional authoritative source of informationfor implementers. The changes, clarifications and corrections defined herein are expected to beincluded in future versions of affected H.323-series Recommendations.This revision contains all updates submitted upto and including those at Study Group 16 meeting inMay, 2003, in Geneva. This Implementor’s Guide provides corrections and clarifications forimplementations of the H.323 system V.4 and supersedes the earlier version approved by StudyGroup 16 in October 2002.Implementers Guide for ITU-T H.323 Systems (2003-05)i
Change LogN/AiiImplementers Guide for ITU-T H.323 Systems (2003-05)
Contact InformationITU-T Study Group 16 /Rapporteur Question 2/16Paul E. JonesCisco Systems, Inc.7025 Kit Creek RoadResearch Triangle Park, NC 27709. USATel:Fax:E-mail: 1 919 392 6948 1 919 392 2177paulej@packetizer.comITU-T Study Group 16 /Rapporteur Question 3/16Christian GrovesEricsson Australia Pty. Ltd.37/360 Elizabeth StreetVictoria 3000. AustraliaTel:Fax:E-mail: 61 3 9301 6116 61 3 9301 1499Christian.Groves@ericsson.comITU-T Study Group 16 /Rapporteur Question G/16Martin EuchnerSiemens AG / ICN M NT 18Hofmannstr. 51D-81359 Muenchen. GermanyTel:Fax:E-mail: 49 89 722 5 57 90 49 89 722 4 68 41martin.euchner@ties.itu.intEditor ITU-T Rec. H.341Craig BlasbergCisco Systems, Inc.7025 Kit Creek RoadResearch Triangle Park, NC 27709. USATel:Fax:E-mail: 1 919 392 5760 1 919 392 6801blasberg@cisco.comEditor ITU-T Rec. H.225.0Vivek BhargavaCisco Systems, Inc.7025 Kit Creek RoadResearch Triangle Park, NC 27709. USATel:Fax:E-mail: 1 919 392 6823 1 919 392 2177vbhargava@cisco.comEditor ITU-T Rec. H.225.0Annex GMiner GleasonCisco Systems, Inc.7025 Kit Creek RoadResearch Triangle Park, NC 27709. USATel: 1 919 392 8752Fax: 1 919 392 7065E-mail: mgleason@cisco.comEditor ITU-T Rec. H.245Mike NilssonBT LabsIpswitch. United KingdomTel:Fax:E-mail: 44 1 473 645413 44 1 473 643791mike.nilsson@bt.comITU-T Study Group 16 /Rapporteur Question 5/16 &Editor ITU-T Rec. forH.450.{1,2,3,4,5, 6,9,10,11,12}Ernst HorvathSiemens AustriaGudrunstrasse 11A-1101 Vienna. AustriaTel:Fax:E-mail: 43 5 1707 45897 43 5 1707 56992ernst.horvath@siemens.atEditor ITU-T Rec. H.450.7Dave WalkerSS8 Networks135 Michael Cowpland Drive, Suite 200Kanata, Ontario, K2M 2E9. CanadaTel:Fax:E-mail: 1 613 592 8450 1 613 592 9634dwalker@ss8networks.comEditor ITU-T Rec. H.450.8Glen FreundlichAvaya Communication1300 W. 120th AvenueWestminster, CO 80234. USATel:Fax:E-mail: 1 303 538 2899 1 303 538 3007ggf@avaya.comEditor ITU-T Rec. H.460.1Editor ITU-T Rec. H.460.4Editor ITU-T Rec. H.460.5Editor ITU-T Rec. H.460.6Editor ITU-T Rec. H.460.{2,7,8}Editor ITU-T Rec. H.460.3Editor ITU-T Rec. H.460.9P. CordellGary ThomSasha RuditskyBob GilmanPaul Jones (see above for Q.2/16)Louis FourieErnst Horvath (see above for omlfourie@cisco.comernst.horvath@siemens.atEditor ITU-T Rec. H.235Editor ITU-T Rec. H.323 andImplementer's GuideNote: Not all Recommendations indicated above have IG issues in this document. The information above is provided for completeness.Implementers Guide for ITU-T H.323 Systems (2003-05)iii
Table of Contents1SCOPE. 12INTRODUCTION . 14REFERENCES. 15NOMENCLATURE. 26TECHNICAL AND EDITORIAL CORRECTIONS TO H.323 SERIES RECOMMENDATIONS . 36.1TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.323 (2000). 36.1.1H.323 Annex L Section 3.4 . 36.1.2Calling party address information Correction . 36.1.3Status/Status Inquiry messages without explicit Call Identifiers . 46.1.4Corrections to the H.323 URL Syntax . 56.1.5H.323v4 Editorial Correction. 56.1.6Pairing of RTP streams for a common bi-directional RTCP channel . 66.1.7H.323 Annex M.1 Section 3 . 76.1.8Editorial Correction . 86.1.9Normative References Update . 86.1.10 Sending of BRQ messages. 86.1.11 Third Party Initiated Pause and Re-routing . 96.1.12 Fast Connect Session IDs . 106.1.13 Restart in RRQ . 106.1.14 Alternate Gatekeeper Procedures in URQ. 116.1.15 Clarification on usage of RFC 2833 in fast connect by using parallel H.245 procedure. 116.2TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.225.0 (2000). 126.2.1Registration Request (RRQ) Corrections. 126.2.2Section 7.6 H.225.0 Common Message Elements Correction. 126.2.3Annex H H.225.0 Message Syntax (ASN.1) Corrections. 136.2.4Clarification for the usage of rasAddress . 146.2.5ReleaseCompleteReason to Cause IE mapping . 146.2.6Clarification for sending PNP numbers in Information messages. 156.2.7Clarification for using Bearer Capability IE in Connect and Progress messages . 166.2.8Clarification on GK response to additive registration requests . 176.2.9Progress Indicator in Setup Message . 186.2.10 Additions to Q.931 timers usage in H.225.0 . 196.2.11 ASN.1 specification error for URQ. 206.2.12 Clarifying the semantics of destCallSignalAddress in ACF for answerCall ARQ . 216.2.13 Clarifying the semantics of sourceInfo in LRQ message . 216.3TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.245 (2/2003) . 216.3.1Annex B Section 3.1 Open Logical Channel. 216.4TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.246 (1998). 226.4.1Annex A Corrections. 226.4.2Reference to ATM Forum Document . 236.5TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.235 (2000). 246.5.1Section 5 – Conventions. 246.5.2Section 7.0 - Connection Establishment Procedures . 256.5.3Section 8.1 - Security in H.245 Control Channel Operations. 256.5.4Section 8 & Annex D Section 7 - Key Management. 256.5.5Section 8.8 – Diffie-Hellman Operation . 276.5.6Section 11.2 - Media Stream Encryption Procedures. 296.5.7Annex B Section 3 – RTP/RTCP issues. 296.5.8Annex B Section 3 - RTP/RTCP issues. 296.5.9Annexes B and D - RTP/RTCP issues and Voice Encryption Security Profile . 306.5.10 Annex D Section 7.1 - Key Management . 316.5.11 Annex D Section 7.2 - Key Update and Synchronization. 316.5.12 Annex D Sections 6 and 7 - Usage Illustration for Procedure I, Key update, and synchronization. 31ivImplementers Guide for ITU-T H.323 Systems (2003-05)
6.5.136.5.146.5.156.5.166.5.176.5.18Annexes D and E - Specific Conventions, Key management, and Call signaling. 32Annex D Section 2 – Specification Conventions . 34Annex D Sections 5 and 12 - Normative References and Bibliography. 34Annex D Section 6.1 – Overview. 36Annex D Section 6.1.1 – Baseline Security Profile . 36Annex D Section 6.3.2 – Symmetric-Key Based Signalling Message AuthenticationDetails (Procedure I) . 366.5.19 Annex D Section 6.3.3.2 – Authentication and Integrity. 376.5.20 Annex D Section 6.3.4.2 – H.225.0 message authentication and integrity . 376.5.21 Annex D Section 6.3.4.3 – H.245 message authentication and integrity . 386.5.22 Annex D Section 6.3.1 - Overview . 386.5.23 Annex D Section 6 - Symmetric-Key Based Signalling Message Authentication Details (Procedure I). 396.5.24 Annex D Section 6.3.4.1 - RAS Authentication and Integrity . 406.5.25 Annex D Section 7 - Voice Encryption Security Profile. 406.5.26 Annex D Sections 7.1 and 11 - Key Management. 406.5.27 Annex D Section 7.1 - Key Management . 416.5.28 Annex D Section 7.1 - Key Management . 416.5.29 Annex D Section 7.2 - Key update and synchronization . 426.5.30 Annex D Section 7.1 - Key Management . 426.5.31 Annex D Section 7.2 – Key update and synchronization . 446.5.32 Annex D Section 11 - List of Object Identifiers . 446.5.33 Annex D Section 11 – List of Object Identifiers. 456.5.34 Annex E Section 2 – Conventions . 466.5.35 Annex E Section 4 - Security Services. 466.5.36 Annex E Section 5 - Digital Signatures with Public/Private Key Pairs Details (Procedure II) . 466.5.37 Annex E Section 5 – Digital Signatures with Public/Private Key Pairs Details (Procedure II). 476.5.38 Annex E Section 7 - End-to-End authentication (Procedure III). 486.5.39 Annex E Section 7 – End-to-End authentication (Procedure III) . 486.5.40 Annex E Section 8 - Authentication-only . 496.5.41 Annex E Section 9 – Authentication and Integrity . 496.5.42 Annex E Section 12 - Security Services. 506.5.43 Annex E Section 12 – Handling of Certificates. 516.5.44 Annex E Section 13 – Usage Illustration for Procedure II . 526.5.45 Annex E Section 13.3 – H.225.0 message authentication, integrity & non-repudiation. 526.5.46 Annex E Section 13.4 – H.225.0 message authentication, integrity & non-repudiation. 526.5.47 Annex E Section 18 – List of Object Identifiers . 536.5.48 Annex F Section 2 - Normative References. 536.5.49 Annex F Section 4 Specification conventions . 546.5.50 Annex F Section 6 – Authentication and Integrity . 546.5.51 Annex F Section 6 - Authentication and Integrity. 556.5.52 Annex F Section 7 - Procedure IV . 566.5.53 Annex F Section 13 – List of Object Identifiers . 576.5.54 Appendix I Section 1 - Ciphertext padding methods. 576.5.55 Appendix I Section 4.6 - Back-end Service Support . 586.6TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.450 SERIES . 596.6.1Technical and Editorial Corrections to ITU-T Recommendation H.450.1 (1998) . 596.6.2Technical and Editorial Corrections to ITU-T Recommendation H.450.2 (1998) . 616.6.3Technical and Editorial Corrections to ITU-T Recommendation H.450.3 (1998) . 636.6.4Technical and Editorial Corrections to ITU-T Recommendation H.450.4 (1999) . 656.6.5Technical and Editorial Corrections to ITU-T Recommendation H.450.5 (1999) . 666.6.6Technical and Editorial Corrections to ITU-T Recommendation H.450.6 (1999) . 666.6.7Technical and Editorial Corrections to ITU-T Recommendation H.450.7 (1999) . 666.6.8Technical and Editorial Corrections to ITU-T Recommendation H.450.8 (2000) . 676.6.9Technical and Editorial Corrections to ITU-T Recommendation H.450.9 (2000) . 676.6.10 Technical and Editorial Corrections to ITU-T Recommendation H.450.10 (2000) . 676.6.11 Technical and Editorial Corrections to ITU-T Recommendation H.450.11 (2000) . 676.6.12 Technical and Editorial Corrections to ITU-T Recommendation H.450.12 (2001) . 676.7TECHNICAL AND EDITORIAL CORRECTIONS TO ITU-T RECOMMENDATION H.341 (1999). 716.7.1Corrections to the RAS MIB in H.341 . 716.7.2Support for Expanded Country Code Values in T.35. 726.8TECHNICAL AND EDITORIAL CORRECTIONS TO ANNEX G/H.225.0 (2002) . 73Implementers Guide for ITU-T H.323 Systems (2003-05)v
6.9TECHNICAL AND EDITORIAL CORRECTIONS TO ANNEX C/H.246 (2000). 736.9.1Additional Message Mappings. 736.9.2Changes for Call Diversion .
Editor ITU-T Rec. H.341 Craig Blasberg Cisco Systems, Inc. 7025 Kit Creek Road Research Triangle Park, NC 27709. USA Tel: 1 919 392 5760 Fax: 1 919 392 6801 E-mail: blasberg@cisco.com Editor ITU-T Rec. H.225.0 Editor ITU-T Rec. H.323 and Implementer’s Guide Vivek Bhargava
R 323.1151 to R 323.1159, R 323.1162 to R 323.1164, and R 323.1169 of the Code are rescinded to read as follows: PART 5. SPILLAGE OF OIL AND POLLUTING MATERIALS . R 323.1158 Rescinded . R 323.1151 Rescinded R 323.1159 Rescinded R 323.1152 Rescinded R 323.1162 Rescinded R 323.1153 Rescinded R 323
USP Health and Wellness Centre ( 679) 323 2362 / 323 2202 USP Security Main Gate ( 679) 323 2211 ext 122 Pedestrian Gate ( 679) 323 2211 ext 121 Back Gate ( 679) 323 2211ext 120 Control Room (after hours) ( 679) 323 2211/ 323 2840 EMALUS CAMPUS, VANUATU Hospital ( 678) 22100 Ambulance - Hospital 112 Emergency - Promedical Ambulance 115
NiIr/Cr2O3 323 0.5 6.0 247.9a S7 Ni0.6Pt0.4/MSC-30 303 0.6 6.0 240a S8 Ni0.9Pt0.1/graphene 323 0.5 6.0 240b S9 Ni0.9Pt0.1-CeO2 323 0.5 5.74 234b S10 Cu0.4Ni0.6Mo 323 2.0 6.0 108b S11 Ni@(RhNi-alloy)/Al2O3 323 without 5.74 72.0a S12 Ni5@Pt 323 without 4.4 2.3a S13 aThe total TOF values were
International Triathlon Union ITU Competition Rules 10-12-2017 1 ITU Competition Rules Approved by the ITU Executive Board, in December 2017 Green highlight - added as of December 2017 Red highlight - deleted as of December 2017 The ITU Competition Rules is the master source document, found on ITU's website at www.triathlon.org.
1. ITU Level 1 Triathlon Coach 2. ITU Level 2 Triathlon Coach 3. ITU Performance Development Triathlon Coach (L2 Extension Programme - invitation only) ITU Coach Education Programmes - Level Descriptors ITU Level 1 Triathlon Coach ITU Level 1 coaches will be able to deliver triathlon sessions to groups of triathletes without supervision.
1 School Phone Number: 754 323 6250 Fax Number: 754 323 6290 Attendance Line: 754 323 6252 Keep your contact info up to date in the front office to receive
9th WTI Meeting Port Louis, Mauritius, 7-9 December 2011 Final List of Participants 1) Member States 2) Resolution 99 (Rev. Guadalaraja 2010) 3) ITU-D Sector Members — Recognized Operating Agencies 4) ITU-D Sector Members — Scientific or Industrial Organizations 5) ITU-D Sector Members — Other Entities dealing with Telecommunications 6) ITU-D Sector Members — Regional and other .
English Language Arts Model Curriculum with Instructional Supports . Code . Standard . Reading Standards for Literature Key Ideas and details . RL.2.1 . Ask and answer such questions as who, what, where, when, why, and how to demonstrate understanding of key details in a text. RL.2.2 : Analyze literary text development. a. Determine the lesson or moral. b. Retell stories, including fables and .
