Hi folks,
RFC3261
sec 16.6 Request Forwarding
6. Postprocess routing information
If the proxy has a local policy that mandates that the request
visit one specific proxy, an alternative to pushing a Route
value into the Route header field is to bypass the forwarding
logic of item 10 below, and instead just send the request to
the address, port, and transport for that specific proxy. If
the request has a Route header field, this alternative MUST NOT
be used unless it is known that next hop proxy is a loose
router. Otherwise, this approach MAY be used,
so I think this means if the request contains no Router header, this
request might
be forwarded to a next element - either a strict-router or
loose-router- directly without
adding Route header.
However, the next sub section
7. Determine Next-Hop Address, Port, and Transport
The proxy MAY have a local policy to send the request to a
specific IP address, port, and transport, independent of the
values of the Route and Request-URI. Such a policy MUST NOT be
used if the proxy is not certain that the IP address, port, and
transport correspond to a server that is a loose router.
It totally forbids this forwarding-to-strict-router, ONLY loose router
is allowed.
Why there's such a difference?
thanks
Regards,
-Rockson
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
