AudioCodes Mediant 3000 User Manual page 293

User's Manual
Parameter
Source URI Input
[IPGroup_SourceUriInput]
Destination URI Input
[IPGroup_DestUriInput]
Version 6.8

[0] Sequential = (Default) Sequentially sends the INVITE to
each contact. If there is no answer from the first contact, it
sends the INVITE to the second contact, and so on until a
contact answers. If no contact answers, the call fails or is routed
to an alternative destination, if configured.

[1] Parallel = Sends the INVITE simultaneously to all contacts.
The call is established with the first contact that answers.

[2] Sequential Available Only = Sequentially sends the INVITE
only to available contacts (i.e., not busy). If there is no answer
from the first available contact, it sends the INVITE to the
second contact, and so on until a contact answers. If no contact
answers, the call fails or is routed to an alternative destination, if
configured.
Note: The device can also fork INVITE messages received for a
Request-URI of a specific contact (user) registered in the database
to all other users located under the same AOR as the specific
contact. This is configured using the SBCSendInviteToAllContacts
parameter.
Defines the SIP header in the incoming INVITE that is used 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

[11] Referred-by
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.
Defines the SIP header in the incoming INVITE to use as a call
matching characteristic based on destination URIs. The parameter
is used for classification and routing purposes. The device first
uses the parameter's settings as a matching characteristic (input)
to classify the incoming INVITE to an IP Group (source IP Group)
in the Classification table. Once classified, the device uses the
parameter for routing the call. For example, if set to To, the URI in
293
18. Control Network
Description
Mediant 3000