Cisco Cisco Unified MeetingPlace Express 2.0 Libro bianco
Cisco Systems
Network Provisioning and Configuration
Page 8
2.3 E n d -U se r I n t e r f a c e a n d Ad m i n i st r a t i on Ce n t e r
On the whole, Cisco MeetingPlace Express HTTP traffic is neither high bandwidth nor
real-time in nature and is relatively insignificant compared to other traffic types.
However, during the period when meetings are starting, particularly in the few minutes
right after the hour, you should assume many users will hit the server for the purpose of
attending a meeting.
The total traffic involved in a client entering a web conference is approximately 400KB
downstream and 70KB upstream. This assumes that the client has accessed the server
before, so some items are in cache. Included are accessing the main server web page,
selecting a meeting, and entering the meeting room, but not any screen sharing.
Assuming 120 users, that is an aggregate of about 50MB of output over approximately 5
minutes, or somewhat less than 1Mbs.
In addition to meeting attendance, web pages are used for scheduling and system
management. Typical transactions involve a few hundred kilobytes, but some, such as
downloading reports, can be arbitrarily large. Compared with attendance, these are low in
frequency.
Note that there is no enforced limit on the number of simultaneous web sessions. Access
limits are imposed only on voice connections and on web conferencing sessions.
real-time in nature and is relatively insignificant compared to other traffic types.
However, during the period when meetings are starting, particularly in the few minutes
right after the hour, you should assume many users will hit the server for the purpose of
attending a meeting.
The total traffic involved in a client entering a web conference is approximately 400KB
downstream and 70KB upstream. This assumes that the client has accessed the server
before, so some items are in cache. Included are accessing the main server web page,
selecting a meeting, and entering the meeting room, but not any screen sharing.
Assuming 120 users, that is an aggregate of about 50MB of output over approximately 5
minutes, or somewhat less than 1Mbs.
In addition to meeting attendance, web pages are used for scheduling and system
management. Typical transactions involve a few hundred kilobytes, but some, such as
downloading reports, can be arbitrarily large. Compared with attendance, these are low in
frequency.
Note that there is no enforced limit on the number of simultaneous web sessions. Access
limits are imposed only on voice connections and on web conferencing sessions.
2.4 D ow n l oa d i n g a n d Pl a y i n g Voi c e Re c or d i n g s
Meeting recordings are published in MP3 format and occupy approximately 6MB of disk
space per hour. Playback involves downloading the file and it is possible for a substantial
number of downloads to be running simultaneously. The speed of the download is limited
only by the capacity of the HTTP server and the available bandwidth. The system is
designed with the assumption that downloading of recordings is not a frequent activity.
space per hour. Playback involves downloading the file and it is possible for a substantial
number of downloads to be running simultaneously. The speed of the download is limited
only by the capacity of the HTTP server and the available bandwidth. The system is
designed with the assumption that downloading of recordings is not a frequent activity.
2.5 W i d e Ar e a Ne t w or k ( W AN) Con si d e r a t i on s
The previous sections in this chapter mostly assume the following:
•
Voice connections are across a high capacity core network.
•
Web conferencing connections are either across a high capacity core network or
on a single-user, single-application link.
Other scenarios that deserve special consideration include:
•
Users employing IP voice from outside the core network.
•
Users sharing a slow to moderate speed link, perhaps in a satellite office.
2.5 .1 Vo i c e o v e r a W A N
Assuming the raw bandwidth is available, external VoIP voice connections should work
adequately provided the DSCP packet marking can be honored and preserved by all the
equipment, end-to-end. However, it is typical for public Internet connections and virtual
private networks to not honor DSCP marking. As a result, it may be necessary to use
adequately provided the DSCP packet marking can be honored and preserved by all the
equipment, end-to-end. However, it is typical for public Internet connections and virtual
private networks to not honor DSCP marking. As a result, it may be necessary to use