AudioCodes Mediant 600 User Manual page 677

User's Manual
Parameter
Web/EMS: Source
Number Preference
[SourceNumberPreferen
ce]
[SelectSourceHeaderFor
CalledNumber]
Web/EMS: Forking
Handling Mode
[ForkingHandlingMode]
Version 6.6

[1] Enable
Note: P-Associated-URIs in registration responses is handled only if the
device is registered per endpoint (using the User Information file).
Determines from which SIP header the source (calling) number is
obtained in incoming INVITE messages.

If not configured (i.e., empty string) or if any string other than "From"
or "Pai2" is configured, the calling number is obtained from a specific
header using the following logic:
a. P-Preferred-Identity header.
b. If the above header is not present, then the first P-Asserted-
Identity header is used.
c. If the above header is not present, then the Remote-Party-ID
header is used.
d. If the above header is not present, then the From header is
used.

"From" = The calling number is obtained from the From header.

"Pai2" = The calling number is obtained using the following logic:
a. If a P-Preferred-Identity header is present, the number is
obtained from it.
b. If no P-Preferred-Identity header is present and two P-Asserted-
Identity headers are present, the number is obtained from the
second P-Asserted-Identity header.
c. If only one P-Asserted-Identity header is present, the calling
number is obtained from it.
Notes:

The "From" and "Pai2" values are not case-sensitive.

Once a URL is selected, all the calling party parameters are set from
this header. If P-Asserted-Identity is selected and the Privacy header
is set to 'id', the calling number is assumed restricted.
Determines the SIP header used for obtaining the called number
(destination) for IP-to-Tel calls.

[0] Request-URI header = (Default) Obtains the destination number
from the user part of the Request-URI.

[1] To header = Obtains the destination number from the user part of
the To header.

[2] P-Called-Party-ID header = Obtains the destination number from
the P-Called-Party-ID header.
Determines how the device handles the receipt of multiple SIP 18x
forking responses for Tel-to-IP calls. The forking 18x response is the
response with a different SIP to-tag than the previous 18x response.
These responses are typically generated (initiated) by Proxy /
Application servers that perform call forking, sending the device's
originating INVITE (received from SIP clients) to several destinations,
using the same CallID.

[0] Parallel handling = (Default) If SIP 18x with SDP is received, the
device opens a voice stream according to the received SDP and
disregards any subsequently received 18x forking responses (with or
without SDP). If the first response is 180 without SDP, the device
responds according to the PlayRBTone2TEL parameter and
disregards the subsequent forking 18x responses.

[1] Sequential handling = If 18x with SDP is received, the device
opens a voice stream according to the received SDP. The device re-
677
52. Configuration Parameters Reference
Description
Mediant 600 & Mediant 1000