I also know little of BSD, but this is what was required on Linux to get a dump
into /tmp:
phil@ua-proxy-01:/etc/sysctl.d$ cat 61-core-pattern.conf
fs.suid_dumpable=2
kernel.core_uses_pid=1
kernel.core_pattern=/tmp/core.%e.%p.%h.%t
From: sr-dev [mailto:sr-dev-boun...@lists.sip-router.org] On
I also know little of BSD, but this is what was required on Linux to get a dump
into /tmp:
```phil@ua-proxy-01:/etc/sysctl.d$ cat 61-core-pattern.conf
fs.suid_dumpable=2
kernel.core_uses_pid=1
kernel.core_pattern=/tmp/core.%e.%p.%h.%t```
--
You are receiving this because you commented.
Reply
If it helps, we use presence heavily and do not see this. However... we don't
use the database implementation because it's never worked properly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Module: kamailio
Branch: master
Commit: 4dbd83b95089719e199f49e799bb13f5a29f329a
URL:
https://github.com/kamailio/kamailio/commit/4dbd83b95089719e199f49e799bb13f5a29f329a
Author: Phil Lavin <phil.la...@cloudcall.com>
Committer: Phil Lavin <phil.la...@cloudcall.com>
Date: 2017-02-
Bug introduced in PR #979
`request` is a null pointer in the event that a dialog expires by means of
Kamailio's internal dialog expiry timer. Check it everywhere, just to be sure.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/993
--
Module: kamailio
Branch: master
Commit: 2a732273fb2fbec4ee5ebca60f2eb4ce84ea2b17
URL:
https://github.com/kamailio/kamailio/commit/2a732273fb2fbec4ee5ebca60f2eb4ce84ea2b17
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2017-02-
Module: kamailio
Branch: master
Commit: 9311025cf76a72853f55fc8c66d842084051c6d7
URL:
https://github.com/kamailio/kamailio/commit/9311025cf76a72853f55fc8c66d842084051c6d7
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2017-02-
- Added 2 new flags, disable_caller_publish_flag and disable_callee_publish_flag
- Wrapped each call to dialog_publish_multi to first check if the flag is set
This is actually quite a strange usecase. It's useful when calls do not route
internally on Kamailio but are always forced out through a
It's been running here for a while and it has had no side effects. That said,
it doesn't resolve any problems that we are facing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I'm not entirely clear what your issue is - can you explain further. As I see
it, changing from `strncpy` to `memcpy` only has benefit if the thing you're
copying has a \0 in the middle of it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
I'm thinking that you're going to lose the NUL byte here as presumably, if it
exists, it is not included in the length of the string
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
We know there are issues restarting Kamailio with presentity entries in place.
The old entries cause problems until they expire. We think we have narrowed
this down to the pua db_mode - we can't store PUA entries in the database
because that logic is broken in quite a few ways.
That said, I'll
This issue has been resolved by recent work on presence
--
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/21#issuecomment-252676156___
Module: kamailio
Branch: master
Commit: a361686b2c872cad6493804eb71b8b8e7e151a4f
URL:
https://github.com/kamailio/kamailio/commit/a361686b2c872cad6493804eb71b8b8e7e151a4f
Author: Phil Lavin <p...@lavin.me.uk>
Committer: Phil Lavin <p...@lavin.me.uk>
Date: 2016-09-19T21:27:25+01:00
Module: kamailio
Branch: master
Commit: 0c36c1b62efef176ae6e9322f14096e3a63ed348
URL:
https://github.com/kamailio/kamailio/commit/0c36c1b62efef176ae6e9322f14096e3a63ed348
Author: Phil Lavin <p...@lavin.me.uk>
Committer: Phil Lavin <p...@lavin.me.uk>
Date: 2016-09-19T21:27:54+01:00
p
DB result is not freed when the resultset has <= 0 rows
Needs backporting to 4.4 branch
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/788
-- Commit Summary --
* purple: Fix multiple memory leaks in DB code
* presence: Fix memory
Module: kamailio
Branch: master
Commit: 839cf89b02f8817156487a960ff62013e3cde530
URL:
https://github.com/kamailio/kamailio/commit/839cf89b02f8817156487a960ff62013e3cde530
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-07-27T15
Module: kamailio
Branch: master
Commit: 122e9b423d1c25bf34f6d7be995b992ca61c2fa3
URL:
https://github.com/kamailio/kamailio/commit/122e9b423d1c25bf34f6d7be995b992ca61c2fa3
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-07-22T10
Yes, all good here. #726 has been running good too.
--
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/724#issuecomment-239379162___
sr-dev
Hi Daniel, no problem at all. Whenever you can.
It's been running in production for a few days now, along with #726. We use BLF
extremely heavily and no further problems have been seen by customers.
That said, give it another week or so such that we can be sure the memory
footprint is
presentity: don't update terminated presentity entries in the database
- This fix is pull requested based on the stuff in pull request #724. That is
because the stuff done here builds on that earlier work. #724 probably wants to
be merged before this one.
- Fixes a race condition caused by,
@phil-lavin pushed 1 commit.
3b206c8 presence: log when presentity is deleted due to already existing
---
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/kamailio/kamailio/pull/724/files/3c09579d5e677ac7a27b2386545dc580697934b5
Found the leak with `valgrind`. Added as a second commit. Going to run in
production for a few days and see if memory stays stable.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@phil-lavin pushed 1 commit.
3c09579 presence: fix memory leak introduced by last commit
---
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/kamailio/kamailio/pull/724/files/122e9b423d1c25bf34f6d7be995b992ca61c2fa3
This may have a memory leak... Going to investigate more so hold off on merging
for now. If anyone can spot it, free beer may be on offer.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
- The presence implementation is a little dubious, to say the least.
It probably wants re-writing at some stage. However, this fixes a
race condition that could have a number of causes in which the PUA
is unaware of the eTag at the point it sends the PUBLISH.
The mechanism is such that the
Module: kamailio
Branch: master
Commit: aa4c37ab756b42f2aafc2b659d09bbe632f702a2
URL:
https://github.com/kamailio/kamailio/commit/aa4c37ab756b42f2aafc2b659d09bbe632f702a2
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-05-17T09
Module: kamailio
Branch: master
Commit: a5e89b42151ba3697835cff4a2a379422a9afc46
URL:
https://github.com/kamailio/kamailio/commit/a5e89b42151ba3697835cff4a2a379422a9afc46
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-05-16T15
Similar to local_log_level - controls the syslog facility of certain log entries
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/625
-- Commit Summary --
* presence: Add local_log_facility configuration parameter
-- File Changes --
I downloaded the source package from the Debian repo and compiled with symbols.
The error traced back to an incorrect Radius client configuration. I've done
some more testing by removing some random directives from the config and it's
surprisingly easy to make it segfault.
Poor error handling
Closed #614.
---
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/614#event-658413908___
sr-dev mailing list
sr-dev@lists.sip-router.org
Looks like a bug with the Debian 8 libfreeradius-client-dev package... or at
least how Kamailio works with it. Compiling the latest from
https://github.com/FreeRADIUS/freeradius-client has fixed the problem.
I'm going to do some more digging.
---
You are receiving this because you are
Ah, thanks Daniel. This is more useful.
```
#0 __strncpy_sse2 (s1=0x7ffc980a968f "", s2=0x208 , n=48) at ./strncpy.c:41
n4 = 12
c =
s = 0x7ffc980a9690 ""
#1 0x7f0ffc54bbc9 in rc_send_server () from
/usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2
No symbol table
Nothing relevant that I can see in the log. Here's the full thing.
Can you see anything relevant?
```
May 11 17:16:36 ua-proxy-00 kamailio: INFO: tls [tls_init.c:403]:
init_tls_compression(): tls: init_tls: disabling compression...
May 11 17:16:36 ua-proxy-00 kamailio: INFO: [sctp_core.c:75]:
Kamailio 4.3 fails to start after building a previously working
sourcetree/config from Debian 7 onto a new Debian 8 server.
Log file is:
```
May 11 16:46:19 ua-proxy-00 /opt/kamailio/sbin/kamailio[312]: INFO: tls
[tls_domain.c:674]: set_verification(): TLSc: Server MAY present
invalid
Good timing. Literally just came out of a meeting where the undesirable
behavior of repeated `terminated` NOTIFY messages was discussed. This is a
useful addition.
You've changed a lot of whitespace that is not related to this PR. Makes it
very difficult to digest :/
Appreciate this isn't
Pcap that demonstrates this (I had to zip it for GitHub) is:
[fork-fail-filtered.zip](https://github.com/kamailio/kamailio/files/221097/fork-fail-filtered.zip).
In this example, Kamailio is a registration proxy.
If two phones answer the call at the same time, it is possible for the CANCEL
to
Do you have a suggestion of the best `malloc` method to use in a production
environment? Some Kamailio blog posts suggest fmalloc is more suited to
production?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Adding `mem_join=1` to the config also appears to resolve the issue. Is this
something that is enabled by default on 4.4? These two links contradict each
other:
https://www.kamailio.org/wiki/tutorials/troubleshooting/memory
https://www.kamailio.org/wiki/cookbooks/4.4.x/core#mem_join
The
Experiencing an issue with QMalloc when Kamailio receives a lot of
subscriptions (dialog-info) in a short period of time. The following is
reported in logs and the TCP (TLS) connection fails:
```Apr 4 18:06:04 ua-proxy-01 /usr/local/sbin/kamailio[28456]: ERROR:
[tcp_main.c:959]:
The limit is 100 chars in the latest master -
https://github.com/kamailio/kamailio/blob/master/modules/kazoo/kz_amqp.c#L623
You're presumably looking at the current stable.
---
Reply to this email directly or view it on GitHub:
Module: kamailio
Branch: 4.3
Commit: 11715a3601629d8f1b79cac4f84f7e0ebebd318e
URL:
https://github.com/kamailio/kamailio/commit/11715a3601629d8f1b79cac4f84f7e0ebebd318e
Author: Daniel-Constantin Mierla <mico...@gmail.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-02-
Module: kamailio
Branch: master
Commit: 8736b2dc8dcd5fd8ee253134b19cb8ce0aa1c0b4
URL:
https://github.com/kamailio/kamailio/commit/8736b2dc8dcd5fd8ee253134b19cb8ce0aa1c0b4
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-02-24T12:21:4
Module: kamailio
Branch: master
Commit: 9dd2760fd337b39b72eb38189c093f5a156292f2
URL:
https://github.com/kamailio/kamailio/commit/9dd2760fd337b39b72eb38189c093f5a156292f2
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-02-24T12
- log shm_available_safe() instead of shm_available() as this is what is
actually compared in the check
- also log the relevant threshold as it is not always obvious if the default
value is being used
You can view, comment on, or merge this pull request online at:
I figured it was worth backporting this crash fix, before the v4.3.5 release
Daniel mentioned on the mailing list
- the structure will be destroyed in a later dlg callback, enabled by
dlg_api.register_dlgcb(), via free_dlginfo_cell()
- based and includes partial patch from GH #492, by Phil
Module: kamailio
Branch: master
Commit: 1c0242fecb1a5ea9a3fde54b8ce331886e564d39
URL:
https://github.com/kamailio/kamailio/commit/1c0242fecb1a5ea9a3fde54b8ce331886e564d39
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-02-19T12:07:4
Module: kamailio
Branch: master
Commit: 897e775a6353ab1e4738ad3b0c3d1c1e53980277
URL:
https://github.com/kamailio/kamailio/commit/897e775a6353ab1e4738ad3b0c3d1c1e53980277
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2016-02-
- pua_dialoginfo: Implement callee_trying parameter in pua_dialoginfo which
causes
a "Trying" state to be sent for both the caller and callee when
a new dialog is created.
- presentity: Implement table locking for all routes through update_presentity
in order
to avoid a number of different
Sending socket isn't the issue here, it's the destination address/port. The
destination can be forced by setting the outbound_proxy setting of PUA -
http://www.kamailio.org/docs/modules/4.3.x/modules/pua.html#idp15445640. This
works in my usecase but probably not in others.
The client isn't
A number of additional ports have been opened on Kamailio - the relevant one
here is TCP 443. An INVITE comes in from a UA whose from URI is suffixed with
:443. PUA generates a PUBLISH out of this. Log is at
https://gist.githubusercontent.com/phil-lavin/c381d556c22fd29b4fde/raw
Thanks, Daniel. All understood :)
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/492#issuecomment-178445057___
sr-dev mailing list
sr-dev@lists.sip-router.org
Hi Daniel,
There's an outstanding crash bug fix on GitHub submitted last week -
https://github.com/kamailio/kamailio/pull/492.
This is also present in 4.3 and probably earlier releases. It'd be helpful for
us if this could be merged to master and I will sort the backports separately.
Cheers
- SHM pointer is freed when it is required later by dialog callbacks. Remove
the free_dlginfo_cell() call.
This is causing crashing after the BYE, when a call is ongoing during a
Kamailio restart
The free is actually done by the callback function `dlg_api.register_dlgcb()`
when it is
I will backport this to 4.3 if/when you're happy with it
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/492#issuecomment-176268420___
sr-dev mailing list
sr-dev@lists.sip-router.org
Module: kamailio
Branch: master
Commit: f703effa2e2d6c6f426374d07d57636ecf248fd2
URL:
https://github.com/kamailio/kamailio/commit/f703effa2e2d6c6f426374d07d57636ecf248fd2
Author: Phil Lavin <phil.la...@synety.com>
Committer: Phil Lavin <phil.la...@synety.com>
Date: 2015-12-
> @@ -90,11 +91,12 @@ static cmd_export_t cmds[] = {
> * Exported parameters
> */
> static param_export_t params[] = {
> - {"radius_config",PARAM_STRING, _config },
Reverted this but the alignment is out-of-wack and there's a mixture of tabs
and spaces
---
Reply to this email
Closed #456.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/456#event-502663775___
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Ok ref master - I'll close this PR, rebase, and open a new one
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/456#issuecomment-167960610___
sr-dev mailing list
sr-dev@lists.sip-router.org
- Implement append_realm_to_username parameter in auth_radius which allows
the unmolested digest username to be passed to RADIUS in the User-Name
attribute. This is required for some RADIUS implementations.
This is the same PR as #456 except based on master
You can view, comment on, or merge
- Implement append_realm_to_username parameter in auth_radius which allows
the unmolested digest username to be passed to RADIUS in the User-Name
attribute. This is required for some RADIUS implementations.
Apologies if this doesn't belong in the 4.3 branch - this is what the commit is
based
61 matches
Mail list logo
