Configuring Sip Interfaces - AudioCodes Mediant 500 E-SBC User Manual

Parameter
Block Unregistered Users
CLI: block-un-reg-users
[SRD_BlockUnRegUsers]
Max. Number of Registered
Users
CLI: max-reg-users
[SRD_MaxNumOfRegUsers]
Enable Un-Authenticated
Registrations
CLI: enable-un-auth-registrs
[SRD_EnableUnAuthenticated
Registrations]
17.4

Configuring SIP Interfaces

The SIP Interface table lets you configure up to 32 SIP Interfaces. A SIP Interface defines
a listening port and type (UDP, TCP, or TLS) for SIP signaling traffic on a specific logical IP
network interface (configured in the Interface table). The SIP Interface can be configured
for a specific application (i.e., Gateway\IP-to-IP, SAS, SBC) and associated with an SRD.
For each SIP Interface, you can assign a SIP message policy rule, assign SIP message
manipulation rules, enable TLS mutual authentication, enable TCP keepalive, assign a
SSL/TLS certificate (TLS Context), and configure the SIP response sent upon classification
failure.
SIP Interfaces can be used, for example, for the following:

Using SIP signaling interfaces per call leg (i.e., each SIP entity communicates with a
specific SRD).

Using different SIP listening ports for a single or for multiple IP network interfaces.

Differentiating between applications by creating SIP Interfaces per application.

Separating signaling traffic between networks (e.g., different customers) to use
different routing tables, manipulations, SIP definitions, and so on.
The following procedure describes how to configure SIP interfaces in the Web interface.
You can also configure this using the table ini file parameter, SIPInterface or the CLI
command, configure voip > voip-network sip-interface.
User's Manual
The reason for this is that in Media Anchoring, the device does
not interfere in the SIP signaling such as manipulation of IP
addresses, which is necessary for calls between LAN and WAN.

When the global parameter SBCDirectMedia is disabled, Media
Anchoring can only be enabled for calls between endpoints
belonging to the same SRD.

For more information on Media Anchoring, see No Media
Anchoring (Anti-Tromboning) on page 443.
Determines whether the device blocks (rejects) incoming calls
(INVITE requests) from unregistered users (pertaining to User-type
IP Groups) for the SRD.

[0] No = Calls from unregistered users are not blocked (default).

[1] Yes = Blocks calls from unregistered users.
Note: When the call is blocked, the device sends a SIP 500 "Server
Internal Error" response to the remote end.
Maximum number of users belonging to this SRD that can register
with the device. By default, no limitation exists for registered users
Determines whether the device blocks REGISTER requests from
new users (i.e., users not registered in the device's registration
database) when the destination is a User-type IP Group.

[0] No = The device sends REGISTER requests to the SIP proxy
server and only if authenticated by the server does the device
add the user registration to its database.

[1] Yes = The device adds REGISTER requests to its database
even if the requests are not authenticated by a SIP proxy
(default).
256
Mediant 500 E-SBC
Description
Document #: LTRT-10427