Difference between revisions of "P-Asserted-Identity"
| Line 7: | Line 7: | ||
This header field has only meaning within what is called a trusted network by mutual aggreement on the requirements for its use by the parties involved. | This header field has only meaning within what is called a trusted network by mutual aggreement on the requirements for its use by the parties involved. | ||
The P-Asserted-Identity header field is defined in [http://www. | The P-Asserted-Identity header field is defined in [http://www.ietf.org/rfc/rfc3325.txt RFC 3325]. | ||
Source: http://www.z9hg4bk.org/sip/hf/p-asserted-identity.html | Source: http://www.z9hg4bk.org/sip/hf/p-asserted-identity.html | ||
<br><br> | <br><br> | ||
= Configuration = | = Configuration = | ||
Revision as of 09:26, 5 May 2010
This option is available starting from MOR 9
Description
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 necessarly 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 aggreement on the requirements for its use by the parties involved.
The P-Asserted-Identity header field is defined in RFC 3325.
Source: http://www.z9hg4bk.org/sip/hf/p-asserted-identity.html
Configuration
Turn it per Provider basis in its Settings:
