sr-users April 2019

sr-users@lists.kamailio.org

81 participants
107 discussions

CDR start time of a canceled call
by Jan-Hendrik Dörner 23 Apr '19

23 Apr '19

Hello, I just noticed that the logged „start_time" as well as „end_time" of a canceled call is set to the „invite time“. If done this way, it is harder to calculate the „ringing time“. Is there an option to change this behaviour (i.e. to log the time of the received „bye“ instead)? (If done so, the ringing time would always be the time between start and invite …) Or is there a special reason for this behaviour? My CDR settings are as followed: modparam("acc", "cdr_enable", 1) … [View More] modparam("acc", "cdr_expired_dlg_enable", 1) # log unanswered / open dialogs modparam("acc", "cdr_on_failed", 1) # log also not answered calls modparam("acc", "cdr_extra", "inviteTime=$dlg_var(inviteTime)" modparam("acc", "cdr_log_enable", 1) # activate write to syslog modparam("acc", "cdr_facility", "LOG_LOCAL6") # syslog modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "time_mode", 0) #syslog timestamp modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) modparam("acc", "detect_direction", 0) modparam("acc", "log_flag", FLT_ACC) # needed for syslog modparam("acc", "log_missed_flag", FLT_ACCMISSED) # need for logging missed calls in syslog Regards Jan-Hendrik [View Less]

1 0

Kamailio-5.2.1 - Issues in NDB_MONGODB module initialisation
by José Seabra 22 Apr '19

22 Apr '19

Hello there, I have NDB_MONGODB loaded in kamailio with following configurations: *loadmodule "ndb_mongodb"* *modparam("ndb_mongodb", "server", "name=mgs1;uri='mongodb://mongodbserver:27017/proxyregistrar'")* Kamailio breaks up on start up and prints the following messages: *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/modparam.c:83]: set_mod_param_regex(): 'ndb_mongodb' matches module 'ndb_mongodb'* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/… [View More]sr_module.c:711]: find_param_export(): found <server> in module ndb_mongodb [/usr/lib64/kamailio/modules/ndb_mongodb.so]* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: <core> [core/modparam.c:99]: set_mod_param_regex(): found <server> in module ndb_mongodb [/usr/lib64/kamailio/modules/ndb_mongodb.so]* *Apr 18 13:16:10.464 proxy-registrar[-]: DEBUG: ndb_mongodb [mongodb_client.c:155]: mongodbc_add_server(): added server[mgs1]=mongodb://10.225.121.12:27017/proxyregistrar <http://10.225.121.12:27017/proxyregistrar>* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 21 rank 8: ndb_mongodb [tcp receiver (generic) child=3]* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: ALERT: <core> [main.c:739]: handle_sigs(): child process 3181 exited by a signal 11* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: ALERT: <core> [main.c:742]: handle_sigs(): core was generated* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/tcp_main.c:3513]: handle_ser_child(): dead child 16, pid 3181 (shutting down?)* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6d0e0, 23, -1, 0x0) fd_no=23 called* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *123: INFO: <core> [main.c:819]: sig_usr(): signal 15 received* *1a7311e30a6793da-3165(a)10.225.121.93 <1a7311e30a6793da-3165(a)10.225.121.93>: DEBUG: ndb_mongodb [ndb_mongodb_mod.c:128]: mod_destroy(): cleaning up * Core dump back trace output: *(gdb) bt full* *#0 0x00007f3daa134f93 in _mongoc_client_new_from_uri () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#1 0x00007f3daa156553 in mongoc_uri_get_ssl () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#2 0x00007f3daa134f88 in _mongoc_client_new_from_uri () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#3 0x00007f3daa135029 in mongoc_client_new () from /lib64/libmongoc-1.0.so.0* *No symbol table info available.* *#4 0x00007f3daae6d75f in mongodbc_init () at mongodb_client.c:63* * rsrv = 0x7f3db0f86728* * __FUNCTION__ = "mongodbc_init"* *#5 0x00007f3daae73c46 in child_init (rank=3) at ndb_mongodb_mod.c:113* * __FUNCTION__ = "child_init"* *#6 0x00000000005470d7 in init_mod_child (m=0x7f3db0f85e88, rank=3) at core/sr_module.c:846* * __FUNCTION__ = "init_mod_child"* *#7 0x00000000005474b6 in init_child (rank=3) at core/sr_module.c:874* * ret = 32573* *#8 0x00000000004b3840 in fork_process (child_id=3, desc=0x7ffecc20c7f0 "udp receiver child=2 sock=10.225.121.93:5060 <http://10.225.121.93:5060>", make_sock=1) at core/pt.c:341* * pid = 0* * child_process_no = 3* * ret = -1* * new_seed1 = 1273263324* * new_seed2 = 1531871627* * sockfd = {14, 15}* * __FUNCTION__ = "fork_process"* *#9 0x0000000000424b9b in main_loop () at main.c:1631* * i = 2* * pid = 3807* * si = 0x7f3db123a988* * si_desc = "udp receiver child=2 sock=10.225.121.93:5060 <http://10.225.121.93:5060>\000\177\000\000P\310 \314\376\177\000\000\000e|\261=\177\000\000 \313 \314\376\177\000\000\063\225{\000\000\000\000\000\027\000\000\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\200\000\000\000\000\000\217e|\261=\177\000\000`~x\000\000\000\000\000\230\304\022\261=\177\000"* * nrprocs = 4* * woneinit = 1* * __FUNCTION__ = "main_loop"* *#10 0x000000000042c4e9 in main (argc=11, argv=0x7ffecc20cc08) at main.c:2675* * cfg_stream = 0x2893010* * c = -1* * r = 0* * tmp = 0x7ffecc20e6fd ""* * tmp_len = 0* * port = 0* * proto = 2496* * options = 0x7697a0 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"* * ret = -1* * seed = 173321635* * rfd = 4* * debug_save = 0* * debug_flag = 0* * dont_fork_cnt = 0* * n_lst = 0x7ffecc20cac0* * p = 0x7f3db177497d <intel_check_word+173> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \316>* * st = {st_dev = 19, st_ino = 21919, st_nlink = 2, st_mode = 16832, st_uid = 993, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1551179759, tv_nsec = 561093463}, st_mtim = {tv_sec = 1551179759,* *---Type <return> to continue, or q <return> to quit---* * tv_nsec = 561093463}, st_ctim = {tv_sec = 1551179759, tv_nsec = 561093463}, __unused = {0, 0, 0}}* * __FUNCTION__ = "main"* *(gdb)* NDB_MONGODB configuration is pretty simples and currently i'm not making any mongodb operations, i'm just loading the module and trying to connect against mongodb. Any thoughts on this issue? Thank you Best regards -- Cumprimentos José Seabra [View Less]

2 1

rtpengine_offer() with ICE not updating o= and m= IP addresses
by David Dean 22 Apr '19

22 Apr '19

I'm using the following rtpengine_offer() to force the use of ICE relay and also replace o= and m= rtpengine_offer("replace-origin replace-session-connection ICE=force-relay RTP"); The SDP is being updated to include an ICE relay candidate, but the IP addresses in the o= and m= lines are not changing to the servers IP address (X.X.X.X). I also tried using the media-address parameter but that didn't change the behaviour. When I use rtpengine_answer() then it's not … [View More]providing an ICE candidate nor changing o= or m=, which I imagine is expected. What am I missing? INVITE from the client (before rtpengine)------------------------------------------------------ INVITE sip:server.domain.com SIP/2.0Via: SIP/2.0/TCP 154.20.1.8:37520;branch=z9hG4bK-1710993570;rportFrom: <sip:username@server.domain.com>;tag=281751229To: <sip:server.domain.com>Contact: <sip:username@154.20.1.8:37520;transport=tcp>Call-ID: c715a8f9-4dd1-38d8-acbd-54153310f59fCSeq: 1756522847 INVITEContent-Type: multipart/mixed;boundary=7efec5a8-3311-0157-fc8b-9af106265507Content-Length: 1506Max-Forwards: 70Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFERPrivacy: noneSupported: 100rel --7efec5a8-3311-0157-fc8b-9af106265507Content-Type: application/sdp v=0o=organization 1983 678901 IN IP4 154.20.1.8s=-c=IN IP4 154.20.1.8t=0 0a=tcap:1 RTP/AVPFm=audio 15418 RTP/AVP 114 115 0 101i=speecha=ptime:20a=minptime:1a=maxptime:255a=silenceSupp:off - - - -a=rtpmap:114 AMR-WB/16000/1a=imageattr:114 octet-align=0a=fmtp:114 octet-align=0a=rtpmap:115 AMR-WB/16000/1a=imageattr:115 octet-align=1a=fmtp:115 octet-align=1a=rtpmap:0 PCMU/8000/1a=rtpmap:101 telephone-event/8000/1a=fmtp:101 0-16a=pcfg:1 t=1a=sendrecva=rtcp-muxa=ssrc:2047236273 cname:e6dcab7948b70d52cd51b75e505c49eba=ssrc:2047236273 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2a=ssrc:2047236273 label:organization@audio INVITE from the server (after rtpengine)------------------------------------------------------ SIP/2.0 200 OKVia: SIP/2.0/TCP 154.20.1.8:37520;branch=z9hG4bK-1710993570;rport=37520;received=2.221.73.230From: <sip:username@server.domain.com>;tag=281751229To: <sip:server.domain.com>;tag=0ea7681ffd64b0ffcde1bff3393fd505.ae3aCall-ID: c715a8f9-4dd1-38d8-acbd-54153310f59fCSeq: 1756522847 INVITEContact: <sip:X.X.X.X:443;transport=tcp>Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFERPrivacy: noneContent-Type: multipart/mixed;boundary=7efec5a8-3311-0157-fc8b-9af106265507Server: kamailio (5.2.2 (x86_64/linux))Content-Length: 1965 --7efec5a8-3311-0157-fc8b-9af106265507Content-Type: application/sdp v=0o=organization 1983 678901 IN IP4 154.20.1.8s=-c=IN IP4 154.20.1.8t=0 0a=tcap:1 RTP/AVPFm=audio 15418 RTP/AVP 114 115 0 101i=speecha=minptime:1a=maxptime:255a=silenceSupp:off - - - -a=imageattr:114 octet-align=0a=imageattr:115 octet-align=1a=pcfg:1 t=1a=rtcp-muxa=ssrc:2047236273 cname:e6dcab7948b70d52cd51b75e505c49eba=ssrc:2047236273 mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2a=ssrc:2047236273 label:organization@audioa=rtpmap:114 AMR-WB/16000/1a=rtpmap:115 AMR-WB/16000/1a=rtpmap:0 PCMU/8000/1a=rtpmap:101 telephone-event/8000/1a=fmtp:114 octet-align=0a=fmtp:115 octet-align=1a=fmtp:101 0-16a=sendrecva=ptime:20a=ice-ufrag:kzgbFAnua=ice-pwd:hnEu9EwTrdIZnTWhYbxtmdugvra=candidate:dzkwmPcB28NPHfRA 1 UDP 16777215 X.X.X.X 30366 typ relay raddr X.X.X.X rport 30366a=candidate:dzkwmPcB28NPHfRA 2 UDP 16777214 X.X.X.X 30367 typ relay raddr X.X.X.X rport 30367a=sendrecva=ice-ufrag:uDE9wbvYa=ice-pwd:dx4CcIjqUNFfnRPJEF8GjatXdU [View Less]

3 3

Config to control TCP connection reuse
by R, Rajkumar (Raj) 22 Apr '19

22 Apr '19

Hi, In my setup(kamailio in stateless mode to a backend server), for any number of client registrations kamailio (in stateless mode) is reusing the TCP connection. Let's say if I register 3 different clients through kamailio to my backend server - see only one TCP connection is used, which I do not want. I have gone through the core modules to see if any TCP config param exists to control on this, but couldn't find one. Could anyone help how to achieve different TCP connections to same … [View More]

1 0

Best tutorial for beginners kamailio
by Gaurav Bmotra 22 Apr '19

22 Apr '19

Hi Plz sujjest best kamailio tutorial or any source where a beginner can start kamailio.. Thanks

2 1

push to talk over cellular application server and related media server implementation
by Thierry Luo 21 Apr '19

21 Apr '19

Hi All, I don't know if this is the appropriate place to ask the following questions: 1. Anyone please recommend open-source implementation of PoC (Push-to-talk Over Cellular) application server? Kamailio can do this? 2. Anyone please recommend open-source implementation of PoC related media server/replicator? Thierry Luo

3 2

Re: [SR-Users] authentication using auth_db
by arish haque 21 Apr '19

21 Apr '19

Hi David, This can solve the issue but depth(records) of that view would be too much. The architecture is like this: One kamailio fronting multiple asterisk. Each of asterisk boxes have their Specific users databases. Thus, I'm trying to create db connections inside request route or completely write my own authentication service if I get the user's Password. So, that would be great if I would be able to pass the db_url to auth_db module in request route. Let me know what you think. Thanks, Arish

2 1

Re: [SR-Users] authentication using auth_db
by arish haque 20 Apr '19

20 Apr '19

Hi David, Thanks for the reply. I checked out sqlops module, this will solve the problem only when I get the authentication password (secret) of the user inside request route. For this I tried checking kamailio pseudovars but haven't found one. Therefore, I am sticking with auth_db module.If this is possible by any other way do let me know. thanks, Arish

2 1

Kamailio, TLS, and LetsEncrypt
by Gaurav Bmotra 19 Apr '19

19 Apr '19

HI this is Gaurav im using kamailio 5.1.2 on ubuntu 18.4 i am trying to configure LetsEncrypt (tls) for kamailio sing following link https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/ but unable to start kamailio ,i m getting these error ------->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Apr 19 11:23:57 ubuntufresh systemd[1]: Starting Kamailio (OpenSER) - the Open … [View More]

3 5

auth by IP
by Yu Boot 19 Apr '19

19 Apr '19

Following code snippet from default kamailio.cfg never gives 403 if you smart enough to set "fromdomain" parameter on Asterisk to Kamailio's IP. How to fix it? I want password-based registration (which is OK now) and permit calls via Kamailio only from permitted IPs. # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here &… [View More]

2 4

← Newer
1
2
3
4
5
6
7
...
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users April 2019