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

Страница: 236 / 872

User's Manual 236 Document #: LTRT-89729
Mediant 3000
Parameter Description
The classification proceeds with checking whether the INVITE's IP
address (if host names, then according to the dynamically resolved IP
address list) is defined for a Proxy Set ID (in the Proxy Set table). If a
Proxy Set ID has such an IP address, the device classifies the INVITE as
belonging to the IP Group associated with this Proxy Set. The Proxy Set
ID is assigned to the IP Group using the IP Group table's 'Proxy Set ID'
parameter (see above).
Notes:

In cases where multiple IP Groups are associated with the same
Proxy Set ID, do not enable this feature. If enabled, the device is
unable to correctly classify the incoming INVITEs to the appropriate
IP Groups.

To enhance security, it is highly recommended to disable this
parameter so that the device can use the Classification table rules to
classify the call. If this parameter is enabled, the Classification table is
not used if an associated Proxy Set is found.

This parameter is applicable only to Server-type IP Groups.
Max Number Of
Registered Users
[IPGroup_MaxNumOfRe
gUsers] Defines the maximum number of users in this IP Group that can register
with the device. By default, no limitation exists for registered users.
Note: This field is applicable only to User-type IP Groups.
Source URI Input
[IPGroup_SourceUriInput
] Defines the SIP header in the incoming INVITE to use for call matching
characteristics based on source URIs.

[-1] Not Configured (default)

[0] From

[1] To

[2] Request-URI

[3] P-Asserted - First Header

[4] P-Asserted - Second Header

[5] P-Preferred

[6] Route

[7] Diversion

[8] P-Associated-URI

[9] P-Called-Party-ID

[10] Contact
Notes:

This parameter is applicable only when classification is done
according to the Classification table.

If the configured SIP header does not exist in the incoming INVITE
message, the classification of the message to a source IP Group fails.

If the device receives an INVITE as a result of a REFER request or a
3xx response, then the incoming INVITE is routed according to the
Request-URI. The device identifies such INVITEs according to a
specific prefix in the Request-URI header, configured by the
SBCXferPrefix parameter. Therefore, in this scenario, the device
ignores this parameter setting.
Destination URI Input
[IPGroup_DestUriInput] Defines the SIP header in the incoming INVITE to use for call matching
characteristics based on destination URIs.

[-1] Not Configured (default)

[0] From

[1] To