R0106-HP MSR Router Series Voice Configuration Guide(V7)

96
receives the INVITE request preferably obtains caller information from this field regardless of
whether the local Remote-Party-ID header field is set.
NOTE:
The Remote-Party-ID header field cannot coexist with the P-Preferred-Identity or P-Asserted-Identity
header field.
To configure caller privacy:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter voice view.
voice-setup N/A
3. Enter SIP view.
sip N/A
4. Add the Privacy header field
into INVITE requests.
privacy
By default, INVITE requests do not
carry the Privacy header field.
5. Add the Remote-Party-ID
header field to INVITE
requests.
remote-party-id
By default, INVITE requests do not
include the Remote-Party-ID header
field.
Setting the P-Asserted-Identity or P-Preferred-Identity header
field
Any two of the P-Asserted-Identity, P-Preferred-Identity, and Remote-Party-ID header fields cannot coexist.
To set the P-Asserted-Identity or P-Preferred-Identity header field:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter voice view.
voice-setup N/A
3. Enter SIP view.
sip N/A
4. Add the P-Asserted-Identity or
P-Preferred-Identity header field
to SIP messages.
asserted-id { pai | ppi }
By default, SIP messages do not
include the P-Asserted-Identity or
P-Preferred-Identity header field.
Configuring reliable provisional responses
This feature can ensure reliable delivery of 18x provisional responses even in bad network conditions.
The following describes the process for reliable provisional responses:
1. The UAC sends an INVITE request with the Require or Supported header field to indicate its
requirement or support for reliable provisional responses.
2. The UAS returns a reliable provisional response (18x response with the Require: value header
field).
3. The UAC sends a PRACK message to confirm the reception of the response.