Are you using newest 3.0 ? (git checkout) I remember I once also had a problem with PVs which had stored old values, but I can not remember naymore which PV it was.
regards klaus
Am 11.05.2010 14:59, schrieb Andreas Granig:
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?
Thanks, Andreas
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users