1 / 45

Gathering of State Networks February 6, 2002

Gathering of State Networks February 6, 2002. IP VIDEO ISSUES. IP VIDEO ISSUES AGENDA. BACKGROUND QUALITY OF SERVICE (QoS) CODECS GATEKEEPERS/GATEWAYS DIAL PLAN DIRECTORY SERVICES. BACKGROUND. TWO-WAY INTERACTIVE VIDEO ATM VIDEO (H.321) 1998 ISSUES COST OF END POINT EQUIPMENT

meryle
Download Presentation

Gathering of State Networks February 6, 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gathering of State NetworksFebruary 6, 2002 IP VIDEO ISSUES

  2. IP VIDEO ISSUES AGENDA • BACKGROUND • QUALITY OF SERVICE (QoS) • CODECS • GATEKEEPERS/GATEWAYS • DIAL PLAN • DIRECTORY SERVICES

  3. BACKGROUND • TWO-WAY INTERACTIVE VIDEO • ATM VIDEO (H.321) 1998 • ISSUES • COST OF END POINT EQUIPMENT • DESKTOP EQUIPMENT COST • CURRENTLY – 165 ENDPOINTS ON NETWORK • FOR CONVERGED NETWORKS ONLY GAME IN TOWN

  4. BACKGROUND • H.323 – IP VIDEO 1999 • PRODUCTS AVAILABLE • IP ACCESS ALREADY IN PLACE • COSTS OF ENDPOINTS MUCH CHEAPER • MORE DESKTOP SOLUTIONS AVAILABLE

  5. BACKGROUND • MCU TESTING – FALL 1999 • Accord , Ezenia, Radvision • Operability issues • Performance • CONCLUSION: TECHNOLOGY TOO IMMATURE FOR A RELIABLE PRODUCTION IMPLEMENTATION

  6. BACKGROUND • H.323 – IP VIDEO 2001 • MCU TESTING – FALL 2000 RESULT: THEY ACTUALLY WORK!! • RECOMMENDATION: Accord MGC 100 • NEED TO LOOK AT THE VARIOUS ISSUES AND COMPONENTS NEEDED TO IMPLEMENT H.323 ON THE NETWORK – IP VIDEO TASK FORCE

  7. QoS (Quality of Service) • What is QoS • Set of techniques to manage network resources in a manner which enables the network to differentiate traffic based on policy • Why implement QoS • Provide reliable and guaranteed delivery of service to users • Bandwidth is not the complete solution

  8. Quality of Service • Challenges providing QoS for IP video • Head of line blocking (HOLB) • IP video uses UDP (universal datagram protocol) for transport of video and only uses TCP for control data – can’t resend lost video packets • Video uses large, variable length packets

  9. Video Conferencing Traffic Packet Size Breakdown 384 kbps Video Call 1%65-128 Bytes 37%1025-1518 Bytes 8%257-512 Bytes 34%129-256 Bytes 20%513-1024 Bytes Courtesy Cisco Systems Inc.

  10. Routingetc. Data Voice Video Provisioning Video Data Rate + 20% = Bandwidth Required Video Data RateBW Required 128kbps = 153kbps 384kbps = 460kbps < 33% of Link Capacity 512kbps = 614kbps < 75% of Link Capacity 768kbps = 921kbps Link Capacity 1.5Mbps = 1.8Mbps “Recommendations” Courtesy Cisco Systems Inc.

  11. CODECs

  12. Requirements • That a vendor have both a desktop (PC based) and a room system in their product line • Support interoperability • Ease of Support • Financial considerations

  13. What We Looked At • Cameras (Fixed and Pan/Tilt/Zoom) • Appliance based • PC based • Ease of installation • Ease of configuration • Chair Control • Far end camera control • MCU capability • QoS

  14. Types of Codecs Tested • Room Systems • Polycom • VCON • VTEL • Tandberg

  15. Types of Codecs Tested cont’d • Desktop Systems (PC Based) • Polycom • VCON

  16. Recommendations • Room Systems • Polycom Viewstation FX (Appliance Based) • VCON Media Connect 8000 (PC Based) • Desktop Systems (PC Based) • Polycom ViaVideo • VCON ViGO, Crusier & Escort

  17. GATEKEEPERS The Brains of an H.323 System

  18. Gatekeeper IP based Address Resolution – Layer 3 Bandwidth Management Call Admission Control (CAC) Call forwarding Technology Prefixes Exist in hierarchies Gateway Can transcode between ISDN, ATM and IP Address Resolution – Layer 2 Difference between Gatekeepers and Gateways

  19. Limitations of Gatekeepers • 4 Levels of Hierarchies • Can have no more than 6 Forwarded Location Requests (LRQ)

  20. IP Video Gatekeeper Hierarchy • Institutional Gatekeepers • 2 levels of hierarchy • Zone = Area Code • Gatekeepers placed at current network nodes • ITN Directory Gatekeeper

  21. DIAL PLAN To DID or Not to DID?

  22. Why Do We Need A Dial Plan? • To support legacy ISDN and ATM codecs • To enable a seamless connection between codecs in various parts of the state. • To let people off net to be able to call IP codecs on net (Inbound calls) • USER FRIENDLY

  23. ITN Dial Plan • E[*T]ZZZNNNNNNN • E = Exit Zone Prefix. “1” • *T = Technology Prefix (Optional) • ZZZ = Area Code • NNNNNNN = Seven digit E.164 number

  24. Technology Prefixes • Used for making off net calls to ISDN codecs • *9 – Single channel voice only call • *6 – 6-B 64 KB ISDN call or 384 kbps • *2 – 2-B 64 KB ISDN call or 128 kbps • *3 – 2-B 64 KB ISDN restricted to 56 KB call or 112 kbps

  25. Common Failures of Video Calls Within the ITN Network • Unit has not been rebooted for several days • PC NIC is not set for 100 Mbps – Full Duplex • LAN is not set for 100 Mbps – Full Duplex • Video call is not set up through a gatekeeper • Gatekeeper not properly configured • WAN is not set for 100 Mbps – Full Duplex

  26. Common Failures of Video Calls Outside the ITN Network • ISDN Cloud • Internet Cloud • WAN is not set for 100 Mbps – Full Duplex • Gatekeeper not properly configured • Video call is not set up through a gatekeeper • LAN is not set for 100 Mbps – Full Duplex • PC NIC is not set for 100 Mbps – Full Duplex • Unit has not been rebooted for several days • LAN is not set for 100 Mbps – Full Duplex

  27. Directory Services How Do I Find You

  28. Two types of Directories • Lightweight Directory Access Protocol - LDAP • Click To Meet

  29. LDAP • Contains information on endpoints • Runs on Unix platform • Can connect to a global directory service • Does not connect to gatekeepers • Will interact with First Virtual Communications Click To Meet in future versions

  30. Click To Meet - CTM • Designed specifically for multimedia applications • Works with VTEL, TANDBERG, VCON, POLYCOM, PICTURETEL and ACCORD • Works with ISDN, ATM and IP protocols • Can schedule calls in advance • T.120 application sharing and whiteboards

  31. CTM – Cont’d • Continuous presence built in • Will handle streaming media • Supports firewall NAT/proxy/VPN transversal • Connects to a gatekeeper • Support for Active Directory December 2001 • Subsequent versions will have native LDAP support

  32. Dialing Made Simple Courtesy First Virtual Communications, Inc.

  33. Scheduling Made Simple Courtesy First Virtual Communications, Inc.

  34. Recommendation • First Virtual Communications Click To Meet for use as directory services for ITN

  35. IP Video Task Force Members • Vern Draper, BSU • Fred Nay, BSU, Co-Chair • Mike Huffman, DOE • Alan Benjamin, DoIT • Tim Holt, INCOLSA • Gerry Oliver, ISU • Jeff Steinmiller, ISU • Steve Egyhazi, IU • Doug Pearson, IU • Art Mahan, Ind. Wesleyan

  36. IP Video Task Force Members • Brain Stone, IMCPL • Jason Whiteaker, ITSC • Jerry Sullivan, Intelinet • Chad Miller, Intelinet • Michael Gay, Purdue University • Don Kindred, Purdue University • Pat Smoker, Purdue University • Ed Stanish, Purdue University • Wayne Bohm, USI • Tim Lockridge, USI

  37. IP Video Task Force Members • Carl Koenig, Vincennes University • Ron Dekoker, IHETS • Dave Kaufman, IHETS • Tony McClelland, IHETS • Kevin Siminski, IHETS • Alan Stillerman, IHETS • Ed Stockey, IHETS, Co-Chair • Marty Stricker, IHETS

  38. IP Video Task Force Dial-Plan Committee Members • Vern Draper, BSU • Fred Nay, BSU • Steve Egyhazi, IU • Michael Gay, Purdue University • Earle Nay, Purdue Unviersity • Ron DeKoker, IHETS • Tony McClelland, IHETS • Kevin Siminski, IHETS • Shawn Solomon, IHETS • Alan Stillerman, IHETS, Chair • Ed Stockey, IHETS

  39. How To Reach Us Ed Tully Tully@ind.net 317-263-8922

More Related