Problems in resolv.conf (search domain is wrong, and it overwrote the nameserver):
4.4: [root@sipx ~]# cat /etc/resolv.conf search murray-hotel.com nameserver 192.168.44.1 [root@sipx ~]# 4.6: # cat /etc/resolv.conf # Generated by sipXecs search sipx.murray-hotel.com nameserver 127.0.0.1 [root@sipx ~]# manually edited resolv.conf in 4.6 to match 4.4 verified forward and reverse lookups from command line, but phones still don't register with 4.6: [5] 23/12/2001 17:00:22:Opening TCP socket on port 5060 [3] 23/12/2001 17:00:22:Invalid Date: 23.12.2001 Time: 17:00 [2] 14/7/2012 18:46:05:start_dst(1331431200) end_dst(1351994400) offset_dst(3600) offset_utc(-25200) [2] 14/7/2012 18:46:05:start DST: 03/11/2012 02:00:00 (1331431200) [2] 14/7/2012 18:46:05:end DST: 11/04/2012 02:00:00 (1351994400) [5] 14/7/2012 18:46:06:timeout::callback: Registering with timeout of 0 ms [5] 14/7/2012 18:46:06:Add dirty host: udp/192.168.44.30/5060 [5] 14/7/2012 18:46:06:timeout::callback: Registering with timeout of 0 ms [2] 14/7/2012 18:46:06:Transport Error: Pending packet 1000000: generating fake [2] 14/7/2012 18:46:06:Registrar [email protected] timed out [5] 14/7/2012 18:46:16:Applying Settings... [5] 14/7/2012 18:46:17:Settings applied! [5] 14/7/2012 18:47:07:timeout::callback: Registering with timeout of 0 ms [5] 14/7/2012 18:47:07:Add dirty host: udp/192.168.44.30/5060 [5] 14/7/2012 18:47:07:timeout::callback: Registering with timeout of 0 ms [2] 14/7/2012 18:47:07:Transport Error: Pending packet 1000002: generating fake [2] 14/7/2012 18:47:07:Registrar [email protected] timed out On Jul 14, 2012, at 18:36 , Kurt Albershardt wrote: > DNS on the sipx box? I've not done anything there, just in pfSense (which is > authoritative for the zone.) When I query the local resolver with the name, > I get 127.0.0.1 > > Both forward and reverse lookups are checked from a workstation before I try > to register phones. The phones resolve the name in order to pull the config > file. > > > On Jul 14, 2012, at 18:01 , Tony Graziano wrote: > >> Please verify the DNS zone is running. It sounds like DNS is not working. >> There is a known issue with DNS in regard to the build. If it is not running >> please change the zone serial number to YYYYMMDDXX save the zone and ensure >> named is running then try again. >> >> On Jul 14, 2012 7:51 PM, "Kurt Albershardt" <[email protected]> wrote: >> After building, destroying and re-building nearly 20 VMs over the past few >> days, I now am confident that I have a reproducible failure getting Snom 320 >> phones to register with 4.6: > > _______________________________________________ > 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/
