Re: [sr-dev] [kamailio/kamailio] pv: fixed error "pv_get_method(): no CSEQ header" (#2761)

2021-06-03 Thread sergey-safarov
maybe implement functions in core 1. `is_request("HTTP")` 2. `is_request("SIP")` 3. `is_reply("HTTP")` 4. `is_reply("SIP")` and move these functions from `siputils` to `core` 1. `is_request()` 2. `is_reply()` -- You are receiving this because you are subscribed to this thread. Reply to this

Re: [sr-dev] [kamailio/kamailio] pv: fixed error "pv_get_method(): no CSEQ header" (#2761)

2021-06-03 Thread sergey-safarov
@sergey-safarov pushed 1 commit. 2579bdf52816d05858ead275882ff2d2de167556 pv: pv_get_method fixed error "pv_get_method(): no CSEQ header" -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [sr-dev] [kamailio/kamailio] pv: fixed error "pv_get_method(): no CSEQ header" (#2761)

2021-06-03 Thread sergey-safarov
yes, Daniel I have observed error `pv: fixed error "pv_get_method(): no CSEQ header"` with HTTP replies when trying to use ``` event_route[siptrace:msg] { if($rm =~ "OPTIONS|HTTP") { xlog("L_DEBUG", "trace|dropping trace for method $rm\n"); drop(); } } ``` My goal to avoid

Re: [sr-dev] [kamailio/kamailio] pv: fixed error "pv_get_method(): no CSEQ header" (#2761)

2021-06-03 Thread Daniel-Constantin Mierla
The example you provided is not an HTTP request, but an HTTP reply and it does not have a method in the first line. HTTP methods are GET, POST, PUT, ... Probably it should return $null for HTTP replies. -- You are receiving this because you are subscribed to this thread. Reply to this email

[sr-dev] [kamailio/kamailio] pv: fixed error "pv_get_method(): no CSEQ header" (#2761)

2021-06-03 Thread sergey-safarov
Pre-Submission Checklist - [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

Re: [sr-dev] [kamailio/kamailio] TLS: same TLSc is used for different outbound connection when it is switched with tls_set_connect_server_id() (#2760)

2021-06-03 Thread Tim Chubb
I was half way through writing a less detailed version of a very similar issue i am having too, having to send options presenting a specific servername and cert same environment as well (ubuntu 18.04, kam 5.5.0) I have noticed that the xavp sni settings seems to only work on one thread as

[sr-dev] [kamailio/kamailio] TLS: same TLSc is used for different outbound connection when it is switched with tls_set_connect_server_id() (#2760)

2021-06-03 Thread arkadiam
### Description Thank you for implementing #2413, I'm looking forward to use it. I was trying it on a dev system. It works fine when the same TLS client needs to be selected for ALL connections. Having issue with it when connection expected to alternate between multiple configured TLS

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread Daniel-Constantin Mierla
You have to set `h_id_start` and `h_id_step` for all servers in the replication group so the generated ids do not overlap: * https://www.kamailio.org/docs/modules/stable/modules/dialog.html#dialog.p.h_id_start Likely the issue was caused by matching a dialog with same `h_id`, which was

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread themsley-voiceflex
[root@kamibt01 ~]# grep -iE "dialog|dmq" /etc/kamailio/kamailio.cfg loadmodule "dmq.so" loadmodule "dialog.so" # -- dialog params -- modparam("dialog", "enable_dmq", 1) modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_match_mode", 1) modparam("dialog",

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread Daniel-Constantin Mierla
If there is dialog replication via dmq, can you paste here all the modparams you set for dialog and dmq modules (hide/replace sensitive data, such as passwords, ips, ... if it is the case). It can be a conflict on dialog matching due to replication. -- You are receiving this because you are

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread themsley-voiceflex
< (gdb) p *cell $1 = {ref = 3, next = 0x7fae15a524a8, prev = 0x0, h_id = 6059, h_entry = 3973, state = 3, lifetime = 0, init_ts = 1622101184, start_ts = 1622542334, end_ts = 0, dflags = 513, iflags = 64, sflags = 0, toroute = 0, toroute_name = {s = 0x0, len = 0}, from_rr_nb = 0, tl = {next =

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread themsley-voiceflex
That's a yes to the dialog replication question. Am checking the p *cell output now. I have two core dumps so it's possible I mixed them up. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread Daniel-Constantin Mierla
Btw, do you do dialog replication via dmq? -- 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/2757#issuecomment-853795330___ Kamailio (SER)

Re: [sr-dev] [kamailio/kamailio] kamailio 5.4.5 crash after dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg (#2757)

2021-06-03 Thread Daniel-Constantin Mierla
I got the pcap via email, the call-id matches the `bt full` output, but does not match the output of `p *cell`. Maybe you used a different corefile, can you get the output from the same corefile as for `bt full`? Otherwise, I cannot correlate the data between them. Also, the `(gdb) p

Re: [sr-dev] [kamailio/kamailio] nathelper: fix_nated_sdp added ignoring RFC3605-param if omitted (#2737)

2021-06-03 Thread Olle E. Johansson
Let me check if I can set up tests. -- 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/2737#issuecomment-853660669___ Kamailio (SER) -

Re: [sr-dev] [kamailio/kamailio] nathelper: fix_nated_sdp added ignoring RFC3605-param if omitted (#2737)

2021-06-03 Thread Daniel-Constantin Mierla
@oej - is there a chance that you can test this PR? I see you discussed #2497, maybe you have some IPv6 environment at hand. If not and no other comments, then it can be merged soon. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on

Re: [sr-dev] [kamailio/kamailio] app_perl change to ignore "die" signals from eval blocks (#2754)

2021-06-03 Thread Daniel-Constantin Mierla
I am not using app_perl, also not that familiar with Perl, so if nobody else has comments, it can be merged soon. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] Smsops 7bit support special chars (#2756)

2021-06-03 Thread Daniel-Constantin Mierla
If no comments from other devs, it can be merged soon. -- 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/2756#issuecomment-853641476___

Re: [sr-dev] [kamailio/kamailio] Update resolve.c handle type 41 (#2759)

2021-06-03 Thread Henning Westerholt
Closed #2759. -- 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/2759#event-4835801761___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] ERROR: [core/resolve.c:941]: get_record(): unknown type 41 (#2758)

2021-06-03 Thread Henning Westerholt
Thanks for the report. Did you tried current already a recent maintained version (e.g. 5.4,x, 5.5.x)? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] Update resolve.c handle type 41 (#2759)

2021-06-03 Thread Henning Westerholt
Thanks for the pull request. This should already taken care of it in the current versions: /* * Older glibc < 2.25 does not include T_OPT in nameser_compat.h yet. * On alpine linux musl library it is also not defined. There is no * musl feature test macro, so we look for glibc instead. */

[sr-dev] git:master:e8fa2b3e: pv: support Contact header in $hfl(...)

2021-06-03 Thread Daniel-Constantin Mierla
Module: kamailio Branch: master Commit: e8fa2b3e8e5a789ac6d6d35f75ec61d09f487d6c URL: https://github.com/kamailio/kamailio/commit/e8fa2b3e8e5a789ac6d6d35f75ec61d09f487d6c Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date: 2021-06-03T11:11:50+02:00 pv: support Contact

[sr-dev] git:master:25834469: core: select - test for HDR_ERROR_T after header name parsing

2021-06-03 Thread Daniel-Constantin Mierla
Module: kamailio Branch: master Commit: 2583446968d81a9351caab1cfdd2cc86434850f3 URL: https://github.com/kamailio/kamailio/commit/2583446968d81a9351caab1cfdd2cc86434850f3 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date: 2021-06-03T10:55:22+02:00 core: select - test

[sr-dev] [kamailio/kamailio] Update resolve.c handle type 41 (#2759)

2021-06-03 Thread Andrew Webster
Possible solution to https://github.com/kamailio/kamailio/issues/2758 !-- 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,

[sr-dev] [kamailio/kamailio] ERROR: [core/resolve.c:941]: get_record(): unknown type 41 (#2758)

2021-06-03 Thread Andrew Webster
### Description ### Troubleshooting Reproduction Debugging Data ``` (paste your debugging data here) ``` Log Messages ``` (paste your log messages here) ``` SIP Traffic ``` (paste your sip traffic here) ``` ### Possible Solutions ### Additional