Technology Standards for Videoconferencing at RutgersCEO Videoconferencing Support line: 732-445-1907 EXT 0 Individual departments are encouraged to contact Continuous Education early in the planning stages for videoconferencing. This page attempts to provide an overview of several critical issues that Unit Computing Specialists need to be aware as they work toward integration into Videoconferencing, or wish to support videoconferencing within their department. This list is not exhaustive and does not include physical room design considerations that are often mistakenly left for the last minute. Physical room design is critical to the success of any Videoconferencing deployment and should be considered at early stages. Resources on videoconferencing classroom design are available.
EquipmentVideoconferencing equipment is available in an array of options and capabilities. The "key" piece of videoconferencing equipment is a unit, referred to as the "CODEC", which draws its name from what it does: it first "COmpresses" video and audio signals for transmission, and virtually simultaneously "DECompresses" synchronized video and audio data it receives. For the purposes of this summary, we shall be dealing with CODECs that perform under Video over IP standard H.323, currently the most common transmission standard. MPEG2 and MPEG4 CODECs are available, as are other emerging standards, but these provide much more limited utility and are not now generally recommended for adoption by schools or departments except for highly experimental purposes. CODECs are usually procured independent of the actual monitor that is used for the display of video, speakers necessary for the audio, and microphones to send audio. For turnkey solutions most vendors provide integrated systems that usually are quite suitable for seminar, conference, or small group meetings, but often entirely unsuitable for interactive classroom use. For the most part, Rutgers DCEO recommends any of the following three vendor choices: Polycom, Sony, and Tandberg. Tandberg and Polycom CODECS have been used the longest at Rutgers. Both are solid vendors with reliable equipment and an extremely high degree of interoperability. Additional details and resources on videoconferencing equipment are available.
Network standardsNetwork standards are outlined at http://www.td.rutgers.edu/documentation/Reference/RUNet_Video_Reference_Checklist One item in the checklist is to verify that your Codec's software/firmware is current. However, it is advisable to be using Tandberg E4 software as it provides new features including H.350. Note that some systems do not register properly in the Rutgers gatekeeper when using 165.230.252.48 and those systems should use 128.6.18.194 instead. Currently, a test to prove registration is that someone outside of RUNet can connect to your system using your GDS address. In addition, please note that the Rutgers gatekeeper will drop your entry 30 minutes (TTL) after your system is turned off.
GDS or global dialing schemeThe Rutgers gatekeeper is the authoritative source for GDS values that only start with:
The GDS number can be at least 4 to 6 digits longer. We recommend that the 4 digits be either the phone extension in the room or the phone extension of someone who can assist when the room is in use. The extra fifth and sixth digit would be used to make GDS values unique when a staff member's extension is used for multiple GDS values. Since the GDS value could be the phone in the room, it would be advisable to only use it when setting up the videoconference session or when there is a need to communicate to correct error conditions (this would be good etiquette). For portable units, the recommended GDS value should be the phone number of the support staff. The distinct advantages for using the GDS value to connect to another site are:
Codec or h.323 nameSince these names will be displayed in a state wide directory as well as in the Rutgers wide gatekeeper, the naming convention should minimally start with RU followed by an abbreviation for department. Hopefully, the department abbreviation can be found with a "University web site search". Also, if the department is not uniquely found at Rutgers, then suggested campus designations for New Brunswick/Piscataway, Newark, and Camden are respectively NBP, Nwk, and Cmd. If the unit moves between rooms (portable), then the name would end with a building abbreviation. e.g. RU-NBP-UHR-ASB-Annex-I. If a department has more than one portable in a building, then it will be necessary to add another character to make each name unique.
Please note that the RU is designating that your Codec is RUNet based and is dependent on the Rutgers gatekeeper and not just a Rutgers location. Additional details on Protocols and Codecs are available.
Test procedure for RUNet hosted CodecsThe RUNet testing should be to connect to at least 1 other Codec using both its IP Address and its GDS name. Testing with IP verifies access and network connectivity while using GDS verifies that the system is registered properly in the gatekeeper. In the short term, each of the contacts below can provide info for an RUNet test Codec. Since some future videoconferences may require more connections than your Codec can handle (a Polycom FX has a theoretical limit of connecting 3 more Codecs though response degrades at that point), it is recommended that you arrange a test with the DCEO MCU located in Hill Center (IP address is 128.6.30.130 and GDS value is 0017324450001). In addition, the DCEO MCU and the NJEdge MCU are more centrally located in their respective networks and also have the ability to use other IP for connections. Please contact Peter Mattaliano to arrange this test. In addition, http://www.njedge.net/techsection lists a set of 4 NJEDge Test Codecs along with other documentation. Below is a recommended NJEDge and Internet2 test pattern:
Steps for NJEdge certificationThe certification process will be testing that the NJEDge MCU can initiate a connection to your Codec using your GDS address, that the video image is acceptable to both sides, and that the web commander database be accurately updated with your unique Codec name and GDS address (max of 15 digits). Since the certification process is testing the acceptability of network connectivity, when you change the network connectivity to another building or totally different/new network, you probably should verify certification prior to use. Please coordinate your certification with one of the contacts below in order to avoid overloading the NJEdge staff member with 80 contacts from Rutgers.
Note that the certification process is with the NJEDge MCU which:
If you need to change either your h.323 name or e.164 address after you have certified your Codec, please work thru your contact to have your web commander directory entry updated. |
|||||||||||||||||||||||||||||