Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-19 Thread Klaus Darilion
On 19.09.2012 16:13, Yufei Tao wrote: I should have made it clearer: $du is null both before and after lookup location in LOCATION_BRANCH when no fix_nated_register was done (thus 'received' column in location table was null). When fix_nated_register was done, $du for each branch was null befor

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-19 Thread Yufei Tao
l be set), or 2. set $du after lookup if it is empty Wonder if it is worth adding fixes in the source code. Thanks very much Klaus for pointing me to the right direction! Yufei Date: Wed, 19 Sep 2012 15:13:29 +0100 From: Yufei Tao Subject: Re: [SR-Users] call forking using dbaliases not worki

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-19 Thread Yufei Tao
I should have made it clearer: $du is null both before and after lookup location in LOCATION_BRANCH when no fix_nated_register was done (thus 'received' column in location table was null). When fix_nated_register was done, $du for each branch was null before lookup location, but set to 'received' a

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-19 Thread Klaus Darilion
On 19.09.2012 12:24, Yufei Tao wrote: Hi Klaus Thanks for the reply! I check the $du, it is always null before and after the lookup. Is it only set when relaying to a proxy (from record-route), and not to a client? That's strange. For NATed clients, $du must contain the 'received' URI. Oth

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-19 Thread Yufei Tao
Hi Klaus Thanks for the reply! I check the $du, it is always null before and after the lookup. Is it only set when relaying to a proxy (from record-route), and not to a client? When no fix_nated_register is called, the lookup location for both clients y2 and y3 is successful from the log, when p

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-18 Thread Klaus Darilion
I suspect that the branch route is first executed for the NATed client. Then the 'received' column is used as destination URI. When executing the branch route again, the destination URI is still the value from the previous branch, and lookup() will not overwrite is as 'received' is not availabl

[SR-Users] call forking using dbaliases not working for un-NATed clients

2012-09-18 Thread Yufei Tao
Hi I have a strange problem on forking calls to a group of users. For example I have two users y2 and y3 in dbaliases, both with alias_username 'group'. And y2 and y3 both registers with Kamailio fine. When I make a call to 'group' from a third client y1, what my kamailio.cfg does is: do an alias_