Hello, Observed that, in release-4.4, if sipxecs-setup script is executed again on a working system (without changing the domain name), sipXproxy fails on its configuration tests. This is because the sipxecs-setup script adds another zone record of same domain to the /etc/named.conf without checking for duplicates. Opened an issue on tracker about this: http://track.sipfoundry.org/browse/XX-10357
To solve this I thought of 2 possible solutions: - Not adding a new zone clause for the same domain if there is an existing one - Deleting the old record for the same domain and adding it again I do not know whether these zone records are changed/updated frequently on working systems. So I am not sure on which solution above I should proceed. Any idea? Regards, -- Kemal EROĞLU Karel Electronics R&D Center Cyberpark, Bilkent 06800 Ankara +903122650290/3234
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
