<!-- 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, ...) - [ ] 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 - [x] 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: <!-- 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 This PR adds support for $hfl(Diversion)[] and $hflc(Diversion).
This parse_diversion.c was inspired by [parse_pai_ppi.c](https://github.com/kamailio/kamailio/blob/master/src/core/parser/parse_ppi_p...). I am not sure if it's breaking the existing implementation and usage. I believe it does not.
During some experimentation with the hfl(name)[-1], I encountered weird behavior with negative indexing for the already supported headers like Via, Route, and Contact. -1 yields null and -2 yields the last one and so on. Separate PR can be introduced if necessary.
Any feedback is welcome.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3650
-- Commit Summary --
* parser: Extend diversion for multiple bodies * pv: Add hfl and hflc support for Diversion header
-- File Changes --
M src/core/parser/parse_diversion.c (149) M src/core/parser/parse_diversion.h (10) M src/modules/pv/pv_core.c (175)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3650.patch https://github.com/kamailio/kamailio/pull/3650.diff
@xkaraman pushed 1 commit.
8075b1c8a213320fd0ad87531fff2be84dc6c48f parser: Fix format
Closed #3650.
Just adding the note, no review was actually done: changing the structure of a parsed header can impact cloning of the sip msg in transaction and how it is freed.
Then, on a quick look, it seems the patch for hfl has also conditions on p-asserted-identity and p-preferred-identity header types, not only on diversion, as the commit message says.
Yeah something went wrong on my branches and the formatting and messed up. I will create another pull request for both (Diversion and PPI).
Regarding the changes on the header parsing, of course, there must be a review since it's probably used in other places as well. I only checked for hfl and hflc usage.