Advanced Options field descriptions

Last Updated : Feb 27, 2025 |

Periodic Statistics tab

Name

Description

Collect Periodic Statistics

Specifies whether collecting periodic statistics must be enabled.

Collection Interval

Specifies the time interval for which the system collects call statistics. The EMS server generates a report with statistics for the specified collection interval.

When you enable collection of periodic statistics, the EMS server purges data collected before the collection interval you specify.

Feature Control tab

Name

Description

AMS Offloading

Enables the AMS offloading feature.

Call Walking Protection

Enables the Call Walking Protection feature.

Media Tunneling

Enables the media tunneling feature.

Phone Dos/DDoS Protection

Enables the Phone DoS/DDoS Protection feature.

Single Source DoS Protection

Enables the Single Source DoS Protection feature.

SIP Overload Control

Enables the SIP Overload Control feature.

Stealth DoS/DDoS Protection

Enables the Stealth DoS/DDos Protection feature.

Transcoding

Enables the media transcoding feature.

Transrating

Enables the transrating feature.

SIP Options tab

Name

Description

DNS Caching

Enables DNS Caching.

AS-SIP Mode

To enable the transmission of SIP and SRTP combination towards SIP trunks or call servers in JITC environment or enclave deployment.

When AS-SIP Mode is enabled Avaya SBC supports SRTP over SIP towards the SIP trunks or call servers. Avaya SBC converts the SIPS to SIP towards the SIP trunks or call servers.

E911 URI Group

Frees the numbers in the Emergency URI group from any dial-out restrictions that might be imposed by Domain Policies.

The Emergency URI group is an integral part of the system that is user defined. The Emergency URI group defines special numbers that must not be restricted by any Domain Policies. Avaya SBC administrators must provide all applicable emergency numbers for their country for special handling.

Maximum Concurrent Sessions

Specifies the number of allowed concurrent dial-out sessions. A value of zero provides unlimited sessions.

Allow Emergency Call Preemption
When enabled and the Maximum Concurrent Sessions limit is reached for a policy group:

  • On receiving a non-emergency call, Avaya SBC rejects call and raise an incident.

  • On receiving an emergency call, Avaya SBC accepts the call and disconnects an active non-emergency call from the same policy group.

When disabled and the Maximum Concurrent Sessions limit is reached for a policy group:

  • On receiving a non-emergency call, Avaya SBC rejects call and raise an incident.

  • On receiving an emergency call, Avaya SBC accepts the call.

By default, this field is disabled.

Network Options tab

Name

Description

Allow Non-Unique IPs for Complex Networks

Enables reusing IPs in complex networks.

Port Ranges tab

For SIP deployments, you must create Internal signaling and media interfaces toward Call Server and External signaling and media interfaces toward Trunk Server.

Note:

The fixed ports for TCP, UDP, or TLS defined under Network & Flows > Signaling Interface must not be assigned a port number that falls within a Signaling Port range. A fixed port for TCP, UDP, or TLS is a shared Listen Port for multiple calls incoming to Avaya SBC from a Trunk Server or Call Server.

Name

Description

Signaling Port Range

Used by Avaya SBC to start connections for outgoing SIP requests from Avaya SBC towards a SIP Server (Call Server or Trunk Server).

The direction of these ports is away from Avaya SBC.

For the changes to the Signaling Port Range field to take effect immediately, ensure that you do one of the following:

  • Select the Enable Grooming check box on the Services > SIP Servers page and select Extensions as None on the Configuration Profiles > Server Interworking page.

  • Clear the Enable Grooming check box on the Services > SIP Servers page and select Extensions as Avaya on the Configuration Profiles > Server Interworking page.

Config Proxy Internal Signaling Port Range

Used by Avaya SBC to start connections from Avaya SBC toward Configuration Servers. For example, configuration servers of the following types: HTTP, HTTP Proxy, HTTPS, LDAP, TFTP, and SCEP.

The direction of these ports is away from Avaya SBC.

Listen Port Range

Used in PORTID Mode. See Managing SIP Server Configurations. Avaya SBC listens to these ports for requests from a SIP Server, usually a Call Server, during intermittent, phone-related communications. For example, during calls and signaling, where a link does not stay up indefinitely.

The direction of these ports is towards Avaya SBC.

HTTP Port Range

Used by Tinyproxy to start connections for Avaya SBC towards the upstream server or http server based on the routing for intermittent communications unrelated to the phone. For example, for web services and media, where a link does not stay up indefinitely.

The direction of these ports is away from Avaya SBC.

RTCP Monitoring

Name

Description

RTCP Monitoring Relay

Enables or disables RTCP monitoring.

Node Type

Specifies the type of Avaya SBC configuration for the node.

The options are:

  • Core

  • DMZ

  • Remote

Relay IP

Specifies the relay IP address.

Note:

  • For CORE Avaya SBC configuration, in the Relay IP field, click Core SBC Internal IP1.

  • Core Avaya SBC Internal IP1 address is used to send RTCP traffic received from DMZ SBC and core phones towards monitoring server.

Port

Specifies the port number for RTCP monitoring.

RTCP Monitoring Report Generation

Specifies whether RTCP monitoring report generation is enabled

SBC Interface IP

Specifies the source IP address of Avaya SBC for communication between Avaya SBC and the monitoring tool.

Note:

The IP address must be the IPv4 address.

SBC Interface Port

Specifies the source port number of Avaya SBC for communication between Avaya SBC and the monitoring tool.

Monitoring server IP/FQDN and Port

Specifies the destination IP address and port number of the remote monitoring tool.

Note:

The IP address must be the IPv4 address.

Monitoring Frequency based on RTCP Report

Specifies the number of RTCP packets received from a SIP trunk after which Avaya SBC generates the RTCP monitoring report.

Monitoring interval in absence of RTCP Report

Specifies the interval (in seconds) between two consecutive RTCP monitoring reports.

HA Pairs

Name

Description

Keep Alive Interval

Used by Avaya SBC to keep track of the status of other Avaya SBC in HA pair.

The default value is 1500 milliseconds.

The time range is 300 to 3000 milliseconds.

Max Retries

The maximum number of attempts for which Avaya SBC must try to reach the HA pair. You can enter a value between 2 and 5. The default value is 4.

Load Monitoring tab

Name

Description

Load Balancer Type

Type of load balancer.

The available options are:

  • INTERNAL: Load balancer on the A1 side of the network. Iview, the Avaya Meetings Server management entity, does load balancing towards the internal side. All HTTP requests sent for dialing out use the internal load balancer logic to identify the appropriate Avaya SBC.

  • EXTERNAL: Load balancer on the B1 side of the network. All HTTP requests sent for dialing in use the external load balancer, depending on the data sent.

Transport

Transport protocol used by the load balancer.

Note:

If TCP/TLS Listen Port in configuring TURN STUN profile is configured as 443, you must use TCP as the Transport protocol in load monitoring to avoid port conflict of Listen IP port and Media Relay IP while configuring TURN Relay.

Listen IP

Load balancer listen IP address.

Note:

Ensure that at least one IP address is configured in Network Management for listen IP configuration. The system supports IPv4 and IPv6.

Service Type

Service type supported by load balancer

The available options are:

  • None

  • TURN

  • Media Tunnel