Can you try with the following commit:
-
https://github.com/kamailio/kamailio/commit/85029d414384912879b45a34bdeb8f1372cc3780
If you installed from git, you can do a:
git pull origin
git cherry-pick -x 85029d414384912879b45a34bdeb8f1372cc3780
Then re-compile, re-install and restart kamailio.
Hello,
the code seems to be similar to the one for searching a subscription. I
am considering to make the matching criteria configurable to see the
results.
Are you using presence for dialog notifications (e.g., blinking lamps,
call pickup) or user presence states?
Cheers,
Daniel
On 02/12/14
Thanks Daniel.
I am now using record_route_advertised_address() to set the alternate
address rather than record_route_preset() followed by record_route(). Also,
I am able to add the tag using add_rr_param(). The documentation for the
record_route_preset function isn't clear that it actually
Hello,
you call record_route_preset() in the switch and record_route() before
t_relay(), therefore you attempt to add two times the record-route header.
I am not sure the add_rr_param() works on the header added by
record_route_preset(), to that function you can include the URI
parameter
Ansuman,
The mohqueue module was designed to redirect waiting callers into a
Music-On-Hold (MOH) queue and when a line became available to pull them out
of queue and redirect them to an available line. I'm not sure if this is
what you have in mind. If so, I'm sorry but I don't understand your
Hi,
I am developing a system using Kamailio 4.2.1 as a front-end to a group
of
Asterisk servers. All of the usual functionality (registations,
inbound, outbound, internal calls) are fine. We need to add call
queueing
to the system.
I looked at the mohqueue module and read that we
On 01/03/2015 04:54 PM, Daniel-Constantin Mierla wrote:
what operating system do you have? How did you start kamailio?
Directly, as root:
kamailio -m 1024 -f kamailio.cfg
The OS environment is CentOS 6.5.
Do you get other messages from the kernel (should be in the default
syslog file),
Thanks, Ovidiu. But since the message core was not generated comes
from handle_sigs() in Kamailio, what I am really interested is in what
reason Kamailio itself would have for not dumping core. I assume that
the situation would look different if Kamailio tried to dump core, but
was restrained
IIRC, you get that message if core dumping is not properly enabled at
system level. Check that you have those settings and kill kamailio with a
SIGSEGV to test.
It always worked for me. I can't afford to install a server without core
dumping enabled.
-ovidiu
On Jan 3, 2015 5:23 PM, Alex Balashov
