On Sun, 9 Jan 2011 10:56:24 -0500, Tony Graziano wrote: > this is correct. it does not have any of the pf6 stuff in it.
I'm back at this but I'm very nervous about making any changes that would suddenly break remotes. I'm still not clear on why this is working as this is the public record I've been using for some time now. What is it about this setup that's wrong? Remote phones are using mydomain.com as their registrar and seem to get in as they should. pf.mydomain.com. IN A 173.8.107.75 - This is the pfsense server and gateway sipx.mydomain.com. IN A 173.8.107.75 - This is the sipx server which has a private address NATed to this mydomain.com. IN NAPTR 2 0 "s" "SIP+D2T" "" _sip._tcp.mydomain.com. mydomain.com. IN NAPTR 2 0 "s" "SIP+D2U" "" _sip._udp.mydomain.com. _sip._tcp.mydomain.com. IN SRV 1 1 5060 pf.mydomain.com. _sip._udp.mydomain.com. IN SRV 1 1 5060 pf.mydomain.com. _sip._tcp.rr.pf.mydomain.com. IN SRV 1 0 5070 pf.mydomain.com. I think the rr record is useless and should be; _sip._tcp.rr.sipx.mydomain.com. IN SRV 1 0 5070 sipx.mydomain.com. The sipx server itself is generating the following and doesn't know about the pfsense firewall. Call Routing for SIP domain 'mydomain.com' sipx.mydomain.com. IN A 192.168.1.220 mydomain.com. IN NAPTR 2 0 "s" "SIP+D2T" "" _sip._tcp.mydomain.com. mydomain.com. IN NAPTR 2 0 "s" "SIP+D2U" "" _sip._udp.mydomain.com. _sip._tcp.mydomain.com. IN SRV 1 0 5060 sipx.mydomain.com. _sip._udp.mydomain.com. IN SRV 1 0 5060 sipx.mydomain.com. _sip._tcp.rr.sipx.mydomain.com. IN SRV 1 0 5070 sipx.mydomain.com. _xmpp-server._tcp.mydomain.com. IN SRV 1 0 5269 sipx.mydomain.com. _xmpp-client._tcp.mydomain.com. IN SRV 1 0 5222 sipx.mydomain.com. _xmpp-server._tcp.conference.mydomain.com. IN SRV 1 0 5222 sipx.mydomain.com. _xmpp-client._tcp.conference.mydomain.com. IN SRV 1 0 5222 sipx.mydomain.com. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
