2 Jun
2004
2 Jun
'04
6:03 p.m.
--On 02 June 2004 18:38 +0100 Alex Bligh alex@alex.org.uk wrote:
Consider the situation whereby after an INVITE occurs which ser initially routes to A (which is, say, busy) and subsequently routes to B. Perhaps it has gone through t_on_failure or some other mechanism of sequential forking. Assume the INVITE has been OK'd and ACK'd.
What mechanism does ser use to ensure subsequent transactions on the call-leg (such as BYE, re-INVITE etc.) are sent to B and not A? IE where is the state being stored and how?
I am obviously assuming (transaction) stateful forwarding and that record_route is on (else the proxy wouldn't even get to see BYE etc.)
Alex