At the first sight, does not seem good.

That protection with msg_id is to ensure that a rtpengine group (set) is used only for the SIP message it was set for.

Now it seems you remove that protection and setting a rtpengine group stays until is set again.

Anyhow, the end of the call (BYE) can be handled by a different SIP worker process than the one which handled the corresponding INVITE, so you can't really have (expect) the rtpengine group to be set to same value from INVITE till BYE. You should store it inside a dlg variable (if you use dialog module) or in a hashtable. It is also an option to add it as a param to record-route header.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.