{'fraction_non_alphanumeric': 0.010416666666666666, 'fraction_numerical': 0.008680555555555556, 'mean_word_length': 5.138297872340425, '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}}
A study on ACK message processing mechanism in SIP transaction layer

According to the RFC3161, ACKs corresponding to 2xx responses to INVITE is handled in the transaction user as separate messages without any transactions. And the transaction user receives all retransmitted ACKs without any filtering. In this paper, ACK transactions and the finite state machines for those are defined. And the rules for matching messages to transactions are also redefined so that the retransmission of ACKs and the filtering of the retransmitted ACKs are treated in the transaction layer.