Diff from version 8 to 10 (current)
@@ -1,6 +1,16 @@ |
-P-Asserted-Identity and Remote Party ID SIP header | +!!Remote-Party-Id | | -Some wholesale providers are now requiring that packets include P-Asserted-Identity or Remote Party ID in the header of SIP packets. | +This header was defined in a failed RFC : http://tools.ietf.org/html/draft-ietf-sip-privacy-00 . Although this header is supported by SIP devices and SIP PBXs, this was never accepted as a standard. __You should not be using this header.__ | + | +!!P-Asserted-Identity and Privacy Headers | + | +P-Asserted-Identity and Privacy headers are defined in RFC 3325. The P-Asserted-Identity contains the caller id information for the call on the INVITE SIP packet. The Privacy header contains information on which parts of the caller id are private. | + | +This is the acceptable way to specify privacy information for calls. | + | +SIP header ''Privacy: user,id'' is equivalent to ''*67'' on the PSTN in North America. | + | +!!Asterisk and Trixbox | | I spent some time messing with this since there is little to no documentation on such things regarding Asterisk or Trixbox. Since I had such a hard time of it, I thought I would write a really short howto so that maybe others will have it bit easier. | |
|
|
@@ -62,4 +72,3 @@ |
!!See also | * changes to sendrpid in Asterisk 1.8 with the pai argument for P-Asserted-Identity | * ((Asterisk func CONNECTEDLINE|CONNECTEDLINE)) and ((Asterisk func REDIRECTING|REDIRECTING)) functions in Asterisk 1.8 | - |
|
|
User | Comment | Time | Version |
---|
dlublink | | 2013-08-02 20:40 | 10 |
dlublink | | 2013-08-02 20:40 | 9 |