Filtering Tables In Web Interface By Srd; Multiple Srds For Multi-Tenant Deployments - AudioCodes Mediant 3000 User Manual

18.2.1 Filtering Tables in Web Interface by SRD

When your configuration includes multiple SRDs, you can filter tables in the Web interface
by a specific SRD. The filter is configured in the SRD Filter drop-down list, located on the
Web interface's toolbar. The filter is applied throughout the GUI. The following figure shows
the SRD Filter with an example of configured SRDs in its' drop-down list.
When you select an SRD for filtering, the Web interface displays only table rows
associated with the filtered SRD. In addition, if you add a new row to a table, the filtered
SRD is automatically selected as the associated SRD (in the 'SRD' parameter of the Add
Row dialog box). For example, if your SRD filter is set to "Comp-A" and you then add a
new Proxy Set, the Proxy Set is automatically associated with SRD "Comp-A" (i.e., the
'SRD' parameter is set to "Comp-A"). All other parameters in the Add Row dialog box are
also automatically set to values associated with the filtered SRD.
SRD filtering is especially useful in multi-tenant setups where multiple SRDs may be
configured. In such a setup, SRD filtering eliminates configuration clutter by "hiding" SRDs
that are irrelevant to the current configuration and facilitates configuration by automatically
associating the filtered SRD, and other configuration elements associated with the filtered
SRD, wherever applicable.

18.2.2 Multiple SRDs for Multi-tenant Deployments

The device can be deployed in a multi-tenant architecture, serving multiple customers
(tenants) from a single, shared physical entity. The device's multi-tenant feature is fully
scalable, offering almost "non-bleeding" partition per tenant, whereby users of one tenant
can't infringe on the space of users of another tenant. The device provides per tenant
configuration, monitoring, reporting, analytics, alarms and interfacing. The device is a real-
time multi-tenant system that provides each tenant with optimal real-time performance, as
each session received by the device is classified and processed only through the tenant's
"orbit".
While some enterprises are large enough to justify a dedicated standalone device, many
enterprises require only a fraction of the device's capacity and capabilities. Service
providers offering SIP Trunking services can funnel multiple enterprises into a single device
and thereby, reap significant cost improvements over a device-per-customer model. Tenant
size in a multi-tenant architecture can vary and therefore, the instance CPU, memory and
interface allocations should be optimized so as not to waste resources for small-sized
tenants on the one hand, and not to allocate too many instances for a single
tenant/customer on the other. For example, it would be a waste to allocate a capacity of
100 concurrent sessions to a small tenant for which 10 concurrent sessions suffice.
In a multi-tenant deployment, each tenant is represented by a dedicated SRD. The different
Layer-3 networks (e.g., LAN IP-PBX users, WAN SIP Trunk, and WAN far-end users) of
the tenant are represented by SIP Interfaces, which are all associated with the tenant's
SRD. As related configuration entities (SIP Interfaces, IP Groups, Proxy Sets,
Classification rules, and IP-to-IP Routing rules) are associated with the specific SRD, each
SRD has its own logically separated configuration tables (although configured in the same
tables). Therefore, full logical separation (on the SIP application layer) between tenants is
achieved by SRD.
User's Manual
Figure 18-8: SRD Filter
332
Mediant 3000
Document #: LTRT-89730