sr-dev April 2018

sr-dev@lists.kamailio.org

19 participants
256 discussions

Kamailio 5.2 stable release
by Saurabh Kumar 22 Jul '18

22 Jul '18

Hi Miconda, We are using Kamailio 5.0.2 right now. We want to use recently introduced db_redis for location queries. So, can you confirm please when kamailio 5.2 stable (with db_redis) will be released (rough expectation). -- Regards, Saurabh Kumar VOIP Application Developer

3 3

[kamailio/kamailio] app_java: gcj is been removed from gcc since gcc7 (#1487)
by Victor Seva 04 Jul '18

04 Jul '18

>From debian bugreport https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892538 ``` Source: kamailio Severity: serious Tags: sid buster User: debian-gcc(a)lists.debian.org Usertags: gcj-rm Hi, kamailio depends or build-depends on GCJ. GCJ has been dropped upstream since GCC 7, so we are dropping it from Debian. Thus please either drop support for GCJ if you are just building an alternative package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to default-jdk / default-jre as appropriate. Cheers, Emilio ``` >From https://gcc.gnu.org/gcc-7/changes.html ``` Java (GCJ) The GCC Java frontend and associated libjava runtime library have been removed from GCC. ``` Can the ``app_java`` module be built with openjdk-9-jdk? -- 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/1487

3 4

[kamailio] set_contact_alias is not applied (#445)
by Olle E. Johansson 20 Jun '18

20 Jun '18

If I run set_contact_alias nothing happens - the contact remains the same on the outbound message There's no error returned and debug logs indicate a proper header However, if I add "msg_apply_changes()" on the line after set_contact_alias the Contact sent to next hop has the alias content No other changes --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/445

3 19

[kamailio/kamailio] cfgutils route_if_exists causing leak (#1503)
by Julien Chavanton 04 Jun '18

04 Jun '18

2 5

[kamailio/kamailio] sipt: Add functions to work with forwarding info (#1498)
by sergey-vb 01 Jun '18

01 Jun '18

#### 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:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description This commits adding some new functions to Get and Change forwarding info in ISUP part of SIP-I/SIP-T messages. sipt_forwarding(origin, nai) - updates the IAM in the body if it exists, setting (or adding) the forwarding number to origin with the nature address specified in nai $sipt_redirection_info - Returns "Redirecting reason" or -1 if no redirection info found. $sipt_redirection_number - Returns number to which redirection will trigered sipt_redirection_number_nai - Returns NAI for redirection number from ISUP You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1498 -- Commit Summary -- * sipt: Add functions to work with forwarding info (#18) -- File Changes -- M src/modules/sipt/doc/sipt_admin.xml (72) M src/modules/sipt/sipt.c (149) M src/modules/sipt/ss7.h (6) M src/modules/sipt/ss7_parser.c (138) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1498.patch https://github.com/kamailio/kamailio/pull/1498.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/1498

3 11

[kamailio/kamailio] db_mongodb has a problem with projection (#1479)
by kelchy 20 May '18

20 May '18

### Description on upgrade to 5.1.2, db_mongodb broke ### Troubleshooting i create a [PR](https://github.com/kamailio/kamailio/pull/1477) to print out any mongo query error then i saw the debug messages below #### Reproduction install 5.1.2, use mongo as db for sip_trace module #### Debugging Data ``` DEBUG: db_mongodb [mongodb_connection.c:55]: db_mongodb_new_connection(): connection open to: mongodb://user:pass@mongo1.abc.com:17017/collection DEBUG: db_mongodb [mongodb_dbase.c:904]: db_mongodb_query(): query to collection [version] DEBUG: db_mongodb [mongodb_dbase.c:938]: db_mongodb_query(): query filter: { "table_name" : "sip_trace" } DEBUG: db_mongodb [mongodb_dbase.c:966]: db_mongodb_query(): columns filter: { "projection" : { "table_version" : 1 } } DEBUG: db_mongodb [mongodb_dbase.c:782]: db_mongodb_store_result(): An error occurred: Unsupported projection option: projection: { table_version: 1 } ERROR: <core> [db.c:450]: db_check_table_version(): invalid version 0 for table sip_trace found, expected 4 (check table structure and table "version") ERROR: siptrace [siptrace.c:435]: child_init(): error during table version check ERROR: <core> [core/sr_module.c:942]: init_mod_child(): error while initializing module siptrace (/usr/lib64/kamailio/modules/siptrace.so) (idx: 39 rank: -2 desc: [Http Async Worker]) ``` #### Log Messages #### SIP Traffic ### Possible Solutions change the way mongo builds the query ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.1.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 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: unknown compiled on 06:43:15 Mar 9 2018 with gcc 4.8.2 ``` * **Operating System**:  ``` Ubuntu 14.04.1 LTS \n \l Linux hostname 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ``` -- 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/1479

2 10

[kamailio/kamailio] kazoo: wrong BLF when used application/dialog-info+xml (#1489)
by sergey-safarov 10 May '18

10 May '18

### Description Yealink phones is subscribes using `application/dialog-info+xml`. In this case for many phones false reported `early` state. ### Troubleshooting #### Reproduction Not knows. Some phones is displayes properly, some is not. #### Debugging Data none #### Log Messages not yet done #### SIP Traffic In provided pcap. is subscribed two clients `yealink` phone and `x-lite` softphone. Created call to extension 201 (sip login). For `x-lite` status is changed properly for `yealink` is not. Filters `udp.port==13322` caller leg `udp.port==1025` callee legs `udp.srcport==5060&&udp.dstport==5060` yealink phone `udp.port==15502` xlite [blf-test.pcap.gz](https://github.com/kamailio/kamailio/files/1849284/blf-te… packet 14 - kamailio reports 201 extension is Available to xlite packet 25 - kamailio reports 201 is early to yealink (unexpected) packet 108 - created call to 201 extension packer 109 - ringing to caller packet 118 - kamailio send ringing to caller packet 119 - INVITE send to callee packet 124 - callee send Trying packet 127 - kamailio reports 201 is ringing to yalink packet 129 - kamailio reports 201 is busy to xlite packet 145 - kamailio send session progress to caller packet 146 - callee send ringing packet 154 - caller send cancel packet 156 - kamailio send early to yealink (unexpected) packet 156 - kamailio send Available to x-lite ### Possible Solutions not known ### Additional Information Kamailio installed from kazoo team repo ``` [root@kamailio01 ~]# kamailio -V version: kamailio 5.0.3 (x86_64/linux) 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: unknown compiled on 11:07:05 Sep 23 2017 with gcc 4.8.5 [root@kamailio01 ~]# ``` * **Operating System**:  ``` [root@kamailio01 ~]# uname -a Linux kamailio01.cloudpbx.ai.co.uk 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@kamailio01 ~]# cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) [root@kamailio01 ~]# ``` -- 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/1489

2 9

[kamailio/kamailio] I_perform_user_authorization_request(): no int value param passed (#1099)
by riccardovarotto 04 May '18

04 May '18

### Description Using I-CSCF Kamailio module with 5.0.1 version we got the error: "I_perform_user_authorization_request(): no int value param passed" Same configuration file works well on 5.0.0 version  ### Troubleshooting #### Reproduction  #### Debugging Data 1(26715) ERROR: *** cfgtrace:request_route=[register] c=[/etc/KAMAILIO_ASTERISK_CFG/IMS_5/icscf/./kamailio.cfg] l=374 a=26 n=I_perform_user_authorization_request 1(26715) ERROR: <core> [core/sr_module.c:1766]: get_int_fparam(): Unexpected param type: 1280329042 1(26715) ERROR: ims_icscf [registration.c:78]: I_perform_user_authorization_request(): no int value param passed 1(26715) ERROR: *** cfgtrace:request_route=[register] c=[/etc/KAMAILIO_ASTERISK_CFG/IMS_5/icscf/./kamailio.cfg] l=375 a=26 n=send_reply [log_ko.gz](https://github.com/kamailio/kamailio/files/961675/log_ko.gz) [kamailio.cfg.txt](https://github.com/kamailio/kamailio/files/961677/kamaili…  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- 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/1099

5 11

[kamailio/kamailio] usrloc: Incorrect date format used to query contacts by expire time. (#1514)
by Konstantin 02 May '18

02 May '18

#### 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 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:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description - In the function get_all_db_ucontacts() date was passed to db module as a regular string, but in some cases that leads to incorrect db query, e.g. in case of mongodb. DATATIME format should be used instead of string. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1514 -- Commit Summary -- * Incorrect date format used to query contacts by expire time. -- File Changes -- M src/modules/usrloc/dlist.c (11) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1514.patch https://github.com/kamailio/kamailio/pull/1514.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/1514

2 4

[kamailio/kamailio] nathelper: it doesn't ping contacts if ping_nated_only=0 (#1516)
by Konstantin 02 May '18

02 May '18

- nathelper sends ping only if nat flag is specified, but if ping_nated_only=0 it should ping all contact in any case. #### 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 in `doc/` subfolder, the README file is autogenerated) #### 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:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description We need to check presence of nat flag with check of ping_nated_only parameter to avoid situation when flag is not specified by user wants to ping all contacts and don't get any pings. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1516 -- Commit Summary -- * nathelper: it doesn't ping contacts if ping_nated_only=0 -- File Changes -- M src/modules/nathelper/nathelper.c (7) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1516.patch https://github.com/kamailio/kamailio/pull/1516.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/1516

2 5

← Newer
1
...
4
5
6
7
8
9
10
...
26
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev April 2018