I am trying to draw a parallel with the INVITE case to understand. If the proxy gets 2XX from first UA and sends cancel to all other UAs, and if one of the other UAs sent a 200 OK before the cancel reached, the second 200 OK will also be forwarded to the client, and it is upto the client to decide which one to pick. For other transcations, if the proxy sent CANCEL, the 487 will be intercepted by the proxy who will send back an ACK, I dont think the 4XX are forwarded to the original client. Are the non-INVITEs supposed to behave differently?
On 4/5/06, Tom K <[EMAIL PROTECTED]> wrote: > > HI, > > First of all apologies , for repeating the following . > > I have some basic transaction layer doubts about non invite server > transactions and forking. > > IN the figure for state machine of non-Invite server transaction (In RFC > 3261)the only timer defined is Timer J (for the absobtion > of retransmissions of requests in cases of non reliable transports). > > Is this mean that > 1) if no response is send , a non INVITE server transaction will hang for > ever ? > Some places i saw a reference to timer F(draft-sparks-sip-noninvite-01) > But what I under stood was timer F is only for non invite clients, not for > non invite servers . > > Another doubt about forking . > > If in the case of a forking proxy ,assume it forked a non invite request > to 3 different destinations .Could you please let me know the correct > behaviour from following scenario (Assuming unreliable transport is used). > > 1) From first destination it got a 2xx response ,will the proxy will > forward the 200 OK for non-INVITE immediately , and the > server transaction associated with that client transaction enters into > completed stage .(Once server txn enters into the completed state > ,whether the associated client txns, will be destroyed? ) > > 2) From the second , it got a 4xx. > 3)From the third it got anther 4xx after some time > > if the proxy forwards a final response for a non-INVITE request , no > further responses are forwarded ? > And > if the non- invite server transaction is in the completed state(For > unreliable transport) , if one of the client transactions associated with > it gets a final response , will it be discarded . > > rgds > -Tom > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------- > Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great > rates starting at 1ยข/min. > _______________________________________________ > 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
