"Product Catgeory","mcu for answan"
"Product Name","Polycom RealPresence Collaboration Server"
"Specification Title","Specification Value"
"VC MCU capacity/features: The MCU should be hardware based and it should support 25 ports at 1080p 60fps (transmit and receive) up to 4Mbps on IP in continuous presence mode with 30fps and H.264 resolution and AES encryption on the same chassis/MCU.(b) Additionally and the same MCU should be field upgradable on the same chassis without cascading or stacking to support 50 ports at HD 1080p 30fps to meet the future requirements.(c) There should be no restrictions on the number of shared conferences/virtual meeting rooms/shared conferences that can be created on the MCU.",Yes
"Interface And Connectivity: (a) The MCU should have support for 2 x 10/100/1000 Ethernet Ports.(b) Multipoint Conference / Control Unit (MCU) features:(c) MCU shall support both desktop software based end points and mobiles andipad and any android mobile device and hardware based endpoints. MCU should support Power supply ( 100- 240VAC 50/60Hz)(d) All the equipment systems to be offered in the bid must be built on the base of latest ITU-T standards related to video conference and transmission on TCP/IP network: Video conference connection: H.323 and SIP protocols to be supported(e) The MCU will be installed in an IP network and any PC on the IP network with software video client should be able to join any ongoing conference using web camera and audio facility.(f) Should provide Individual / personal layouts per conference participant",Yes
"Video Standards And Resolutions:The MCU should natively support H.323 and SIP standards for communication.(b) The MCU should support H.263/H.263+/H.263++ and H.264 AVC/SVC,H.264 High Profile/H.265(c) The MCU should support resolution up to 1080p 60 fps(d) The MCU should support content sharing using standard based H.239 and BFCP over SIP with HD1080p resolution along with Full HD 1080p30fps main video.(e) The MCU should support H.239 & BFCP and encryption in SIP & H.323 modes(f) The software and hardware based video endpoints should be highly interoperable with the MCU offered. And it should work on standard based technology just to ensure to interoperable with existing video infra if any(g) Should have min 20 HD continuous presence up to 1080p 30 fps and 720 60fps.(h) The MCU shall support aspect ratio of 16:9 and 4:3.(i) MCU should support minimum 25 HD 1080p 60fps endpoints in single or multiple concurrent sessions.(j) Should support Live video resolutions – CIF up to 1080p(k) Should have Dynamic layout according to the number of participants(l) Should provide Enhanced lecture mode or presentation mode (creates classroom-like environment)(m) Should provide data collaboration and presentation sharing features using H.239 (H.323) and BFCP (SIP)",Yes
"Audio Protocols : Should have Audio encoding: G.711 and G.722 andG.722.1 or better or equivalent. Automatic Gain Control and Automatic Noise Suppression. Keyboard noise reduction and instant adaptation echo cancellation",Yes
"Performance:The speed of the MCU per video link should be @ 2 mbps/1 mbps/768kbps/512kbps/384 kbps in a concurrent session and even with a PC as a node. And the available Video bandwidth should be minimum 4 mbps.(B) The MCU shall support a mix of resolutions in both Voice Activated mode and Continuous Presence. Each endpoint shall receive at the maximum of its capacity without reducing the capacity of another.(c) The MCU should be capable of supporting H.323 and SIP based participants in the same conference(d) The MCU should be capable of supporting AES Encryption at conference level and individual participant level.",Yes
"Security : The MCU should support password based entry into the conference",Yes
"Other Compliance/ Support : a)QoS - Diffserv and TOS and IP Precedence(b) The MCU should have natively integration capability with Microsoft Lync/SFB(c) All endpoint can control the conference using standard protocol H.243 and DTMF(d) Should support easily distinguishable entry tone and exit tone to inform conference participants when parties join or drop from the conference.(e) Should support an end-of-conference warning tone when the conference approaches its scheduled end time(f) Should have User-friendly interface for MCU configuration and conference operation",Yes