Thanks for your response, Nathaniel. This makes sense. At this point I'd rather not change the sipXecs machine name, which would be required if I used a solution similar to yours.
If possible and not too complicated, I'd like to use the workaround mentioned (but not described) in the "DNS Concepts for sipXecs" page for scenario 1. Tony recently wrote "Remotes users resolve (via DNS SRV) to connect via port 5060". So why am I able to get calls through port 5080 and not 5060? I checked my firewall settings again and they appear to be correct (5060 udp, 5060 tcp, 5080 udp and ports 30000 - 31000 udp). On Wed, Jul 21, 2010 at 3:01 PM, Nathaniel Watkins < [email protected]> wrote: > Tim – this is what we are doing: > > > > Internal DNS (DNS/DHCP is entirely Microsoft based) and separate from our > external DNS server > > Internally: > > 1) Created a sipx.garrettcounty.org entry in DNS that resolves to > sipx internally (192.168.x.x) > > 2) Created SRV records internally for garrettcounty.org -> these > point to sipx.garrettcounty.org > > > Externally (We host our own DNS records – but internal users do not use > this for DNS resolution) –will be the same if your ISP hosts your DNS: > > 1) Created a sipx.garrettcounty.org entry in DNS that resolves to our > external IP address (the internet) > > 2) Created SRV records externally that point to > sipx.garrettcounty.org > > > > I believe they call this ‘split DNS’ – the nice thing about this – you can > take a phone that is at your desk and plug it in for a remote worker…if > you’ve done everything correctly, it will just work… > > > > The ports have nothing to do with DNS entries –5060/5080/30,000-31,000 are > just rules that need added on your firewall to allow traffic into the > sipXecs server. >
_______________________________________________ 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/
