Parameter | Length/Range | Description |
|---|
dedicatedBWForNonRTPMedia
| 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. | enhancedApplicationMediaSupport
| N/A | This flag is specific to application media. disabled (default)enabled
When the flag is enabled, the following functionality is supported: - The SBC initiates and establishes TCP on the egress leg only after the TCP connection is successful on ingress leg.
- The SBC supports transmitting URG (urgent) data from one leg to another.
- The SBC supports establishing and disconnecting a TCP connection multiple times within the same SIP session.
| mediaPeerInactivity
| N/A | Use this control to set detection of media peer inactivity (inactivityTimeout) which can be used in conjunction with packet loss rate parameter (packetLossThreshold) of Packet Service Profile. When both RTP and RTCP are enabled, the timeout will only occur if both packet types remain undetected for the configured inactivityTimeout duration. If RTCP is not enabled, then only the absence of RTP causes the timer to expire. When mediaPeerInactivity is enabled (configured with an inactivityTimeout value), the SBC detects media inactivity within the configured inactivity timeout value + X, and then executes the configured action (where the X is from 0 - 10 seconds). INFO: When using this feature, you must also set the "peerAbsenceAction" flag from Packet Service Profile (refer to Packet Service Profile - CLI). NOTE: If a valid RTP stream does not send enough packets, use mediaPeerInactivity with RTCP only. NOTE: If the endpoint does not send both RTP and RTCP packets frequently enough within the inactivityTimeout duration, Ribbon recommends to avoid using mediaPeerInactivity. Note: On the PSX Manager > Packet Service Profile screen, the field "Media Peer Inactivity Timeout (s)" allows the user to reduce the timeout duration to 0-1260 seconds for specific zones during emergency calls such as 911 calls. By default it is set to 0 (disabled). The value set on the PSX Manager takes precedence over the value set on the SBC side. When the field "Media Peer Inactivity Timeout (s)" on the PSX is set to 0 (disabled), the SBC uses the configuration value set on the SBC side. | mediaPortRange
| N/A | Use this control to set the UDP media port range for RTP and RTCP. baseUdpPort – Base UDP port number (inclusive) for RTP/RTCP media. (range: 1024-65534 / default = 1024).maxUdpPort – Maximum UDP port number (inclusive) for RTP/RTCP media. (range: 1024-65534 / default = 65148). An error message appears if you set the range to a value greater than 65148 because that overlaps a Linux reserved port range (65150 to 65535). Do not specify a value greater than 65148.highPriorityPortRangeLocation – Specifies whether the high priority port range, if specified, occurs at the top or the bottom of the media port range.bottom – high priority ports are at the bottom of the range.top – high priority ports are at the top of the range.
highPriorityPortRangeSize – Specifies the percentage of the configured port range to include in the high priority range. Specifying 0 disables having a high priority range.(range: 0-25)
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, recommends they reside within the high priority port range so that packets are not dropped. Note: - Starting with SBC Core 8.1, the SBC supports configuring the parameters
highPriorityPortRangeLocation and highPriorityPortRangeSize across all supported hardware, software, and cloud platforms. - The configuration for the parameters
highPriorityPortRangeLocation and highPriorityPortRangeSize defines the High Priority Media Port Range (HPMPR) as a subset of the overall MPR. The SBC uses the configuration to quickly identify UDP packets (both media and non-media) arriving within the overall MPR, and prioritizes them while processing ingress UDP packets. For GETS/HPC applications, Ribbon recommends reserving 10% of the MPR as HPMPR. If additional SIP Signaling Ports (besides the default port 5060), and/or other Control UDP ports are within the overall MPR, Ribbon recommends configuring them within the HPMPR. Such configuration ensures that during congestion, they are prioritized while processing ingress packets.
For example, if the overall MPR is defined as 1024-65535, and the High Priority Port Range is 10% (starting with the lower limit of MPR), then the HPMPR is 1024-7475. Ribbon recommends configuring additional SIP Signaling and other Control UDP ports within the range 1024-7475. In case of congestion, such configuration ensures that while processing ingress packets, packets received at ports within the range configured for HPMPR are prioritized. Normal calls are allocated local UDP ports ranging from 7476-65535, and GETS/HPC calls are allocated local UDP ports ranging from 1024-7475.
| mediaProbe | N/A | | Multiexcerpt include |
|---|
| MultiExcerptName | mediaProbe-Protect_overview |
|---|
| PageWithExcerpt | SBXDOC120:Protect - CLI |
|---|
|
NOTE: To establish communication to Protect, refer to Protect - CLI. Configure mediaProbe with the following values to capture and report media quality statistics (RTP/RTCP) and DTMF packets to Protect. dscpValue <DSCP value> – The DSCP value for Media Probe RTCP application packets. Range: 0-63. Default = 0.encryptionType – The encryption type used towards the Ribbon Protect server. Currently, the does not support any encryption.format – The Media Probe format used to report qCDR (quality CDR capturing QoS statistics associated for a leg for each RTP-based stream). Currently, the only supports RTCP.mediaProbeAddressContext – Address Context associated with the Media Probe IP Interface Group.mediaProbeIpInterfaceGroup – Media IP Interface Group used to transmit Media Probe packets to the remote Protect server.protocolType – The network protocol used to transfer the data to the remote server. Currently, the supports only UDP.reportingInterval <1-8> – The interval at which RTCP application packets are sent to the remote Ribbon Protect server, expressed as an integral multiple of the Media RTCP Control senderReportInterval value (configurable to 5-16 seconds). Default is "1".
For example, if senderReportInterval is set to 5 seconds, then- set
reportingInterval to "1" to send media probe packets every 5 seconds (senderReportInterval x 1).
- set
reportingInterval to "8" to send media probe packets every 40 seconds (senderReportInterval x 8).
state – Use this flag to enable/disable the system-wide Media Probe state.disabled (default)enabled
| mediaRtcpControl
| N/A | Use this control to configure the RTCP session. | tcpPortRange
| 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 baseServerPort and maxServerPort to specify the minimum and maximum values as described below. baseServerPort – Base port number (inclusive) for TCP media server (range: 1-65534 / default = 1024).maxServerPort – Maximum port number (inclusive) for TCP media server (range: 1-65534 / default = 65534).
|
|