Juha,
In that case "example.com" would be the server interface (and configured as
such in DNS SRV). Clients would be given "x.example.com", where x can be
anything you like (or "x.y.z", as long as you control the y.z domain in DNS
SRV)
It's not exactly the same as for XMPP, where you say each element uses a
prefix based on its role. But it would have a similar effect of separating
preferred protocols (and other SRV attributes) per client
(registration/outbound) versus other elements (e.g. proxies)
Regards,
Jeroen
Juha Heinanen wrote:
Jeroen van Bemmel writes:
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).
i don't get this. the domain of SIP UAs' SIP uris is example.com for
which the queries are done, not something else. clients would need to
prefix that with _sip-client and servers with _sip-server. currently
there is no standard for that.
-- juha
_______________________________________________
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
