Kurt, sipXecs relies 100% on the accuracy of DNS. One of the beautiful things about this product, especially for a small installation, you can have DHCP and DNS right on the server. I think that makes for a much cleaner installation that trying to rely on the firewall (PFSense) for those duties. In using the DNS and DHCP, you will automagically have Option 66 enabled and configured correctly, DNS configured correctly, etc. for a fast, turnkey installation.
It seem you have opted to go a different route. If you continue down that path, I'd recommend you get familiar with Diagnostic Tests from the GUI, and sipviewer, a free tool you can find on the wiki that will help you read the registrations, and other sip events to understand why things aren't working correctly. There are some troubleshooting tools on the wiki as well which will help you do tracing of sip messaging, packet captures, etc. Once you start reading these log files, or sharing them with the user community, you will be able to resolve your issues much quicker. It would be hard to help diagnose your DNS issues without seeing some details trace files of what is actually failing. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kurt Albershardt Sent: Sunday, July 15, 2012 2:46 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Snom 320 phones registering with 4.4 but not with 4.6 On Jul 15, 2012, at 2:38 , Michael Picher wrote: > resolv.conf isn't going to help your phones any... it's just for that server itself. It tells the server where to go for DNS. For someone who is quite familiar with DNS, what is the issue I'm trying to solve? > where are the phones getting DHCP from, and can you verify that the phones have proper addressing / options? A pfSense gateway (at 192.168.44.1) provides both DHCP and DNS for the segment. They are getting proper DHCP address assignments (on screen every time they boot.) The DHCP server does not properly handle options 66 & 67, so I've hard-coded the settings URL into their webUIs. All phones pick up their assigned DHCP address at boot and are resolving names (or they could not pull the config XML.) > Try hardcoding a phone with the IP & DNS and see what happens. Did that earlier while I was debugging. I can try again... _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
