Transcript
IOCOM Grid Collaboration Software Technical Paper February, 2008
inSORS Integrated Communications, Inc. dba IOCOM 111 West Jackson Blvd Suite 1412 Chicago, IL 60604 312-786-9169 www.IOCOM.com
Confidentiality Statement This document may contain service or pricing related information, which, if disclosed to third parties, can have a detrimental effect on IOCOM. Such information is provided in confidence and is intended solely for the use of the named recipient and should not be disclosed to any third party for a period of at least one (1) year from the date of this document.
Table of Contents EXECUTIVE SUMMARY .............................................................................................1 OVERVIEW ...................................................................................................................2 IG UCS .......................................................................................................................3 IG CLIENT .................................................................................................................4 DEPLOYING IOCOM....................................................................................................7 Ultra Mobile Personal Computers (UMPC’s)...............................................................8 Laptop and Desktop Personal Systems.........................................................................9 Small Group/Mobil Systems......................................................................................10 Conference Rooms/Modular Systems ........................................................................11 Command Centers .....................................................................................................12 NETWORK REQUIREMENTS....................................................................................13 UCS Bandwidth Requirements ..................................................................................13 Client Bandwidth Requirements ................................................................................14 Codecs.......................................................................................................................15 Firewall Settings, QoS, Proxy and Encryption Settings ..............................................16 Security - Firewall Settings........................................................................................16 Quality of Service (QoS) ...........................................................................................16 Proxy Settings ...........................................................................................................17 Encryption.................................................................................................................17 MANAGEMENT ..........................................................................................................18 Access .......................................................................................................................18 Usage Statistics .........................................................................................................18 Limits: Meeting Settings............................................................................................20 Limits: UCS Master Settings .....................................................................................21 INTEROPERATION.....................................................................................................22 H.323 ........................................................................................................................23 SIP ............................................................................................................................24 PSTN ........................................................................................................................25 ISDN.........................................................................................................................26 APPENDIX A – Bandwidth Calculations ......................................................................27 APPENDIX B – Firewall Configurations ......................................................................30 Cisco Firewall Configurations ...................................................................................30 Checkpoint Firewall Configurations ..........................................................................30 Other Firewall Configurations ...................................................................................31
EXECUTIVE SUMMARY The IOCOM Grid (IG) multimedia collaboration platform is a scalable, adaptable, software solution enabling geographically distant users to easily and reliably meet face to face in rich collaborative environments. In addition to robust scheduling and presence components, IG’s advanced audio, video, and data sharing tools provide an unparalleled multipoint video conferencing experience. IG’s unique method of centrally managing multiple streams enhances the user experience by allowing customization of meeting environments based on their current system and network capabilities. The IG software solution is an IP network based client and server application. The IG Unified Collaboration Server (UCS) runs on commodity hardware running the Linux (i.e., RHEL) operating system. An IG UCS is grid architected and can be readily scaled with commodity hardware to increase capacity while still functioning as a single centralized system. IG client software runs on commercially available computers and operating systems and likewise uses commodity audio-visual display systems. This document provides an overview with examples of deployments. Network requirements, management tools and interoperability with existing communications are also covered.
inSORS Integrated Communications, dba IOCOM
OVERVIEW The IG Platform delivers a superior, secure, real-time, interactive, multi-point voice and video meeting experience. IG software connects virtually everything from auditoriums and offices to hand held computers and smart phones. The Unified Collaboration Server or UCS is at the core of the IG platform. The IG UCS is a Linux based software application that coordinates connections between multiple IG software clients and other compatible video/audio endpoints. Room systems, desktops, telephones, and ISDN/H.323/SIP endpoints can all collaborate with each other, even in the same meeting, via an IG UCS.
IG client software runs on Windows XP/Vista and Mac OS X and connects to the IG UCS over standard IP based networks. The IG Client may be licensed to run in environments ranging from a notebook computer with a single USB camera up to a large conference room system with multiple cameras.
inSORS Integrated Communications, dba IOCOM
page 2
Please refer to the sections that follow for a more detailed summary of IG UCS and IG Client functionality.
IG UCS The IG Unified Collaboration Server (UCS) runs on RedHat Enterprise Linux. An IG UCS may be configured to run autonomously on a single computer or configured to run in a grid configuration across multiple computers. There are several advantages to IG architecture over traditional MCU solutions: •
Since an IG UCS is deployed on commodity hardware, it’s more easily and inexpensively replaced. Traditional video conferencing infrastructure typically requires several different appliances which significantly increases the administration and replacement cost of these systems.
•
Lower support cost through a common user interface running on a standard operating (e.g., RHEL4) system. In traditional video conferencing environments, the costs for training are higher as administrators must learn different interfaces for each proprietary appliance.
•
Bandwidth costs are lowered and performance improved by configuring the IG UCS to run in federated mode. In a federated configuration, IG Client sites may connect to the geographically closest UCS, yet seamlessly initiate meetings with sites connected to geographically distant servers. All audio/video/data traffic, between connected sites, is proxied back and forth between servers communicating over a dedicated high speed network connection. (Availability of this functionality is expected in Q2 2008)
•
Higher scalability as enterprises only need to add additional commodity Linux systems to a distributed computer cluster to increase capacity. Enterprises previously had to make growth decisions early in the deployment phase. Once capacity is reached in a traditional MCU system, the costs of adding additional capacity are extremely high. Decisions such as purchasing a closed box or large chassis system must often be made early in the deployment phase, before it may be apparent what capacity is actually required. IOCOM architecture takes such decisions out of the equation.
inSORS Integrated Communications, dba IOCOM
page 3
•
Higher redundancy as each UCS server may act as backup for other UCS servers on a network. In addition to working in tandem with other servers for load balancing and performance optimization, a UCS may also be configured as an autonomous entity for use in various failover scenarios.
CORE FEATURES • Grid architected solution that scales with the needs of the organization • Interoperates with existing video conferencing infrastructure
• Web based management console • Robust usage statistic collection and reporting
• Built-in H323/SIP gateway
• SNMP facilitates monitoring of various UCS conditions
• Connectivity to ISDN and PSTN endpoints via deployed gateways
• Support for multi-point, multiple camera room based systems
• Support for a wide array of endpoints
• Support for desktop/notebook/handheld systems and smart phone devices
• RedHat Enterprise Linux based software solution that is installed on commodity hardware • Integrated presence engine • Support for ODBC compliant databases • Support for deployed LDAP/AD servers
• Integrated firewall traversal technology • Tools for limiting system and network usage on a per-server or per-meetings basis • Support for multicast networks
• Standard and wideband audio codec support • All audio/video/data traffic is sent and received as discreet streams for maximum meeting environment control • Enforces minimum client version and facilitates easy client upgrades • Recurring meeting support • All audio/video/data traffic may be DSCP tagged for QoS classification • Optimized for multi-core CPU systems • Mechanism for recording and storing live meetings for subsequent playback in future meetings
• H.261, H.263, and H.264 video codec support
IG CLIENT IG Client software connects to the IG UCS and provides users with instant access to personal networks. Integrated presence controls provide tools for setting one’s own availability or quickly determining the availability of others for instant meetings. The meeting scheduling component provides granular control on various meeting (e.g., enforced video codecs) parameters as well as other scheduling tools.
inSORS Integrated Communications, dba IOCOM
page 4
IG Client software will interface with any number of different endpoints including other IG Client sites running on room and desktop/notebook systems as well as telephone and ISDN/H.323/SIP endpoints. The meeting environment is readily customizable with various options for transmitting and receiving voice, video, and data as well as desktop layout options for optimizing the meeting experience. Various in-meeting options and tools facilitate rich collaboration environments including desktop sharing, whiteboard exchange, and meeting record/playback, among several other tools.
inSORS Integrated Communications, dba IOCOM
page 5
CORE FEATURES • Support for Windows XP/Vista and Mac OS X • Setup Wizard facilitates quick and optimal node configuration • Meetings may be quickly initiated and managed via an easy to access systray/dock application • Strong encryption support • Integrated firewall traversal technology
• IGMeeting web interface provides alternative means for users to quickly schedule and join meetings
• In-meeting real-time video statistics
• All video windows are drag-resizable and may be placed anywhere on any desktop for an optimal meeting experience
• Files application supports in-meeting file exchange
• Optimized for multi-core CPU systems • H.261, H.263, and H.264 video codec support
• Quickly and easily collaborate with multiple endpoints in the same meeting
• Standard and wideband audio codec support
• Invite dialog provides real-time availability status of users in your personal network
• Audio settings configurable for each site or aggregately for all sites • Desktop sharing support
• User presence and availability settings are fully configurable
• Support for external VGA capture devices
• Support for multiple join meeting modes including Conference (send/receive all video/voice) and View (receive audio/voice without audio/voice transmit) modes among others
• Multiple camera support
• Multiple display/desktop support • PTZ camera support
• Tools for scheduling one-time and recurring meetings with options for easily importing scheduled meetings into your calendar (e.g., Outlook, Notes) of choice • Various options to selectively control audio/video/data meeting traffic (transmitted to/from IG Client) which provide users with means to optimize the meeting experience, even when there are significant network/system limitations
• Dial application supports connection to H.323/SIP/PSTN endpoints
• Whiteboard application facilitates a shared in-meeting drawing space where users may create group editable diagrams, workflow illustrations, and annotated images • Chat application allows meeting participants to exchange simple text messages in meetings • Record application provides means for users to record and play back audio/video content from a meeting • IGPix application captures a snapshot image of your desktop and makes it available to others running IG Client software or via a web URL • PowerPoint integration facilitates sharing .PPT presentations with others running IG Client software or via a web URL • Moderator provides tools to manage meeting time as well as the means to eject or ban sites from meetings or disable audio/video being transmitted from specified sites • Multiple moderator support • Microsoft Office Communicator integration allows users to quickly invite other Communicator users to IG Client instant meetings • IG Client software observes limits set by meeting creators/server administrators on the use of specific codecs and tools
inSORS Integrated Communications, dba IOCOM
page 6
DEPLOYING IOCOM The IOCOM client software runs on off-the shelf, standard computers using Windows XP or Vista operating systems and has four versions: • • • •
Single camera personal desktop license (Mac OS X version also available) Two-camera room license Three-camera room license Four-camera room license
All of these software versions may be installed on workstations, laptops and ultra mobile devices and provide organizations with unparalleled flexibility when deploying communication endpoints. Integrators simply install the software on the PC and connect commodity displays, cameras, and sound systems to the computer. From mobile PCs, laptops, offices, conference rooms and command centers, IOCOM uses the same core software with the same consistent easy to use interface to provide advanced collaboration everywhere.
inSORS Integrated Communications, dba IOCOM
page 7
Ultra Mobile Personal Computers (UMPC’s) Mobile endpoints on UMPC devices use the embedded camera and audio components for visual conferences on the go. A headset/mic is recommended to eliminate echo. Connecting wirelessly via 802.11x, Rev-A or WiMAX technologies, these systems are able to participate in IOCOM meetings with full audio video and data through the standard user interface.
inSORS Integrated Communications, dba IOCOM
page 8
Laptop and Desktop Personal Systems Personal systems include IOCOM one-camera client software installed on desktops or laptops. Off the shelf USB cameras are connected with either a headset and boom microphone, or an echo cancellation microphone (shown below) to give full voice video and data participation. Other PC applications such as OLAPs, Excel, PowerPoint, and Outlook may be used and shared while participating in IOCOM meetings.
inSORS Integrated Communications, dba IOCOM
page 9
Small Group/Mobil Systems IOCOM offers mobile cart systems for use in offices and small conference rooms. The system below includes a dual camera software package installed on a workstation. The computer is placed in cart and connected to a 50-inch Plasma display and two Pan-TiltZoom (PTZ) cameras. Two wireless microphones, speakers and a wireless keyboard and mouse are also included for quick room setup.
inSORS Integrated Communications, dba IOCOM
page 10
Conference Rooms/Modular Systems For larger groups, additional plasmas and cameras may be added. The system below includes the three-camera client software installed on a workstation, a wireless keyboard and mouse, dual 50-inch plasmas, speakers, three PTZ cameras, and two-wireless microphones.
inSORS Integrated Communications, dba IOCOM
page 11
Command Centers The IOCOM cube combines a workstation and a room echo cancellation unit into single integrated unit for easy plug-in connectivity to cameras, microphones, speakers, projectors, and plasma monitors. The cube may be integrated with existing audio visual equipment and works with up to nine microphones, four cameras, and/or four displays. Cube System
In the example below, the command center includes three projectors and four cameras for full room coverage.
inSORS Integrated Communications, dba IOCOM
page 12
NETWORK REQUIREMENTS Simultaneous multiple displays provide a compelling user experience and improve productivity in remote collaborations. IOCOM’s software approach maximizes each participant’s experience based on available resources without impacting the experience or network needs of remote users. IOCOM uniquely manages independent video streams and directs them to any endpoint requesting a particular view. Higher bandwidth locations can simultaneously view all meeting participants while other locations may choose to only view some of the video streams based on their available screen real estate and network capacity. Meeting planners and system administrators may set bandwidth limits on their meetings. Refer to the Management section for more information on specifying UCS limits.
UCS Bandwidth Requirements All audio, data, and video streams are routed to endpoints via the UCS. As such, the UCS needs to be connected to a high speed IP network, with appropriate bandwidth, to support multiple meetings. IOCOM strongly recommends deploying the UCS in datacenters because bandwidth pricing is often dramatically lower than ‘last mile’ IP connectivity. The following points should be considered when calculating UCS bandwidth requirements: •
All audio, data and video streams are routed through the UCS.
•
The number of participants does NOT affect audio bandwidth as audio streams at mixed at the UCS. The UCS sends each client either a single 64Kbs or 128Kbs stream depending on the client’s audio setting.
•
The number of participants does affect video bandwidth because the video streams are not mixed. Each viewed video stream adds to the total UCS bandwidth usage. Factors that affect UCS video bandwidth include o The number of endpoints viewing video o The number of video views displayed at each endpoint o The video codec used with each video stream.
inSORS Integrated Communications, dba IOCOM
page 13
Client Bandwidth Requirements The IOCOM platform was architected under the assumption that endpoints in a meeting will have varying degrees of network and system capabilities. IOCOM software can provide an immersive multi-view meeting environment to endpoints with sufficient bandwidth without excluding endpoints, with more modest capabilities, from participating in the same meeting.. IOCOM does not degrade the performance of all participants because of the network constraint on a particular endpoint. The network requirements will vary for each client endpoint based on the number of cameras views sent and received. •
The minimum bandwidth for each client is 180Kbs and assumes sending and receiving one H.264 (QCIF) video image at 25 frames per second with full audio participation.
•
Upstream bandwidth requirements depend on the local audio and video codec selection and the number of transmitted video streams. See the Codec section for supported codecs.
•
Downstream audio bandwidth usage equals the audio upstream settings. Audio streams from remote participants are mixed and transcoded at the UCS for each site. Within the same multi-point meeting, some locations may receive the standard audio stream while others may receive the enhanced wideband audio stream.
•
Downstream video bandwidth requirements depend on the number of received video streams and the codec used with those streams
•
If an endpoint closes a video image they will reduce their downstream bandwidth usage.
•
The numbers quoted for video codecs are maximums. Actual use varies depending on factors such as the motion in the frames. Real time video usage statistics may be viewed in the Video Statistics dialog.
Please refer to Appendix A for bandwidth usage calculation examples.
inSORS Integrated Communications, dba IOCOM
page 14
Codecs IOCOM software provides a variety of codec options for video transmission. For example, an IOCOM endpoint may be configured to transmit a full motion (30 frames per second) video source at 176x144 resolution. This would require a maximum of 64kbps of bandwidth. The same system, on a very high speed network, could potentially transmit the same video source at HD resolution (e.g., 1280x1024) while still maintaining a 30 fps framerate. This would require significantly more (~20 Mbps) bandwidth. For video sources, such as desktop capture, IG provides codecs that transmit higher resolutions images at lower framerates, while maintaining economical bandwidth usage. Because IOCOM software has the unique ability to simultaneously support multiple video codecs, meetings may be customized to combine different frame rates and/or resolutions. IOCOM software allows each endpoint in a meeting to optimize their meeting environment based on their respective network/system capabilities, or lack thereof. The table below lists IG supported codecs, resolutions, and bandwidth requirements. Codec H.264 Small H.264 Medium
Frame Resolution Rate 30 fps QCIF (176x120) 30 fps
CIF (352 x 240)
Bandwidth
Type
Up to 64Kbs
Video Transmitted from low
Up to 256 Kbps
Video Recommend - Optimal for
bandwidth locations
H.264 Large
30 fps
VGA (640 x 480)
Up to 1Mbs
Video
H.261
30 fps
CIF (352 x 240)
Video
Desktop Capture Desktop Capture Desktop Capture Desktop capture 720p 1080p
1 fps
Native Desktop Res up to 2048x1536 Native Desktop Res up to 2048x1536 Native Desktop Res up to 2048x1536 Native Desktop Res up to 2048x1536 1280 x720 1920 x 1080
Adjustable: Standard up to 800Kbs Up to 128Kbs Up to 256 Kbps Up to 512 Kbps Up to 1024 Kbps 1 to 15 Mbs 2 to 20 Mbs
1 fps 2 fps 3 fps 25 fps 25fps
inSORS Integrated Communications, dba IOCOM
Comment
video performance within normal bandwidth constraints Improved quality assuming network is available. Used for interoperability with legacy VTC endpoints.
Data Data Data Data HD HD
Full Motion HD Full Motion HD
page 15
Firewall Settings, QoS, Proxy and Encryption Settings Audio and video streams are transmitted via UDP (User Datagram Protocol). UDP is the optimal transport method for real time streaming traffic on IP networks.
Security - Firewall Settings IOCOM software works through NAT/PAT and securely traverses firewalls using Real Time Streaming Protocol (RTSP – see RFC 2326). RTSP was jointly developed by Real Networks, Netscape Communications and Columbia University in April 1998. RTSP is the same protocol used by QuickTime, Real Networks, and Windows Media players. In a typical IOCOM deployment, the Network Administrator only needs to configure the firewall to allow outbound TCP traffic on ports 80 and 554 with RTSP inspection to facilitate IG video conferences.
Some key attributes when using RTSP: 1. All sessions are initiated from inside the firewall. 2. RTSP inspection maintains state during each individual session and closes UDP ports if either endpoint drops out of the meeting. 3. RTSP traffic is commonly inspected and allowed by default in many firewall configurations. In addition to general RTSP attributes, there are some IOCOM specific attributes: 1. Each media stream (audio and video) is set up and controlled using RTSP. 2. Presence information and invitations are communicated using RTSP. 3. IG software uses dynamic RTP/UDP ports ranging from 10000-65535. 4. RTSP is used to control UDP streaming traffic only. 5. IG traffic passes through NAT/PAT devices. 6. Data passes through web proxies (caching must be disabled for the UCS). 7. Video and audio may optionally pass through streaming media proxies. See appendix B for more information on specific firewall settings.
Quality of Service (QoS) With QoS, organizations can ensure that IG audio, video, and/or tools traffic is appropriately prioritized, with sufficient network resources, so that meetings may be conducted under optimal conditions. IOCOM software may be configured to include specified DSCP values with audio, video, and tools traffic to facilitate Quality of Service (QoS) control over IOCOM network traffic. IOCOM supports DIFF-SERV (RFC 2474) which is backwards compatible with inSORS Integrated Communications, dba IOCOM
page 16
IP Precedence ToS described in RFC 791. See the UCS Management section for more information on where to configure QoS (DSCP) settings for voice, video and data.
Proxy Settings IG software may be optionally configured to pass audio, video, and data traffic via an RTSP streaming media proxy server, including the Microsoft Internet Security and Acceleration (ISA) Server. This is a simple client-side configuration option.
Encryption By default, all IG meeting traffic is encrypted using the randomly generated meeting code as the encryption key. If desired, stronger keys may be used. Furthermore, since IG software communicates over standard IP networks, any IG traffic can likewise be encrypted using IPSEC or other VPN encryption methods. HTTP based IG traffic (e.g., IGFile, IGPix) may optionally be encrypted using SSL.
inSORS Integrated Communications, dba IOCOM
page 17
MANAGEMENT Access IG Client software typically connects to a UCS before initiating meetings with other endpoints. Access to a UCS is restricted by a password protected user account and access attributes associated with that account. The UCS may be configured to authenticate against user records stored in a local or ODBC accessible database or optionally against user records stored in an existing LDAP or Active Directory database. A local or ODBC accessed user database is administered via the User Manager in the UCS web based management console. If the UCS is configured for LDAP/AD, user accounts would be administered via the directory server’s management (Active Directory Users and Computers snap-in) tools. Customers who wish to maintain IOCOM user records in an LDAP or Active Directory database must create the following groups on the LDAP/AD server: • • • • • •
IGUSER IGADMIN IGPLAY IGRECORD IGRDELETE IGDIALER (available Q2 2008)
Membership in these groups likewise determines which access rights a user has to IG Client software functionality. IOCOM users may optionally join meetings on a UCS where they do not have a user account, provided that they know the server address and meeting code. In such scenarios, users may only have access to voice and video streams and subset of tools functionality. For more advanced access control, administrators may optionally configure the iptables firewall to filter traffic to the UCS at the packet level. The iptables firewall may be configured to filter traffic based on parameters such as IP address or port.
Usage Statistics An IG UCS provides a variety of usage statistics and graphs for administrator analysis. This usage information may be useful for diagnosing issues, planning capacity, and detecting anomalies on the UCS or the network. The Usage Viewer is accessed via the UCS web based management console. UCS Administrators may search for specific users and meetings and determine the resources consumed by users in those meetings. The following Usage Viewer output illustrates two users in a three-plus minute meeting:
inSORS Integrated Communications, dba IOCOM
page 18
The following usage statistics are displayed: Column Header USER NAME IP ENTERED MINUTES RA SA RV SV RT ST DIAL FILE WB CHAT REC PIX CAM
Description User account IG Client site name IP address of site Time site entered meeting Duration of meeting Amount of audio traffic (in kilobytes) received in meeting Amount of audio traffic (in kilobytes) sent in meeting Amount of video traffic (in kilobytes) received in meeting Amount of video traffic (in kilobytes) sent in meeting Amount of tools traffic (in kilobytes) received in meeting Amount of tools traffic (in kilobytes) sent in meeting Number of calls initiated via the Dial application Number of files uploaded via the File application Number of times Whiteboard application was accessed Number of messages sent via the Chat application Number of recordings initiated/played via Record application Number of pushed IGPix captures Number of instances IGCam interface was accessed
UCS Usage Graphs provide a variety of graphs detailing statistics such as the number of active meetings displayed in daily/weekly/monthly/yearly graphs. Others statistics such as load average, CPU utilization, and network utilization are similarly graphed. Here’s an example of network utilization graph viewable via UCS Usage Graphs:
inSORS Integrated Communications, dba IOCOM
page 19
These statistics can likewise be gleaned using third party SNMP applications. The UCS makes this data available to facilitate the monitoring of various conditions (e.g., license usage, concurrent bridge users) that might require administrative attention or be useful for tracking UCS usage statistics over a span of time. Contact IOCOM for a detailed listing of current MIB definitions.
Limits: Meeting Settings Meeting creators have the option of setting various limits on a per meeting basis. These limits include allowed video codecs, maximum number of video streams, and available tools. Scheduled meeting creators are automatically designated as moderators and may grant moderator privileges to other meeting participants. Meeting limits do not apply to moderators and are only enforced on other participants for the duration of the specified meeting. Similar limits settings may also be specified in fixed virtual meeting rooms. Please refer to the illustration that follows for all available scheduled meeting settings.
inSORS Integrated Communications, dba IOCOM
page 20
Limits: UCS Master Settings UCS Administrators may optionally set limits for all users, in all meetings. Server wide limits such as allowed codecs and tools are configured here as well as other options such as audio/video/tools and DSCP settings to facilitate Quality of Service (QoS) control over IG network traffic. Please refer to the illustration that follows for an overview of all available IG Server Limits Manager options.
inSORS Integrated Communications, dba IOCOM
page 21
INTEROPERATION The IOCOM platform interoperates with traditional videoconference (VTC) systems such as Polycom or Tandberg. IOCOM meetings often include multiple video streams from different sites while traditional VTC endpoints typically only send and receive one video stream. IOCOM client software provides an option to designate any video stream, in an IOCOM meeting, as the "Priority" video stream. This video stream will be transmitted from the UCS to any VTC endpoints participating in the meeting. This "Priority" designation may be changed by any IG client site, on demand, without interrupting the meeting. Other key factors about IOCOM’s interoperation with traditional VTC endpoints include • • • • • • • • •
All VTC/PSTN calls are routed through a UCS Calls to VTC/PSTN endpoints are initiated from the dialer through the UCS to the VTC endpoints VTC/PSTN endpoints may also call into IG meetings using the IP address, domain name, or phone number of the designated UCS with the specified meeting number. The UCS may register with standards based VOIP gatekeeper. Multiple VTC/PSTN connections may be initiated in the same meeting. Caller ID information from VTC/PSTN participants appears in the IOCOM client user interface Audio from each VTC call may be adjusted through IOCOM’s independent audio controls. For compatibility, video sent via a UCS to a VTC endpoint is transcoded into H.261/H.263 format Video images from VTC endpoints appear to IOCOM users as an additional video window and may be moved and resized
inSORS Integrated Communications, dba IOCOM
page 22
H.323 The diagram below shows the connection between the UCS and an H.323 device (endpoint or MCU). IOCOM end users may initiate calls through the dialer in the client application, The call is placed via the UCS, which then establishes a direct connection over an IP network. The designated priority video stream is sent to the VTC endpoint. The VTC video stream is sent to the UCS and appears to all IOCOM endpoints as an additional video stream which may be moved and resized.
inSORS Integrated Communications, dba IOCOM
page 23
SIP The UCS may also establish direct connections to SIP based endpoints such as VoIP phones. The end user may invoke the dialer application (see below) from the client tools menubar, select the SIP protocol, and enter the IP address, qualified domain name or phone number. Like an H.323 connection, voice and video streams from a SIP endpoint are sent to the UCS and then distributed to other IOCOM meeting participants.
inSORS Integrated Communications, dba IOCOM
page 24
PSTN IOCOM uses 3rd party VoIP gateways to connect to the public switched telephone network. The UCS may be configured to route all outbound phone numbers through an IP to PSTN gateway. Conversely, people may call into meetings by dialing the UCS phone number and entering the 5-digit IOCOM meeting code.
inSORS Integrated Communications, dba IOCOM
page 25
ISDN IOCOM endpoints may also connect to ISDN based video conference units by using 3rd party IP to ISDN gateways. Similar to PSTN connections, voice and video streams are routed through the UCS to the IP to ISDN gateway and then out to the VTC unit.
inSORS Integrated Communications, dba IOCOM
page 26
APPENDIX A – Bandwidth Calculations Assumptions: The following assumptions will be made for calculating bandwidth over 3 scenarios 1) Each camera is set to H.264 medium using a maximum of 256 Kbps of bandwidth. This is a worst case as actual bandwidth usage will be lower and varies based on movement within the video image. 2) Audio is set to “standard” which uses 64 Kbps of bandwidth 3) IP headers for audio streams are assumed to consume 36 Kbps of bandwidth. 4) IGPix is assumed to consume 20 Kbps of bandwidth 5) Conference Room A is simultaneously transmitting 2 PTZ cameras views 6) Desktops endpoints are transmitting one USB video image 7) Upstream and downstream bandwidth numbers are shown for reference in asymmetric networks. 8) The UCS is on a symmetrical IP connection and the total bandwidth required number is the greater of the upstream and downstream usage.
Conference Room = 632 Kbps Upstream Stream Video – H.264 medium Audio IP Headers IGPIX Total
Qty 2 1 1 1
Bandwidth Per Stream 256 Kbps 64 Kbps 36 Kbps 20 Kbps
Extended 512 Kbps 64 Kbps 36 Kbps 20 Kbps 632 Kbps
Desktop System = 376 Kbps Upstream Stream Video – H.264 medium Audio IP Headers IGPIX Total
Qty 1 1 1 1
Bandwidth Per Stream 256 Kbps 64 Kbps 36 Kbps 20 Kbps
inSORS Integrated Communications, dba IOCOM
Extended 256 Kbps 64 Kbps 36 Kbps 20 Kbps 376 Kbps
page 27
Scenario 1: Two desktops in a meeting (Kbps)
Desktop 1 Desktop 2 UCS
Upstream 376 376 752
Downstream 376 376 752
Total 376 376 752
This connection would require 376Kbps of bandwidth for each desktop endpoint and 752Kbps for the UCS.
Scenario 2: Three Desktops in the same meeting (Kbps): Assumes each endpoint views both remote video views.
Desktop 1 Desktop 2 Desktop 3 UCS
Upstream 376 376 376 1128
Downstream 632 632 632 1896
Total 632 632 632 1896
The down stream bandwidth for each endpoint is increased by the additional video image (632 = 376 + 256).
Scenario 3: Conference A and three desktops Assumes each endpoint views all video images
Desktop 1 Desktop 2 Desktop 3 Conference Rm A UCS
Upstream 376 376 376 632 1760
Downstream 1144 1144 1114 888 4320
Total 1144 1144 1144 888 4320
The downstream bandwidth for each desktop increases by 512 Kbps to account for the two additional video views from the conference room. This scenario assumes that each desktop would be viewing 4 remote images. (Local images are still displayed but do not use bandwidth) The conference room would only be viewing 3 remote desktop images, therefore it’s downstream usage would be 888 Kbps, (888 = 1114 -256)
inSORS Integrated Communications, dba IOCOM
page 28
Scenario 4: Conference A and three desktops – Selected Video Assumes that the first desktop is viewing one of the four available video images, the second desktop is viewing two video images, and the Conference Room and third desktop are viewing all available images.
Desktop 1 (view 1 video images) Desktop 2 (view 2 video images) Desktop 3 (view all 4 video images) Conference Rm A (view all 3 remote videos) UCS
inSORS Integrated Communications, dba IOCOM
Upstream 376 376 376 632 1760
Downstream 376 632 1114 888 3010
Total 376 632 1114 888 3010
page 29
APPENDIX B – Firewall Configurations
Cisco Firewall Configurations For Cisco firewalls simply enter the “fixup protocol rtsp 554” command to enable RTSP.
Checkpoint Firewall Configurations 1) Confirm that your Checkpoint firewall is updated to the latest patch level. There have been a number of issues reported with older Checkpoint firewalls including no passage of streaming traffic or random disconnects after the streaming has started. This solution has been verified with patch level HFA01 for the NGX R60 and patch level HFA04 for the NG R55. Go to the downloads section at Checkpoint and check the hotfix accumulators for your specific version and for other products. 2) Add an external network group definition for the UCS that you are trying to connect to. Check with your IOCOM representative for the specific UCS IP address(es) and net mask. 3) Add a rule to allow internal clients to contact the external UCS using the RTSP service (TCP port 554). The Checkpoint firewall will then inspect the RTSP traffic and dynamically open and close the inbound UDP streaming ports from the UCG as requested by the client software. See rule #3 in the attached picture. This rule uses the standard rtsp service definition in the predefined TCP services.
inSORS Integrated Communications, dba IOCOM
page 30
4) Add a rule to allow internal clients to send streaming UDP to the external UCG. See rule #4 in the picture above. This rule uses the standard udp-high-ports service definition in the predefined UDP services and it will allow the client to stream outbound to the UCG. If desired, this outbound port range can be further limited to UDP ports 10000-20000. Other than normal http/https access to these servers, and DNS rules that are probably already in place, adding these two rules and applying the latest hotfixes should be the only changes required.
Other Firewall Configurations If RTSP is not available on the firewall: Port triggering may be used. Port triggering should be configured to use port 554 as the signal port. Some firewalls will then open the requested ports dynamically while others will open a range. The range should be UDP ports 10000 thru 65535. Again this should be limited to the IOCOM UCS. As a last resort all ports can be set to open but restricted to the IOCOM UCS.
inSORS Integrated Communications, dba IOCOM
page 31
