Identity

On this panel, you can find service policy attributes that allow you to set up the outgoing identity. To see an attribute description, hover over the attribute name and then over the question mark . To configure a specific attribute, select the corresponding checkbox.

This attribute defines the value that must be used as the username part in the URL in the Contact SIP header in the outgoing INVITE request.

The following values are available:

• ACLI (Asserted Calling Line Identification) – provides the actual caller identity if the CLI is hidden or unknown. The caller identity is taken from the id parameter (or, if it’s not available, from the bill_to parameter) of the PortaOne-Calling-Party attribute of the authorization response from PortaBilling.

• CLI (Calling Line Identification) – the identifier of the calling party. It is taken from the cli parameter of the authorization response from PortaBilling.

The Out HDR contact attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.

This attribute adds the Diversion SIP header to the outgoing INVITE request if the call is forwarded and specifies the value to be used as the username part in the URL in this header.

The following value is available:

• FCLI (Calling Line Identification) – provides the redirecting party identity. If it is unavailable, the ACLI value is used.

The Out HDR diversion attribute is applied within a service policy assigned to a connection. The Diversion SIP header is added only if the call is forwarded. This attribute is applied to the called party and is ignored for the calling party.

By default, this option is disabled, and the Diversion header is added for each of the multiple forwards (e.g., the call is forwarded three times, so three Diversion headers are added).

When this option is enabled, it instructs PortaSIP to include only the newest Diversion header in the outgoing INVITE request.

This option is useful when a vendor requires the passed Diversion headers in the predefined format. Thus, you need PortaSIP to pass only one (the most recent) Diversion header, so the special hardware can further transform it to the required format.

The Out HDR diversion cut off attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.

This attribute adds the History-Info SIP header to the outgoing INVITE request if the call is forwarded and specifies the value to be used as the username part in the URL in this header.

The following value is available:

• FCLI (Calling Line Identification) – provides the redirecting party identity.

The Out HDR history (FCLI) attribute is applied within a service policy assigned to a connection. The History-Info SIP header will be added only if the call is forwarded. This attribute is applied to the called party and is ignored for the calling party.

This attribute adds the P-Asserted-Identity (PAI) SIP header to the outgoing INVITE request and specifies the value to be used as the username part in the URL in this header.

The following values are available:

• ACLI (Asserted Calling Line Identification) – provides the actual caller identity if the CLI is hidden or unknown. The caller ID is taken from the PAI header (or RPID header, if the PAI is absent) of the incoming INVITE request.

• FCLI (Calling Line Identification) – provides the redirecting party identity.

The Out HDR PAI attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.

This attribute adds the Remote-Party-ID (RPID) SIP header to the outgoing INVITE request and specifies the value to be used as the username part in the URL in this header.

• ACLI (Asserted Calling Line Identification) – provides the actual caller identity if the CLI is hidden or unknown. The caller ID is taken from the PAI header (or RPID header, if the PAI is absent) of the incoming INVITE request.

• FCLI (Calling Line Identification) – provides the redirecting party identity.

The Out HDR RPID attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.

You can configure whether to include the privacy headers P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) in the outgoing INVITE request sent to a trusted remote connection.

By default, when this attribute is disabled, both PAI and RPID headers are included in the outgoing INVITE request.

To choose a particular header or “none”, select the Outgoing headers trusted checkbox and choose one of the following options:

• PAI – to send only the PAI header;

• RPID – to send only the RPID header;

• None – to send neither PAI, nor RPID header.

Privacy headers are used when, for example, a caller’s identity must be hidden from a called party, but a vendor still requests this information. In this case, the identity information can be included in the privacy header, which indicates that the caller’s info must be withheld from the called party.

Different vendors require and can properly process different privacy headers. Thus, the ability to specify which privacy header to send to trusted vendors enables you to satisfy both the end user’s request for anonymity and vendor’s request for identity data.

The Outgoing headers trusted attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.

You can configure whether to include the privacy headers P-Asserted-Identity (PAI) and Remote-Party-ID (RPID) in the outgoing INVITE request sent to an untrusted remote connection.

By default, when this attribute is disabled, both PAI and RPID headers are included in the outgoing INVITE request.

To choose a particular header or “none”, select the Outgoing headers trusted checkbox and choose one of the following options:

• PAI – to send only the PAI header;

• RPID – to send only the RPID header;

• None – to send neither PAI, nor RPID header.

Privacy headers are used when, for example, a caller’s identity must be hidden from a called party, but a vendor still requests this information. In this case, the identity information can be included in the privacy header, which indicates that the caller’s info must be withheld from the called party.

The Outgoing headers untrusted attribute is applied within a service policy assigned to a connection. This attribute is applied to the called party and is ignored for the calling party.