Hi, Maybe, for a scenario where offer was there in invite and answer in 2xx, but in case where response to the offer is expected ACK, UAS should probably send error to RE-Invite with retry-after if it is still waiting for ACK.
- Harmeet Singh On Wed, 14 Jul 2004 16:14:06 -0700, Marc Petit-Huguenin <[EMAIL PROTECTED]> wrote: > I would like to have a confirmation that an UAS must be ready to receive a > new INVITE in a dialog as soon a response was sent for the previous INVITE. > More precisely, the UAS must not wait for the ACK before accepting the next > INVITE. > > My reasoning is based on the fact that RFC3261 section 14.1 says that "If > there is an outgoing INVITE client transaction, the TU must wait until the > transaction reaches the completed or terminated state before initiating the > new INVITE." As an INVITE transaction reaches the completed or terminated > state as soon a non-provisional response is received, the next INVITE can > be sent at the same time the ACK for the 200 response is sent. As the > packet ordering can change, the INVITE can arrive at the UAS before the > ACK. So this mean that the server should be prepared to receive the next > INVITE before receiving the ACK. > > Is it correct? > > Thanks. > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- ------------------------------------------------------ Harmeet Singh _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
