SIP Privacy
From TBwiki
(Difference between revisions)
(→SIP 'Remode-Party-ID') |
|||
| Line 58: | Line 58: | ||
|- | |- | ||
!style="background: none repeat scroll 0% 0% rgb(200, 200, 200);" | '''Routing script param''' | !style="background: none repeat scroll 0% 0% rgb(200, 200, 200);" | '''Routing script param''' | ||
| − | | {calling} | + | | [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{calling}]] |
| − | | {calling_presentation} | + | | [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{calling_presentation}]] |
| − | | {calling_screening} | + | | [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{calling_screening}]] |
| ''not mapped'' | | ''not mapped'' | ||
| ''not mapped'' | | ''not mapped'' | ||
| Line 124: | Line 124: | ||
|} | |} | ||
| − | == SIP 'Remode-Party-ID' == | + | == SIP 'Remode-Party-ID' header == |
=== RPID URI === | === RPID URI === | ||
| − | The RPID URI display-name is | + | The RPID URI display-name is filled from [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{private_display}]]. <br \> |
| − | The RPID URI address-spec is filled | + | The RPID URI address-spec is filled from [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{calling}]]. |
=== RPID "screen" param === | === RPID "screen" param === | ||
| Line 206: | Line 206: | ||
|} | |} | ||
| − | == SIP 'P-Asserted-Identity' == | + | == SIP 'P-Asserted-Identity' and 'Privacy' headers == |
| + | === PAID URI === | ||
| + | The PAID URI display-name is filled from [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{private_display}]]. <br \> | ||
| + | The PAID URI address-spec is filled from [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|{calling}]]. | ||
| + | |||
| + | === "Privacy" header === | ||
Revision as of 07:24, 14 May 2012
|
WARNING: the information on this page might be incomplete or inacurate |
|---|
Contents |
Supported Standards
- draft-ietf-sip-privacy-04.txt for support of Remote-Party-ID.
- RFC3323 A Privacy Mechanism for the Session Initiation Protocol (SIP)1
- RFC3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks2
- ITU Q.1912.5 Interworking between SIP and BICC/ISUP
[1] Partial support. Support Section 4.1. Constructing Private Messages
[2] Partial support. Doesn't support P-Preferred-Identity.
Acronyms
| RPID | Remode-Party-ID header |
| PAID | P-Asserted-Identity header |
| CLI | Calling Party Number (ISUP or ISDN) |
| GN | Generic Number for additional calling party number (ISUP ITU) |
| APRI | Address Presentation Restricted Indicator (ISUP) or Presentation indicator (ISDN) |
| SI | Screening Idicator (ISUP or ISDN) |
| {param} | Scripting call parameters |
Privacy mapping
ISUP/ISDN
| SS7 param | CLI digits | CLI APRI | CLI SI | GN digits | GN APRI | GN SI |
|---|---|---|---|---|---|---|
| Routing script param | {calling} | {calling_presentation} | {calling_screening} | not mapped | not mapped | not mapped |
The CLI APRI is mapped according to the following table.
| {calling_presentation} to ISUP/ISDN | ||
| {calling_presentation} | CLI APRI | |
| "not_available" | Address/Number not available | |
| "restricted", "addr_restricted", "name_restricted" | Presentation Restricted | |
| "unspecified", "allowed" | Presentation Allowed | |
| ISUP/ISDN to {calling_presentation} | ||
| CLI APRI | {calling_presentation} | |
| Address/Number not available | "not_available" | |
| Presentation Restricted | "restricted" | |
| Presentation Allowed | "allowed" | |
| Other value | "unspecified" | |
The CLI SI is mapped according to the following table.
| {calling_screening} to/from ISUP/ISDN | ||
| {calling_screening} | CLI SI | |
| "pass" | User provided, verified and passed | |
| "fail" | User provided, verified and failed | |
| "no" | User provided, not screened/verified | |
| "network_provided" | Network Provided | |
SIP 'Remode-Party-ID' header
RPID URI
The RPID URI display-name is filled from {private_display}.
The RPID URI address-spec is filled from {calling}.
RPID "screen" param
The RPID "screen" param is filled according to the following table.
| {calling_screening} to SIP | ||
| {calling_screening} | RPID screen param | |
| "unspecified", "pass", "network_provided" | screen="yes" | |
| "fail", "no" | screen="no" | |
| SIP to {calling_screening} | ||
| RPID screen param | {calling_screening} | |
| screen="yes" | "pass" | |
| screen="no" | "no" | |
| not screen param | "unspecified" | |
RPID "privacy" param
The RPID "privacy" param is filled according to the following table.
| {calling_presentation} to SIP | ||
| {calling_presentation} | RPID privacy param | |
| "unspecified", "not_available", "allowed" | privacy="off" | |
| "restricted" | privacy="full" | |
| "addr_restricted" | privacy="uri" | |
| "name_restricted"" | privacy="name" | |
| SIP to {calling_presentation} | ||
| RPID privacy param | {calling_presentation} | |
| privacy="off" | "allowed" | |
| privacy="full" | "restricted" | |
| privacy="uri" | "addr_restricted" | |
| privacy="name" | "name_restricted"" | |
| no privacy param | "unspecified"" | |
SIP 'P-Asserted-Identity' and 'Privacy' headers
PAID URI
The PAID URI display-name is filled from {private_display}.
The PAID URI address-spec is filled from {calling}.
