Daniel-Constantin Mierla writes:
> It would require C coding to get it nicely, I see three options:
> - try to get the values as in branch_route -- seems complex at first look
> - try to get the values via $T_branch(attr) -- sounds simpler now
> - try to get a function t_reuse_branch() -- create a
On 16/04/14 18:46, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Why would you need all attributes of the branch that just failed, do you
want to send the request to the same destination again?
that is exactly the requirement. the idea is to assign some avps/branch
flags differently
Hello Daniel,
Thank you for your reply. I checked the RFC 4662 document witch contains
the rls notify body. Indeed, the watcherinfo body should not be present in
the multipart response. But, I think that it's an issue with the RLS or
(but I can't see how I could break this) in my configuration. Let
On 04/16/2014 06:53 PM, Daniel-Constantin Mierla wrote:
> Hello,
Ciao Daniel,
>
> most likely the messages are looped back, be sure you allow requests from
> 'myself' without authentication.
>
> You can watch loopback interface with ngrep to see if the messages are sent
> out.
Yep! Allowing re
Hello,
most likely the messages are looped back, be sure you allow requests
from 'myself' without authentication.
You can watch loopback interface with ngrep to see if the messages are
sent out.
Cheers,
Daniel
On 16/04/14 18:46, Roberto Fichera wrote:
Hi All,
I've started to play with M
Daniel-Constantin Mierla writes:
> Why would you need all attributes of the branch that just failed, do you
> want to send the request to the same destination again?
that is exactly the requirement. the idea is to assign some avps/branch
flags differently so that mediaproxy-offer in branch rout
Hi All,
I've started to play with MSILO module on kamailio v4.1.2, but it seems that
all the stored
messages aren't delivered to the give user even if, looking at the debug log,
the given messages
are found and queued for shipping. Another info I can add is that all the users
are connected in
On 16/04/14 18:29, Juha Heinanen wrote:
Hugh Waite writes:
As you and Daniel saw from the code, I replicated the behaviour of the
'failure-route' but with the current branch index. I didn't deliberately
choose the behaviour of $ru etc. so I'm happy with it being classed as a bug
if that's what
Hello,
by looking at the code, I would say that keeping the same behaviour as
now is the easiest way to go. Changing the attributes in the request
would require a lot of backups and restores of values.
It might be easier to add a special class of pvs to access branch
attributes, like:
$T_b
Hugh Waite writes:
> As you and Daniel saw from the code, I replicated the behaviour of the
> 'failure-route' but with the current branch index. I didn't deliberately
> choose the behaviour of $ru etc. so I'm happy with it being classed as a bug
> if that's what's expected in this situation.
>
>
Hello,
Sorry for being slow to join the discussion.
The requirements I had for the branch-failure route was to be able to run
t_next_contact_flow() etc. and also to retrieve the usrloc RUID so that the
entry could be de-registered. The latter can be done with $T_reply_ruid.
As you and Daniel saw
Hi Alex,
Thanks for the quick response.I will give it a try.
-Özgün İleti- From: Alex Balashov Sent: Wednesday, April 16, 2014
3:10 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Register
request forwarding from kamailio to asterisk
Hi Betül,
There is no necessity to f
Hi Betül,
There is no necessity to forward the request to Asterisk. You can use
the local registrar to save the contact binding instead. It's all a
question of what kind of architecture you, yourself, want to have. :-)
The integration instructions are just an example of a particular sort of
Hi to all
We integrated kamailio and asterisk as explained here
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
When kamailio receives a register request it authenticates and forwards the
request to asterisk.Why do we need to do this?What happens if we dont pass
regis
ups, replied to wrong message -- ignore this and previous message in
this thread.
Daniel
On 16/04/14 13:32, Daniel-Constantin Mierla wrote:
Hello,
On 16/04/14 12:49, Daniel-Constantin Mierla wrote:
Hello,
On 16/04/14 09:52, Keith wrote:
Hi All,
I am looking to apply some security on invi
Hello,
On 16/04/14 12:49, Daniel-Constantin Mierla wrote:
Hello,
On 16/04/14 09:52, Keith wrote:
Hi All,
I am looking to apply some security on invites so I only accept from
IP addresses in the address table or authenticated users. I have the
address table bit working but I am struggling wi
Hello,
there is a limitation of uac_auth() mentioned in the readme of uac
module. Perhaps asterisk doesn't accept the follow up request with
credentials having the same cseq value.
You should just configure asterisk to allow traffic from kamailio based
on ip address, without username/passwor
Hello,
On 16/04/14 09:52, Keith wrote:
Hi All,
I am looking to apply some security on invites so I only accept from
IP addresses in the address table or authenticated users. I have the
address table bit working but I am struggling with the authenticated
users bit. Wondering if anyone has don
Daniel-Constantin Mierla writes:
> - default private memory is 4MB - if the config is not that small, it
> might not be sufficient free pkg to play with (e.g., for sql_query()
> result, storage of $var(...) values). Should it be increased to 8MB or
> other value? Debian/Centos have startup scri
Hello,
I am considering releasing v4.1.3 by mid of next week, on Wednesday or
Thursday (April 23 or 24). If there are issues you are aware of and not
reported to the bug tracker, add them there asap to investigate them.
Also, if you noticed some fixes in the master branch not backported
yet
Hello,
I am opening this discussion to decide if there is need to adjust some
of the default values we have in Kamailio. Many of them were set even
like 10 years ago, so they might not be very actual anymore.
The main goal is to get the best possible settings for common usage.
To start with,
Hello,
I would go for this logic: if lookup("location") returns false and the
source ip different than the other server, then relay to the other server.
Say the other server ip is a.b.c.d:
if(!lookup("location")) {
if(src_ip != a.b.c.d) {
$du = "sip:a.b.c.d";
route(RELAY);
Hi All,
I am looking to apply some security on invites so I only accept from IP
addresses in the address table or authenticated users. I have the address
table bit working but I am struggling with the authenticated users bit.
Wondering if anyone has done it? I was thinking of using the location ta
Hello,
They can register to any of the servers as the registration process is
independent of domain part of user id.
My scenario is that once there are two users registered to different
servers. And one user make a call to other. How will server decide using
domain part from location table of dat
Hi all sorry for my english!
Iam trying to authenticate as uac on 3rd party server(Asterisk).
Kamailio get 401, send next invite with DIGEST but Asterisk send 401 again(((
Asterisk don’t write in log what auth is failed.
115.600045 xxx.xxx.xxx.xxx -> yyy.yyy.yyy.yyy SIP/SDP 1093 Request: INVITE
25 matches
Mail list logo
