Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: nat_bflag shall be branch-aware
As it is called a branch flag, nat_bflag shall IMO be branch_aware ;-)
* REGISTER two UACs, one of them with and the other one without NAT issue
* check your location table (cflags, received)
* Place a call, log the branch flag
You will see, that if one branch has the flag set, it is also true for
the other branch. Tested with r6115.
Comment By: Thomas Gelf (thomas_gelf)
Date: 2009-09-15 16:35
No, branch flags are fine. What I discovered was the following:
During a REGISTER request, I'm doing my NAT checks and set bflag_nat
if able to detect such an issue.
A location lookup call will then set this flag on calls for this
specific location. However, if one user is registered multiple times,
and only one of them has this flag set in location table, lookup()
applies the flag to each branch - while it should only be set on those
really having a NAT issue.