Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <6369cb70bfd88942b9705ac1e639a33821f6fbb...@dc-us1mbex4.global.avaya.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <43569> Message-ID: <[email protected]>
Quote: > Correct, seems like the port conversion is not > happening. Can you check your alarm history under the > Diagnostcis section of sipXconfig to see if the sipXproxy > complains about not being able to enable the NAT traversal > service? > > Also, did you restart the sipXproxy and sipXrelay > services after you have finished configuring the NAT > traversal feature on sipXecs? > > WRT to your port range, I don't think its wide enough. > You may have hit on a bug here but I believe that you need > a minimum range of 8 (sipXconfig should really police > that) I have checked Diagnostics -> Alarms page, but I don't see any alarm history there. Only type of alarms. Probably alarm history is empty...maybe its not implemented in version 4.0.4 I'm using now. I have enabled notification on alarms, but no emails I have received, even after restart of server (linux server restart). I always restart services after configurations, at least because sixconfig complains about this. And also I have restarted that linux server maybe 30 times laready, and it stil doesn't work :) I have increased port range from 31112 to 31128 and still on my far end nat machine I'm receiving office local ips in CONTACT sip headers. I really need to make some diagram to explain current situation what I have now :) _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
