@Tony: It is not that. I'm aware of 4.2.1 DNS slave misconfiguration (all times expire in 1800seconds). I have manually changed the times to proposed ones in jira. And the problem is immediate, as soon as I change the public port on the second sipx.
@Douglas: I don’t think it is the DNS. It looks fine in the advisor and the files. We actually tried a couple of different HA approaches with the DNS, including master-master with manual tuning.. It is not DHCP either. We tried 3 different combinations (external, on sipx1, dual DHCP with DHCP safe failover protocol) Why exactly is it proposed in WIKI to change the public port on the secondary sipx in HA configuration to support remote workers? It seems to work fine even if primary and secondary have the same public port (tested with just 1 remote endpoint) Regards, On Mon, Jan 24, 2011 at 4:11 PM, Douglas Hubler <[email protected]> wrote: > On Mon, Jan 24, 2011 at 5:51 AM, Tony Graziano > <[email protected]> wrote: > > it sounds like an internal dns issue. I "think" there is a JIRA on this. > > > > How long before the local phones stopped being able to register, 30 > minutes? > > I found the DNS advisor found in the System menu fairly useful to check DNS > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Irena Dolovčak
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
