RTP headers are not changed, only the speech samples are replaced.The VoIP Analyzer Tool can anonymize RTP speech packets inside a wireshark file RTP voice is overwritten with a new anonymous voice sample.customer IP addresses are overwritten with with a unique 10.x.x.x value.hashed digest passwords responses are overwritten with xxx.If that sounds like heaven to you, then the VoIP AnalyzerTool will fit you like a glove. What if you could convert your existing wireshark capture to a wireshark capture that still contains all SIP messages, errors, warnings, flows etc, but where the sensitive info was by some magic replaced? Many customer fear to share so much personal and company sensitive information with third parties. However, if you face any VoIP issues, the helpdesk of your external partner will ask for such Wireshark captures. Sensitive information that you don't want to pass to any third party. Phone numbers, names, who is calling who, IP addresses, (hashed) digest passwords and if RTP is present it contains even the full voice stream of what was said during a phone call. Lets face it: a Wireshark VoIP capture contains a lot of personal data. We support this for the SIP protocol and the RTP protocol. We can also overwrite specific data inside wireshark packets with e.g. This way, no customer details are visible anymore. This means we can generate based on an existing Wireshark capture a new wireshark capture where all customer IP addresses are replaced by unique 10.x.x.x IP addresses. We can generate GDPR compliant Wireshark captures: we can make any wireshark capture "anonymous". Generating GDPR compliant Wireshark captures In principle, we can anonymize any protocol or flow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |