On Thu, 2008-12-11 at 13:26 -0500, Dale Worley wrote: > I'm attempting to start the proxy in the latest development code. I see > these error messages: > > "2008-12-11T18:17:16.449011Z":158:NAT:ERR:victoria-pingtel-com.us.nortel.com:pid-13142:00000000:SipXProxy:"NatTraversalRules::initializeNatTraversalInfo > - No child Node named 'publicaddress', using host IP: '47.16.90.165'" > "2008-12-11T18:17:16.449063Z":159:NAT:ERR:victoria-pingtel-com.us.nortel.com:pid-13142:00000000:SipXProxy:"NatTraversalRules::initializeNatTraversalInfo > - No child Node named 'stun-server-address'" > > Those make sense, since my etc/sipxpbx/nattraversalrules.xml doesn't > have those elements. > > However, I have NAT Traversal disabled in sipXconfig, so either the NAT > Traversal function in the proxy should not be trying to start, or > sipXconfig should provide a suitable dummy configuration that does not > cause errors on startup. > > The etc/sipxpbx/nattraversalrules.xml file is newly created, which makes > sense since I just started sipX. But it's not clear why there is no > publicaddress element, as the Public IP Address field in the GUI is > present. STUN Server Address is empty in the GUI, which is legal, but > it's not clear why that causes sipXconfig to generate a > nattraversalrules.xml that sipXproxy complains about.
Does this cause any problem other than 'ERR' entries in the log file? I believe that sipXconfig just isn't generating the latest version of the config file yet. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
