Thanks for the fixed pull request. @miconda probably want to review it. I just noticed two copied files from topoh regarding the call-id masking. Maybe it make sense to discuss if this could be avoided, but there might be no easy solution.

It will be hard to replace the CallID in the same data storage of other headers as CallID is used as the key. hence it will be a chicken-egg problem if we replace the callID. Hence I found it better to mask it with a key so that it can be unmasked and used as key. Unlike other headers, Call-ID will not make overhead strings and make the header bigger like via in topoh. Masking and unmasking were already available in Topoh hence it was better to use the same algorithm for masking which will be better during the maintenance process.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.