From: [EMAIL PROTECTED] The RFC however does not specify the UAS behaviour in case a request is recieved which has a CSeq number that is EQUAL to the remote CSeq number (which could be possible due to network delays).
The second request is sent to the server transaction that was started by the first request. See RFC 3261 section 17.2, especially figure 2 -- in states Proceeding and Completed, re-receiving the request causes the UAS to re-send the response. Which, indeed, is the only sensible thing to do. Of course, that only works if the second request is the same as the first request with that CSeq. But if the UAC is functioning correctly, that will always be the case. If the two are different, it seems that the UAS is also expected to re-send the response to the first request. But if the two are different, the UAC is malfunctioning so badly that it hardly matters what the UAS does. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
