On Wednesday 28 January 2015 13:52:26 Daniel-Constantin Mierla wrote:
One solution I thought of is to propagate the direction via topoh 'cookie' header, as it is done by the dialog module for the local generated BYE. Tm code needs to be changed, but I haven't found the time for it yet.
Being an hob-by-hop ack for a within dialog request, there is no info that can be used to determine the direction. Topoh hooks are in the core, after the new sip message is printed, with no relation to transaction (or in this case, the reply).
I also found a similar flaw with reINVITEs due to session timers in 4.2.4
A new random callid gets generated and sent to an endpoint, which reacts with a 481.
109.235.34.226 contain the endpoints 109.235.32.240 is a loadbalancer 109.235.32.243 is the sipserver doing the topoh stuff