When set_rtpengine_set() config function is called.

Pre-Submission Checklist

• Commit message has the format required by CONTRIBUTING guide
• Commits are split per component (core, individual modules, libs, utils, ...)
• Each component has a single commit (if not, squash them into one commit)
• No commits to README files for modules (changes must be done to docbook files
  in doc/ subfolder, the README file is autogenerated)

Type Of Change

• Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)

Checklist:

• PR should be backported to stable branches
• Tested changes locally
• Related to issue #XXXX (replace XXXX with an open issue number)

Description

After calling set_rtpengine_set(), the new set is not set for further rtpengine delete(). This is because active_rtpp_set is set to default_rtpp_set when msg id != current_msg_id (which is set once by set_rtpengine_set())

I've removed the msg id != current_msg_id condition, and initialized active_rtpp_set in mod_init().

Basically tested locally with 2 sets with 1 rtpengine each.

You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/2965

Commit Summary

• 2a31c54 rtpengine: Fix set selection

File Changes

(1 file)

• M src/modules/rtpengine/rtpengine.c (4)

Patch Links:

• https://github.com/kamailio/kamailio/pull/2965.patch
• https://github.com/kamailio/kamailio/pull/2965.diff

—
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.