Jeroen van Bemmel wrote:
Juha,
For clients one would distribute "client-interface.example.com" as the
outbound proxy FQDN to use, and upstream proxies would be given
"server-interface.example.com" (by using that as domain in AORs).
For R-R, the proxy would use "client-interface.example.com" if it
performed a location service lookup (i.e. assuming that next hop is
then an endpoint), or "server-interface.example.com" otherwise.
Nevertheless, in the R-R it would probably be better to be explicit
about the transport to use, and not rely on DNS SRV. Then there is no
need to worry about client vs server interface protocol preferences,
or proxies that use dynamic registration, or DNS SRV misconfiguration
or lack of support for it.
I agree with the last point, but does everybody agree?
I would really like to know because this exactly the type of scenario I
would like to see clarified in draft-froment-sip-record-route-fix-00...
Thomas
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
