You may need to support RFC-4028 Session Timers in the Session Initiation Protocol (SIP). Also, if B disconnets because of 408 to BYE, you can assume A also disconnects by sending BYE as there is no use for A listenting to silence.
On 4/5/07, NC Reddy <[EMAIL PROTECTED]> wrote: > Hi Vikram, > B side dialog cleanup is fine, how about A and P1 side dialog > cleanup? > > Regards > Channa > > > On 4/5/07, Vikram Chhibber < [EMAIL PROTECTED]> wrote: > > In this case, assuming there is no high availability mechanism (backup > > of P2), B should receive 408 for BYE transaction and should terminate > > INVITE dialog. > > > > On 4/4/07, NC Reddy < [EMAIL PROTECTED]> wrote: > > > Hi, > > > Pls give your comments/solution for the following error scenario: > > > > > > A, B are endpoints, P1, P2 are transaction stateful proxies with record > > > route enable feature. > > > > > > > > > A<---------->P1<---------->P2<-----------B> > > > > > > Scenario: > > > > > > 1. Session is established and continuing between A and B. > > > 2. P1 and P2 are record route enabled. > > > 3. P2 is down. > > > 4. B initiate the Re-IVITE to B with route hdrs P2,P1. > > > 5. Since P2 is down, Re_Invite is Txn timeout. > > > 6. *So in this scenario, How to send BYE msg from B to A for to > > > terminate the session?.* > > > > > > > > > Regards > > > Channa > > > _______________________________________________ > > > Sip-implementors mailing list > > > [email protected] > > > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
