Kyle, the concept with your SRV records looks right, but someone more 
knowledgeable than me will have to answer whether sipX can perform SRV lookups 
instead of A lookups. I'm thinking it performs A lookups in the out-of-the-box 
setup but I'm not sure if that's configurable. The reason I say that is that we 
have a second open-source sipX 3.10 server that our production (commercial) 
sipXecs 3.8.2 server passes calls to for student extensions, and at first the 
SRV records for that second server were messed up and its SIP clients wouldn't 
stay registered. However, long before I figured it out and fixed the SRV 
records for the 3.10 server (which the 3.8.2 server treats as an unmanaged 
gateway), calls could be passed to the 3.10 server from the 3.8.2 server, which 
leads me to believe it's using A lookups since they were the only thing 
working...

The way we do load balancing is maybe a little less high tech but it goes 
something like this: We have two PRI's and two Mediant 2000's. The median 
2000's are called gw2 and gw3. At the telco, the hunt group is set up so that 
inbound calls get routed first to the PRI  on gw3, then to the PRI on gw2 if 
the first one was full or down. On the sipXecs side, we first route calls to 
gw2, then to gw3, so that at any given time, most of the outbound calls are on 
gw2 and most of the inbound calls are on gw3. We set the hunt method on the 
Mediant 2000's to "descending" so that while the Telco's inbound calls are 
always trying channel 1 first, and we're always trying channel 23 first on 
outbound calls. In general the load is spread fairly evenly between the two 
gateways. In fact, if your telco is like ours, you may not be able to have 
inbound calls load-balanced between the two trunks very easily, so it may make 
more sense to adopt something like this if the goal is to have approximate!
 ly the same number of calls on each gateway at a given time. 

-Steve


-----Original Message-----
From: Kyle Haefner [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 8:52 AM
To: [email protected]
Subject: [sipx-users] Load balanced Gateways

Hello everyone,

I am looking to do load balancing across two gateways in SIPX.

Does SIPX use SRV records on gateway lookups?

I have an HA configuration and was considering the following zone file to load 
balance between two gateways.  I would set up an unmanaged gateway using 
gw.state.edu

Does this look like it will work?


Thanks!

Kyle


TTL 1D
@       IN      SOA    ns1.state.edu.  root.state.edu. (
                       200802134       ; serial#
                       3600            ; refresh, seconds
                       3600            ; retry, seconds
                       3600            ; expire, seconds
                       3600 )          ; minimum TTL, seconds
                NS     ns1.state.edu.   ; Inet Address of nameserver
state.edu.     MX     10 mail           ; Primary Mail Exchanger

ns1             CNAME  sipx1
mail            CNAME  sipx1

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; sipX Servers for SIP domain 'state.edu'
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
sipx1.state.edu.    IN      A       10.174.0.11
sipx2.state.edu.    IN      A       10.174.0.12

gateway1.state.edu.     IN      A       10.174.0.13
gateway2.state.edu.     IN      A       10.174.0.14

;state.edu.         IN      NAPTR   2 0 "s" "SIP+D2T" "" _sip._tcp.state.edu.
;state.edu.         IN      NAPTR   2 0 "s" "SIP+D2U" "" _sip._udp.state.edu.

_sip._tcp.otc.state.edu.    IN      SRV     1 0 5060 sipx1.state.edu.
_sip._tcp.otc.state.edu.    IN      SRV     1 0 5060 sipx2.state.edu.
_sip._udp.otc.state.edu.    IN      SRV     1 0 5060 sipx1.state.edu.
_sip._udp.otc.state.edu.    IN      SRV     1 0 5060 sipx2.state.edu.


_sip._tcp.gw.state.edu.    IN      SRV     1 0 5060 gateway1.state.edu.
_sip._tcp.gw.state.edu.    IN      SRV     1 0 5060 gateway2.state.edu.
_sip._udp.gw.state.edu.    IN      SRV     1 0 5060 gateway1.state.edu.
_sip._udp.gw.state.edu.    IN      SRV     1 0 5060 gateway2.state.edu.


; sipx1.state.edu routing for registry/redirect service
_sip._tcp.rr.sipx1.state.edu.       IN      SRV     1   0 5070 
sipx1.state.edu.
_sip._udp.rr.sipx1.state.edu.       IN      SRV     3   0 5070 
sipx1.state.edu.
_sip._tcp.rr.sipx1.state.edu.       IN      SRV     2 100 5070 
sipx2.state.edu.
_sip._udp.rr.sipx1.state.edu.       IN      SRV     4 100 5070 
sipx2.state.edu.

; sipx2.state.edu routing for registry/redirect service
_sip._tcp.rr.sipx2.state.edu.       IN      SRV     1   0 5070 
sipx2.state.edu.
_sip._udp.rr.sipx2.state.edu.       IN      SRV     3   0 5070 
sipx2.state.edu.
_sip._tcp.rr.sipx2.state.edu.       IN      SRV     2 100 5070 
sipx1.state.edu.
_sip._udp.rr.sipx2.state.edu.       IN      SRV     4 100 5070 
sipx1.state.edu.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to