On Fri, 2010-02-05 at 16:21 -0600, mkitchin.pub...@gmail.com wrote: > I'm relatively new to sipx, but it would seem to me that there should > be a sipx bug report opened on this. Am I missing something? Without > some method of tracking it, does anyone that there is even a change in > 4.2 that might fix this? Does the version of Freeswitch change? It > isn't going to be pleasant to have to deal with this issue until 4.2, > but it would help to know there is at least hope. That is my $.02.
Agreed, but so far the only information we could put in an issue is "sometimes freeswitch sucks up the entire cpu". We don't know what configurations those systems have, or what event triggers it. As one of the people that screens New issues, I can promise that that report would just be returned with a request for more information. If someone can get a core file while this is happening, and take a snapshot that includes the symbol data (this must be done from the command line: see sipx-snapshot --help) and attach that too an issue, then we'd have a starting point. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
