On Wed, 13 Oct 2010, Tony Graziano wrote:
> Yes. You need DNS SRV records.
>
> _sip._udp.SIPDOMAIN.TLD. IN SRV 1 0 5060 hostname.SIPDOMAIN.TLD.
> _sip._tcp.SIPDOMAIN.TLD. IN SRV 1 0 5060 hostname.SIPDOMAIN.TLD.
>
> As a minimum for sip. These need to be hosted at the domain
> name server for your primary domain name (as a minimum).
I guess the question becomes -- What unit is a 'consumer' of
those SRV records? On the chart at:
http://www.myitdepartment.net/support/sipx_bridge_pfsense_bandwidth-dot-com.pdf
I had understood that the sipXecs unit behind the firewall
(upper right corner) was reaching out to, and transferring
non-local content in and out across a 'trunk' to a
counterparty sipXecs ISP (lower right corner)
The sipXecs ISP (lower right corner) is out in fully routable
space, and in in turn is connection and authentication to [in
this example] bandwidth.com (center lower cloud). Why do we
care where the unit behind the fireswall is, as it will never
receive direct content, as I understand the setup
[I may be wholly wrong here, and some unit other than the
sipXecs ISP may be initiating connections ... ]
I ask, because we added support in our DNS management GUI for
SRV records for a customer wanting it for FreeSwitch support,
but we cannot see any queries hitting it in our domain query
logs A sanitized version of a zone file, not showing that
customer's details, is at:
http://gallery.herrold.com/pmman_srv.png
-- Russ herrold
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
