[Serusers] sequential forking / t_on_failure

Klaus Darilion klaus.mailinglists at pernau.at
Wed Jun 2 19:43:14 CEST 2004


Hi Alex!

This is done in outside the proxy - for in-dialog requests, the request 
URI contains the "contact" of the other party (or the Route header for 
strict routers (old SIP RFC))

regards,
klaus

Alex Bligh 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?
> 
> Alex
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
> 




More information about the sr-users mailing list