Automatic Configuration Based On Srd; Configuring Sip Interfaces - AudioCodes E-SBC User Manual

CHAPTER 18 Core Entities

Automatic Configuration based on SRD

To facilitate configuration and eliminate possible flaws in configuration due to invalid associations
between configuration entities, the Web interface automatically configures configuration entities
based on SRD:
■ If you delete an SRD (in the SRDs table) that is associated with other configuration entities in
other tables, the device automatically deletes the associated table rows. For example, if you
delete an SRD that is associated with a Proxy Set, the device automatically deletes the Proxy
Set.
■ If you associate an SRD with a configuration entity in another table (i.e., other than the SRDs
table), the device automatically configures certain parameters of the configuration entity
according to the SRD or associated SRD. For example, if you add a rule in the IP-to-IP Routing
table and you select a Routing Policy, the 'Source IP Group' and 'Destination IP Group'
parameters list only IP Groups that re associated with the SRD to which the Routing Policy is
assigned (and IP Groups belonging to a Shared SRD, if exists).
■ If your configuration setup includes only a single SRD, the device automatically selects the
SRD when adding related configuration entities. For example, when adding an IP Group, the
single SRD is automatically selected in the Add Row dialog box.

Configuring SIP Interfaces

The SIP Interfaces table lets you configure up to 82 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 SIP Interfaces for the different types of applications (SBC and Gateway). 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
■ Intrusion Detection System (IDS) for applying the IDS policy to a specific SIP Interface. For
more information, see
Configuring Proxy
Configuring IDS Policies.
- 331 -
Mediant 1000 Gateway & E-SBC | User's Manual
Sets.