sr-dev March 2018

sr-dev@lists.kamailio.org

17 participants
327 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] 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] error while dumping dialog via RPC (#145)
by Savolainen Dmitri 01 May '18

01 May '18

In part of profiles and/or variables section while using `static inline void internal_rpc_print_dlg(rpc_t *rpc, void *c, dlg_cell_t *dlg, int with_context) ` May be it is an error of ctl module ``` # kamcmd dlg.list { h_entry: 6718 h_id: 20440 call-id: 48c9fe85f6750163(a)192.168.5.60 from_uri: sip:000*051@xxxxxx.xx:5068 to_uri: sip:002@xxxxxx.xx:5068 state: 4 start_ts: 1430324850 init_ts: 1430324847 timeout: 1430368049 lifetime: 43200 dflags: 515 sflags: 0 iflags: 0 caller: { tag: bda5e24faa4c4ff5 contact: sip:000*051@192.168.5.60:5066;transport=udp;alias=xxx.xxx.78.202~5066~1 cseq: 5457 route_set: socket: udp:xxx.xxx.66.150:5068 } callee: { tag: 4y2gjr7N9231K contact: sip:002@xxx.xxx.66.151:5080;transport=udp cseq: 0 route_set: socket: udp:xxx.xxx.66.150:5068 } profiles: { ERROR while parsing the record 62, @698: 03 : bad record ``` --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/145

4 6

[kamailio/kamailio] Feature Request: possibility to reload dialogs from db without restarting kamailio (#1274)
by alexsosic 14 Apr '18

14 Apr '18

Hi, we're trying to have scalable Kamailio nodes that are stateless. That means that we can for example load dispatchers and reload them from an API endpoint. Now we're stuck on the dialog part. All our nodes load the dialogs from a shared db, what happens when a node gets down is that a packet reaches another node and does not know how to handle that because the dialog does not have it's ip address. Also there is no possibility to reload the dialogs from db so that we could update the records in the db and have the dialogs ip changed on an anctive node's ip. Is there a possibility to have a function to reload the dialogs from db on a running kamailio? -- 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/1274

8 28

[kamailio/kamailio] KeepAlive Module (#1476)
by voztovoice 14 Apr '18

14 Apr '18

Hello, I'm using keepalive module with drouting module... the event route works fine: NOTICE: <script>: Gateway up: OPTIONS sip:1.2.3.4 NOTICE: <script>: Gateway up: OPTIONS sip:5.6.7.8 but kamcmd command not: kamcmd keepalive.list foobar 42 foobar 42 { text: foobar number: 42 } { list: { nn: 17 nn: 22 } } { uri: sip:1.2.3.4 owner: drouting last checked: Wed Feb 21 11:20:12 2018 last up: Wed Dec 31 19:00:00 1969 last down: Wed Feb 21 11:20:13 2018 } { uri: sip:5.6.7.8 owner: drouting last checked: Wed Feb 21 11:20:12 2018 last up: Wed Dec 31 19:00:00 1969 last down: Wed Feb 21 11:20:12 2018 Thank you Regards... -- 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/1476

3 8

module FAQ, private contact replacement
by Henning Westerholt 11 Apr '18

11 Apr '18

Hello, in many modules we have a template text about our support contacts in the "FAQ" part: "E-mails regarding any stable Kamailio release should be sent to <sr-users(a)lists.kamailio.org> and e-mails regarding development versions should be sent to <sr-dev(a)lists.kamailio.org>. If you want to keep the mail private, send it to <sr-users(a)lists.kamailio.org>." The lower part (about the private contact) makes no sense anymore. It used contain a private SER contact address, and lost somehow its meaning during the conversion to Kamailio. I would like to change to this text to: "If you need to keep the e-mail private (e.g. for security issues) send it to management at kamailio dot org." Any objections against this change, or remarks about the replacement text? Regards, Henning

3 7

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2018