I found your commit in branch master, "dialog: check for cseq value only when getting it for caller/request".
And I tested, It works well !
Could you commit that patch to branch 5.2?
--
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/commit/79946bbb6d1731f503fc378ae38311b…
Hello,
it was brought into discussions several times in the past about core
functions not accepting variables in the parameters. I think it is time
to update them during the 5.3 release development. For few of them, I
added in the past some alternative function in the corex module (e.g.,
force_send_socket() in core and set_send_socket() in corex module).
So, I see two options:
1) add a function with similar name in corex module and same behaviour
like the one from core
2) remove the function export from the core and export one with the same
name from the corex module
First one will ensure that configs using the functions right now keep
working without any update.
The second one will be better in long term from the point of
documentation (no duplicated docs), but there might be few cases that
would require updates in the config -- iirc, there are some functions
that can get special tokens in the parameters (like forward(uri:host,
uri:port)), they will get an equivalent with variables, but old config
will not be compatible.
Obviously the reason for this email is to ask the developers and users
what would be the preferred way from own point of view.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com
Looks like a regression introduced with a patch that tried to avoid a crash -- I pushed another commit to skip the test on cseq when not taken from sip request. It is already in branch 5.2, can you test and see if all ok now?
--
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/commit/79946bbb6d1731f503fc378ae38311b…
Hi, My kamailio configuration file works well on the first release 5.2.0(535e13b).
When I update kamailio server to the 5.2.0 branch last version, include this commit, dialog always ERROR like:
ERROR: {...} dialog [dlg_handlers.c:212]: populate_leg_info(): empty CSeq number
Why? And how can I fix it?
Thanks!
--
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/commit/79946bbb6d1731f503fc378ae38311b…
#### 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
- [x] Related to issue #1757
#### Description
<!-- Describe your changes in detail -->
Note: This PR follows the discussion in #1757.
- introduce new global variable `ksr_tcp_accept_proxy`.
- this variable can be modified by using the `tcp_accept_proxy=yes`
configuration parameter.
- when active, inbound TCP connections are expected to behave according
to the PROXY protocol[1].
- Both the v1 (human-readable) and v2 (binary) versions of the protocol
are supported.
[1]: https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1765
-- Commit Summary --
* core: Add PROXY protocol implementation
-- File Changes --
M src/core/cfg.lex (3)
M src/core/cfg.y (9)
M src/core/globals.h (1)
M src/core/tcp_main.c (244)
M src/core/tcp_read.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1765.patchhttps://github.com/kamailio/kamailio/pull/1765.diff
--
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/pull/1765