Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Indeed, I've seen wrongly the condition about accepting event talk.
As I looked at the code and took in consideration this case, I've just pushed a different commit that should handle any NOTIFY even during the INVITE-based call setup, by ignoring the method type in loading the storage record.
Given that the method value is not explicitly needed for identifying the messages within dialog, I think this way is more flexible, to be able to cope also with other Event header values. It is also from the perspective that I would prefer to have it more in the style of the SIP proxy forwarding, where it does not really care about the header values, but the type of traffic.
Can you test with git master branch and see if it works for your case? I had no option to test something like that here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.