xiaoxiongxyy left a comment (kamailio/kamailio#4292)

The SIP transaction status is not synchronized, and it can also not be easily implemented. This was discussed several times on the sr-users mailing list. Please contact this mailing list with your question about other architectural approaches for high availability. The issue tracker is for tracking issues in the source code.

I understand that the transaction status is out of sync. Is there a solution for the situation I encountered? For example, copy 180/200 to another node. Is there any similar implementation/solution that can be used?

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