Cisco Cisco Unified MeetingPlace Web Conferencing Manual De Mantenimiento

Descargar
Página de 335
Chapter 11  Troubleshooting  269
Yes, there is a separate buffer pool for each bandwidth channel. 
This is so flow control can be handled completely separately for 
each channel. Clients from one channel cannot affect clients in 
another.
Do clients belonging to different bandwidth channels receive 
the same packets? Or in order to make the slow clients catch up 
quickly, does DCMS send fewer packets to the slow clients? If 
DCMS send fewer packets to the slow clients, what is the ratio 
for high, medium, and slow channels?
DCMS sends fewer packets to clients in the lower bandwidth 
pool. For example, if you were to share a clock, a high bandwidth 
client may see a change in the second hand every one to two 
seconds, whereas a low bandwidth client may only see the second 
hand change every five seconds. Another example would be if 
you share a PowerPoint slide presentation that includes 
animation. Participants in the web conference will only see the 
final slide, but not the animation. 
The maximum rate at which DCMS will send data on each 
bandwidth channel is (in bytes per second):
Low channel bandwidth = 2000 (i.e., 16kbps)
Medium channel bandwidth = 5000 (i.e., 40kbps) 
High channel bandwidth = 200000 (i.e., 3200kbps — 
effectively unlimited for a LAN connection)
This does not, however constitute a constant ratio, as usually the 
send-rate will not max out these bandwidths.
What are the TCP ports that need to be opened in order to host 
a web conference?
If a socket connection needs to be established, TCP port 1627 
should be opened for WebShare and TCP port 1503 should be 
opened for a T.120 application such as NetMeeting. 
OL-6033-01                           Cisco MeetingPlace Web 3.0 System Manager's Guide