document the new context argument for privacymanager

so people can do pattern matching on the input


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@143840 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Michiel van Baak
2008-09-21 09:31:54 +00:00
parent faa847f0ed
commit 11f9bf9ad0

View File

@@ -48,6 +48,12 @@ instead of giving you theirs. A simple test can detect this. More
advanced tests would be to look for -555- numbers, numbers that count
up or down, numbers of all the same digit, etc.
PrivacyManager can be told about a context where you can have patterns
that describe valid phone numbers. If none of the patterns match the
input, it will be considered a non-valid phonenumber and the user
can try again until the retry counter is reached.
This helps in resolving the issues stated in the previous paragraph.
My logs show that 39 have hung up in the PrivacyManager script over
the last year.