In this section:
Overview
The Media System Configuration contains system-wide settings for the Media System. Configuring the media system means setting the number of RTP/RTCP port pairs and the starting port. Other aspects of media handling, such as Media Profiles, Lists, and Managing SDES-SRTP Profiles, are handled in different UI sections and explained on their own topic pages.
UDP ports transmit VoIP calls employing RTP protocols (RTP over UDP). The start port is the first port that can be used for a call. Calls require a pair of ports, one for the voice and the other for the control information (RTP/RTCP). The number of port pairs determines the number of simultaneous IP Call Legs on the SBC Edge (SBC). For example, if you have 100 pairs, you can have 100 simultaneous IP Call Legs. This does not affect the number of TDM/TDM calls.
SBC Reserved Ports
Port | Protocol | Port | Protocol |
|---|---|---|---|
1 | RAW | 500 | UDP |
22 | TCP | 514 | UDP |
| 53 | TCP | 4500 | UDP |
80 | TCP | 30000 | UDP |
161 | UDP | 30001 | UDP |
443 | TCP | 16384 to17583 | RTP/RTCP |
Port Pair Considerations
For SWe Lite Release 7.0 and later only: The number of RTP Port Pairs must be slightly larger than the number of ports required to support the projected number of calls. We recommend you over-allocate the number of port pairs by approximately 25 - 30% above the number of calls you want to support.
SBC Reserved Ports - Example
Projected Number of Calls | Approximate Number of Port Pairs | Applies To |
|---|---|---|
| 100 sessions | 250 | Audio calls only * |
| 1000 sessions | 2500 | Audio calls only * |
* Multiple audio and video stream proxy calls will require twice the number of RTP port pairs with the examples provided above.
How Ping Affects Media
The SBC periodically (approximately every 30 seconds) pings all the media endpoints engaged in calls with the SBC. For local endpoints (that are on the same subnet as the SBC), this ping mechanism is used to keep the ARP cache refreshed in the SBC. The call may have audio issues if a local endpoint does not respond to the pings and the media IP address differs from the signaling IP address.
Configuring the Media System
- In the WebUI, click the Settings tab.
In the left navigation pane, go to Media > Media System Configuration.
SBC Edge - Media System Configuration
SBC SWe Lite - Media System Configuration
Media System Configuration
Port Range - Field Definitions
| Field Definition | Description |
|---|---|
| Start Port | Specifies the starting number for the RTP and RTCP port range. |
| Number of Port Pairs | The number of media port pairs used by the SBC system.
To determine the last port number: First Port Number + (2*Number of Port pairs) - 1. Example: Given: For starting port number (16384), the number for port pairs is 600. |
Music on Hold - Field Definitions
| Field Definition | Description |
|---|---|
| Music on Hold Source | Specifies the audio source. Sources can be an uploaded music file (File) or live audio sourced from an FXS port (Live). The default option is File. If you select Live, the FXS Port option is displayed. When uploading a Music file, the maximum file sizes are as follows:
Music files must be in one of the following formats:
For detailed information about how to upload a Music on Hold file, see Uploading Music on Hold Files - SBC Edge or Uploading Music on Hold Files - SBC SWe Lite. |
| FXS Port | A lists available FSX ports from which live audio may be sourced. The FXS Port field is only visible when Live is selected from the Music on Hold Service drop-down list. |
Other Options - Field Definitions
| Field Definition | Description |
|---|---|
| Echo Canceller Type Option | Note: Field only applies to SBC 1000/2000. Specifies the type of Line Echo Cancellation (standard or dual filter). The standard LEC covers 128ms tail length (echo delay) and employs a 24ms sparse (non-zero coefficients) filter. The Dual Filter (background and foreground) Line Echo Canceller (LEC) covers a 128ms tail length and uses a 48ms sparse foreground filter. The Dual Filter is expected to perform better during double talk or slow echo-path change. Selection of the Dual Filter option may result in reduced channel densities. Warning
Ribbon recommends that you not Apply any change to the Echo Canceller Type Option unless the system is idle (no calls). Applying a change while the system is not idle may result in unknown behavior. |
| Echo Cancel NLP Option | Note: Field applies to SBC 1000/2000 only. Specifies the level of echo cancellation employed by the SBC Nonlinear Signal Processor. The default value is Mild. However, there are two additional levels of echo cancellation: Strong and Aggressive. As the implementation of each telephony system varies, their echo characteristics similarly vary. Adjust the level of echo cancellation to suit your particular deployment. Too little cancellation may result in a persistent echo; too aggressive, and you may experience voice "clipping." |
| Send STUN Packets | Note: Field applies to SBC 1000/2000 only. Specifies whether STUN packets are generated from the SBC. The SBC sends STUN packets on the RTP and RTCP ports on all outbound IP call legs to open ports in the firewall (between the SBC and the Internet). The ability to turn this option on/off is for customers who do not have a firewall and would like a way to turn off STUN packet generation. Three options are available:
|
Overview
Content Tools