Configuring Sip Interfaces - AudioCodes Mediant 3000 User Manual

User's Manual
18.3

Configuring SIP Interfaces

The SIP Interface table lets you configure up to 32 SIP Interfaces. A SIP Interface
represents a Layer-3 network in your deployment environment, by defining a local, listening
port number and type (e.g., UDP), and assigning an IP network interface for SIP signaling
traffic. For example, if your deployment consists of an IP PBX in the LAN, a SIP Trunk in
the WAN, and remote far-end users in the WAN, you would need to configure a SIP
Interface for each of these SIP entities. You can configure the SIP Interfaces for the
different types of applications - SBC, Gateway, and SAS. Gateway SIP Interfaces are
required for Tel-to-IP and IP-to-Tel calls. You can also configure various optional features
for the SIP Interface such as assigning it a Media Realm, blocking calls received on the
SIP Interface from users not registered with the device, and enabling direct media.
Each SIP Interface can be associated with only one SRD. As the SRD configuration entity
represents your VoIP deployment SIP network (Layer 5), you need to associate your SIP
Interfaces with a specific SRD in order to represent your Layer-3 networks. For most
deployments (except multi-tenant deployments), your SRD represents your entire network
and thus, only one SRD is required. The device provides a default SRD and in such
scenarios where only a single SRD is required, your SIP Interfaces are automatically
assigned to the default SRD. Therefore, there is no need to even handle SRD configuration
entity.
Once configured, you can apply SIP Interfaces to calls, by assigning them to the following
configuration entities in their respective tables:

(Mandatory) Proxy Set to specify the SIP Interface for communication with the proxy
server (i.e., IP Group). For more information, see ''Configuring Proxy Sets'' on page
355.

IP-to-IP Routing rules for specifying the destination SIP Interface to where you want to
route the call. For more information, see ''Configuring SBC IP-to-IP Routing Rules'' on
page 603.

Classification rules for specifying the SIP Interface as a matching characteristic of the
incoming call. This is especially useful for the single SRD-configuration topology,
where each SIP Interface represents a Layer-3 network (SIP entity). Therefore,
classification of calls to IP Groups (SIP entities) can be based on SIP Interface. For
more information, see ''Configuring Classification Rules'' on page 595.

Admission Control rules to apply call admission control per SIP Interface. For more
information, see ''Configuring Admission Control'' on page 587.

Tel-to-IP Routing rules for specifying the destination SIP Interface to where you want
to route Tel-to-IP calls. For more information, see Configuring Tel-to-IP Routing Rules
on page 496.

IP-to-Trunk Group Routing rules for specifying the SIP Interface as a matching
characteristics for the incoming IP call.

Intrusion Detection System (IDS) for applying the IDS policy to a specific SIP
Interface. For more information, see ''Configuring IDS Policies'' on page 179.
Note:
following scenarios:
•
If you delete the associated SIP Interface.
•
If you edit any of the following fields of the associated SIP Interface: 'Application
Type', 'UDP Port, 'TCP Port', 'TLS Port' or 'SRD' fields.
•
If you edit or delete a network interface in the Interface table that is associated
with the SIP Interface.
Version 7.0
The device terminates active calls associated with a SIP Interface in the
337
18. Control Network
Mediant 3000