Hello,
it is asterisk that asks second time - kamailio is verifying the auth
ok, then forwards to asterisk which asks again for authentication. Read
the notes from the Asterisk Database section in the tuorial:
On 24/07/14 19:34, Asgaroth wrote:
On 24/07/2014 17:26, Daniel-Constantin Mierla wrote:
checking docs, it seems like that. I will have to look at the code
and eventually make an option without parameter. Otherwise, like it
is not, the parameter forces an outbound proxy to be used for
Thanks for testing and reporting the results, I will look to backport it
soon to 4.1 branch.
Cheers,
Daniel
On 23/07/14 18:46, Anthony Messina wrote:
On Monday, July 21, 2014 10:16:38 AM Daniel-Constantin Mierla wrote:
Hello,
can you try the patch from next commit?
Hello,
On 14/07/14 15:49, Peter Villeneuve wrote:
Hi Daniel,
Thanks for your input. Since I couldn't decide which one to use, I've
been experimenting with using both.
The problem with my mixed approach is that there are too many ICE
candidates created (I counted 10 in the last logs I looked
using the default cfg file, whenever a WITHINDLG BYE is received, 4.1.4
needs a retransmission before passing it through, the first BYE would
generate this in syslog
tm [tm.c:1518]: _w_t_relay_to(): ERROR: w_t_relay_to: unsupported route
type: 64
and the 2nd retransmitted BYE would go on fine.
On 25/07/14 11:46, Kelvin Chua wrote:
using the default cfg file, whenever a WITHINDLG BYE is received,
4.1.4 needs a retransmission before passing it through, the first BYE
would generate this in syslog
tm [tm.c:1518]: _w_t_relay_to(): ERROR: w_t_relay_to: unsupported
route type: 64
and
Hi,
On 25/07/2014 11:03, Daniel-Constantin Mierla wrote:
I pushed a patch to master branch that allows to use t_replicate()
without any parameters.
Apparently the same behaviour can be achieved using:
t_replicate()
so the parameter is an empty string. Can you try it and see if works?
Also,
On 25/07/14 12:20, Asgaroth wrote:
Hi,
On 25/07/2014 11:03, Daniel-Constantin Mierla wrote:
I pushed a patch to master branch that allows to use t_replicate()
without any parameters.
Apparently the same behaviour can be achieved using:
t_replicate()
so the parameter is an empty string. Can
Hi,
Another quick question on the git checkout, do I need to checkout the
4.1 branch for this patch, or is it in 4.2 branch?
I did the following:
git clone --depth 1 git://git.sip-router.org/sip-router kamailio
make FLAVOUR=kamailio tar
this generates the following tar file which I will use
On 25/07/2014 11:33, Daniel-Constantin Mierla wrote:
$ru = sip: + BACKUP_REGISTRAR_1 + :5060;
append_branch(sip: + BACKUP_REGISTRAR_2 + :5060);
*t_replicate();*
Yes, and this should work on existing versions 4.1.x or older
OK, trying to test this and I'm seeing an error with debug=2:
On 25/07/14 12:51, Asgaroth wrote:
On 25/07/2014 11:33, Daniel-Constantin Mierla wrote:
$ru = sip: + BACKUP_REGISTRAR_1 + :5060;
append_branch(sip: + BACKUP_REGISTRAR_2 + :5060);
*t_replicate();*
Yes, and this should work on existing versions 4.1.x or older
OK, trying to test this and I'm
On 25/07/2014 12:04, Daniel-Constantin Mierla wrote:
I read the condition on uri wrong -- it was only on a null pointer for
the uri, not on length (in this case pointer is to a empty string). I
pushed an enhanced check for length as well, but it is only in master
for the moment.
ok, I will
The second one is with the patch to the code and it is enough to pick
only that one.
The first one is for docs (readme file), which is not really necessary
to test (main reason to split the commit, because patches to docs
typically throw conflicts when backporting, due to different formatting
Hi,
On 25/07/2014 13:49, Daniel-Constantin Mierla wrote:
The second one is with the patch to the code and it is enough to pick
only that one.
OK, I tried 4.1.4 with this patch applied and I still get the following
error message:
/usr/sbin/kamailio[22158]: ERROR: tm [tm.c:1618]:
Hello,
use t_replicate() without any parameter.
I said before that I mistakenly evaluated the code as working with empty
parameter, but it was not. Later today I pushed a new patch for this
case as well.
Cheers,
Daniel
On 25/07/14 19:35, Asgaroth wrote:
Hi,
On 25/07/2014 13:49,
Hi,
using t_replicate() did the trick! it appears to be replicating to both
systems now, thanks alot for looking at this.
The only difference i can see is that the r-uri is re-written for both
replicated regesters although this shouldnt make any difference as the
registration is already
You have to upgrade to latest sources from branch 4.1. There was a
regression with execution of event routes from dialog module, which
should be fixed already.
Cheers,
Daniel
On 25/07/14 14:13, Kelvin Chua wrote:
right, i missed this one
from route.h
#define LOCAL_ROUTE (1 6)
for the
17 matches
Mail list logo
