Enable transaction matching using callid and cseq values instead of via md5 value.
<!-- Kamailio Pull Request Template -->
<!-- IMPORTANT: - for detailed contributing guidelines, read: https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md - pull requests must be done to master branch, unless they are backports of fixes from master branch to a stable branch - backports to stable branches must be done with 'git cherry-pick -x ...' - code is contributed under BSD for core and main components (tm, sl, auth, tls) - code is contributed GPLv2 or a compatible license for the other components - GPL code is contributed with OpenSSL licensing exception -->
#### Pre-Submission Checklist <!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply --> <!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above--> <!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list --> - [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [X] Each component has a single commit (if not, squash them into one commit) - [X] 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) - [X] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist: <!-- Go over all points below, and after creating the PR, tick the checkboxes that apply --> - [ ] PR should be backported to stable branches - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description <!-- Describe your changes in detail -->
Hello,
We had an issue with kamailio that the generated tm p_cell->md5 was not sent out in Via "branch=" parameter. Instead, other value was sent. Thus when comparing the replies Via "branch=" md5 value back to p_cell->md5, the transactions mismatched and dialogs were not setup. This happened for the most of the transactions/dialogs.
We could not really figure out why the above was happening. Because this was an isolated system, we decided to do this workaround using callid and cseq matching for transactions, and it helped. Now most of the dialogs are setup.
Let me know what you think, if other had this problem and if this PR helps.
Thank you, Stefan You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2868
-- Commit Summary --
* <a href="https://github.com/kamailio/kamailio/pull/2868/commits/ab42c71fa814a9d2f3d85f10c1519ffd0fdf3369">tm: Add callid_cseq_matching param</a>
-- File Changes --
M src/modules/tm/config.c (3) M src/modules/tm/config.h (1) M src/modules/tm/doc/params.xml (23) M src/modules/tm/t_lookup.c (20) M src/modules/tm/tm.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2868.patch https://github.com/kamailio/kamailio/pull/2868.diff
The indentation inside `src/modules/tm/t_lookup.c` does not seem right -- it should be consistent with the existing content in order to be easy to read the changes and figure out the impact. Please fix it (use tabs, not whitespaces).
@smititelu pushed 1 commit.
25a49a3f7e2bf4a53b38a4d1b9222e1195a0201e tm: Add callid_cseq_matching param
Updated t_lookup.c with tabs indentation.
Merging, the new modparm controls the behaviour.
Merged #2868 into master.
Is this matching actually compliant to the [standard](https://datatracker.ietf.org/doc/html/rfc3261#section-17.2.3)? I just wondered, it should be probably documented in the README then.
No, this is non-RFC compliant. I will update the tm doc for this new param and push it.
thanks!