RFC3261: SIP:13.3.1.1进度

13.3.1.1 Progress
13.3.1.1进度

   If the UAS is not able to answer the invitation immediately, it can choose to indicate some kind of progress to the UAC (for example, an indication that a phone is ringing).  This is accomplished with a provisional response between 101 and 199.  These provisional responses establish early dialogs and therefore follow the procedures of Section 12.1.1 in addition to those of Section 8.2.6.  A UAS MAY send as many provisional responses as it likes.  Each of these MUST indicate the same dialog ID.  However, these will not be delivered reliably.

​如果UAS不能立即回答邀请，它可以选择向UAC指示某种进展（例如，指示电话正在响）。这是通过在101和199之间的临时响应来实现的。这些临时响应建立了早期对话，因此除了遵循第8.2.6节的程序外，还遵循第12.1.1节的程序。UAS可以发送任意数量的临时回复。每个对话都必须指示相同的对话ID。但是，这些对话不能可靠地传递。

   If the UAS desires an extended period of time to answer the INVITE, it will need to ask for an "extension" in order to prevent proxies from canceling the transaction.  A proxy has the option of canceling a transaction when there is a gap of 3 minutes between responses in a transaction.  To prevent cancellation, the UAS MUST send a non-100 provisional response at every minute, to handle the possibility of lost provisional responses.

如果UAS希望延长应答INVITE的时间，则需要请求“延期”，以防止代理取消事务。当事务中的响应间隔为3分钟时，代理可以选择取消事务。为了防止取消，UAS必须在每分钟发送一个非100临时响应，以处理丢失临时响应的可能性。

      An INVITE transaction can go on for extended durations when the user is placed on hold, or when interworking with PSTN systems which allow communications to take place without answering the call.  The latter is common in Interactive Voice Response (IVR) systems.

当用户被挂起时，或者当与允许在不应答呼叫的情况下进行通信的PSTN系统交互工作时，INVITE事务可以持续较长的持续时间。后者在交互式语音响应（IVR）系统中很常见。