<!-- Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment). -->
I am getting following error when ts_store() is called
Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25676]: {1 2 INVITE 2d24732c962aa49859622eb9d214a115@192.168.2.7} DEBUG: tsilo [ts_store.c:80]: ts_store(): storing transaction 5967:208972607 for r-uri: Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/tcp_main.c:3279]: handle_tcp_child(): dead tcp child 2 (pid 25676, no 19) (shutting down?) Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6cf40, 37, -1, 0x0) fd_no=37 called Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34 Dec 21 12:50:57 ejabberd /usr/local/kamailio-5.1/sbin/kamailio[25696]: DEBUG: <core> [core/tcp_main.c:3512]: handle_ser_child(): dead child 19, pid 25676 (shutting down?)
<!-- Explain what you did, what you expected to happen, and what actually happened. -->
``` if (lookup("location")) { xlog("L_INFO","PUSHASYNC: for new transaction [$T(id_index):$T(id_label)] $fU => $rU \n"); if(t_newtran()) { xlog("L_INFO","PUSHASYNC: storing transaction [$T(id_index):$T(id_label)] fU=[$fU] => rU=[$rU] ru=[$ru] \n"); ts_store(); xlog("L_INFO","PUSHASYNC: stored transaction [$T(id_index):$T(id_label)] [$fU] => [$rU]\n"); } $sht(vtp=>stored::$rU) = 1; return; } ``` ### Troubleshooting
#### Reproduction
<!-- If the issue can be reproduced, describe how it can be done. -->
#### Debugging Data
<!-- If you got a core dump, use gdb to extract troubleshooting data - full backtrace, local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile bt full info locals list
If you are familiar with gdb, feel free to attach more of what you consider to be relevant. -->
``` (paste your debugging data here) ```
#### Log Messages
<!-- Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` (paste your log messages here) ```
#### SIP Traffic
<!-- If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` (paste your sip traffic here) ```
### Possible Solutions
<!-- If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix. -->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
``` (paste your output here) ```
* **Operating System**:
<!-- Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...; Kernel details (output of `uname -a`) -->
``` (paste your output here) ```
Did you get a core dump? If yes, paste here the backtrace taken with gdb.
I was able to see this from core
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/kamailio-5.1/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /usr'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f43f5c63428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0 0x00007f43f5c63428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 resultvar = 0 pid = 3131 selftid = 3131 #1 0x00007f43f5c6502a in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x7f43ebe3b3c0, sa_sigaction = 0x7f43ebe3b3c0}, sa_mask = { __val = {8229927, 133143986226, 47244640269, 506806140935, 953482739718, 140728898420736, 0, 44373472, 139929697103872, 17184162608, 4303193040, 139929863774160, 140730082576896, 8087364, 0, 2}}, sa_flags = -263151403, sa_restorer = 0x0} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007f43f050a0f3 in locking_f (mode=9, n=1, file=0x7f43f000be5b "err.c", line=375) at tls_locking.c:106 __func__ = "locking_f" #3 0x00007f43eff5784f in ERR_load_ERR_strings () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 No symbol table info available. #4 0x0000000300678ee3 in ?? () No symbol table info available. #5 0x00000000007789f0 in ?? () No symbol table info available. #6 0x00000000323e406d in ?? () No symbol table info available. #7 0x0000000000418330 in ?? () No symbol table info available. #8 0x00007ffe4694cde0 in ?? () No symbol table info available. #9 0x0000000000000000 in ?? () No symbol table info available.
@ForGuru can you please try that fix
@linuxmaniac Thanks for ur reply. After us suggested fix, crash is gone. but I see this in logs
ERROR: tsilo [ts_store.c:75]: ts_store(): malformed aor from uri[sip:192.168.8.100:5090;transport=TCP;registering_acc=example.com]
What is the mistake on my side
``` ts_store(); $sht(vtp=>stored::$rU) = 1; ```
I'm not the author of the module, so @grumvalski can explain in a better way. But looking into the code, the problem here is that the r-ruri has no user part, you are not passing a uri value so module is trying to get it from r-uri.
Hi, thanks Victor for pointing that out (and for the patch). You are right, the problem there is that the r-uri does not contain a user part, and TSILO right now expect the aor to be in the form sip:user@domain, also because otherwise it wouldn't be able to match stored transactions to AOR used for registering. Is the INVITE coming this way or is being modified in the script? You could try to use the To uri ($tu) to store the transaction if it contains the user part.
Best regards,
Federico
On Thu, Jan 10, 2019 at 7:54 AM Victor Seva notifications@github.com wrote:
I'm not the author of the module, so @grumvalski https://github.com/grumvalski can explain in a better way. But looking into the code, the problem here is that the r-ruri has no user part, you are not passing a uri value so module is trying to get it from r-uri.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kamailio/kamailio/issues/1775#issuecomment-452990105, or mute the thread https://github.com/notifications/unsubscribe-auth/ADip4y2BlgmC8Fr8tZri87z_1Dws9T2Dks5vBuOugaJpZM4Zd8uy .
Closed #1775 via #1802.
@grumvalski and @miconda Thanks for your support I have been able to get it working with this
``` $avp(ruri) = "sip:" + $tU + "@" + $td; ts_store($avp(ruri)); ```