SIP Headers
This document explains some common SIP message headers
Headers formats. URI
sip uri with user=phone parameter:
RFC3398 - Standard - Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping RFC3261 Section-19.1.6 - Relating SIP URIs and tel URLs
P-Asserted-Identity
The P-Asserted-Identity header field can be used to convey the proven identity of the originator of a request within a trusted network. Since the From header field is populated by the originating UA it may not necessarily contain the actual identity. It usually is established by means of authentication between the originating UA and its outgoing proxy. The outgoing proxy then adds a P-Asserted-Identity header field to assert the identity of the originator to other proxies.
This header field has only meaning within what is called a trusted network by mutual agreement on the requirements for its use by the parties involved.
The P-Asserted-Identity header field is defined in RFC 3325.
Source: z9hg4bk.org
RFC3325 - Informational - Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
P-Preferred-Identity
Privacy
Privacy framework allows to hide address information from non-trusted network elements(usually end-user terminals or gateways). In Yeti trusted domain boundaries configured by customers auth Privacy mode and termination gateway Privacy mode.
RFCs to read:
- Critical private calls
Calls where Privacy header includes value critical. Such calls should be dropped if system can’t provide proper privacy level. See RFC3323 section-4.2 for details