On 11/03/2010 05:31 PM, Tony Graziano wrote: > At some point it gets exposed and hidden again. It would sure be nice to > have a configuration report where one could surmise a safe port range (or > have it suggest one for you). The log message is, in your case, right on > that there is a conflict, it's unfortunate you had to dig to find it.
I don't understand why these services bound to these high udp ports all of a sudden? We've been running a few weeks now with this config and yesterday the system started this. Is there no way to prevent them from using these ports? sipX config is very specific and I cannot find mention of e.g. sipregistrar==5060,5061,<high udp port range>. Our system's been dead for almost 24 hrs now due to this. :( -- ================================================================== Joe Micciche [email protected] Red Hat, Inc. http://www.redhat.com Senior Communications Engineer X(81) 44554 +1.919.754.4554 ================================================================== _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
