I've tracked this issue down to a combination of using HEP mode siptrace and turning on the track_cseq_updates at the same time. It looks like when HEP mode is turned on it adds the HEP header in front of the message it's duplicating, then uses msg_send() to send it. When this happens the callback for SREV_NET_DATA_OUT triggers dlg_cseq_msg_sent() in the dialog module which runs a parse_msg() on the buffer sent in. Since the buffer has the HEP data in the front when it tries to parse the message it leads to a parse error.

I'm not sure how to fix this, though, since there's really only this special case where msg_send() has some additional metadata at the beginning of the data.

This is a minimal config that reproduces the issue: kam-cseq-parse-error.txt

—
Reply to this email directly or view it on GitHub.