Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <61930> Message-ID: <[email protected]>
I have a sipx box (latest x64 iso) deployed at a site which uses a draytek vigor 2820 for dhcp and as nat router to wan, and we have a Microsoft DNS server for the required records (all present except the rr. srv Record). We found that the setup works perfectly until the server is rebooted which causes the server to fail to register with ITSP. This continues until the router is rebooted. To recreate this fault, at our head office, I have a nat pfsense router, but as this is for our production envoironment/office lan I have a draytek vigor 2820 with the office lan plugged into the wan2 side of it and I have created another mini lan for testing. In this setup stun didn't correctly work so I manually entered the wan ip in sipx Within this mini lan, the sipx server is serving dhcp and dns with domain name voip.local. I have found if the draytek has dhcp on, the server will never re-register on rebooting. If the draytek has dhcp off then the server will successfully re-register for the first reboot only. At first I was not using correct domain name on the draytek but this has been specified and issue remains. The only major difference should be that we have the rr. SRV record as sipx is serving dns. However if I swap out the draytek with a pfsense set up in the same manner, the server has no problem after any number of reboots. The differences I have determined from the packet traces are that when it fails to re-register: I can see the SIP keep alives still coming from ITSP and the server will reply with ICMP port unreachable during boot period when it is going to work but it doesn't reply unreachable when booting if it is not going to work. Then the next difference I have determined is that if it works, the server first attempts to register with ITSP without authentication - ITSP returns a 401 unauthorized. It then immediately attempts again with authentication and succeeds. However whenever it fails to work, the server does keep trying and I can see two successive attempts numerous times but does not attempt with authentication on any of these attempts. Strange thing is once I've rebooted the router the server behaves fine. I have numerous packet traces which show the same thing and no difference between using the two routers except some of the mdns packets and the order of a few packets, but I'm certain I must be missing something. Does anyone have any ideas on what I could be doing wrong or could this be a bug worth reporting. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
