...
Add_workflow_for_techpubs |
---|
AUTH2 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c857f0393d015845e3e4d4000f8a00a0c87befb553017c1aa323650024, userName='null'} |
---|
JIRAIDAUTH | SYMCHOR-2719710125 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a0c87befb553017c1aa323650024, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a02355cd1c2f0155cd26cb8305e9, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce5f0b8d8a00a02355cd1c2f0155cd26cef20cbf, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdea0ac18a00a02355cd1c2f0155cd26cef20cbf, userName='null'} |
---|
|
...
Modifying a Media List
...
Start
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Media > Media Lists.
Image Added
- Click the expand (Image Added) Icon next to the entry you wish to modify.
- Edit the entry properties as required, see details below.
...
Modifying a Media List
...
Creating a Media List
Start
Click the Create Media List () icon at the top of the Media List View page. pane.
Create Media List - SBC 1000/2000
Image Added
Create Media List - SBC SWe Edge
Image AddedImage Removed
Media List - Field Definitions
Include Page |
---|
| UXDOC120:_Object_within_ObjectUXDOC120: |
---|
| _Object_within_Object |
---|
|
Info |
---|
|
note |
When selecting the G729 profile: If your device supports only G729a, then be sure to configure Silence Suppression to Disable Disabled. The G729a codec does not support Silence Suppression. SBC SWe Edge: The G.722 codec does not support Silence Suppression. |
Caption |
---|
0 | Table | 1 |
---|
Media List Fields
Field | Description |
---|
Description | A name that describes the Media List. Typically, the SIP Signaling Group specifies the Media List for calls that use the Signaling Group. |
Media Profiles List | Specifies a list of Media Profiles for use with this Media List. Codec profile order determines the order in which codecs are specified in SIP message(s) sent to a peer. Consider user preferences when ordering codec profiles, placing the more desirable codecs above the less desirable ones. Use the following options to edit the profile: |
...
- : Moves the profile up in the list.
- Down
|
...
- : Moves the profile down in the list.
- Add/Edit
|
...
- : From the Select Media Profile box, click to select a profile and click OK. The profile is added to the list.
- Remove
|
...
- : Removes the profile from the list.
|
SDES-SRTP Profile | Specifies the profile for authentication/encryption protocols applied with this Media List. For details about profiles for Source Description RTP packet (SDES) and Secure Real-time Transport Protocol (SRTP), refer to Managing SDES-SRTP Profiles. |
...
| If you are not using SRTP, set this parameter to None. |
|
DTLS-SRTP Profile | Specifies the profile for secure communications protocols applied with this Media List. The DTLS-SRTP extension of the Datagram Transport Layer Security (DTLS) protocol negotiates SRTP keying between the SBC 1000/2000 and Microsoft Teams over the UDP media port. Options in the |
...
dropdown list are derived from the DTLS-SRTP Profiles configured on the SBC Edge. For details, refer to Working with DTLS-SRTP Profiles. |
Media DSCP | The Differentiated Services Code Point (DSCP) value to assign for all media flows created using this Media List. The default Media DSCP value is 46 and the allowed range is [0..63]. Choose an appropriate DSCP value based on the QoS policies of the IP network traversed by the media packets. |
RTCP Mode | Specifies the mode for carrying statistical and control data for RTP when using this media list: |
...
...
...
- : Sends basic RTCP messages to the peer.
- RTCP-XR (Extended Reports): Sends Real Time Control Protocol - Extended Reports (RTCP-XR) packets to the peer. Some SIP endpoints cannot handle the RTCP-XR packets that include more information, so specify basic RTCP to lessen the risk of overloading. Only select RTCP-XR when you know that the far end supports it.
RTCP-XR provides packet transport quality metrics designed to supplement the packet-loss metrics and the roundtrip delay measurements provided by RTCP. The extended reports also include metrics for IP Packet Delay Variation (IPDV) based on the activity of the RTP end system's receiver's jitter buffer, and metrics for reporting "errored" and "severely errored" seconds.
For more information about RTCP-XR, see RFC 5093. Info |
---|
| RTCP Mode is not applicable for . |
|
Dead Call Detection | Specifies whether or not to use RTCP-based Dead Call Detection (DCD). DCD is accomplished by monitoring incoming RTCP packets. If this feature is enabled and no RTCP packets are received from the peer for 30 seconds, the call is considered "dead" and is disconnected. Disable DCD for any peer that does not send RTCP packets. |
Silence Suppression | Specifies whether or not to use Voice Activity Detection and send PT13 packets when on. - If Silence Suppression is
|
...
...
- the monitors outgoing audio (towards the IP network). Upon detecting silence, voice packet transmission ceases to save network bandwidth. Enabling Silence Suppression saves network bandwidth; however, voice quality may be slightly degraded.
- If Silence Suppression is
|
...
- Disabled, voice packets are sent regardless of whether audio is present.
|
Enforce SG Codec Priority | Specifies whether or not to force codec priority order as configured in the Media List. - If Enforce SG Codec Priority is Enabled, the SBC SWe Edge forces codec priority order for both inbound and outbound calls.
- If Enforce SG Codec Priority is Disabled, the SBC SWe Edge uses codec priority order only for outbound calls. For inbound calls, the SBC SWe Edge continues to use the codec priority as received in the Session Description Protocol (SDP) offer.
Info |
---|
| Enforce SG Codec Priority is available for SBC SWe Edge only. |
|
Include Page |
---|
Include Page |
---|
|
UXDOC120:_Multiselect_WidgetUXDOC120: | | _Multiselect_Widget |
---|
nopanel | true |
---|
|
Gain Control - Field Definitions
Set the gain control Gain Control fields to manipulate gain or loss (in decibels) for received and transmitted signals. With gain control Gain Control, the negative values represent signal attenuation (lower volume) and the positive values represent signal amplification (higher volume).
Info |
---|
|
Gain Control fields are not applicable for . |
...
Gain Control Field Definitions
Field | Description |
---|
Receive Gain | Specifies the gain or loss in decibels to apply to received signals. (Packet → PCM direction). |
Transmit Gain | Specifies the gain or loss in decibels to apply to transmitted signals (PCM → Packet direction). |
Passthrough/Tone Detection - Field Definitions
...
Passthrough/Tone Detection Field Definitions
Field | Description |
---|
Modem Passthrough | Specifies whether or not modem passthrough is enabled when using the G.711 codec. If |
the user wants you wish to support modem calls, enable this option |
should be Enabled the the does not distinguish between voice and modem calls. When Enabled, and |
the the detects a modem call, it switches to Modem Passthrough mode (based on G.711 codec). |
Fax Passthrough | Controls whether or not the supports G.711 faxing.- If you wish to force fax calls to use G.711 (uLaw/aLaw) codec, then Fax Passthrough must be Enabled. Also, G.711 must be the only codec in the Media List. In this configuration, the will only offer/accept G.711 in the
|
reINVITE- If you wish to support both G.711 and T.38 faxing simultaneously, the Fax Passthrough must be Enabled, and
|
the - the must be configured with both G.711 and T.38 codecs. Which faxing type is selected will depend upon the codecs offered/accepted in the
|
reINVITE- re-INVITE.
- If you wish to force fax calls to use T.38 codec, configure the Fax Passthrough to
|
Disable The - The must be configured for both G.711 and T.38 codecs. In this configuration, the will only offer/accept T.38 in the
|
reINVITE: | If the fax destination offers only T.38 in the |
|
reINVITE the the must be configured for both G.711 and T.38. As noted above, T.38 fax negotiation is possible whether Fax Passthrough is set to |
|
Enable DisableNote: The CNG Tone Detection field is not applicable for .
Specifies whether or not the detects Fax tones produced by the origination-side fax machine. CNG tone detection is required when Fax calls are received from TDM for a Fax server, and the voice call needs to be switched to a Fax call using T.38. If CNG |
tone detection enabled the the detects the Fax tone from TDM and switches to Fax mode (it will initiate a re-INVITE with T.38 support to the Fax Server). If CNG |
tone detection disabled the pass-through passthrough the Fax tones to the Fax server and the Fax server must detect the tones and initiate a re-INVITE to switch to Fax mode with T.38. Info |
---|
| CNG Tone Detection is not applicable for . |
|
Fax Tone Detection | Specifies whether or not the system will detect Fax tones produced by the |
terminating side terminating side fax machine. Fax tone detection (V.21 flags) is used when Fax calls are received from TDM to a Fax server and the voice call needs to be switched to a Fax call using T.38. If Fax |
tone detection enabled the the detects the Fax tone from TDM and switches to Fax mode (it will initiate a re-INVITE with T.38 support to the Fax Server). If Fax |
tone detection disabled the pass-through passthrough the Fax tones to the Fax server and the Fax server will have to detect them and initiate a re-INVITE to switch to Fax mode with T.38. |
DTMF Signal to Noise |
Note: The DTMF Signal to Noise field is not applicable for .
Sets the Signal to Noise Ratio that affects DTMF detection. Setting higher Signal-to-Noise ratio values reduces the chance of false detection; however, a setting can be too high for the amount of noise in an audio stream. Use this field to set a value in the range -3 dB to +6 dB. The default value for the field is 0 dBM. |
DTMF Minimum Level: The DTMF Minimum Level field |
DTMF Minimum Level | Sets the minimum signal level for DTMF detection; DTMF digits lower than the minimum are not detected. Valid entries: -48 to -14 dBm0. The default value of the field is -38 dBm0. Info |
---|
| DTMF Minimum Level is not applicable for . |
|
Digit Relay - Field Definitions
...
Digit Relay Field Definitions
Field | Description |
---|
Digit (DTMF) Relay Type | Specifies how DTMF digits are passed through the data network; as normal voice or encoded as specified in RFC 4733 (RFC 2833). RFC 4733 (RFC 2833): When a DTMF digit is detected in the voice stream coming from the TDM side, the digit is removed from the voice stream (going to the IP network), and is sent out-of-band using the RFC 4733 (RFC 2833) mechanism. As Voice: The DTMF digits are sent in the voice stream without any special treatment. |
Digit Relay Payload Type | Specifies the payload type used for RFC 4733 (RFC 2833) packets. Available only when RFC 4733 (listed as RFC 2833) is specified for Relay Type. |