Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tm: flag core to use forced socket when uac socket is set #1451

Merged
merged 1 commit into from Feb 20, 2018

Conversation

mslehto
Copy link
Member

@mslehto mslehto commented Feb 20, 2018

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

While testing Kamailio instance with multiple interfaces I noticed that dispatcher probing does not use the socket defined on dispatcher list_file.
By setting flag SND_F_FORCE_SOCKET, in tm module, dispatcher probing or tm t_uac_send() is sourced as per socket attribute.

Tested on FreeBSD 11.1 and Ubuntu 16.04.

- without flag SND_F_FORCE_SOCKET probing by dispatcher module
  and route script function t_uac_send() will choose incorrect source socket
@miconda
Copy link
Member

miconda commented Feb 20, 2018

Thanks!

@miconda miconda merged commit 7da5e5b into kamailio:master Feb 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants