It is used by the proxy on sipx1 when it wants to send a request to
the
registrar.
Is it so that in HA mode, sipxproxy queries for this quasi-domain to
obtain the registrar's address? So the rr comes from the way sipxproxy
implemented?
Regards,
Gabor
On Thu, 2009-07-02 at 10:02 +0100, Gabor Paller wrote:
It is used by the proxy on sipx1 when it wants to send a request to
the
registrar.
Is it so that in HA mode, sipxproxy queries for this quasi-domain to
obtain the registrar's address? So the rr comes from the way sipxproxy
implemented?
On Thu, 2009-07-02 at 10:02 +0100, Gabor Paller wrote:
It is used by the proxy on sipx1 when it wants to send a request to
the
registrar.
Is it so that in HA mode, sipxproxy queries for this quasi-domain to
obtain the registrar's address? So the rr comes from the way sipxproxy
implemented?
Hi,
I try to understand the High Availability DNS configuration and I am
stuck with these entries.
; sipx1.example.com routing for registry/redirect service
_sip._tcp.rr.sipx1.example.com. IN SRV 1 0 5070 sipx1.example.com.
_sip._udp.rr.sipx1.example.com. IN SRV 3 0 5070
On Wed, 2009-07-01 at 16:26 +0100, Gabor Paller wrote:
; sipx1.example.com routing for registry/redirect service
_sip._tcp.rr.sipx1.example.com. IN SRV 1 0 5070 sipx1.example.com.
_sip._udp.rr.sipx1.example.com. IN SRV 3 0 5070 sipx1.example.com.
_sip._tcp.rr.sipx1.example.com. IN SRV 2