Polycom manual RSS 2000 Maximum Capacity, Scenario Description Maximum Capacity

RSS 2000 Getting Started Guide & Release Notes – Version 3.0.2

RSS 2000 Maximum Capacity

Table 2 Maximum Capacity

Scenario

Description

Maximum Capacity

Conference	How many conferences can	2 conference recording links, or 2 endpoints
		dialing in the same time. Only 1 recording
Recording	be recorded simultaneously?
		session at a time may utilize H.239.
Point to Point	How many point to point calls	1 point to point call can be recorded, as the
	can be recorded (if both are	two connections to the recording room
recording	dialing into the POLYCOM ™	utilize both available ports on the RSS
	RSS 2000)?	2000.
H323	How many recordings can be	10 recordings. This includes playback from
	simultaneously played back in	the local RSS 2000, or from other units in a
Playback
	H323?	clustering group.
Archive	How many streams/archives	50 streams/archives. This is based on the
playback
	can be simultaneously viewed
(WMV		Web Server’s capacity.
	(unicast)?
Unicast)
Archive	How many streams/archives	2 streams can be viewed using the RSS
		2000 Multicast Viewer. The archives must
playback	can be simultaneously viewed
		be enabled for multicast streaming. See the
(Multicast)	(multicast)?
		User Guide for details.
		There is no limitation for the amount of RSS
		2000 devices that can be in a single
		clustering group.
		1. In clustering mode, each RSS 2000 still
		supports 10 H.323 playback sessions.
		For example: One H.323 endpoint
		connects to RSS-A to playback an
		archive residing on RSS-B (B is in a
		clustering group with A in this example).
	How many RSS 2000 devices	The H.323 playback resource it occupies
		is taken from RSS-A, even though the
Clustering	can be clustered in a single	archive resides on RSS-B. RSS-A has 9
	group?	additional H.323 playback sessions
		available, while RSS-B still has all 10
		sessions available.
		2. WMV playback via the archive list in the
		web UI of a clustered RSS 2000 will
		utilize unicast streaming resources from
		the RSS device where the archive
		actually resides, not from the clustered
		device that the user is connected to. Note
		this is the reverse of the resource usage
		behavior for H.323 playback.

6