Module: kamailio
Branch: 5.0
Commit: dccca1959b6f96bb508baa9dab0eacba7c69f20c
URL:
https://github.com/kamailio/kamailio/commit/dccca1959b6f96bb508baa9dab0eacba7c69f20c
Author: Daniel-Constantin Mierla
Committer: Juha Heinanen
Date: 2017-04-08T09:02:38+03:00
pv: declare the pv_empty as buffer w
Module: kamailio
Branch: 5.0
Commit: 2705a9d36481d66ea86f79b574760f3009118775
URL:
https://github.com/kamailio/kamailio/commit/2705a9d36481d66ea86f79b574760f3009118775
Author: Daniel-Constantin Mierla
Committer: Juha Heinanen
Date: 2017-04-08T09:02:39+03:00
core: use buffers instead of static
Module: kamailio
Branch: 5.0
Commit: f9fbd7a97cae4431a64ab350c2eed7bbc0586049
URL:
https://github.com/kamailio/kamailio/commit/f9fbd7a97cae4431a64ab350c2eed7bbc0586049
Author: Daniel-Constantin Mierla
Committer: Juha Heinanen
Date: 2017-04-08T09:02:39+03:00
pv: renamed empty buf variable
(che
The issue is in the tm module. While processing the resumed reply, since we are
in a case of final reply for the transaction, we delete it after sending it
out. This is causing the carsh when, at the end of t_continue we try to access
the branch's reply.
I've open a PR https://github.com/kamaili
Fix for https://github.com/kamailio/kamailio/issues/1056.
If the reply is continued we need the reply after sending it out, even if it's
a final reply.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1063
-- Commit Summary --
* tm: d
Module: kamailio
Branch: master
Commit: 8bfabb975a59e43bf5a18fde0b0ab2b2feef94f6
URL:
https://github.com/kamailio/kamailio/commit/8bfabb975a59e43bf5a18fde0b0ab2b2feef94f6
Author: lazedo
Committer: lazedo
Date: 2017-04-07T18:27:43+01:00
kazoo: add exchange bindings
---
Modified: src/modules/k
Merged #1062.
--
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/1062#event-1034483137___
sr-dev mailing list
sr-dev@lists.sip-router.org
http
please don't merge
--
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/1062#issuecomment-292580810___
sr-dev mailing list
sr-dev@lists.sip-rout
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1062
-- Commit Summary --
* kazoo: add exchange bindings
-- File Changes --
M src/modules/kazoo/kz_amqp.c (743)
M src/modules/kazoo/kz_amqp.h (54)
M src/modules/kazoo/kz_j
On 07.04.17 17:38, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> A quicker solution will be to disable method matching based on presence
>> of To-tag, because this is anyhow part of an established dialog and this
>> can be end-to-end without involving the proxy/registrar.
> Sounds
Daniel-Constantin Mierla writes:
> A quicker solution will be to disable method matching based on presence
> of To-tag, because this is anyhow part of an established dialog and this
> can be end-to-end without involving the proxy/registrar.
Sounds good to me, although in case of gruu, registrar (
Daniel-Constantin Mierla writes:
> It was the parser setting the value of host part to "", not the
> transformation, so the change had to be done in other file. Can you try
> again with latest master?
thanks for the fix. now the crash is gone. statements:
$var(test_uri) = "tel:+358447058060";
It was the parser setting the value of host part to "", not the
transformation, so the change had to be done in other file. Can you try
again with latest master?
Cheers,
Daniel
On 07.04.17 16:05, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Thanks, I just pushed a patch, can you
Module: kamailio
Branch: master
Commit: cdd7bc29a900d787b8d99f7296306f99c53a5e29
URL:
https://github.com/kamailio/kamailio/commit/cdd7bc29a900d787b8d99f7296306f99c53a5e29
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2017-04-07T17:05:27+02:00
pv: renamed empty buf
Module: kamailio
Branch: master
Commit: 6aa2b91b581d7e0f138a9a19f61d848caeb61a19
URL:
https://github.com/kamailio/kamailio/commit/6aa2b91b581d7e0f138a9a19f61d848caeb61a19
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2017-04-07T17:05:44+02:00
core: use buffers inst
Daniel-Constantin Mierla writes:
> Thanks, I just pushed a patch, can you try it?
Unfortunately still the same crash with this placed as the first thing
in main routing block:
$var(test_uri) = "tel:+358447058060";
xlog("L_INFO", "** extracting domain from <$var(test_uri)>\n");
$r
Thanks, I just pushed a patch, can you try it?
Cheers,
Daniel
On 07.04.17 15:32, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> What OS do you have and which version of gdb? The list command should
>> list the code around the line where the crash happens, but it doesn't do
>> it for
Module: kamailio
Branch: master
Commit: 1e37b31f8a28ccc6f44eaf75e5f02e836df20411
URL:
https://github.com/kamailio/kamailio/commit/1e37b31f8a28ccc6f44eaf75e5f02e836df20411
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2017-04-07T15:37:07+02:00
pv: declare the pv_emp
Daniel-Constantin Mierla writes:
> What OS do you have and which version of gdb? The list command should
> list the code around the line where the crash happens, but it doesn't do
> it for you.
this is debian jessie with GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1.
> Anyhow, you can extract the code aro
On 07.04.17 10:50, Juha Heinanen wrote:
> if registrar method_filtering param is set, lookup produces -2 and $du
> is not set if method is not listed in allow header of register request.
>
> this is fine with initial requests, but in case of an invite dialog,
> initial invite may list another set
On 07.04.17 10:50, Juha Heinanen wrote:
> if registrar method_filtering param is set, lookup produces -2 and $du
> is not set if method is not listed in allow header of register request.
>
> this is fine with initial requests, but in case of an invite dialog,
> initial invite may list another set
What OS do you have and which version of gdb? The list command should
list the code around the line where the crash happens, but it doesn't do
it for you.
Anyhow, you can extract the code around src/modules/pv/pv_core.c:2243
and send it here, to be sure it is the one you use at the time of crash.
Daniel-Constantin Mierla writes:
> Is it latest master? The line is matching an LM_ERR() with only static
> string.
master as it was on april 3.
> You should list the code, in gdb:
>
> frame 0
>
> list
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f9d268703e0 in pv_se
Is it latest master? The line is matching an LM_ERR() with only static
string.
You should list the code, in gdb:
frame 0
list
Cheers,
Daniel
On 07.04.17 14:20, Juha Heinanen wrote:
> k 5.1 crashes when executing this:
>
> $var(test_uri) = "tel:+358447058060";
> xlog("L_INFO", "**
k 5.1 crashes when executing this:
$var(test_uri) = "tel:+358447058060";
xlog("L_INFO", "** extracting domain from <$var(test_uri)>\n");
$rd = $(var(test_uri){uri.host});
xlog("L_INFO", "** request uri is <$ru>\n");
Apr 7 15:15:17 lohi /usr/bin/sip-proxy[14477]: INFO: ***
Hello,
probably it is the time to have another IRC devel meeting to discuss the
plans for the project and the roadmap to next major release, v5.1.
First proposed date would be Apr 20, with secondary options for Apr 24
or 25, but other dates can be taken in consideration if more convenient
for a c
Module: kamailio
Branch: master
Commit: 60aa7ec193950249a1610a943b767421e310fb10
URL:
https://github.com/kamailio/kamailio/commit/60aa7ec193950249a1610a943b767421e310fb10
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2017-04-07T11:16:43+02:00
modules: readme files regenerated - sdpops ...
Module: kamailio
Branch: master
Commit: 8a38f369b01a642b92704cc0e6efeb6e108f8a02
URL:
https://github.com/kamailio/kamailio/commit/8a38f369b01a642b92704cc0e6efeb6e108f8a02
Author: Carsten Bock
Committer: Carsten Bock
Date: 2017-04-07T11:09:14+02:00
sdpops: Add note about sdp_remove_media() and
if registrar method_filtering param is set, lookup produces -2 and $du
is not set if method is not listed in allow header of register request.
this is fine with initial requests, but in case of an invite dialog,
initial invite may list another set of methods that the ua supports in
in-dialog reque
29 matches
Mail list logo
