You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When libsrtp fires a provisioned callback it calls it with a srtp_event_data_t struct as argument. The struct contains some fields, including the srtp_t session the event belongs to.
The problem is that I cannot associate my "application SRTP handler" with such a srtp_t session so when the callback is fired I do not know which of my SRTP handlers the session belongs to.
I suggest adding a void* user_data into the srtp_t struct, and two new functions:
When libsrtp fires a provisioned callback it calls it with a
srtp_event_data_t
struct as argument. The struct contains some fields, including thesrtp_t
session the event belongs to.The problem is that I cannot associate my "application SRTP handler" with such a
srtp_t
session so when the callback is fired I do not know which of my SRTP handlers the session belongs to.I suggest adding a
void* user_data
into thesrtp_t
struct, and two new functions:NOTE: This is similar to what other C libraries do. For example OpenSSL provides some functions for this same purpose:
The text was updated successfully, but these errors were encountered: