Your REGISTER is something like:
REGISTER sip:example.com
To: sip:[EMAIL PROTECTED]
...
The endpoint sends this like any other request. If there is a Route
header, then the first entry is used to determine the next hop. Or if
you just hava a default proxy you use, it may be the next hop.
Otherwise, the next hop is determined from sip:example.com. If other
proxies are involved, one of them will eventually route based on
sip:example.com.
RFC3263 says how to route to sip:example.com. In normal systems that
would be a proxy. It may also be a registrar and handle the registration
request directly. Or it may decide to proxy the request to a separate
server that handles registrations. The choice is its to make. To the UAC
this is just a normal request.
Paul
Huang Xiaoqian wrote:
> Hi,
> I have some confusion about REGISTER request routing.When registrar/proxy
> co-location,UA sends REGISTER request to the registrar/proxy co-location.But
> when registrar/proxy not co-location, will UA send the REGISTER request to
> proxy first and then be forwarded to the registrar by the proxy,or UA send
> the REGISTER request to the registrar directly according to the register URI.
>
> Best Regards
> Qian
>
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
