… forked INVITEs auths
#### 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
#### 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: <!-- Go over all points below, and after creating the PR, tick the checkboxes that apply --> - [ ] PR should be backported to stable branches - [ *] Tested changes locally - [ ]* Related to issue #[4266](https://github.com/kamailio/kamailio/issues/4266)
#### Description If a Negative reply for forked REGISTER comes after the first 200 response, it won't be ignored by Kamailio and will be processed the same way as replies processed for the INVITEs You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4304
-- Commit Summary --
* tm: allow pending forked REGISTER auths being handled the same way as forked INVITEs auths
-- File Changes --
M src/modules/tm/t_reply.c (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4304.patch https://github.com/kamailio/kamailio/pull/4304.diff