In section "7.1 Server Transaction Impacts, RFC 6026", it has statements like this.
A server transaction MUST NOT discard transaction state based only on encountering a non-recoverable transport error when sending a response. Instead, the associated INVITE server transaction state machine MUST remain in its current state. (Timers will eventually cause it to transition to the "Terminated" state). This allows retransmissions of the INVITE to be absorbed instead of being processed as a new request. Which timer will eventually cause the server transaction to transition to the "Terminated" state? For example, if the current state is "Proceeding", due to transport error we fail to send response, the state will remain in "Proceeding" state. There is no timer in current Server Transaction, so how we eventually make the state transition to "Terminated" state? Best Regards, Caixia _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
