On Mon, 2009-11-09 at 12:20 -0600, [email protected] wrote: > On Mon, 9 Nov 2009 12:12:15 -0500, Tony Graziano wrote: > > Yes. It registered just fine (using sipdomain.com, not host.sipdomain.com). > > This is the public side DNS setup. > > sipdomain.com. IN NS ns1.mydomain.com. > sipdomain.com. IN NS ns2.mydomain.com. > > $ORIGIN sipdomain.com > > hst1.sipdomain.com. IN A (wan ip #1) > hst2.sipdomain.com. IN A (wan IP #2) > _sip._tcp.sipdomain.com. IN SRV 10 50 5060 hst1.sipdomain.com. > _sip._tcp.sipdomain.com. IN SRV 10 50 5060 hst2.sipdomain.com. > _sip._udp.sipdomain.com. IN SRV 10 50 5060 hst1.sipdomain.com. > _sip._udp.sipdomain.com. IN SRV 10 50 5060 hst2.sipdomain.com. > > Someone had told me at one time that I didn't need the following records; > > sipdomain.com. IN NAPTR 2 0 "s" "SIP+D2T" > "" _sip._tcp.sipdomain.com. > sipdomain.com. IN NAPTR 2 0 "s" "SIP+D2U" > "" _sip._udp.sipdomain.com.
those records tell whoever gets them that your system can use either TCP or UDP (but not TLS, because there's no record that says it can). Many SIP implementations (including most components of sipXecs) will just assume that those two both work if there are no NAPTR records. _______________________________________________ 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/
