19 Apr
2012
19 Apr
'12
9:20 a.m.
when lookup() is called on in-dialog request that includes gruu in its
request uri, is $du set based on received field of location table if the
field is not null?
-- juha
19 Apr
19 Apr
10:08 a.m.
Hello,
On 4/19/12 9:20 AM, Juha Heinanen wrote:
when lookup() is called on in-dialog request that
includes gruu in its
request uri, is $du set based on received field of location table if the
field is not null?
yes, $du is set like for a normal location lookup.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
10:19 a.m.
On 4/19/12 10:08 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Just came in my mind, it sets other fields, including Route headers
built out of Path. Wonder if would be conflicts if first hop is not the
registrar/location server and for the call will be other Route set.
Regarding the docs, lookup sets all the attributes that are specific for
a branch: uri, dst_uri, local socket, branch flags (struct branch in
dset.h).
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
yes, $du is set like for a normal location
lookup.
good. by the way, lookup() function documentation in registrar/README
does not say anything about setting of $du.
10:33 a.m.
Daniel-Constantin Mierla writes:
Just came in my mind, it sets other fields, including
Route headers
built out of Path. Wonder if would be conflicts if first hop is not the
registrar/location server and for the call will be other Route set.
i don't know about path, but i call lookup() on in-dialog requests
containing gruu in ruri only if $du is empty after loose_route().
Regarding the docs, lookup sets all the attributes
that are specific for
a branch: uri, dst_uri, local socket, branch flags (struct branch in
dset.h).
yes, and nothing about that is mentioned in description of lookup()
function.
-- juha
11:02 a.m.
On 4/19/12 10:33 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
just add what you find missing. It is one of the oldest functions in the
application, most if its behavior in relation with the config is there
for long time...
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
http://www.asipto.com/index.php/kamailio-advanced-training/
Just came in my mind, it sets other fields,
including Route headers
built out of Path. Wonder if would be conflicts if first hop is not the
registrar/location server and for the call will be other Route set.
i don't
know about path, but i call lookup() on in-dialog requests
containing gruu in ruri only if $du is empty after loose_route().
Regarding the docs, lookup sets all the
attributes that are specific for
a branch: uri, dst_uri, local socket, branch flags (struct branch in
dset.h).
yes, and nothing about that is mentioned in description of lookup()
function.
4611
days inactive
4611
days old
5 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Juha Heinanen