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 sections of the UI and are explained on their own topic pages.
UDP ports are used for transmission of 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 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 Portfolio (SBC). For example; if you have 100 pairs, you can have a maximum of 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 SBC SWe Edge Release 7.0 and later only: The number of RTP Port Pairs must be configured slightly larger than the actual 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 that are 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. If a local endpoint does not respond to the pings, and if media IP address is different than signaling IP address, the call may have audio issues.
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 Edge - Media System Configuration
Media System Configuration
Port Range - Field Definitions
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.
- For SBC 1000/2000. Valid entry: 1 - 4800.
- For SBC SWe Edge. Valid entry: 2 - 5000.
To determine the last port number, use the formula: First Port Number + (2*Number of Port pairs) - 1.
Example using starting port number (16384) and the number for port pairs is 600.
There are 600 pairs, meaning there are 1200 individual ports. 16384 + (1200-1) = 17583
Music on Hold - Field Definitions
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). 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:
- For SBC 1000: 1MiB
- For SBC 2000: 4MiB
- For SBC SWe Edge: 5MiB
Music files must be one of the following formats:
- WAV
- PCMA (not supported in SBC SWe Edge)
- PCMU (not supported in SBC SWe Edge)
- PCM (not supported in SBC SWe Edge)
For detailed information about how to upload a Music on Hold file, see Uploading Music on Hold Files - SBC Edge Portfolio or Uploading Music on Hold Files - SBC SWe Edge.
FXS Port
A list of 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
Echo Canceller Type Option
This field applies to SBC 1000/2000 only.
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 128ms tail length and uses 48ms sparse foreground filter. The Dual Filter is expected to provide better performance during double talk or slow echo-path change. Selection of the Dual Filter option may result in reduced channel densities.
Ribbon recommends to 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
This 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 each telephony system implementation 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
This 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 enable/disable this option is for customers who do not have a firewall and would like a way to disable STUN packet generation. Two options are available: Enable (STUN packets are generated and sent by the SBC) or Disable (STUN packets are not generated). Default option: Enable.
Overview
Content Tools