[asterisk-commits] mvanbaak: branch 1.6.1 r143839 - in /branches/1.6.1: ./ doc/tex/privacy.tex

[SVN commits to the Asterisk project]

Author: mvanbaak
Date: Sun Sep 21 04:29:27 2008
New Revision: 143839

URL: http://svn.digium.com/view/asterisk?view=rev&rev=143839
Log:
Merged revisions 143837 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

........
  r143837 | mvanbaak | 2008-09-21 11:27:08 +0200 (Sun, 21 Sep 2008) | 2 lines
  
  fix privacy documentation. We no longer do priority jumping +101
........

Modified:
    branches/1.6.1/   (props changed)
    branches/1.6.1/doc/tex/privacy.tex

Propchange: branches/1.6.1/
------------------------------------------------------------------------------
Binary property 'trunk-merged' - no diff available.

Modified: branches/1.6.1/doc/tex/privacy.tex
URL: http://svn.digium.com/view/asterisk/branches/1.6.1/doc/tex/privacy.tex?view=diff&rev=143839&r1=143838&r2=143839
==============================================================================
--- branches/1.6.1/doc/tex/privacy.tex (original)
+++ branches/1.6.1/doc/tex/privacy.tex Sun Sep 21 04:29:27 2008
@@ -35,8 +35,10 @@
 unlisted number, or some charity looking for a handout. The
 PrivacyManager application can help here. It will ask the caller to
 enter a 10-digit phone number. They get 3 tries(configurable), and this is
-configurable, with control being passed to priority+101 if they won't
-supply one.
+configurable, with control being passed to next priority where you can
+check the channelvariable PRIVACYMGRSTATUS. If the callerid was valid this
+variable will have the value SUCCESS, otherwise it will have the value
+FAILED.
 
 PrivacyManager can't guarantee that the number they supply is any
 good, tho, as there is no way to find out, short of hanging up and