2 Jun
2004
2 Jun
'04
8:38 p.m.
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?
Alex