Yes I did: Two different A records (not CNAMEs). I set a different branch for each gateway and made sure the "shared" checkbox was not checked. The way my system is currently set up is I have one main "shared" Audiocodes mediant 1000 with a PRI connection to the outside world. In the dial plan I put all the non-shared gateways that sipX should try before the main shared gateway (for location based dialing) in the dial plan order and then add the non-shared "emergency dial" gateways (in the event the main gateway is down) after the shared gateway in the dial plan order.
In the case of the gateway that required two hostnames, I have a need for two extensions (6177 and 6536) to use that gateway "before" the shared gateway and another group of extensions to use it "after" the shared gateway so in the event the audiocodes gateway is unavailable the local gateway can be used. What actually happened when I set it up that way was that all of the extensions that pointed to the two different hostnames would stop at the first gateway (I am assuming because the IP matched even though I was using A records) that was supposed to be used by the two extensions 6177 and 6536. Did any of that make sense? What kind of logs should I gather? Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 6/21/2010 2:30 PM, WORLEY, Dale R (Dale) wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Josh Patten > [[email protected]] > > OK this didn't work. The hostname method simply causes sipX to see them > as the same gateway so a match on one gateway will be a match on the other. > _______________________________________________ > > It *ought* to work! Did you use two *different* hostnames whose A records > give the same IP address? > > Dale > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
