AudioCodes Mediant 800B MSBR User Manual page 269

User's Manual
Parameter
SRD
CLI: srd
[SIPInterface_SRD]
Message Policy
CLI: message-policy
[SIPInterface_MessagePolicy]
TLS Context Name
CLI: tls-context-name
[SIPInterface_TLSContext]
TLS Mutual Authentication
CLI: tls-mutual-auth
[SIPInterface_TLSMutualAuth
entication]
Enable TCP Keepalive
CLI: tcp-keepalive-enable
[SIPInterface_TCPKeepaliveE
nable]
Version 6.8
Assigns an SRD ID to the SIP Interface (configured in ''Configuring
SRDs'' on page 264).
The default is 0.
Notes:

You can assign the same SRD ID to up to two SIP Interfaces of
the same application type.

For the SAS application, use only SRD ID 0.

Each SIP Interface of the same application type (e.g., SBC) that
is assigned to the same SRD must be configured with the same
IP version (IPv4 or IPv6).

All the SIP Interfaces that are assigned to the same SRD must
have the same network interface (assigned in the 'Network
Interface' parameter, above).
Assigns a SIP message policy to the SIP interface (configured in
''Configuring SIP Message Policy Rules'').
Assigns a TLS Context (SSL/TLS certificate) to the SIP Interface.
The TLS Context is assigned by name, as configured in the 'Name'
field of the TLS Contexts table.

Incoming calls: This TLS Context is used if no TLS Context is
configured for the Proxy Set associated with the call or
classification to an IP Group based on Proxy Set fails.

Outgoing calls: This TLS Context is used if no TLS Context is
configured for the Proxy Set associated with the call.
For more information about how certificates are associated with
calls and for configuring TLS Contexts, see ''Configuring SSL/TLS
Certificates'' on page 109.
Enables TLS mutual authentication for the SIP Interface (when
device acts as a server).

[-1] Not Configured = (Default) The
SIPSRequireClientCertificate global parameter setting is
applied.

[0] Disable = Device does not request the client certificate for
TLS connection on this SIP Interface.

[1] Enable = Device requires receipt and verification of the client
certificate to establish the TLS connection on this SIP Interface.
Enables the TCP Keep-Alive mechanism with the IP entity on this
SIP Interface. TCP keep-alive can be used, for example, to keep a
NAT entry open for clients located behind a NAT server, or simply
to check that the connection to the IP entity is available.

[0] Disable (default)

[1] Enable
Note: For configuring TCP keepalive, use the following ini file
parameters: TCPKeepAliveTime, TCPKeepAliveInterval, and
TCPKeepAliveRetry.
269
21. Control Network
Description
Mediant 800B MSBR