Supported Privacy Types for 911 Services

Follow

Molly Katolas

Updated

Details are available in the Bandwidth 911 Implementation Guide

 

Supported Privacy Types

SIP peers can be configured with the following privacy types:

  • P_ASSERTED (default option)
  • REMOTE_PARTY_ID
  • P_CHARGE_INFO

Bandwidth will pull the address information associated with the TN populated in either P-Asserted-Identity, Remote-Party-ID, or P-Charge-Info headers, based on what is selected in the peer configuration. Privacy types are used as follows:

P_ASSERTED

  1. If P_ASSERTED is the selected privacy type, Bandwidth will pull the TN from the ' P-Asserted-Identify' field only.
  2. If there is no TN information populated in 'P-Asserted-Identify', the value in the 'Remote-Party-ID' field will then be used.
  3. If no TN information is populated in 'Remote-Party-ID', the TN in the ‘From’ header will be used.

REMOTE_PARTY_ID

  1. If REMOTE_PARTY_ID is the privacy type, the value in the 'Remote-Party-ID' header will then be used as the ANI.
  2. If the Remote-Party-ID header is empty, the TN populated in the ‘From’ header will be used.

P_CHARGE_INFO

  1. If P_CHARGE_INFO is the privacy type, the value in the 'P-Charge-Info' header will be used as the ANI.
  2. If there is no TN information populated in 'P-Charge-Info', the value in the 'Remote-Party-ID' header will then be used.
  3. If no TN information is populated in 'Remote-Party-ID', the TN populated in the 'P-Asserted-Identify' header will be used.
  4. Finally, if there is no value in 'P-Asserted-Identify', the TN in the ‘From’ header is used.

If no information is populated in any of the above fields, the call will receive a generic ANI and will be passed to the ECC (Emergency Call Center) for processing, unless you have requested that unprovisioned calls be denied.

Populating values in all privacy headers (P-Asserted-Identity, Remote-Party-ID, and P-Charge-Info) is not recommended.

Article is closed for comments.