[SR-Users] lookup(), received an $du

[Daniel-Constantin Mierla]

Hello,

On 5/11/10 2:59 PM, Andreas Granig wrote:
> Hi,
>
> Some interesting behavior with kam-3.0, which I haven't experienced 
> with <= 1.5:
>
> Let's say I have two subscribers A and B registered. A has a 
> received-value in location table, B has it set to NULL.
>
> If I call lookup() for A, $ru is set to the registered contact, and 
> $du is set to the received-value. When for example A is busy, I catch 
> it with a failure route and rewrite $ru to B. Calling lookup() again 
> sets my $ru to the contact of B, but since the received-value of B is 
> NULL in the DB, the $du is still pointing to the received-value of A, 
> instead of being set to null.
>
> A quick-fix is to set $du to null before calling lookup(), but I'm 
> wondering if this is a bug or intended behavior?
>
at the first sight, looking into the code, should be the same in 1.5. 
Are you sure is different? Practically the registrar/usrloc were touched 
just a bit, nothing in the lookup or save functionality.

Looking in tm at execution of failure route, the dst_uri is recovered 
from the winning branch. lookup updates the dst_uri only if it is a 
value in location record.

Right now, I would say that lookup should reset any existing dst_uri if 
received is null. Other opinions? Is anyone setting dst_uri before 
lookup and needs it after?

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
* http://www.asipto.com/
* http://twitter.com/miconda
* http://www.linkedin.com/in/danielconstantinmierla