Hi, >All server transactions linger for the 3 minutes Hmm can you point me such place in rfc ? If i look rfc 3261 17.2.x Server transactions will destroy too if final response, only in some cases linger for 4 seconds. Also what the use of Cancel then if transaction linger so long time. And also normally retransmit of request ot server transaction won't happen, because server transaction must send 100 trying (i mean at least time you in real life cancel transaction). The only idea is to cancel Invite when ringing. And i suspect Cancel will terminate transaction or there is no meaning/use of cancel.
[EMAIL PROTECTED] wrote: > From: Ivar <[EMAIL PROTECTED]> > > But what happens to server transaction after cancel ? > Logical is that it will be terminated and disposed (because nothing to > do with that server transaction), but can't see place what describes it. > > Client transaction can't dispose at once, thats clear, because invite > transaction should get 487 'Request Terminated'. > There I'm thinking about linger terminate 5 sec for 478 to arrive. > > All server transactions linger for the 3 minutes (or whatever it says > in 3261), so that if a re-transmission of the request is received, the > server can re-send the response. > > The client INVITE transaction can be terminated immediately once a > final response is received. (Which might not be 487, due to race > conditions, and may even be a success response.) > > Similarly for the client CANCEL transaction. > > Dale > _______________________________________________ > 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
