I have made some tests with those two lines and the case I reported gets fixed, but I get cseq_tracking disabled for following eventual transactions.

I mean:

• First carrier needs authentication but once authenticated it answers >300 code.
• The call is sent to another carrier:
  • If it doesn't need authentication (the case I reported), the ACK and everything is fine now.
  • If this carrier also needs authentication, the cseq is not updated even though uac_auth() function is called again.

It seams that once cseq tracking is reset with those two lines, the cseq adaptation mechanism gets disabled for new calls to uac_auth() function.

I will do more tests to figure out what is happening and update this issue.

Thank you and regards,

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