/conferences/spr2003/presentations/day_two/edward_stockey ...


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • CIF – common interface format 352X288 pixels QCIF 176X144
  • RAS Registration Admission Status protocol. The communication protocol used to convey registration, admission and status messages between H.323 endpoints and the gatekeeper. RED - Random Early Detection Random Early Detection is a service that tells the router to slow down transmission of packets until all of the packets have reached their destination. During this process, some packets may be dropped. The router resumes speed of transmission after it senses job has reached its destination.
  • PAT – Port Address Translation. Will not work with H.323 or SIP. Any codec or PC could grab a port. The ports cannot be set to any specific device. DHCP – Will work with any PC or codec.
  • DHCP works with any codec.
  • Only version that works with H.323 and Proxy
  • Ready to Go
  • This is a LOGICAL Map.
  • Works with Novel e-directory, Netscapes i-planet CTM Premier V 3.17 does not have good support for ATM
  • This process has enabled us to ensure that faculty, students and other users have a good experience with H.323 video
  • /conferences/spr2003/presentations/day_two/edward_stockey ...

    1. 1. How To Successfully Implement IP Video SURA/ViDE 5 th Annual Digital Video Workshop March 26, 2003 ED STOCKEY IHETS Assistant Director, Product Research And Development
    2. 2. AGENDA <ul><li>HISTORY AND BACKGROUND </li></ul><ul><li>QUALITY OF SERVICE (QoS) </li></ul><ul><li>FIRE WALLS & PROXYS </li></ul><ul><li>GATEKEEPERS/GATEWAYS </li></ul><ul><li>DIAL PLAN </li></ul><ul><li>CODECS </li></ul><ul><li>DIRECTORY SERVICES </li></ul><ul><li>REGISTRATION/SCHEDULING </li></ul>
    3. 3. IHETS: Basics <ul><li>Indiana Higher Education Telecommunication System </li></ul><ul><li>Consortium of all accredited public and private postsecondary institutions in Indiana </li></ul><ul><li>Created by enabling legislation in 1967 </li></ul><ul><li>INDNET begun 1995 </li></ul><ul><li>IHETS becomes Manager of the Indiana Telecommunications Network 1997 </li></ul><ul><li>ITN serves all public institutions – this includes: </li></ul><ul><li>Higher Education, K-12 schools, Public Libraries, State, County and Local government </li></ul><ul><li>Total Sites Connected to ITN > 1,800 </li></ul>
    4. 5. BACKGROUND <ul><li>TWO-WAY INTERACTIVE VIDEO </li></ul><ul><ul><li>H.323 – IP VIDEO 2001 </li></ul></ul><ul><ul><ul><li>MCU TESTING – FALL 2000 </li></ul></ul></ul><ul><ul><ul><li>RESULT: THEY ACTUALLY WORK!! </li></ul></ul></ul><ul><ul><ul><li>RECOMMENDATION: Accord MGC 100 </li></ul></ul></ul><ul><li>NEED TO LOOK AT THE VARIOUS ISSUES AND COMPONENTS NEEDED TO IMPLEMENT H.323 ON THE NETWORK – IP VIDEO TASK FORCE </li></ul>
    5. 6. Quality of Service (QoS) <ul><li>Challenges providing QoS for IP video </li></ul><ul><ul><li>Head of line blocking (HOLB) </li></ul></ul><ul><ul><li>IP video uses UDP (universal datagram protocol) for transport of video and only uses TCP for control data – cannot resend lost video packets </li></ul></ul><ul><ul><li>Video uses large, variable length packets </li></ul></ul><ul><li>Bandwidth is not the complete solution </li></ul>
    6. 7. Video Conferencing Traffic Packet Size Breakdown (CIF) 37% 1025-1518 Bytes 20% 513-1024 Bytes 34% 129-256 Bytes 1% 65-128 Bytes 8% 257-512 Bytes 384 kbps Video Call VVT-230 2917_05_2001_c1 ©2001, Cisco Systems, Inc. All rights reserved
    7. 8. Video Data Rate + 20% = Bandwidth Required 128kbps = 153kbps 384kbps = 460kbps 512kbps = 614kbps 768kbps = 921kbps 1.5Mbps = 1.8Mbps Video Data Rate BW Required Provisioning < 33% of Link Capacity < 75% of Link Capacity Link Capacity “ Recommendations” VVT-230 2917_05_2001_c1 ©2001, Cisco Systems, Inc. All rights reserved Video Voice Data Routing etc.
    8. 9. Quality of Service - Approaches <ul><li>Big Pipes </li></ul><ul><li>QoS </li></ul><ul><li>Both </li></ul>
    9. 10. QoS – How We Do It <ul><li>ACLs (access control lists) </li></ul><ul><ul><li>to identify traffic and set IP precedence. For video and/or voice precedence is set to 5. </li></ul></ul><ul><li>Service policies push traffic into: </li></ul><ul><ul><li>Low latency queuing (Priority queue) </li></ul></ul><ul><ul><li>Reserve bandwidth for RAS </li></ul></ul><ul><ul><li>Data queues which use RED </li></ul></ul><ul><li>Caveat – hardware limitations – </li></ul><ul><li>example: Cisco 25xx routers </li></ul>
    10. 11. QoS <ul><li>Bandwidth guarantees for a </li></ul><ul><li>T1 (1.544 Mbps): </li></ul><ul><li>512 kb/s for video </li></ul><ul><li>128 kb/s for voice </li></ul><ul><li>64 kb/s for SNA </li></ul><ul><li>Remainder for everything else </li></ul>
    11. 12. FIRE WALLS <ul><li>Used to block traffic by disabling ports that allow traffic to come in to a users intranet. </li></ul><ul><li>Usual strategy </li></ul><ul><ul><li>Incoming: Block everything coming in. Open ports only as necessary based on need. </li></ul></ul><ul><ul><li>Outgoing: Allow everything. </li></ul></ul><ul><li>H.323 Video requires the following ports to be open in both directions to allow for optimal two way videoconferencing. </li></ul><ul><ul><li>1718, 1719, 1720 </li></ul></ul>
    12. 13. PROXYS <ul><li>Allows a user to be anonymous to the outside world. </li></ul><ul><li>Acts as a filter for incoming traffic. </li></ul><ul><li>Requires a proxy server on both sides of firewall for H.323 video </li></ul>
    13. 15. FIRE WALLS <ul><li>Tested and Certified </li></ul><ul><ul><li>CISCO PIX V.6.2 </li></ul></ul><ul><li>Currently Being Tested </li></ul><ul><ul><li>NetScreen </li></ul></ul><ul><ul><li>Checkpoint </li></ul></ul><ul><ul><li>Cisco IOS Firewall </li></ul></ul><ul><ul><li>Sonic Wall </li></ul></ul><ul><li>Firewalls that will not work with H.323 </li></ul><ul><ul><li>Novell Border Manager </li></ul></ul>
    14. 16. IP Video Gatekeeper Hierarchy <ul><li>Institutional Gatekeepers </li></ul><ul><ul><li>2 levels of hierarchy </li></ul></ul><ul><li>Gatekeepers located on node routers </li></ul><ul><li>IHETS Directory Gatekeeper </li></ul><ul><li>National Gatekeeper </li></ul><ul><li>International Gatekeeper </li></ul>
    15. 18. INDnet Dial Plan <ul><li>E[T]CCCZZZNNNNNNN </li></ul><ul><li>E = Exit Zone Prefix. “1” (Optional) </li></ul><ul><li>T = Technology Prefix (Optional) </li></ul><ul><li>CCC = Country Code </li></ul><ul><li>ZZZ = Area Code </li></ul><ul><li>NNNNNNN = Seven digit E.164 number </li></ul><ul><li>Based on North American Numbering Plan (NANP) </li></ul>
    16. 19. Dial Plan <ul><li>Dialing between all protocols supported </li></ul><ul><li>13 digit E.164 number required in order to register with IHETS core gatekeeper </li></ul><ul><li>First three numbers must match a valid country code as defined by E.164 ITU-T standard. (Default will be 001 for all calls made in the US and its territories) </li></ul><ul><li>Next three numbers must match a valid area code as defined by NANP </li></ul><ul><li>Next seven digits can be either: a user defined number or a valid seven digit Direct Inward Dial (DID) number such as the phone number on their desk </li></ul>
    17. 20. Dial Plan <ul><li>Seven digit number on desk ensures uniqueness of 13 digit number within an area code </li></ul><ul><li>Technology prefix required in order to dial off net to ISDN endpoint </li></ul><ul><li>Automatically scales to national and international dial strings based on E.164 </li></ul><ul><li>Allows for future migration to ENUM standard when implemented </li></ul><ul><li>GDS Compliant </li></ul>
    18. 25. Codec Recommendations <ul><li>That a vendor have both a desktop (PC based) and a room system in their product line </li></ul><ul><li>Support interoperability </li></ul><ul><li>Ease of Support </li></ul><ul><li>Financial considerations </li></ul><ul><li>Based on IPVTF </li></ul>
    19. 26. Codec Recommendations <ul><li>Room Systems </li></ul><ul><ul><li>Polycom Viewstation FX (Appliance Based) </li></ul></ul><ul><ul><li>VCON Media Connect 8000 (PC Based) </li></ul></ul><ul><li>Desktop Systems (PC Based) </li></ul><ul><ul><li>Polycom ViaVideo </li></ul></ul><ul><ul><li>VCON ViGO </li></ul></ul><ul><li>Based on IPVTF </li></ul>
    20. 27. DIRECTORY SERVICES Click To Meet TM <ul><li>Connects Point-to-Point any protocol </li></ul><ul><ul><li>IP – ATM, IP – ISDN, ATM - ISDN </li></ul></ul><ul><li>Creates multipoint conferences on the fly </li></ul><ul><li>Can schedule Point-to-Point or multipoint conferences in the future </li></ul><ul><li>Sends out e-mails notifying end users of upcoming meetings </li></ul><ul><li>Can program all calls to go through a gateway or bridge </li></ul>
    21. 28. DIRECTORY SERVICES Click To Meet TM <ul><li>Continuous presence built in </li></ul><ul><li>Will handle streaming media </li></ul><ul><li>Supports firewall NAT/proxy/VPN transversal </li></ul><ul><li>Connects to a gatekeeper </li></ul><ul><li>CTM Premier V 3.17 uses Microsoft’s Active Directory for user accounts </li></ul><ul><ul><li>LDAP support provides the capability to support connectivity to external, 3 rd party data stores like Novell’s eDirectory, Sun ONE Directory Server (formerly iPlanet LDAP Server) and Netscape’s Directory Server </li></ul></ul>
    22. 29. Dialing Made Simple Courtesy First Virtual Communications, Inc.
    23. 30. Scheduling Made Simple Courtesy First Virtual Communications, Inc.
    24. 31. REGISTRATION AND CERTIFICATION <ul><li>http://www.ihets.org/network/ipvideo/ctm/index.html </li></ul><ul><li>Allows QoS to be enabled on the edge and core routers </li></ul><ul><li>Provides data for directory entry </li></ul><ul><li>Verified by Point-to-Point and multipoint test calls </li></ul><ul><li>For more information on IP Video and the Certification process go to http://research.ihets.org/research/ ipvc/ipvideo_home.jsp </li></ul>
    25. 32. How To Reach Us <ul><li>Ed Stockey </li></ul><ul><li>Assistant Director, Product Research and Development </li></ul><ul><li>[email_address] </li></ul><ul><li>317-263-8943 </li></ul>