Re: [sr-dev] [kamailio/kamailio] Lost selectors (#2705)

@sergey-safarov pushed 2 commits. 0a624c9c001d2903599b93281bc84a1221a62f4e removed typos 3a33c7c430a0208e0bca3f9802384dc030b0302a replased own code to get_body_part_by_filter -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/kamailio

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

Closed #2711. -- 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/2711#event-4618322186___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

closing this PR -- 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/2711#issuecomment-823164530___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] rtpengine: session refresh, do not try use other rtpengine node on rtpengine node failure (#2713)

Closed #2713. -- 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/2713#event-4618311614___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] rtpengine: session refresh, do not try use other rtpengine node on rtpengine node failure (#2713)

Closing for future development. -- 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/2713#issuecomment-823163217___ Kamailio (SER) -

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

> I think such benefits can be used in some CI testing Yes, I agreed. Most of the features related to recent GCC version automatic checks may be implemented in CI process. Yes, definitely we can improve automatic checks in CI builds. > There can be cases when one wants to replace a RPM

Re: [sr-dev] [kamailio/kamailio] rtpengine: session refresh, do not try use other rtpengine node on rtpengine node failure (#2713)

Also looks as to this issue relevant to another use case. After call established on RTPengine host I execute ``` rtpengine-ctl set maxsessions 0 ``` Now when Kamailio receives ReINVITE in Kamailio log I can see ``` 10(32768) INFO: {1 34826098 INVITE e139ffde-a05a-11eb-8f1b-f7192ebf791d} rtpengine

[sr-dev] [kamailio/kamailio] rtpengine_manage: send SDP two times (#2715)

### Description When used `rtpengine_manage` function then `RTPengine` node returns the correct response but in the outbound SIP message, SDP is duplicated. ### Troubleshooting Reproduction Updated /etc/kamailio/kamailio.cfg like in this patch. ```diff diff --git a/etc/kamailio.cfg

[sr-dev] [kamailio/kamailio] rtpengine: session refresh, do not try use other rtpengine node on rtpengine node failure (#2713)

### Description I want to use Session timers to refresh SDP on RTPengine node failure. If call RTP streams established via first RTPengine node, and then this RTPengine node is stopped, then rtpengine Kamailio module do not try to use other RTPengine nodes. ### Troubleshooting

Re: [sr-dev] [kamailio/kamailio] build warnings (#2710)

Also this looks as memory access outside of `pzflag->v.asciiz` array boundaries. [Link](https://github.com/kamailio/kamailio/blob/2df6f9d6cb74bc115206e8b200af7234267f74d5/src/modules/mohqueue/mohq_funcs.c#L2178) > pzflag->v.asciiz [pstream->ptime.len + 1] = 0; -- You are receiving this

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

One more benefit. The recent GCC version makes more automatic checks than the old GCC version. We can enable GCC flags that allow handling warnings as errors. So any PR that generates a warning will automatically fail automatic checks. This will improve PR code quality. -- You are receiving

Re: [sr-dev] [kamailio/kamailio] build warnings (#2710)

Also `fparam_t pzflag [1]` mean array of one element. Why not used? ``` fparam_t pzflag = {"", FPARAM_STRING, {pflagbuf}, 0}; ``` Just a question. -- 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] build warnings (#2710)

could you check this https://stackoverflow.com/questions/14670864/gcc-member-initialization-in-array-of-struct Maybe ```diff sdp_session_cell_t *psession; char pflagbuf [5]; strcpy (pflagbuf, "z20"); -fparam_t pzflag [1] = {"", FPARAM_STRING, {pflagbuf}, 0}; +fparam_t pzflag [1] = { +{"",

Re: [sr-dev] [kamailio/kamailio] build warnings (#2710)

Ok, Kamailio python modules will lease as it now without any changes. -- 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] build warnings (#2710)

If other modules use python2 they not affected. I will remove only python Kamailio module packaging that not more supported. Now affected only CenOS 6. CentOS 7 and CenOS 8 not affected because they have python3 Kamailio modules. -- You are receiving this because you are subscribed to this

Re: [sr-dev] [kamailio/kamailio] build warnings (#2710)

I will remove `python` module and lease only `python3` module. -- 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] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

I think the main benefit is no required to write code that must be compiled in some way by different GCC versions. For `C` code this may be not actual, but for `C++` think this applicable. For example, the old GCC has broken regular expressions support. More details at

[sr-dev] [kamailio/kamailio] pkg/kamailio/obs: used more recent gcc for RHEL and CentOS dists (#2711)

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

[sr-dev] [kamailio/kamailio] build warnings (#2710)

**missing braces around initializer** *mohq_funcs.c:2163* ``` LD (gcc) [M matrix.so] matrix.so CC (gcc) [M mohqueue.so] mohq_locks.o CC (gcc) [M mohqueue.so] mohq_funcs.o mohq_funcs.c: In function 'send_rtp_answer': mohq_funcs.c:2163:23: warning: missing braces around initializer

[sr-dev] git:master:2df6f9d6: pkg/kamailio/obs: added lwsc module packaging

Module: kamailio Branch: master Commit: 2df6f9d6cb74bc115206e8b200af7234267f74d5 URL: https://github.com/kamailio/kamailio/commit/2df6f9d6cb74bc115206e8b200af7234267f74d5 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-04-16T15:28:43+03:00 pkg/kamailio/obs: added lwsc module

[sr-dev] RHEL 6 and CentOS 6 deprecated

I try to refresh the build image for CentOS 6 and can't do it now. This directory (and version of CentOS) is deprecated. Please see this FAQ concerning the CentOS release scheme: https://wiki.centos.org/FAQ/General Please keep in mind that 6.0, 6.1, 6.2, 6.3, 6.4 , 6.5, 6.6, 6.7, 6.8 , 6.9 and

Re: [sr-dev] fresh GCC

; > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > *From:* sr-dev *On Behalf Of *Sergey > Safarov > *Sent:* Friday, April 16, 2021 10:30 AM > *To:* Kamailio (SER) - Devel Mailing List > *Subject:* [sr-dev] fres

[sr-dev] fresh GCC

I have created a pull request that allows the use of fresh GCC for the FreeSwitch project. https://github.com/signalwire/freeswitch/pull/1161 Think we can use the same approach to use fresh GCC for the Kamailio project. For RHEL based dist and old Debian dest. Is it a useful approach to use

Re: [sr-dev] [kamailio/kamailio] absolute dns names trigger error (#2706)

yes, you are right. This name modification made by linux core libs. I have checked the `resolve.conf` settings and this managed by `domain` directive in `/etc/resolv.conf`. *example* ``` domain . ``` I now fixed extra DNS request generation. But the original request still actual. Should

Re: [sr-dev] [kamailio/kamailio] absolute dns names trigger error (#2706)

In one config I use ``` dns_cache_flags = 4 dns_cache_init = off ``` Looks as when Kamailio try to resolve DNS hostname sended two DNS requests: 1. A for IPv4 address resolving; 2. for IPv6 address resolving. When DNS hostname has only record and do not has A record, then 1.

Re: [sr-dev] [kamailio/kamailio] absolute dns names trigger error (#2706)

To test absolute DNS name us can use `curl` ``` [root@safarov-server ~]# curl -v telnet://ipv6.test-ipv6.com.:80 * Rebuilt URL to: telnet://ipv6.test-ipv6.com.:80/ * Trying 2001:470:1:18::115... * TCP_NODELAY set * Connected to ipv6.test-ipv6.com (2001:470:1:18::115) port 80 (#0) ``` -- You

[sr-dev] [kamailio/kamailio] absolute dns names trigger error (#2706)

### Description To avoid extra DNS requests I want to use absolute DNS names instead of relative. To do this I configured ``` modparam("siptrace", "duplicate_uri", "sip:sip-trace6.example.com.:9060" ``` And now I can see errors ``` CRITICAL: [core/proxy.c:264]: mk_proxy(): could not resolve

[sr-dev] [kamailio/kamailio] List selectors (#2705)

Pre-Submission Checklist - [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) - [ ] No commits to README files for

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

yes, have checked "ERROR" generation. This happens because `part_multipart_headers_cmp()` try search content by "Content-Id". The first content element (SDP in the example) does not have "Content-Id". Function reaches the end of the content element and generates the error. Then

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

Hell @wkampich let me review the change about ERROR waring. I want to try to understand in detail why the error generated. Maybe I can suggest another approach. Please give today and tommorow. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

Use case when the call contains two `Geolocation` headers. Example ``` Geolocation: Geolocation: ``` Technically such a call contains Geolocacation by_value and does not require deference first Geolocation header by_reference. >From my point of view. When used

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

tested config ``` listen=udp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "pv.so" loadmodule "http_client.so" loadmodule "lost.so" loadmodule "textopsx.so" modparam("lost", "exact_type", 1) modparam("lost", "post_request", 1) modparam("http_client", "httpcon",

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

Tested config ``` listen=udp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "pv.so" loadmodule "http_client.so" loadmodule "lost.so" loadmodule "textopsx.so" modparam("lost", "exact_type", 1) modparam("lost", "post_request", 1) request_route { $var(id) = "sip:al...@ca.nga911.com"; $var(res)

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

@sergey-safarov commented on this pull request. > @@ -168,7 +176,59 @@ Set location_type parameter ... -modparam("lost", "location_type, "civic geodetic locationURI") +modparam("lost", "

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

tested this config file ``` listen=udp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "pv.so" loadmodule "http_client.so" loadmodule "lost.so" loadmodule "textopsx.so" modparam("lost", "exact_type", 1) request_route { $var(geo_uri) = @hf_value.geolocation[1].uri; if

Re: [sr-dev] [kamailio/kamailio] extensions to lost and http_client modules (#2675)

@sergey-safarov commented on this pull request. > + + + The return value is 200 on success, 400 if an internal error occured, or 500 if an +error code is returned in the HELD respo

Re: [sr-dev] [kamailio/kamailio] not properly compassion (#2701)

Tanks you Daniel for your clarification I have tested this config ``` listen=udp:[::1]:5060 listen=udp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "sdpops.so" request_route { if (sdp_get_address_family() && $rc ieq 6 ) { xlog("L_WARN", "sdp_get_address_family == 6\n"); } else if

[sr-dev] [kamailio/kamailio] not properly compassion (#2701)

### Description I think something wrong with integer comparison when tested this config file ``` listen=udp:[::1]:5060 listen=udp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "sdpops.so" request_route { if (sdp_get_address_family() ieq 6 ) { xlog("L_WARN", "sdp_get_address_family ==

Re: [sr-dev] [kamailio/kamailio] siptrace: duplicate_uri with multiple values (#2693)

Maybe we can introduce another label, that will allow easy search feature requests closed but may be useful for implementation in the future? -- 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] siptrace: duplicate_uri with multiple values (#2693)

I closing this and add the tag `wontfix`. So this can be easily found in the future using tags `feature-request` and `wontfix` -- 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] siptrace: duplicate_uri with multiple values (#2693)

Closed #2693. -- 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/2693#event-4543385525___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] import_file - wildcard support (#2125)

Closed #2125. -- 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/2125#event-4536210145___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] import_file - wildcard support (#2125)

Closing as no devs to implement. -- 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/2125#issuecomment-811273926___ Kamailio (SER) -

Re: [sr-dev] [kamailio/kamailio] tls.cfg: resolve macros (#2691)

Closed #2691. -- 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/2691#event-4530369033___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] tls.cfg: resolve macros (#2691)

Thanks, Daniel @miconda for clarification. Closing. -- 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/2691#issuecomment-810575908___

Re: [sr-dev] [kamailio/kamailio] ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2] (#2697)

For RPM dist this fixed at 468ec8f26ff8496bdf62a7bfbbb1b1e2e3452c0f For any other dist that use systemd you can make similar change. -- 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] siptrace: duplicate_uri with multiple values (#2693)

Thanks, @ovidiusas. Sure this will help in my use case. -- 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/2693#issuecomment-808331729___

[sr-dev] [kamailio/kamailio] siptrace: duplicate_uri with multiple values (#2693)

### Description As admin, I want check TLS encrypted call signaling on local Kamailio. To do this I can use [this instruction](https://voipembedded.wordpress.com/2021/03/22/troubleshooting-kamailio-encrypted-sip-traffic/). Here used `siptrace` module. But at the same time, I need to send the

[sr-dev] [kamailio/kamailio] tls.cfg: resolve macros (#2691)

### Description I want use macros defined in `kamailio.cfg` inside `tls.cfg` like: ``` [server:[IPV6_ADDR]:5061] method = TLSv1.2+ verify_certificate = yes require_certificate = no private_key = /etc/kamailio/tls/example.com.key certificate = /etc/kamailio/tls/example.com.pem server_name =

[sr-dev] git:master:d0434c21: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: master Commit: d0434c21962ad92b92108f9f7cf761617bb6ec58 URL: https://github.com/kamailio/kamailio/commit/d0434c21962ad92b92108f9f7cf761617bb6ec58 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-03-24T09:26:13+03:00 pkg/docker: updated submodule [skip ci

Re: [sr-dev] [kamailio/kamailio] failed build on CentOS 7 (#2687)

Closed #2687. -- 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/2687#event-4498648147___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] failed build on CentOS 7 (#2687)

Looks as this fixed by d82d95a824d6f8a6c0246b78ac6642d4d6fed9e1 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] [kamailio/kamailio] failed build on CentOS 7 (#2687)

``` CC (gcc) [M geoip.so] geoip_mod.o LD (gcc) [M geoip.so] geoip.so CC (gcc) [M gzcompress.so]

Re: [sr-dev] [kamailio/kamailio] phonenum: cannot build on fresh dist (#2684)

Closed #2684. -- 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/2684#event-4484169936___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] phonenum: cannot build on fresh dist (#2684)

I will close the issue. If some think similar will rise with CentOS, then will open new. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] [kamailio/kamailio] phonenum: cannot build on fresh dist (#2684)

``` make[3]: 'libsrdb1.so.1.0' is up to date. LD (gcc) [M db_perlvdb.so] db_perlvdb.so CC (gcc) [M phonenum.so] phonenum_mod.o CC (gcc) [M phonenum.so] phonenum_pv.o Compiling cphonenumber.cpp g++ -std=c++11 -fPIC -DPIC -g -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops

[sr-dev] git:master:2d971f5f: pkg/kamailio/obs: packaged lrkproxy module [skip ci]

Module: kamailio Branch: master Commit: 2d971f5f0577255fa6192b5584a612ffe88fa347 URL: https://github.com/kamailio/kamailio/commit/2d971f5f0577255fa6192b5584a612ffe88fa347 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-03-15T19:10:58+03:00 pkg/kamailio/obs: packaged lrkproxy

Re: [sr-dev] [kamailio/kamailio] Infinity read from socket (#2658)

The issue can be reproduced using this config file ``` listen=tcp:eth0:5060 tcp_accept_haproxy=yes request_route { drop; } ``` When you started kamailio, then need telnet to 5060 and do not send any data. Just make TCP connect. As a result, one server core will be 100% loaded. -- You

Re: [sr-dev] [kamailio/kamailio] Infinity read from socket (#2658)

I also attached PCAP for connection from 32519 port. [port32519.pcap.gz](https://github.com/kamailio/kamailio/files/6083317/port32519.pcap.gz) This is AWS heal check probe. This looks correct. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or

Re: [sr-dev] [kamailio/kamailio] Infinity read from socket (#2658)

You are right, this is an inbound connection. details in attached PCAP. [haproxy-stuck.pcapng.gz](https://github.com/kamailio/kamailio/files/6083218/haproxy-stuck.pcapng.gz) What is strange here 1. after packet `#2` must be `TCP/ACK` packet. This packet does not exist. We have a half-open TCP

Re: [sr-dev] [kamailio/kamailio] Infinity read from socket (#2658)

@teotwaki could you look -- 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/2658#issuecomment-789709565___ Kamailio (SER) - Development

Re: [sr-dev] [kamailio/kamailio] Infinity read from socket (#2658)

As I understand haproxy protocol may be used only for `inbound` connections and can't be used for outbound connections. According to` lsof` output, problem connection is outbound ``` [root@sbc-13 ~]# lsof -a -p 56907| grep 3931924 kamailio 56907 kamailio 58u IPv43931924

[sr-dev] [kamailio/kamailio] Infinity read from closed socket (#2658)

### Description I observing a case when Kamailio stop processing calls. What is found: *Lot of connections with CLOSE_WAIT state* ``` [root@sbc-13 ~]# netstat -anp | grep 5060 tcp 129 0 100.85.118.66:5060 0.0.0.0:* LISTEN 56907/kamailio tcp 153 0

[sr-dev] [kamailio/kamailio] add ASAN build options (#2650)

### Description I want to be sure my customization does not produce memory leack. To get this work I want to use the ASAN project. Could you add `mode=asan` build option that adds gcc ` -fsanitize=address -static-libasan` options `-lasan` linker flags. More info

Re: [sr-dev] [kamailio/kamailio] Random crashes on tcp_main.c:handle_tcp_child() on FreeBSD (#2638)

I think this also not will work with `libressl`. Reson: some time ago `Alpine Linux` have used `libressl` and with `libressl` TLS connection also lead to Kamaili crashes. -- 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] lost: resolve geolocation url using POST (#2641)

Thanks @wkampich for the `response_time` modparam reference. Looks as here required support of two string values `emergencyRouting` and `emergencyDispatch`. When used these string values we can set `0` timeout value for http_client AIP call. -- You are receiving this because you are subscribed

Re: [sr-dev] [kamailio/kamailio] lost: resolve geolocation url using POST (#2641)

@miconda This ticket for requirements definition not only. When I or another developer will be ready to implement then it can be reopened. P.S. May we need some live cycle for tickets. Like "if the feature ticket not commented by somebody from Kamailio team, then automatically close with tag

Re: [sr-dev] [kamailio/kamailio] lost: resolve geolocation url using POST (#2641)

According [rfc5985](https://tools.ietf.org/html/rfc5985) `responseTime` may contain values 1. `emergencyRouting` 2. `emergencyDispatch` 3. non Negative Integer value ```xml

Re: [sr-dev] [kamailio/kamailio] lost: resolve geolocation url using POST (#2641)

I observed that http_client drop the HTTP request after a timeout. So will be good to let LIS know Kamailio timeout. To do this may be used `responseTime` paramer according rfc5985#section-6.1 > The "responseTime" attribute MAY be included in a location request message. The "responseTime"

[sr-dev] [kamailio/kamailio] lost: resolve geolocation url using POST (#2641)

### Description According [RFC5985](https://tools.ietf.org/html/rfc5985) > The POST method is the only method REQUIRED for HELD. If a LIS chooses to support GET or HEAD, it SHOULD consider the kind of application doing the GET. So not all LIS servers support the GET method and only the

Re: [sr-dev] [kamailio/kamailio] Build warnings (#2636)

Thanks, @miconda. I will ignore this error in future. -- 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/2636#issuecomment-779435019___

Re: [sr-dev] [kamailio/kamailio] Build warnings (#2636)

Closed #2636. -- 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/2636#event-435218___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] update libphonenum (#2635)

Closed #2635. -- 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/2635#event-4330559967___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] update libphonenum (#2635)

Please check the `master` branch (daily builds) and release `5.4.4` tomorrow. If not fixed please reopen. -- 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] core on broken config (#2599)

Added commit 9a35a5b95e8144dbdb18003f40e49e5b497274f3. Added `--atexit=no` option for `Fedora`, `OpenSUSE`, `CentOS 8` and other `RHEL 8` based dists. Should I backport this commit into `5.4`, `5.3` and `5.2` branches? -- You are receiving this because you are subscribed to this thread. Reply

Re: [sr-dev] git:master:9a35a5b9: pkg/kamailio/obs: added --atexit=no into systemd unit file [skip ci]

o it now if you > want to be part of 5.4.4. > > Cheers, > Daniel > > On 15.02.21 09:10, Sergey Safarov wrote: > > Module: kamailio > > Branch: master > > Commit: 9a35a5b95e8144dbdb18003f40e49e5b497274f3 > > URL: > https://github.com/kamailio/kamailio/commit/9a3

[sr-dev] git:5.4:57fb85e2: pkg/kamailio/obs: added --atexit=no into systemd unit file [skip ci]

Module: kamailio Branch: 5.4 Commit: 57fb85e2a1dc50618179b79901563bab502169da URL: https://github.com/kamailio/kamailio/commit/57fb85e2a1dc50618179b79901563bab502169da Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-15T13:43:09+03:00 pkg/kamailio/obs: added --atexit

[sr-dev] git:master:9a35a5b9: pkg/kamailio/obs: added --atexit=no into systemd unit file [skip ci]

Module: kamailio Branch: master Commit: 9a35a5b95e8144dbdb18003f40e49e5b497274f3 URL: https://github.com/kamailio/kamailio/commit/9a35a5b95e8144dbdb18003f40e49e5b497274f3 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-15T11:10:24+03:00 pkg/kamailio/obs: added --atexit

[sr-dev] [kamailio/kamailio] Build warnings (#2636)

**core/receive.c:300 - CentOS 7** ``` CC (gcc) [kamailio] core/ip_addr.o CC (gcc) [kamailio] core/rvalue.o CC (gcc) [kamailio] core/receive.o core/receive.c: In function 'receive_msg': core/receive.c:300:2: warning: missing braces around initializer

Re: [sr-dev] [kamailio/kamailio] core on broken config (#2599)

Should I add `--atexit=no` to systemd kamailio unit file? -- 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/2599#issuecomment-776970772___

Re: [sr-dev] [kamailio/kamailio] master: failed build on CentOS7 (#2631)

@miconda, are you use docker on your dev PC? -- 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/2631#issuecomment-776959493___ Kamailio

Re: [sr-dev] [kamailio/kamailio] master: failed build on CentOS7 (#2631)

On current master on CentOS 7 ``` CC (gcc) [kamailio] core/utils/tmrec.o bison -d -b core/cfg core/cfg.y flex -o core/lex.yy.c core/cfg.lex CC (gcc) [kamailio] core/lex.yy.o core/cfg.lex:45:25: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ksr_yy_fatal_error' static void

Re: [sr-dev] [kamailio/kamailio] master: failed build on CentOS7 (#2631)

Reopened #2631. -- 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/2631#event-4311491417___ Kamailio (SER) - Development Mailing List

Re: [sr-dev] [kamailio/kamailio] core on broken config (#2599)

I have tested commit d8643c on CentOS 8 with the latest updates. Used config ``` [root@bcf-a0 tmp]# cat /root/kam.cfg listen=tls:eth0:25061 enable_tls=1 ### tls module ## loadmodule "tls.so" loadmodule "http_client.so" request_route { if (is_request()) { } exit; } ```

[sr-dev] [kamailio/kamailio] master: failed build on CentOS7 (#2631)

``` CC (gcc) [kamailio] core/cfg/cfg.o CC (gcc) [kamailio] core/utils/srjson.o CC (gcc) [kamailio] core/utils/sruid.o CC (gcc) [kamailio] core/utils/tmrec.o bison -d -b core/cfg core/cfg.y flex -o core/lex.yy.c core/cfg.lex CC (gcc) [kamailio] core/lex.yy.o core/cfg.lex:45:25: error: expected '=',

Re: [sr-dev] [kamailio/kamailio] core on broken config (#2599)

yes, not solved. When I make a compilation from sources than not crash. When I install from RPMs files compiled, then I have a core. Now I want to compare each RPM file version on build and target host. Think this give me hooks to find the important difference. -- You are receiving this because

Re: [sr-dev] [kamailio/kamailio] Segmentation fault while parsing incorrect config (#2630)

This duplicate of #2599 This not yet resolved -- 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/2630#issuecomment-776080472___ Kamailio

Re: [sr-dev] [kamailio/kamailio] Segmentation fault while parsing incorrect config (#2630)

Closed #2630. -- 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/2630#event-4310257503___ Kamailio (SER) - Development Mailing List

[sr-dev] [kamailio/kamailio] mod kazoo: wrong kazoo_publish example (#2627)

### Description Example 1.21. kazoo_publish usage contains string ``` $var(amqp_payload_request) = "{'Event-Category' : 'directory', 'Event-Name' : 'reg_success', 'Contact' : '" + $var(fs_contact) + "', 'Call-ID' : '" + $ci + "', 'Realm' : '" + $fd +"', 'Username' : '" + $fU + "', 'From-User'

Re: [sr-dev] [kamailio/kamailio] core on broken config (#2599)

I found the issue. The build CenOS version is older than the target CentOS version. I go to refresh the build CentOS and RHEL versions. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] [kamailio/kamailio] Build warnings (#2619)

**crypto_mod.c:343:12** ``` make[3]: 'libsrdb1.so.1.0' is up to date. LD (gcc) [M db_sqlite.so] db_sqlite.so CC (gcc) [M

[sr-dev] git:5.2:baed04d1: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: 5.2 Commit: baed04d18b3f07dbaeda92faf93c94dc837fc5c0 URL: https://github.com/kamailio/kamailio/commit/baed04d18b3f07dbaeda92faf93c94dc837fc5c0 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-02T12:39:58+03:00 pkg/docker: updated submodule [skip ci

[sr-dev] git:5.3:a9ce71b9: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: 5.3 Commit: a9ce71b9372e9aa8ddc921495f6b97534266a8b6 URL: https://github.com/kamailio/kamailio/commit/a9ce71b9372e9aa8ddc921495f6b97534266a8b6 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-02T12:36:17+03:00 pkg/docker: updated submodule [skip ci

Re: [sr-dev] [kamailio/kamailio] Main process exited, code=dumped, status=11/SEGV with http_async (#2616)

I think this case is delicate to https://github.com/kamailio/kamailio/issues/2616 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] git:5.4:dbe358d2: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: 5.4 Commit: dbe358d2d0df1ea2d8441b39ae460966e5edb164 URL: https://github.com/kamailio/kamailio/commit/dbe358d2d0df1ea2d8441b39ae460966e5edb164 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-01T11:55:24+03:00 pkg/docker: updated submodule [skip ci

[sr-dev] git:master:7358d6bd: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: master Commit: 7358d6bdf26861e0886898d59837307b728137e5 URL: https://github.com/kamailio/kamailio/commit/7358d6bdf26861e0886898d59837307b728137e5 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-02-01T09:36:58+03:00 pkg/docker: updated submodule [skip ci

Re: [sr-dev] [kamailio/kamailio] lost: new features LoST redirect and NAPTR lookup (#2606)

I have tested this PR on my local PC. During tests, I found module works as expected. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] [kamailio/kamailio] build warings (#2611)

**core/ut.h:751** ``` core/ut.h:751:13: warning: ‘shm_str_dup_block’ defined but not used [-Wunused-function] static str* shm_str_dup_block(const str* src) ^ CC (gcc) [kamailio] core/proxy.o In file included from core/ip_addr.h:39, from

[sr-dev] git:master:862543af: pkg/docker: updated submodule [skip ci]

Module: kamailio Branch: master Commit: 862543af16b0f19fd748819d446d9833b5d42cb0 URL: https://github.com/kamailio/kamailio/commit/862543af16b0f19fd748819d446d9833b5d42cb0 Author: Sergey Safarov Committer: Sergey Safarov Date: 2021-01-17T20:06:05+03:00 pkg/docker: updated submodule [skip ci

Re: [sr-dev] [kamailio/kamailio] dispatcher: updated failover example (#2602)

Closed #2602. -- 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/2602#event-4200857852___ Kamailio (SER) - Development Mailing List

<    1   2   3   4   5   6   7   8   9   10   >