RFC3261: SIP:12.2对话中的请求

12.2 Requests within a Dialog
12.2对话框中的请求

   Once a dialog has been established between two UAs, either of them MAY initiate new transactions as needed within the dialog.  The UA sending the request will take the UAC role for the transaction.  The UA receiving the request will take the UAS role.  Note that these may be different roles than the UAs held during the transaction that established the dialog.

一旦在两个UA之间建立了对话，它们中的任何一个都可以根据需要在对话中启动新的事务。发送请求的UA将承担事务的UAC角色。接收到请求的UA将担任UAS角色。请注意，这些角色可能与建立对话的事务期间所扮演的UA不同。

   Requests within a dialog MAY contain Record-Route and Contact header fields.  However, these requests do not cause the dialog's route set to be modified, although they may modify the remote target URI. Specifically, requests that are not target refresh requests do not modify the dialog's remote target URI, and requests that are target refresh requests do.  For dialogs that have been established with an INVITE, the only target refresh request defined is re-INVITE (see   Section 14).  Other extensions may define different target refresh requests for dialogs established in other ways.

​对话中的请求可能包含记录路由和Contact报头字段。但是，这些请求不会导致对话的路由集被修改，尽管它们可能会修改远程目标URI。具体而言，非目标刷新请求不会修改对话的远程目标URI，而目标刷新请求会修改。对于使用INVITE建立的对话，唯一定义的目标刷新请求是re-INVITE（请参阅第14节）。其他扩展可以为以其他方式建立的对话定义不同的目标刷新请求。

      Note that an ACK is NOT a target refresh request.

请注意，ACK不是目标刷新请求。

   Target refresh requests only update the dialog's remote target URI, and not the route set formed from the Record-Route.  Updating the latter would introduce severe backwards compatibility problems with   RFC 2543-compliant systems.

​目标刷新请求只更新对话的远程目标URI，而不更新由记录路由形成的路由集。更新后者将引入与符合RFC 2543的系统的严重向后兼容性问题。