Summary:ASTERISK-07883: Remote-Party-ID has wrong screen tag values
Reporter:hristo (hristo)Labels:
Date Opened:2006-10-05 15:42:33Date Closed:2006-10-13 11:02:40
Versions:Frequency of
Description:I believe the screen tag in Remote-Party-ID is being set to the wrong values of "pass" and "fail" instead of "yes" and "no"

SetCallerPres(allowed_passed_screen) -> ;privacy=off;screen=pass
SetCallerPres(prohib_passed_screen) -> ;privacy=full;screen=pass
SetCallerPres(allowed_failed_screen) -> ;privacy=off;screen=fail
SetCallerPres(prohib_failed_screen) -> ;privacy=full;screen=fail


More details (Cisco):
search for:
"Table 1 SIP to PSTN Translation of Screening And Presentation Information" and
"Table 2 PSTN to SIP Translation of Screening and Presentation Information"

It is clear that "fail"/"pass" PSTN screening translates to "no"/"yes" in SIP.

Also, http://tools.ietf.org/id/draft-ietf-sip-privacy-04.txt which defines Remote-Party-ID header never mentions "pass" or "fail" as legal values for the "screen" tag. The only allowed values are "yes" or "no"
Comments:By: Olle Johansson (oej) 2006-10-09 07:59:10

Fixing in 1.2 and up. Thanks!!!

By: Jason Parker (jparker) 2006-10-09 16:46:38

oej, was this fixed?  Should it be closed now?

By: hristo (hristo) 2006-10-10 10:22:41

it still seems to be a problem with 1.4-r44743. which revision has the fix?

By: Serge Vecher (serge-v) 2006-10-13 08:16:40

afaik, the fix has only gone into the 1.2 branch in r44757. 1.4/trunk is still pending due to some merge failures ...

By: Joshua C. Colp (jcolp) 2006-10-13 11:02:40

::wobbles in::

Fixed in 1.2 as of revision 44757 by oej, 1.4 as of revision 45040 and trunk as of revision 45047 by myself. Thanks!