[Users] nat flag and branch routes
jh at tutpro.com
Wed Aug 31 12:18:59 CEST 2005
Bogdan-Andrei Iancu writes:
> - to have per-branch flags also before transaction creation; will be
> a new param to append_branch (8 in total :-/), but this flags will not
> be accessible from script; only in branch route;
this is what i thought would need to be done, i.e., add int nat_flag as
a new field in struct branch. yes, append_branch would need a new param
> - use something else than flags for NAT marking (something already
> present in all branch stages): nathelper, when builds the received URI
> (which will become dst_uri) will append a "nat=yes" parameter; this
> parameter will be easyly identify in branch route and NAT traversal may
> be activated....
where is this "nat=yes" parameter added and by which nathelper function?
More information about the sr-users