I dont know why this is. In the meantime why dont you adjust media relay ports to compensate so the system is functional while an answer can be looked into?
(i.e. 30000-42000) On Wed, Nov 3, 2010 at 5:38 PM, Joe Micciche <[email protected]> wrote: > 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 > ================================================================== > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
