Considerations for a successful demo and implementation of Simplicity Video

Transcription

1 CLOUD SOLUTIONS Considerations for a successful demo and implementation of Simplicity Video Client Requirements: PC Requirements Windows Software Processor RAM Video Memory Hard Drive Space Camera Audio Devices Monitor Windows XP; 32-bit with Service Pack 3 or later Windows 7; 32-bit and 64-bit Windows 8 Standard, Pro, and Enterprise; 32-bit and 64-bit Microsoft.Net Framework Version 4.0 Polycom CMA Management Application Version 6.2 or later Polycom RealResence Resource Manager Version 7.1 or later Intel Core i5, 2.5GB or more 4 GB Minimum: 256 MB 200 MB Integrated or external Standard PC97 audio devices Recommended: 16:9, 1920 x 1080 Minimum: 1024 X 768 Mac Requirements Standard Processor - (up to 360p Tx/Rx) Premium Processor - (up to 720p Tx/Rx) OS X RAM Intel Core 3 Duo 2.0 GHz Intel Core i3 Dual Cores 1.6 Gz Intel i5 Dual Cores 1.6 GHz or higher Intel Core i3 Dual Cores 2.5 GHz or higher (up to 15fps Tx, 30ftps Rx) Intel Core i5 Quad Cores 2.0 GHz or higher 9up to 30fps Tx/Rx) Lion (10.7) Mountain Lion (10.8) 2 GB Video Memory Minimum 256 MB Storage 200 MB

2 Mobile Clients ios Requires ios 5.0 or later. Compatible with ipad 2 Wi-Fi, ipad 2 Wi-Fi + 3G, ipad (3rd generation), ipad Wi-Fi + 4G, ipad (4th generation), ipad Wi-Fi + Cellular (4th generation), ipad mini and ipad mini Wi-Fi + Cellular. Android Requires Android 4.0 and higher. Installation/Configuration Make sure end user has latest client software version. 3.0 or greater. During the installation of Polycom RealPresence Desktop (RPD) your Windows antivirus program may prompt you. If it does it is important you select Trust RPD. Open Polycom RealPresence and selecting Settings and then Audio Devices and confirm that the correct audio input and output devices are selected. Next still under Settings select Camera. You should see a self-view displayed. If you do not use the drop down to select a webcam. After successful installation of the RPD client it is important to make sure no other applications are utilizing the computer resources such as microphone and camera. It is common for applications such as Skype, Scopia Desktop, Vidyo, Jabber/Movi, etc. to place themselves in your start up group so that the application automatically runs when booting up your machine. Check your taskbar for any such programs: Close down any of these other apps or better yet go into that programs setting and disable the auto start. If having connection issues after installation insure Windows Firewall is set to Allow RPD.

3 Call Quality / Troubleshooting If Windows local Host FW settings are enabled for RPD we will need to make sure the following ports are enabled through the Enterprise or SOHO Firewall. Inbound Ports Port Function 1720 (TCP) H.323 Signaling 1719 (UDP) Registration, Admission, and Status (RAS) (TCP) Call Signaling (UDP) Media (RTP/RTCP) 5060 SIP 3238 (UDP and TCP) BFCP Outbound Ports Port Function 443 (TCP) Provisioning, Monitoringm Help Files, HTTPS 389 (TCP) LDAP 5060 SIP 5061 (TCP) SIP TLS signaling 1720 (TCP) H.323 Signaling 1719 (UDP) Registration, Admission, and Status (RAS) (TCP) Call Signaling (UDP) Media (RTP/RTCP) 3238 (UDP and TCP) BFCP LIST of know FW s and SW revs that are compatible is being developed by Polycom. In addition to the above required ports being open NAT will be utilized and is often broken by Firewalls that are H.323 aware and will require that H.323 Fix-up /ALG be disabled as is a known issue on Cisco ASA s as well as other Firewalls. Bandwidth Requirements Call Speed Video Format Resolution 64 kbps kbps 180p 320 x kbps kbps 360p 640 x kbps kbps 720p (HD) 1280 x 720 Call quality packet loss/latency/jitter Packet loss should be at 5% or below. Packet loss of up to 10% can sustain a call in most instances but call quality will suffer. Latency of 300 milliseconds or less is preferable. Jitter should be at 2% or less. QOS can be assigned on the ports but not set on the RPD client. VLans not typically utilized due to this being a Desktop client.

4 Once in a call you can click on the Statistics bars (green) on the bottom left of the application and see the call statistics such as Protocol used, screen format, rate connected at, rate used, packet loss, jitter and if encryption is enabled. The mobile client Call Status screen looks different but delivers the same information: For connections across a VPN, do not use long keys and hence applying too much encryption as this can cause an unacceptable delay in the transmission between sites and impact the overall efficiency of the video conference.

5 Further trouble shooting can be conducted in conjunction with Polycom and customer. Polycom will be able to look at logs on the bridge and see what if any packets are reaching it. We could conduct some ping, tracerts and port scans (nmap) to see where traffic is dying or being delayed. WireShark or other utilities may need to be used to trouble shoot. Ping - use the l to set the mtu to 1500 otherwise the command uses the default 32 bytes which is not typical of a video packet Tracert can show path and how many hops etc. NMap use the PN as some clients wont reply to ping request WireShark - These commands can be use for testing and not necessarily to the VMR bridge. We are trying to determine if ports are open, the number of hops and trip time.