RFC3261: SIP:8.2.2.1To和请求URI

8.2.2.1 To and Request-URI
8.2.2.1To和请求URI

   The To header field identifies the original recipient of the request designated by the user identified in the From field.  The original recipient may or may not be the UAS processing the request, due to call forwarding or other proxy operations.  A UAS MAY apply any policy it wishes to determine whether to accept requests when the To  header field is not the identity of the UAS.  However, it is RECOMMENDED that a UAS accept requests even if they do not recognize the URI scheme (for example, a tel: URI) in the To header field, or if the To header field does not address a known or current user of this UAS.  If, on the other hand, the UAS decides to reject the request, it SHOULD generate a response with a 403 (Forbidden) status code and pass it to the server transaction for transmission.

“To”报头字段标识由“From”字段中标识的用户指定的请求的原始收件人。由于呼叫转发或其他代理操作，原始接收方可能是处理请求的UAS，也可能不是。当“To”报头字段不是UAS的标识时，UAS可以应用其希望确定是否接受请求的任何策略。但是，建议UAS接受请求，即使它们不识别To标头字段中的URI方案（例如，tel:URI），或者To报头字段没有寻址该UAS的已知或当前用户。另一方面，如果UAS决定拒绝请求，它应该生成一个具有403（禁止）状态代码的响应，并将其传递给服务器事务进行传输。

   However, the Request-URI identifies the UAS that is to process the request.  If the Request-URI uses a scheme not supported by the UAS, it SHOULD reject the request with a 416 (Unsupported URI Scheme) response.  If the Request-URI does not identify an address that the UAS is willing to accept requests for, it SHOULD reject the request with a 404 (Not Found) response.  Typically, a UA that uses the REGISTER method to bind its address-of-record to a specific contact address will see requests whose Request-URI equals that contact address.  Other potential sources of received Request-URIs include the Contact header fields of requests and responses sent by the UA that establish or refresh dialogs.

但是，请求URI标识要处理请求的UAS。如果请求URI使用UAS不支持的方案，它应该使用416（不支持的URI方案）响应来拒绝请求。如果请求URI没有标识UAS愿意接受请求的地址，它应该用404（未找到）响应来拒绝请求。通常，使用REGISTER方法将其记录地址绑定到特定联系人地址的UA将看到其请求URI等于该联系人地址的请求。接收到的请求URI的其他潜在来源包括UA发送的建立或刷新对话的请求和响应的Contact报头字段。