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
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
On 4/19/12 10:08 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
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.
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 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
On 4/19/12 10:33 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.
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.
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 -
Juha Heinanen