A selection can be made which items will be anonymized :
When the IP addresses are anonymized ( Anonymize IP addresses checked) then the following mapping is used :
● Every private IP address (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16) is converted to a 10.x.x.x IP address, e.g.
the first private IP address detected is replaced with 10.0.0.1, the second IP address with 10.0.0.2, etc...
● Every public IP address is converted to a 192.168.x.x IP address, e.g.
the first public IP address detected is replaced with 192.168.0.1, the second IP address with 192.168.0.2, etc...
Important remark: multicast IP addresses (ranging from 188.8.131.52 to 184.108.40.206) are not converted as these IP addresses do no reveal any privacy information.
● Inside a SIP URI the domain name is converted to a 172.16.x.x IP address, e.g.
the first domain name detected is replaced with 172.16.0.1, the second domain name with 172.16.0.2, etc...
After anonymizing all original IP addresses are changed to either a 10.x.x.x IP address (coming from a private IP address ) or
a 192.168.x.x IP address (coming from a public IP address ) or a 172.16.x.x IP address (coming from a SIP URI domain name).
So the anonymized output still gives an indication what the original IP address was without revealing any details.
Digest Authentication credentials are always anonymized :
Example of user name anonymizing:
Example of call number anonymizing:
Example of IP address anonymizing:
For the anonymizing of the RTP packets the voice is replaced with a beep tone :
The beep tone can be listened to by performing an Audit with the flag Convert RTP to wav files checked.
The result of this Audit gives links to the anonymized voice in the generated wav files :