Hugh Waite writes:
This function was written because the "record_route_preset()" function did not create double record-routes and "record_route()" did not use the advertised address correctly. When Daniel implemented the feature to specify an advertised address per listen socket in March, it also fixed the standard "record_route()" function so that advertised addresses specified in the cfg file work correctly in a record route.
hugh,
thanks for the explanation. it turned out that i cannot use "record_route_advertised_address()" anyhow, because i need to also have different ports on each side. so switched to "record_route_preset()", which does what i want.
anyhow, i can add tracker item just in case someone later would need a working record_route_advertised_address().
-- juha