To run dns onboard, would like to confirm if the procedure is identical to that for a CD version. (i.e as per what is shown the Quickstart). Reason for asking we started it on AWS and it hung after the 50% mark. Or do we need to follow the procedure described in http://wiki.sipfoundry.org/display/sipXecs/DHCP+and+DNS+Server+Configuration .
We have a AMI instance with elastic IP which obviously is on a different subnet then the Amazon Gateway IP. Could this be why the installation hung. On Tue, Jun 14, 2011 at 7:45 AM, Tony Graziano <[email protected] > wrote: > you would be better served to install sip locally to understand d things > like dns, logging and nat traversal before employing this in an aws > environment.environment IMO. > > /var/log/sipxpbx > > is where the logs are kept. > > your aws firewall must be using a symmetrical port nat type. > > I think if you run the dns advisor it will give you the records you need. > you are well advised to run dns onboard as well. > > good luck. > On Jun 14, 2011 7:28 AM, "Nalin Mistry" <[email protected]> wrote: > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
