sure, here it is:
```
# gdb /usr/sbin/kamailio /core.16234
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio.pid -m 1024 -M
64 -u root -g root'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f5a82f68985 in mem_insert_ucontact (_r=0x7f5a409ec948,
_c=0x7ffcc26f3
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165248337___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Can you attach the backtrace (just 'bt', not 'bt full' for the moment) from gdb
here? Replace any IP/sensitive info there, but I would like to see the
backtrace here to correlate easier with the logs above.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamail
when subs_mode <> 3 the notify version is always the same (first watcher) for
all watchers
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/448
-- Commit Summary --
* presence : fix notify version when subs_node <> 3
-- File Changes
Thanks Fred -- it is now in place.
Cheers,
Daniel
On 16/12/15 21:37, Fred Posner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/16/2015 04:41 AM, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> Therefore, as of today, Kamailio project is officially
>> using the new logo -- see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/16/2015 04:41 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
> Therefore, as of today, Kamailio project is officially
> using the new logo -- see it at:
>
> - http://www.kamailio.org/w/2015/12/new-logo-for-kamailio-project/
>
Attached is an
To make IPV6 work with Solaris, add_interfaces() had to be modified.
I decided to reimplement it with a getifaddrs() based implementation,
which is available from Solaris 11 upwards, and also on FreeBSD and
Linux. By default, the latter continues to use the netlink based
variant.
You can view, comm
ยดยดยด
# - request routing logic ---
request_route {
xlog("L_INFO", "--> Incoming request: $rm from $si to $ru \n$mb\n");
# Always try to fix contact alias if needed
if(!set_contact_alias()) {
sl_send_reply("400", "Contact alias failed");
If you have a simple config, can you paste it here, at least the request_route
and any branch_route used for this case (also onsend_route if in config).
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/445#issuecomment-165116170___
Main request route.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/445#issuecomment-165115209___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-d
Backported this to 4.X for the part of the feature each branch had.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165114967___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://li
Module: kamailio
Branch: 4.1
Commit: 655ee6eb1698aef2f788a271d68a663bde73
URL:
https://github.com/kamailio/kamailio/commit/655ee6eb1698aef2f788a271d68a663bde73
Author: smititelu
Committer: Stefan Mititelu
Date: 2015-12-16T16:01:36+02:00
debugger: Fix coredump when kamailio stopped
Upo
I couldn't track any change on the code used by set_contact_alias(). Are you
using the function in main request_route or a branch_route/etc.?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/445#issuecomment-165112975__
Module: kamailio
Branch: 4.2
Commit: 43d01aab8b0dd4d6bdfa25e22a399ed81b468db1
URL:
https://github.com/kamailio/kamailio/commit/43d01aab8b0dd4d6bdfa25e22a399ed81b468db1
Author: smititelu
Committer: Stefan Mititelu
Date: 2015-12-16T15:58:11+02:00
debugger: Fix coredump when kamailio stopped
Upo
Module: kamailio
Branch: 4.3
Commit: a562275acacb2bd98b075f3132ddbce8de456f41
URL:
https://github.com/kamailio/kamailio/commit/a562275acacb2bd98b075f3132ddbce8de456f41
Author: smititelu
Committer: Stefan Mititelu
Date: 2015-12-16T15:53:26+02:00
debugger: Fix coredump when kamailio stopped
Upo
On 16/12/15 09:55, yasir ay wrote:
> Hi,
>
> Dec 16 14:22:51 localhost.localdomain systemd[1]: Starting LSB:
> Kamailio (OpenSER) - the Open Source SIP Server...
> Dec 16 14:22:51 localhost.localdomain kamailio[30289]: Kamailio not
> yet configured. Edit /etc/default/kamailio first.
the last part
I think this needs to be backported at least to 4.3. Not sure if 4.2 has the
feature.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165108366___
sr-dev mailing list
sr-dev@lists.sip-r
Thank you also for the nice description of the problem :D
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165081474___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-ro
Closed #446.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#event-493374075___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello smititelu,
```
version: kamailio 4.4.0-dev7 (i386/linux) 645838-dirty
flags: STATS: Off, EXTRA_DEBUG, 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
Managed to reproduce and fix the issue. Can you try again with the latest
upstream master?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165078780___
sr-dev mailing list
sr-dev@lists.
Module: kamailio
Branch: master
Commit: 64583809c677384e2fcd54a5ba7f921b3ea59c51
URL:
https://github.com/kamailio/kamailio/commit/64583809c677384e2fcd54a5ba7f921b3ea59c51
Author: smititelu
Committer: smititelu
Date: 2015-12-16T13:28:43+02:00
debugger: Fix coredump when kamailio stopped
Upon k
I send in a contact that is a 10.10.x.x address - clearly not the same as $si
that is in 192.168.40.x (also tested on public IP for server) - and both
functions return true, indicating no failure. The outbound message keeps the
same contact as the inbound message.
If I run msg_apply_changes() t
Yes I forgot to mention those, they were in my shared configuration
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165052305___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://li
do you also have:
```
modparam("debugger", "mod_hash_size", 2(or any size))
modparam("debugger", "mod_level_mode", 1)
```
?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446#issuecomment-165050790___
s
Hello,
based on the feedback after the proposal, there were no voices against
the new logo. Therefore, as of today, Kamailio project is officially
using the new logo -- see it at:
- http://www.kamailio.org/w/2015/12/new-logo-for-kamailio-project/
If you display one of the old Kamailio logos, w
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/446___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi,
Dec 16 14:22:51 localhost.localdomain systemd[1]: Starting LSB: Kamailio
(OpenSER) - the Open Source SIP Server...
Dec 16 14:22:51 localhost.localdomain kamailio[30289]: Kamailio not yet
configured. Edit /etc/default/kamailio first.
Dec 16 14:22:51 localhost.localdomain systemd[1]: PID file
/v
Agreed
On 16 Dec 2015 10:36 AM, "Carsten Bock" wrote:
> Hi,
>
> I agree, if the dialog_ng module is only used with IMS deployments, it
> may be confusing that it's called dialog_ng (despite the original
> ideas/thoughts, Richard mentioned).
> I have no objections renaming it to ims_dialog; if we
Hi,
I agree, if the dialog_ng module is only used with IMS deployments, it
may be confusing that it's called dialog_ng (despite the original
ideas/thoughts, Richard mentioned).
I have no objections renaming it to ims_dialog; if we manage to merge
it at some point with the existing dialog-module an
actually looking at the log for the mesages around 15:23 on Dec 13, it looks
like it crashed and restarted at that time too, those dmq messages appear to be
just after the restart, when, I presume, dmq is replacting the contacts upon
the restart, full log at that time is as follows:
```
Dec 13
no, not around that time, but an entire log search for that pid results in the
following:
the log file date starts from 30th June, so I presume it would have caught
anything if it was logged.
```
# fgrep '\[16234\]' kamailio.log
# fgrep '16234' kamailio.log
Dec 13 15:23:08 /usr/sbin/kamail
To be more specific now: any log messages before the crash from the process
with pid 16234 ?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/440#issuecomment-165028337___
sr-dev mailing list
sr-dev@list
i did not change the source code. if changes done i will post. i am using
ims_charging module.will it work in dialog module.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/444#issuecomment-165027385___
34 matches
Mail list logo
