Hi,
I have found a behaviour in the registrar module that I do have a question
about. Is the current behaviour correct and wanted?
Using the save() method in the script I see the following:
* Processing a register request for a user gives return code 1 ( or 2 )
* Processing a
Hi @tdimitrov @ngvoice
Do you have any updated example script files (.cfg) and perhaps a sql table
definition?
I have several errors with the current example script file. Even if fixing the
small errors, I am unsure if it will work out of the box for concatenated SMS?
Best Regards
Lars
--
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
Ok, great. Will try create a patch during the evening.
--
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/1579#issuecomment-414682202___
@linuxmaniac , Something like this?
(gdb) print *_r
$3 = {domain = 0x7fe96dea0dd8, aor = {s = 0x7fe96deb24d8
"\320\063\r\301\376\177", len = 6}, aorhash = 2857371829, contacts = 0x0, slot
= 0x0, prev = 0x0,
next = 0x0}
(gdb) print _r->slot
$4 = (struct hslot *) 0x0
(gdb) print *_r->slot
`Core was generated by `/usr/local/sbin/kamailio -f /root/kamailio-test.cfg'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fe975560399 in release_urecord (_r=0x7fe96deb2430) at urecord.c:555
555 mem_delete_urecord(_r->slot->d, _r);
(gdb) bt full
#0
Issue seen from beginning when using module together with Kamailio IMS.
SIPp scenario tries to simulate register/unregister as seen in IMS network.
launched with:
sipp -sf notify.xml -inf register.csv 192.168.55.20 -r 1 -m 1
-default_behaviors none
[notify.patch.txt](https://github.com/kamailio/kamailio/files/2155657/notify.patch.txt)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
### Description
While testing to implement an IMS AS, I used the PUA_REGINFO module to receive
details about the SIP registration. PUA_REGINFO module uses PUA and USRLOC
modules.
However, a couple of issues was found including a crash:
1) Crash when processing SIP Notify with registration
