From: "Stephen Paterson" <[EMAIL PROTECTED]> Question is: What should the UAS do if it receives a re-INVITE after it has sent the final response but before it receives the ACK for the initial INVITE?
"Final response" means "final response". You should process the INVITE. But it seems problematic, as the ACK might bear the SDP response, and the UA may want to know the initial SDP before formulating its SDP response for the re-INVITE. Currently our stack ignores the second INVITE but my gut feeling is there should be some sort of 4xx response, possibly containing a Retry-After header. I do like the idea of solving the ambiguity by forcing the sender to re-send, hoping you receive the ACK followed by a re-send. Blame it on the network! Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
