Hi,
When using dialog module and track_cseq_updates when needing to update CSeq for authenticated invites, if early media is present the CSeq in the Rack header is not also incremented.
Kamailio version:
version: kamailio 4.4.2 (x86_64/linux) 892ad6
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 892ad6
compiled on 11:18:36 Sep 28 2016 with gcc 5.4.0
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/801
Sipwise hat ON:
We have more than one server and we need to keep things in db in order to share sca subscription/appearance between servers
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/781
<!--
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
- [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 -->
- [x] PR should be backported to stable branches
- [ ] Tested changes locally
#### Description
From https://github.com/kamailio/kamailio/pull/3569
After initial subscription by the SCA device, if we power off and on again, we won't get an unsubscribe notification and we are getting a new record-route with sca-subscription. In this case kamailio not updating the new record-route for the SCA Device.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3571
-- Commit Summary --
* sca: update rr if necessary for subscriptions
-- File Changes --
M src/modules/sca/sca_subscribe.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3571.patchhttps://github.com/kamailio/kamailio/pull/3571.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3571
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3571(a)github.com>
Module: kamailio
Branch: master
Commit: 145659f9b81a0d489548fa8a0f75c0bd05660e2e
URL: https://github.com/kamailio/kamailio/commit/145659f9b81a0d489548fa8a0f75c0b…
Author: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-11-22T14:50:21+01:00
github: set ``expired`` label when closing PR or issues automatically [skip ci]
---
Modified: .github/workflows/issue_management.yml
---
Diff: https://github.com/kamailio/kamailio/commit/145659f9b81a0d489548fa8a0f75c0b…
Patch: https://github.com/kamailio/kamailio/commit/145659f9b81a0d489548fa8a0f75c0b…
---
diff --git a/.github/workflows/issue_management.yml b/.github/workflows/issue_management.yml
index 063df358c62..0d0b2ef9aa5 100644
--- a/.github/workflows/issue_management.yml
+++ b/.github/workflows/issue_management.yml
@@ -17,6 +17,8 @@ jobs:
stale-pr-message: 'This PR is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks.'
days-before-stale: 42
days-before-close: 14
+ close-issue-label: expired
+ close-pr-label: expired
exempt-issue-labels: bug
remove-stale-when-updated: true
operations-per-run: 500