This is the document I was thinking about. Ignoring the views part of it,
you simply get to the meat of the matter...

http://wiki.sipfoundry.org/display/xecsuser/DNS+Concepts+for+sipXecs

The document title is not what the whole thing is about. Here you see the RR
(resource record) for sip1/sip2/sip3 weighted differently but the SIP (both
udp and tcp) all has the same priority, so there is no preference set on
that.

In this example the SIP SRV records all have the same priority. The document
explains "views", but no matter how you do it, you can set a different
priority for DNS based on the value (1,2,3, 10, 20, 30, 100,200,300, it is
just a weight). The DNS must also be stated to be MASTER on the MASTER and
SLAVE on any HA members (/etc/named.conf). So internally you can create
views that say "if you come from this network A I want you to have sip1 as
first priority and if thats not there sip2 is second. If you come from
network B I want to change the priority around. This is how you would do
"qwasi" load balancing based on DNS, etc.

example.com.            IN     NS     sip1.example.com.example.com.
        IN     NS     sip2.example.com.example.com.            IN
NS     sip3.example.com.
example.com.            IN      NAPTR   2 0 "s" "SIP+D2T" ""
_sip._tcp.example.com.example.com.              IN      NAPTR   2 0 "s" 
"SIP+D2U" ""
_sip._udp.example.com.

_sip._tcp.example.com.  IN      SRV     1 0 5060 sip1.example.com.
_sip._udp.example.com.  IN      SRV     1 0 5060 sip1.example.com.

_sip._tcp.example.com.  IN      SRV     1 0 5060 sip2.example.com.
_sip._udp.example.com.  IN      SRV     1 0 5060 sip2.example.com.

_sip._tcp.example.com.  IN      SRV     1 0 5060 sip3.example.com.
_sip._udp.example.com.  IN      SRV     1 0 5060 sip3.example.com.

_sip._tcp.rr.sip1.example.com.  IN      SRV     1   0 5070 sip1.example.com.
_sip._tcp.rr.sip1.example.com.  IN      SRV     2 100 5070 sip2.example.com.
_sip._tcp.rr.sip1.example.com.  IN      SRV     3 100 5070 sip3.example.com.

_sip._tcp.rr.sip2.example.com.  IN      SRV     1   0 5070 sip2.example.com.
_sip._tcp.rr.sip2.example.com.  IN      SRV     2 100 5070 sip1.example.com.
_sip._tcp.rr.sip2.example.com.  IN      SRV     3 100 5070 sip3.example.com.

_sip._tcp.rr.sip3.example.com.  IN      SRV     1   0 5070 sip3.example.com.
_sip._tcp.rr.sip3.example.com.  IN      SRV     2 100 5070 sip1.example.com.
_sip._tcp.rr.sip3.example.com.  IN      SRV     3 100 5070 sip2.example.com.



On Fri, Sep 17, 2010 at 5:02 PM, Douglas Hubler <dhub...@ezuce.com> wrote:

> On Fri, Sep 17, 2010 at 3:58 PM, Tony Graziano
> <tgrazi...@myitdepartment.net> wrote:
> > On Fri, Sep 17, 2010 at 3:44 PM, Mark Theis <mth...@socaltelephone.com>
> >> I know about the DNS SRV records and I think that I have it setup
> >> correctly, but… maybe I don’t and it is causing me the problems. Would
> it be
> >> bad to post my domain name here so someone (who feels like it), could
> look
> >> at the DNS records?
> > Sure. Feel free to change the SIPDOMAIN and IP's (find and replace).
> There
> > should be a good example on the wiki. Let me find it and send it to you.
>
> If you find it, please let me know, I'm currently struggling with this
> myself on 4.2.1 install.   I have a wireshark where when i shutdown
> primary, the secondary node gets contacted then returns 404 and I
> cannot figure out why.
>
> Relevant DNS is this
> ===============================
>
> hubler.us.      IN      NAPTR   2       0       "s"     "SIP+D2T"
>  ""      _sip._tcp
> hubler.us.      IN      NAPTR   2       0       "s"     "SIP+D2U"
>  ""      _sip._udp
>
> finch   IN      A       192.168.1.173
> _sip._tcp       IN      SRV     1       0       5060    finch
> _sip._udp       IN      SRV     2       100     5060    finch
> _sip._tcp.rr.finch IN   SRV     1       0       5070    finch
> _sip._udp.rr.finch IN   SRV     2       100     5070    finch
>
> parrot          IN      A       192.168.1.171
> _sip._tcp       IN      SRV     1       0       5060    parrot
> _sip._udp       IN      SRV     2       100     5060    parrot
> _sip._tcp.rr.parrot IN  SRV     1       0       5070    parrot
> _sip._udp.rr.parrot IN  SRV     2       100     5070    parrot
>
> Proxy log on secondary node's proxy
> ==============================
> "2010-09-17T21:00:32.733957Z":13125:SIP:ERR:finch.hubler.us:
> SipRouter-11:41E9A940:SipXProxy:"SipUserAgent::send
> outgoing call 1"
> "2010-09-17T21:00:32.735080Z":13126:SIP:WARNING:finch.hubler.us:
> SipSrvLookupThread-19:41A84940:SipXProxy:"DNS
> query for name 'rr.finch.hubler.us', type = 1 (A): returned error"
>

What is the SOA on finch? Is the named.conf setup as SLAVE?

>
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to