Preferred Format #1

The most preferred encryption method for media traffic. Available selections are:

• RTP

• SRTP_AES_CM_128_HMAC_SHA1_32

• SRTP_AES_CM_128_HMAC_SHA1_80

• SRTP_AES_192_CM_HMAC_SHA1_32

• SRTP_AES_192_CM_HMAC_SHA1_80

• SRTP_AES_256_CM_HMAC_SHA1_32

• SRTP_AES_256_CM_HMAC_SHA1_80

Preferred Format #2

The second most preferred encryption method for media traffic. Available selections are the same as those in Preferred Format #1.

Preferred Format #3

The third most preferred encryption method for media traffic. Available selections are the same as those shown in Preferred Format #1.

Encrypted RTCP

Indicates whether RTCP uses encryption.

MKI

MKI is the Master Key Identifier. Specifies the master key of the SRTP session and is stored in the SRTP context. You can derive other session keys from this master key after the lifetime expires.

Lifetime

Specifies the time interval after which session keys are generated. These keys are not passed in signaling. Session keys are based on MKI. Currently, Avaya SBC does not support the interworking of different lifetime values.

You can leave this field blank to match any value.

Interworking

Indicates whether media from encrypted endpoints can flow to unencrypted endpoints and vice versa. Select this check box for media rules in both the endpoint flows. Enable this setting unless you want to enforce end-to-end encryption.

Symmetric Context Reset

There are two types of SRTP context reset: Symmetric and Asymmetric. For Symmetric, both the Tx and Rx context are set while sending the new offer. For Asymmetric, only Tx is set while sending the new Offer. Avaya media servers support Asymmetric SRTP context reset. However, some Avaya endpoints such as H.323, 96xx, and Avaya Workplace Client do not support Asymmetric SRTP context reset.

By default, this option is enabled.

Key Change in New Offer

Use this option to control whether a new cryptography key is generated when a new OFFER message is received. A new OFFER message is defined by a change in any of the following scenarios:

• Media direction, such as hold/unhold or video mute/unmute

• SDP version change

• Delayed offer

By default, this option is disabled.

Capability Negotiation

Enables SIP and SDP signaling compliant to the RFC-5939 specification. Select this check box only if the Remote Worker supports SDP Capability Negotiation.

Codec Prioritization

Force audio codecs to be matched according to the priority defined by the Preferred Codec Priority 1 through Preferred Codec Priority 5 fields.

Allow Preferred Codecs Only

Matches only the codecs listed in the previous Preferred Codec Priority fields. Audio codecs not listed are not matched.

Transcode

Specifies that the media matched by this media rule must transcode traffic when possible. When you select this option, the system displays [Transcodable] next to the codecs that can be transcoded.

Transrating

Specifies that the media matched by this media rule must use transrating to reduce the bit rate of the media.

Preferred Codecs

Names of audio codecs that you want matched in a particular order. These are optional fields to be completed only if Codec Prioritization is selected.

The Available column lists all the available codecs. You can select a single codec, or hold down the Ctrl key and click to select multiple codecs simultaneously. Click > to move the codecs to the Selected column. Click ^ or v to change the order of the codecs in the Selected column.

The P-Time column lists the available packetization times. When you select a codec and a p-time, and click > to move the codecs to the Selected column, the Selected column displays the codecs with the p-time next to the codec name. This means the system applies transrating at the selected p-time for the preferred codecs.

Codec Prioritization

Forces audio codecs to be matched according to the priority defined by the Preferred Codec Priority 1 through Preferred Codec Priority 5 fields.

Allow Preferred Codecs Only

Matches only the codecs listed in the previous Preferred Codec Priority fields. Audio codecs not listed are not matched.

Transcode When Needed

This field is unavailable for video codecs. Avaya SBC does not support transcoding for video codecs.

Transrating

This field is unavailable for Video Codecs. Avaya SBC does not support transrating for video codecs.

Preferred Codecs

Names of video codecs that you want specifically matched in a particular order. These are optional fields you must administer only if Codec Prioritization is selected.

The Available column lists all the available codecs. You can select a single codec, or hold down the Ctrl key and click to select multiple codecs simultaneously. Click > to move the codecs to the Selected column. Click ^ or v to change the order of the codecs in the Selected column.

The P-Time column lists the available packetization times. When you select a codec and a p-time, and click > to move the codecs to the Selected column, the Selected column displays the codecs with the p-time next to the codec name. This means the system applies transrating at the selected p-time for the preferred codecs.

Silencing Enabled

Indicates whether Avaya SBC detects media packets from both legs of a call within the set time. If no media packets are detected, Avaya SBC sends an incident report to the Syslog, and the call is disconnected.

By default, this option is enabled.

Timeout

Indicates the period (in seconds) within which the media silencing feature processes media packets from both legs of a call. If no media packets are detected in this period, Avaya SBC sends an incident report to the Syslog or the call is terminated.

By default, this option is set to 60 seconds.

BFCP Enabled

Indicates whether Binary Floor Control Protocol (BFCP) is used in a people and content telepresence scenario to control the content channel. Content information is passed as a video stream and is controlled by the BFCP channel. It enables the moderator to release floor control to participants and vice versa to give control of the content channel to various participants. The system works on sending a token on the BFCP control signaling. The moderator allows or denies the access to the token. Avaya SBC can support one BFCP channel for multiple video content channels.

FECC Enabled

Indicates whether Far End Camera Control (FECC) is enabled. It provides mixed encryption support for audio, main video, and FECC. In the media path, using an RTP payload type sends control signaling to control the far end camera. The FECC channel facilitates setting up the signaling for the media path, and control signals are sent on this path using the RTP payload type of a particular codec type (H.224).

RTT Enabled

Real Time Text (RTT) defines a payload type in the SDP offer answer for carrying a text conversation in real time sessions in RTP packets. The text conversation is used along with voice, video and other multimedia conversations. RTT is used with the NG911 feature of Avaya SBC to facilitate sending real time text messages to an emergency PSAP. It can also be used if any other application that requires RTT.

When the RTT Enabled option is enabled, Avaya SBC relays RTT (media type = text) in SDP. Avaya SBC invokes NAT for the addresses on SDP and at Media Plane while relaying the RTT in SDP. Avaya SBC does not filter or modify the parameters in SDP in case of RTT.

An SDP with RTT enabled looks similar to the following example:

m=text 11000 RTP/AVP 100 98
a=rtpmap:98 t140/1000
a=rtpmap:100 red/1000
a=fmtp:100 98/98/98

When the RTT Enabled option is disabled, Avaya SBC responds with Port 0. The default setting for RTT Enabled is disabled.

ANAT Enabled

Specifies whether Alternate Network Address Types (ANAT) semantics are enabled for SDP to permit alternate network addresses for media streams. ANAT semantics are useful in environments with IPv4 and IPv6 hosts.

Local Preference

Specifies the order of preference for the Alternate Network Address Types IPv4 and Dual Stack IPv6.

Use Remote Preference

Specifies that the remote party must be given ANAT preference to answer the 200 OK response offer, irrespective of the ANAT preference configured on Avaya SBC.

TTL Override Enabled

When enabled, a TTL value between 1 and 255 can be configured. Avaya SBC overrides TTL value in all outgoing media packets. When configured, it changes TTL field in IPV4 packets and HopLimit field in IPV6 packets.

The default value is disabled.

This field setting will not have any effect on following Avaya SBC media handling features:

• Media tunneling

• Turn Controller

Media Line Compliance Enabled

Use this field to maintain compliance between the media lines especially for transfer. For example, if the transferee supports audio and video lines and the transfer target supports only audio and if this field is enabled, Avaya SBC maintains audio lines towards the transfer target and audio and video lines towards the transferee.

As per RFC 3264 compliance media lines should match in offer and answer. In case of there are devices on either side of Avaya SBC where media lines are different, Avaya SBC interworking maintains parity of media lines on both sides of Avaya SBC.

ICE Gateway Support

Enables support for Interactive Connectivity Establishment (ICE) used when connecting with Microsoft Teams. When enabled, you can administer the Local Media Optimization options.

Local Media Optimization options

Use these options to set the site name, site domain, and the action taken when enabling the Local Media Optimization and Media Bypass features.

As an example, you have salespeople who work at the main sales office, one of your many branch offices, and visit customers who might be at any location. Avaya SBC and Teams can be administered to handle calls efficiently for the salespeople no matter where they are located, using the call processing facilities that are local to them. For example:

• When sales people are in the main sales office, calls placed or received are administered to use the main, or core, Avaya SBC system configured for the main sales office.

• When the salespeople are working at the branch sales office, calls placed or received are administered to use the branch Avaya SBC system configured for the branch sales office.

• When the salespeople are on the road visiting customers, calls placed or received using their mobile devices are administered to use the PSTN.

When administering the Local Media Optimization options, follow this general scenario:

• On the local Avaya SBC, administer a local site name, the domain name for that site, and set the action to Local User.

• On the proxy Avaya SBC that is visible to the Microsoft Phone system, administer the proxy site name, the domain name for that proxy site, and set the action to Media Bypass.

Site Name

Use this option to set the site name used within the X-MS message header.

Site Domain

Use this option to set the domain name used within the X-MS message header.

Action

Select one of the following actions as required:

• Media Bypass – Use this option to enable Local Media Optimization on the proxy Avaya SBC that is visible to the Microsoft Phone system.

• Local User – Use this option when you want to enable Local Media Optimization on the downstream Avaya SBC in a local branch office.

Audio Port Change on New Offer Enabled

Specifies whether Avaya SBC generates new ports when a new OFFER message is received. By default, this option is disabled, meaning Avaya SBC will not generate new ports.

Video Port Change on New Offer Enabled

Specifies whether Avaya SBC generates new ports when a new OFFER message is received. By default, this option is disabled, meaning Avaya SBC will not generate new ports.

RTCP-MUX Enabled

Enables RTCP-Mux (Real-time Transport Control Protocol Multiplexing).

Enabling RTCP-Mux works only when Ice Gateway Support is enabled.

Enabled

Indicates whether Media QoS marking is enabled.

ToS

Indicates whether Type-of-Service (ToS) is enabled. The Audio Precedence, Audio ToS, Video Precedence, and Video ToS fields are activated if the ToS option is selected.

The following options are available for the Audio Precedence and Video Precedence fields:

• Network Control

• Internetwork control

• CRITIC/ECP

• Flash Override

• Flash

• Immediate

• Priority

• Routine

The following options are available for the ToS field:

• Minimize Delay

• Maximize Throughput

• Maximize Reliability

• Minimize Monetary Cost

• Normal Service

• Other...

DSCP

Indicates the significant values for Differentiated Services (DiffServ). These values, referred to as the Differentiated Services Point Code (DSCP), provide guaranteed service to critical network traffic.

The following options are available for the Audio and Video fields:

• EF

• AF11

• AF12

• AF13

• AF21

• AF22

• AF23

• AF31

• AF32

• AF33

• AF41

• AF42

• AF43

• Other...