sr-dev November 2019

sr-dev@lists.kamailio.org

22 participants
380 discussions

[kamailio/kamailio] ims_ipsec_pcscf: fixed warnings, added a new config param (#2148)

by alexyosifov

- fixed a defect reported from Coverity Scan - Concurrent data access violations in spi_gen.c for spi_data->spi_val. - added a new conf param - ipsec_reuse_server_port - reuse or not PCSCF server port for UA Re-registration. - added description for the new parameter in ims_ipsec_pcscf_admin.xml. - in fill_contact() for Request messages set received host, port and proto fro request uri if alias is presented. - A new server port is used for Re-registration, depending on the new parameter ipsec_reuse_server_port. - in create_ipsec_tunnel() return -1 when unable to convert ip address. - in ipsec_forward() add supported and require secagree headers only for Register reply with code 200. Set SND_F_FORCE_SOCKET for request messages.   #### 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  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2148 -- Commit Summary -- * ims_ipsec_pcscf: fixed warnings, added a new config param -- File Changes -- M src/modules/ims_ipsec_pcscf/cmd.c (209) M src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml (22) M src/modules/ims_ipsec_pcscf/ims_ipsec_pcscf_mod.c (2) M src/modules/ims_ipsec_pcscf/spi_gen.c (14) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2148.patch https://github.com/kamailio/kamailio/pull/2148.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/2148

4 years, 10 months

[kamailio/kamailio] avpops: avp_subst() support pvar as subst parameter (#2158)

by Victor Seva

4 years, 11 months

[kamailio/kamailio] centos7 rpm for evapi (#2098)

by sergey-safarov

Please package evapi into centos7 rpm. -- 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/2098

4 years, 11 months

[kamailio/kamailio] Kamailio not using SNI in for incoming requests (#1938)

by Laszlo

I'm using Kamailio 5.2.2+xenial. Set up a basic tls.cfg like this: ``` [server:default] verify_certificate = no require_certificate = no private_key = /tmp/default.key certificate = /tmp/default.pem [server:any] method = TLSv1 verify_certificate = no require_certificate = no private_key = /tmp/domain.key certificate = /tmp/domain.pem server_name = sip.domain.com server_name_mode = 1 ``` Connect with openssl like this `openssl s_client -connect server:5061` and Kamailio will - obviously - offer the default.pem certificate. However, use `openssl s_client -connect server:5061 -servername sip.domain.com` and Kamailio will still offer the default.pem certificate, where I'd expect it to offer domain.pem. I tested these `openssl` commandline invocations against an nginx server that's working with these same certificates, and SNI is working properly there. >From the Kamailio logs on starting up, it does seem to detect that a SNI callback should be registered with OpenSSL. ``` Apr 25 11:43:37 kamailio[7447]: NOTICE: tls [tls_domain.c:1083]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='sip.domain.com' ... ``` However, it's not triggering: ``` Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 4.1.3.1 Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:999]: tcpconn_new(): on port 55428, type 3 Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:1305]: tcpconn_add(): hashes: 3726:2401:2691, 1 Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa86c60, 60, 2, 0x7f00ad8279b0), fd_no=51 Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa86c60, 60, -1, 0x0) fd_no=52 called Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 1 Apr 25 11:39:04 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:3875]: send2child(): selected tcp worker idx:0 proc:44 pid:7342 for activity on [tls:1.6.1.6:5061], 0x7f00ad8279b0 Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_read.c:1759]: handle_io(): received n=8 con=0x7f00ad8279b0, fd=10 Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:199]: tls_complete_init(): completing tls connection initialization Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:228]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7f00ad1b02e8 ctx 0x7f00ad406408 sn []) Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_domain.c:1155]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f00ad406408: (nil) Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_domain.c:737]: sr_ssl_ctx_info_callback(): SSL handshake started Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2460]: tcpconn_do_send(): sending... Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7f00ad8279b0 n=2817 fd=10 Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2495]: tcpconn_do_send(): buf=#012#026#003#001 Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xae0200, 10, 2, 0x7f00ad8279b0), fd_no=1 Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_domain.c:1155]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f00ad406408: (nil) Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_domain.c:749]: sr_ssl_ctx_info_callback(): SSL handshake done Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_domain.c:753]: sr_ssl_ctx_info_callback(): SSL disable renegotiation Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:424]: tls_accept(): TLS accept successful Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:431]: tls_accept(): tls_accept: new connection from 4.1.3.1:55428 using TLSv1/SSLv3 AES256-SHA 256 Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:434]: tls_accept(): tls_accept: local socket: 1.6.1.6:5061 Apr 25 11:39:04 kamailio[7342]: DEBUG: tls [tls_server.c:445]: tls_accept(): tls_accept: client did not present a certificate Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2460]: tcpconn_do_send(): sending... Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7f00ad8279b0 n=266 fd=10 Apr 25 11:39:04 kamailio[7342]: DEBUG: <core> [core/tcp_main.c:2495]: tcpconn_do_send(): buf=#012#026#003#001 Apr 25 11:39:10 kamailio[7342]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xae0200, 10, -1, 0x10) fd_no=2 called Apr 25 11:39:10 kamailio[7342]: DEBUG: <core> [core/tcp_read.c:1680]: release_tcpconn(): releasing con 0x7f00ad8279b0, state 1, fd=10, id=1 ([4.1.3.1]:55428 -> [4.1.3.1]:5061) Apr 25 11:39:10 kamailio[7342]: DEBUG: <core> [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7f00ad7c4ab8 Apr 25 11:39:10 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:3307]: handle_tcp_child(): reader response= 7f00ad8279b0, 1 from 0 Apr 25 11:39:10 kamailio[7344]: DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa86c60, 60, 2, 0x7f00ad8279b0), fd_no=51 Apr 25 11:39:10 kamailio[7344]: DEBUG: <core> [core/tcp_main.c:3434]: handle_tcp_child(): CONN_RELEASE 0x7f00ad8279b0 refcnt= 1 ``` Looking at other issues like #1574, I think I'm supposed to see a `tls_server_name_cb` log line upon connecting, but there is none. -- 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/1938

4 years, 11 months

[kamailio/kamailio] dispatcher ds_probing_mode inconsistent behaviour (#2100)

by Henning Westerholt

I observed inconsistent behaviour in the dispatcher module. In some modes either the code needs to be fixed or the documentation adapted. As it is a widely used module, some feedback about this would be appreciated. 1) ds_probing_mode 0 This mode don't work together with a ds_inactive_threshold > 1 and gateway set to "IP". It will set a gateway to IX after the first successful ping. Therefore gateways will not be activated automatically. In mode "TP" it works and sets the gateway to "AX". My suggestion would be to fix this in the code, that it behaves as mode 1 and 3: count to the ds_inactive_threshold and then set to "AX". 2) ds_probing_mode 2 According to the docs this should like this: “only gateways in inactive state with probing mode set are tested”. I understood it that it means gateways with mode "IP". But according to my tests it also probes gateways in "TP" or "AP" probing state and changes this both to AX. Either the documentation or the module behaviour should be fixed. The same issue mentioned above (ds_probing_mode 0 together with ds_inactive_threshold > 1) is also present. I also would suggest to fix it in the code here as well. root@sip:/etc/kamailio# kamcmd core.version kamailio 5.4.0-dev1 (x86_64/linux) 8ee711 -- 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/2100

4 years, 11 months

[kamailio/kamailio] dialog: adding RPC dlg.kill_active_dlg command (#2111)

by jklingenmeyer

- only handles active dialogs in state 4 - wipes out a given dialog callously - no subcalls to dialog-ending functions - dialog is then removed by the recurring cleaning function execution - as discussed in sr-users in topic "[Dialog] Removing entries from dialog memory" #### 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 Hi, As discussed in the sr-users mailing-list, I am proposing this PR to add a very simple new rpc command to the dialog module. dlg.kill_active_dialog kills any given active dialog from memory. A paragraph in the dialog documentation precises the dangerous nature of this command, to be used with caution. Please feel free to discuss about it. Thanks! Julien You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2111 -- Commit Summary -- * dialog: adding RPC dlg.kill_active_dlg command -- File Changes -- M src/modules/dialog/dialog.c (56) M src/modules/dialog/doc/dialog.xml (5) M src/modules/dialog/doc/dialog_admin.xml (33) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2111.patch https://github.com/kamailio/kamailio/pull/2111.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/2111

4 years, 11 months

[kamailio/kamailio] keepalive : added new function del_destination and added .cfg functions (#2133)

by Yasin CANER

#### 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 - [ ] 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 added new function del_destination that deletes sip address from list added add_destination module functions for kamailio.cfg added counter parameter for attempt count. after count pass, module dont try until it adds again. added kemi interfaces both of them added lock to stack added find_destination function You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2133 -- Commit Summary -- * keepalive : added new function del_destination and added .cfg functions -- File Changes -- M src/modules/keepalive/api.h (4) M src/modules/keepalive/keepalive.h (10) M src/modules/keepalive/keepalive_api.c (117) M src/modules/keepalive/keepalive_core.c (14) M src/modules/keepalive/keepalive_mod.c (93) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2133.patch https://github.com/kamailio/kamailio/pull/2133.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/2133

4 years, 11 months

[kamailio/kamailio] pv_headers: Initial commit (#2156)

by Victor Seva

#### 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) - [ ] 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) - [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 #### Description The main goal of the module is to offload the intermediate header processing into the XAVP dynamic container as well as provide with high level methods and pseudovariables to simplify SIP message header modifications. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2156 -- Commit Summary -- * pv_headers: Initial commit -- File Changes -- A src/modules/pv_headers/Makefile (12) A src/modules/pv_headers/README (332) A src/modules/pv_headers/doc/Makefile (4) A src/modules/pv_headers/doc/functions.xml (131) A src/modules/pv_headers/doc/params.xml (186) A src/modules/pv_headers/doc/pv_headers.xml (39) A src/modules/pv_headers/doc/pv_headers_admin.xml (116) A src/modules/pv_headers/pv_headers.c (351) A src/modules/pv_headers/pv_headers.h (51) A src/modules/pv_headers/pvh_func.c (388) A src/modules/pv_headers/pvh_func.h (38) A src/modules/pv_headers/pvh_hash.c (132) A src/modules/pv_headers/pvh_hash.h (39) A src/modules/pv_headers/pvh_hdr.c (235) A src/modules/pv_headers/pvh_hdr.h (39) A src/modules/pv_headers/pvh_str.c (144) A src/modules/pv_headers/pvh_str.h (38) A src/modules/pv_headers/pvh_xavp.c (1050) A src/modules/pv_headers/pvh_xavp.h (64) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2156.patch https://github.com/kamailio/kamailio/pull/2156.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/2156

4 years, 11 months

[kamailio/kamailio] cfgt: RPC command to reset/clean test scenario (#574)

by Victor Seva

allow to clean the shared and private info of a test scenario in order to be able to re-trigger it without restart 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/574

4 years, 12 months

[kamailio/kamailio] Crash in permissions module (#2151)

by sjthomason

### Description Crash in permissions module when `load_backends` set to 1 ``` modparam("permissions", "db_url", DBURL) modparam("permissions", "db_mode", 0) modparam("permissions", "address_table", "gw_auth_ip") modparam("permissions", "trusted_table", "user_auth_ip") modparam("permissions", "load_backends", 1) ``` ### Troubleshooting #### Reproduction To avoid Kamailio complaining about an old version table during an upgrade, I attempted to disable the "trusted" backend as we're not using it. Kamailio seg faults on startup. This is on 5.1.8 but I didn't see much difference in permissions with master #### Debugging Data ``` (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0xffffffff3ee2991c in init_child_trusted (rank=rank@entry=-2) at trusted.c:267 __func__ = "init_child_trusted" #2 0xffffffff3ee2d1d0 in child_init (rank=<optimized out>) at permissions.c:651 No locals. #3 0x000000010014a230 in init_mod_child (m=0x1007affd8, rank=rank@entry=-2) at core/sr_module.c:943 __func__ = "init_mod_child" #4 0x000000010014a0ec in init_mod_child (m=0x1007b0658, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #5 0x000000010014a0ec in init_mod_child (m=0x1007b0d80, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #6 0x000000010014a0ec in init_mod_child (m=0x1007b1a88, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #7 0x000000010014a0ec in init_mod_child (m=0x1007b1ea0, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #8 0x000000010014a0ec in init_mod_child (m=0x1007b22b8, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #9 0x000000010014a0ec in init_mod_child (m=0x1007b29c0, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #10 0x000000010014a0ec in init_mod_child (m=0x1007b33d8, rank=rank@entry=-2) at core/sr_module.c:939 __func__ = "init_mod_child" #11 0x00000001001565d0 in init_child (rank=rank@entry=-2) at core/sr_module.c:970 No locals. #12 0x000000010018cbf4 in fork_process (child_id=child_id@entry=-2, desc=<optimized out>, make_sock=make_sock@entry=1) at core/pt.c:338 pid = <optimized out> child_process_no = <optimized out> ret = -1 new_seed1 = <optimized out> new_seed2 = <optimized out> sockfd = {6, 13} __func__ = "fork_process" #13 0xffffffff3f211cd4 in mod_child (rank=<optimized out>) at ctl.c:327 pid = <optimized out> cs = <optimized out> rank = 0 rpc_handler = 1 rpc_handler = 1 #14 0x000000010014a230 in init_mod_child (m=0x1007af178, rank=rank@entry=0) at core/sr_module.c:943 __func__ = "init_mod_child" #15 0x000000010014a0ec in init_mod_child (m=0x1007af800, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #16 0x000000010014a0ec in init_mod_child (m=0x1007affd8, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #17 0x000000010014a0ec in init_mod_child (m=0x1007b0658, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #18 0x000000010014a0ec in init_mod_child (m=0x1007b0d80, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #19 0x000000010014a0ec in init_mod_child (m=0x1007b1a88, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #20 0x000000010014a0ec in init_mod_child (m=0x1007b1ea0, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #21 0x000000010014a0ec in init_mod_child (m=0x1007b22b8, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #22 0x000000010014a0ec in init_mod_child (m=0x1007b29c0, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #23 0x000000010014a0ec in init_mod_child (m=0x1007b33d8, rank=rank@entry=0) at core/sr_module.c:939 __func__ = "init_mod_child" #24 0x00000001001565d0 in init_child (rank=rank@entry=0) at core/sr_module.c:970 No locals. #25 0x00000001000c4c44 in main_loop () at main.c:1419 i = <optimized out> pid = <optimized out> si = <optimized out> si_desc = "\000\000\000\001\000h\200\000\000\000\000\000\000\000\000\330\000\000\000\001\000o6H\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000n\000\000\000\000\000\000\000\t\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\004\377\377\377\377\177\377\357\241\000\000\000\001\000\f\345\004", '\000' <repeats 11 times>, "\001\000\003\277\320\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" nrprocs = <optimized out> woneinit = <optimized out> __func__ = "main_loop" #26 0x00000001000ce704 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2663 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffffff7ffffbb5 "" tmp_len = 0 port = 0 proto = 0 options = 0x10003ee20 ":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 = 1842495819 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> p = <optimized out> st = {st_dev = 70325794504717, st_ino = 205858632, st_mode = 16872, st_nlink = 2, st_uid = 1, st_gid = 12, st_rdev = 18446744073709551615, st_size = 334, st_atim = {tv_sec = 1574807105, tv_nsec = 898072627}, st_mtim = {tv_sec = 1574810139, tv_nsec = 861570968}, st_ctim = {tv_sec = 1574810139, tv_nsec = 861570968}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __func__ = "main" (gdb) info locals cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffffff7ffffbb5 "" tmp_len = 0 port = 0 proto = 0 options = 0x10003ee20 ":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 = 1842495819 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> p = <optimized out> st = {st_dev = 70325794504717, st_ino = 205858632, st_mode = 16872, st_nlink = 2, st_uid = 1, st_gid = 12, st_rdev = 18446744073709551615, st_size = 334, st_atim = {tv_sec = 1574807105, tv_nsec = 898072627}, st_mtim = {tv_sec = 1574810139, tv_nsec = 861570968}, st_ctim = {tv_sec = 1574810139, tv_nsec = 861570968}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __func__ = "main" ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ```kamailio -v version: kamailio 5.1.8 (sparc64/solaris) 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, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, select, /dev/poll. id: unknown compiled with gcc 7.3.0``` * **Operating System**: Solaris 11.4 -- 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/2151

4 years, 12 months

← Newer
1
...
10
11
12
13
14
15
16
...
38
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2019