19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

Network Traffic Control<br />

A Network Traffic Control mechanism has been added to the <strong>RMX</strong> that controls the level of<br />

UDP packets generated by the system. Network Traffic Control regulates a set of queuing<br />

Only supported in the MPMx Card Configuration mode.<br />

systems and mechanisms by which UDP packets are received and “transmitted” to the<br />

network router. During a conference, MPMx cards occasionally blast-out UDP packets<br />

which can cause overloads on the network. <strong>RMX</strong> bandwidth usage can increase to above the<br />

designated conference participant line rate settings, causing network bandwidth issues such<br />

as latency and packet loss.<br />

Three Network Traffic Control Flags are added:<br />

• ENABLE_TC_PACKAGE - default = NO. When the flag is set to NO, Network Traffic<br />

Control is disabled on the <strong>RMX</strong>. Set the flag to YES to enable Network Traffic Control.<br />

• TC_BURST_SIZE - default = 10, flag range: 1-30. This flag regulates the Traffic Control<br />

buffer or maxburst size as a percentage of the participant line rate. In general, higher<br />

traffic rates require a larger buffer. For example, if the flag is set to 10 and the<br />

participants line rate is 2MB, then the burst size is 200Kbps.<br />

• TC_LATENCY_SIZE - default = 500, flag range: 1-1000 (in milliseconds). This flag limits<br />

the latency (in milliseconds) or the number of bytes that can be present in a queue.<br />

SIP Proxy Failover With <strong>Polycom</strong>® Distributed Media<br />

Application (DMA) 7000<br />

<strong>RMX</strong> systems that are part of a DMA environment can benefit from DMA’s SIP Proxy<br />

Failover functionality.<br />

SIP Proxy Failover is supported in DMA’s Local Clustering mode with redundancy achieved<br />

by configuring two DMA servers to share a single virtual IP address.<br />

The virtual IP address is used by the <strong>RMX</strong> as the IP address of its SIP Proxy.<br />

No additional configuration is needed on the <strong>RMX</strong>.<br />

Should a SIP Proxy failure occur in one of the DMA servers:<br />

• The other DMA server takes over as SIP Proxy.<br />

• Ongoing calls may be disconnected.<br />

• Previously ongoing calls will have to be re-connected using the original IP address,<br />

registration and connection parameters.<br />

• New calls will connect using the original IP address, registration and connection<br />

parameters.<br />

15-32 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!