In this section:
RTCP Modes for Media
|
|
---|---|
RTCP Relay for pass-through calls with RTCP enabled on both legs | RTCP is relayed between two end users. The SBC will not terminate the RTCP sessions; however, it will set up the media-path to forward RTCP packets from one party to the other. This is the default and recommended approach for handling RTCP for pass-through calls. |
RTCP termination for a pass-through call with RTCP enabled on only one leg | |
RTCP for transcoded calls legs | If RTCP is enabled on the leg, the SBC will terminate RTCP. |
In either pass-through or termination modes, the SBC collects packet RTCP statistics and reports them for output to CDRs. Configurable parameters include:
peerAbsenceAction
, from the Packet Service Profile.
% set system media dedicatedBWForNonRTPMedia (0-50) mediaPeerInactivity inactivityTimeout <20-1260, in multiples of 10> mediaPortRange baseUdpPort <1024-65534> maxUdpPort <1024-65534> highPriorityPortRangeLocation <top | bottom> highPriorityPortRangeSize <0 to 25)> mediaRtcpControl sendBYEPacket <disabled | enabled> senderReportInterval <5-120> tcpPortRange baseServerPort <1-65534> maxServerPort <1-65534>
System Media
Parameter | Length/Range | Description |
---|---|---|
| 0-50 | Use this control to specify (reserve) an amount, as a percentage, of bandwidth usage to limit across all physical interfaces for non-RTP media (default = 0). NOTE: This feature only applies to TCP media traffic such as MSRP. |
| N/A | Use this control to set detection of media peer inactivity (
When both RTP and RTCP are enabled, the timeout will only occur if both packet types remain undetected for the configured When INFO: When using this feature, you must also set the " NOTE: If a valid RTP stream does not send enough packets, use NOTE: If the endpoint does not send both RTP and RTCP packets frequently enough within the |
| N/A | Use this control to set the UDP media port range for RTP and RTCP.
High priority port range is optional configuration that divides the media port range into a high-priority port range and a low-priority port range. Under congestion conditions, all the packets received on ports outside the high priority media range are dropped automatically by the network processing layer. Therefore, if you choose to configure SIP signaling ports within the media port range, Ribbon recommends they reside within the high priority port range so that packets are not dropped. |
| N/A | Use this control to configure the RTCP session.
|
| N/A | This port range is used by the SBC to advertise its TCP port on which it can accept connections. A unique unused port from this range will be included in the SDP media line in the offer or answer towards the MSRP UAs. SBC uses a port from this range per MSRP call leg if it takes up a TCP server role. To create a TCP port range, use the
|
The following example sets inactivityTimeout
value to 90, the baseUdpPort
to 6000, the maxUdpPort
number to 65100 and the senderReportInterval
to 6 seconds and sendBYEPacket
to enabled, plus sets the peerAbsenceAction
parameter from packetServiceProfile
object to send a trap if inactivity is detected.
set system media mediaPeerInactivity inactivityTimeout 90 set system media mediaPortRange baseUdpPort 6000 maxUdpPort 65100 set system media mediaRtcpControl senderReportInterval 6 set system media mediaRtcpControl sendBYEPacket enabled set profiles media packetServiceProfile DEFAULT peerAbsenceAction peerAbsenceTrap show system media mediaPortRange { baseUdpPort 6000; maxUdpPort 65200; } mediaPeerInactivity { inactivityTimeout 90; } mediaRtcpControl { senderReportInterval 6; sendBYEPaket enabled; }