You are here: CSP Developer’s Guide: Internet Protocol > 5 Session-Initiation Protocol (SIP) Software > Report and Control of P-Asserted and P-Access Network Info Headers

Report and Control of
P-Asserted and P-Access Network Info Headers

Overview

The CSP SIP stack can report the "Remote-Party-ID" and the "RPID Privacy" headers if present in the SIP INVITE message.

By default, the SIP stack does not report these P-headers. You have to enable this functionality. See Configuring the CSP to Report P-headers.

The SIP stack does not modify any other SIP headers for privacy related to this feature.

Pertinent Specifications

• Privacy (Defined in RFC 3323)

Private headers (P-Headers):

• P-Asserted-Identity (Defined in RFC 3325)

• P-Preferred-Identity (Defined in RFC 3325)

• P-Access-Network-Info (Defined in RFC 3455)

Description

Reporting Privacy Header and P-Headers in TLVs

The TLVs in this section report the Privacy header and P-Headers to the host within the NPDI ICB 0x0033 in the following messages:

• Request for Service with Data message

• PPL Event Indications message (for subsequent data)

0x2960 Privacy Header

This TLV reports the "Privacy" header if present in the inbound INVITE message. The following are the defined set of Privacy header contents but they are not limited to these.

"header" / "session" / "user" / "none" / "critical" / "id"

Byte | Description
0, 1 | Tag 0x2960
2, 3 | Length Variable (Maximum of 250)
4-n | Value Null terminated ASCII string

0x2961 Private Header Container

This TLV contains nested TLVs that in turn contain the P-Header type and P-Header content. This TLV uses the following nested TLVs:

• 0x2962 Private Header Type TLV

• 0x2963 Private Header Data TLV

This TLV along with the two nested TLVs is reported in the RFS as many number of times as the number of P-Headers appear in the INVITE message. The total length of the NPDI data that can be reported to the host limits this number.

Byte | Description
0, 1 | Tag 0x2961
2, 3 | Length Variable (Maximum of 250)

0x2962 Private Header Type

This TLV contains the P-header type. Use it within the Private Header Container TLV (0x2961) as a nested TLV and in combination with the Private Header data TLV (0x2963). It does not have any meaning if used as a standalone TLV.

Byte | Description
0, 1 | Tag 0x2962
2, 3 | Length 0x0001
4-n | Value 0x01 - P-Asserted-Identity 0x02 - P-Preferred-Identity 0x03 - P-Access-Network-Info

0x2963 Private Header Data

This TLV contains the content of the P-header. Use it within the Private Header info TLV (0x2961) as a nested TL and in combination with the Private Header Type TLV (0x2962). It does not have any meaning if used as a standalone TLV.

Byte | Description
0, 1 | Tag 0x2963
2, 3 | Length Variable (Maximum of 241)
4-n | Value Null terminated ASCII string

Example

The following example shows the format of the TLVs:

29 61 - Private Header Container TLV

00 32

29 62 - Private Header Type TLV

00 01

01

29 63 - Private Header Data TLV

00 29

22 43 75 6C 6C 65 6E 20 4A 65 6E 6E 69 6E 67 73 22
20 3C 73 69 70 3A 66 6C 75 66 66 79 40 63 69 73 63
6F 2E 63 6F 6D 3E 00

Write Access to P-Headers

Use the Privacy Header TLV (0x2960) to add the Privacy header in the outbound INVITE message.

Use the combination of Private Header Type TLV (0x2962) and Private Header Data TLV (0x2963) within the Private Header Container TLV (0x2961) to add the following P-Headers:

• P-Asserted-Identity

• P-Preferred-Identity

• P-Access-Network-Info

Include the TLVs above in the NPDI ICB (0x0033) in the Outseize Control (0x002C) or Route Control (0x00E8) messages.

The Private Header Container TLV (0x2961) could appear multiple times depending on the number of P-Headers that the host needs to add.

The CSP limits this number based on the NPDI size that it can accept.

API Messages Used

• Request for Service with Data (0x002D)

• PPL Event Indications (0x0043)

• Outseize Control (0x002C)

• Route Control (0x00E8)

Configuring the CSP to Report P-headers

By default, the CSP will not report the Privacy header and P-Headers. To enable the reporting, set bit 15 of the Signaling Information TLV (0x027F).

Session-Initiation Protocol. A signaling protocol used for establishing sessions in an IP network. A session could be a simple, two-way telephone call, or it could be a collaborative multi-media conference session.
Network Protocol Data Intelligence. Also called “Interworking,” it is a software product that operates within Excel’s Call Control (Layer 4) and Services (Layer 5) call processing layers. NPDI is meant to enhance Excel’s call processing product offering by allowing call processing layers (specifically Layers 4 and 5) to perform advanced analysis, generation, and conversion of Network Signaling (NS) Layer 3 information.
See Information Control Block.
See Programmable Protocol Language.
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
American Standard Code for Information Interchange
See Request For Service.
Outgoing call setup during real-time call processing on a specific channel.
A condition that, when met, drives a state machine from one state to another. A condition that drives a Component out of its current state by invoking an associated primitive.