AudioCodes Mediant 4000 SBC, Руководство пользователя

Страница: 357 / 1037

CHAPTER 18 Core Entities
Mediant 4000 SBC | User's Manual
Parameter Description
■ The port range must not overlap with any other media port
range configured for other Media Realm Extensions, Media
Realms, or SIP Interfaces that are associated with the same
IP network interface.
'Port Range End'
[MediaRealmExtension_
PortRangeEnd]
Defines the last (upper) port in the range of media UDP ports for
the Media Realm Extension.
Note: It is unnecessary to configure the parameter. The device
automatically populates the parameter with a value, calculated by
the summation of the 'Number of Media Session Legs' parameter
(multiplied by the port chunk size) and the 'Port Range Start'
parameter. After you have added the Media Realm Extension row
to the table, the parameter is displayed with the calculated value.
'Number Of Media
Session Legs'
[MediaRealmExtension_
MediaSessionLeg]
Defines the number of media sessions for the port range. For
example, 100 ports correspond to 10 media sessions, since ports
are allocated in chunks of 10.
By default, no value is defined.
Note: The parameter is mandatory.
Configuring SRDs
The SRDs table lets you configure up to 280 signaling routing domains (SRD). The SRD is a logical
representation of an entire SIP-based VoIP network (Layer 5) consisting of groups of SIP users and
servers. The SRD is associated with all the configuration entities (e.g., SIP Interfaces and IP
Groups) required for routing calls within the network. Typically, only a
single SRD is required
(recommended) for most deployments. Multiple SRDs are only required for multi- tenant
deployments, where the physical device is "split" into multiple logical devices. For more information
on multi-tenant architecture, see
Multiple SRDs for Multi-tenant Deployments .
As the device is shipped with a default SRD ("DefaultSRD" at Index 0), if your deployment requires
only one SRD, you can use the default SRD instead of creating a new one. When only one SRD is
employed and you create other related configuration entities (e.g., SIP Interfaces), the default SRD
is automatically assigned to the new configuration entity. Therefore, when employing a single-SRD
configuration topology, there is no need to handle SRD configuration (i.e., transparent).
You can assign SRDs to the following configuration entities:
■ SIP Interface (mandatory) - see Configuring SIP Interfaces
■ IP Group (mandatory) - see Configuring IP Groups
■ Proxy Set (mandatory) - see Configuring Proxy Sets
■ (SBC application only) Classification rule - see Configuring Classification Rules
As mentioned previously, if you use only a single SRD, the device automatically assigns it to the
above-listed configuration entities.
As each SIP Interface defines a different Layer-3 network (see Configuring SIP Interfaces for more
information) on which to route or receive calls and as you can assign multiple SIP Interfaces to the
same SRD, for most deployment scenarios (even for multiple Layer-3 network environments), you
only need to employ a single SRD to represent your VoIP network (Layer 5). For example, if your
VoIP deployment consists of an corporate IP PBX (LAN), a SIP Trunk (WAN), and far-end users
(WAN), you would only need a single SRD. The single SRD would be assigned to three different
SIP Interfaces, where each SIP Interface would represent a specific Layer-3 network (IP PBX, SIP
Trunk, or far-end users) in your environment. The following figure provides an example of such a
deployment:
- 324 -