Polycom RSS 2000 - Manual (Page 14)

RSS 2000 Getting Started Guide & Release Notes – Version 3.0.2
6
RSS 2000 Maximum Capacity
Table 2 Maximum Capacity
Scenario Description Maximum Capacity
Conference
Recording
How many conferences can
be recorded simultaneously?
2 conference recording links, or 2 endpoints
dialing in the same time. Only 1 recording
session at a time may utilize H.239.
Point to Point
recording
How many point to point calls
can be recorded (if both are
dialing into the POLYCOM ™
RSS 2000)? 1 point to point call can be recorded, as the
two connections to the recording room
utilize both available ports on the RSS
2000.
H323
Playback
How many recordings can be
simultaneously played back in
H323? 10 recordings. This includes playback from
the local RSS 2000, or from other units in a
clustering group.
Archive
playback
(WMV
Unicast)
How many streams/archives
can be simultaneously viewed
(unicast)?
50 streams/archives. This is based on the
Web Server’s capacity.
Archive
playback
(Multicast) How many streams/archives
can be simultaneously viewed
(multicast)?
2 streams can be viewed using the RSS
2000 Multicast Viewer. The archives must
be enabled for multicast streaming. See the
User Guide for details.
Clustering
How many RSS 2000 devices
can be clustered in a single
group?
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).
The H.323 playback resource it occupies
is taken from RSS-A, even though the
archive resides on RSS-B. RSS-A has 9
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.