{'fraction_non_alphanumeric': 0.02586206896551724, 'fraction_numerical': 0.0, 'mean_word_length': 4.666666666666667, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The Session Initiation Protocol (SIP) and Spam

Spam, defined as the transmission of bulk unsolicited messages, has
plagued Internet email. Unfortunately, spam is not limited to email.
It can affect any system that enables user to user communications. The
Session Initiation Protocol (SIP) defines a system for user to user
multimedia communications. Therefore, it is susceptible to spam, just
as email is. In this document, we analyze the problem of spam in SIP.
We first identify the ways in which the problem is the same and the
ways in which it is different from email. We then examine the various
possible solutions that have been discussed for email and consider
their applicability to SIP.