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.

On 2/5/2010 3:58 PM, Tony Graziano wrote:
I had posted some time ago to the dev list with no real replies. After looking through my FS logs, I see errors marked CRIT which happen sporadically throughout the day, and when the system boots up. The CRIT errors on bootup signify a FS config error where some unneeded statements should have been REMARKED out I think. The others pertain to CPU timing being lost as CPU usage goes through the roof and on new calls complaining about mismatched rates (again probably because the CPU is in a loop somewhere on FS).

Looking at the specific errors on the FS tracker, it's resolved, but since there are no patches being made to 4.0.4 the fixes are likely not getting in until 4.2. I would have a better sense of this if the unstable repo was updated and useable, but it's not been updated since December 24th.

On Fri, Feb 5, 2010 at 4:51 PM, mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com> <mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com>> wrote:

    On 2/5/2010 3:45 PM, Matt White wrote:

                    On 2/4/2010 at 10:27 AM, in message

        <d99f07871002040727i13924393o730eb2b486208...@mail.gmail.com
        <mailto:d99f07871002040727i13924393o730eb2b486208...@mail.gmail.com>>,
        Tony Graziano
        <tgrazi...@myitdepartment.net
        <mailto:tgrazi...@myitdepartment.net>>  wrote:

            I don't think anything will go down. I think it's a stuck
            process.


        Anybody make any head way with this.  This has begun to occur
        on two of our installs.  Logging into the GUI and restarting
        "media services" clears it up for a while.

        -M


    It didn't happen to me today (first time in 3 days), so I didn't
    get to troubleshoot.



_______________________________________________
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/

Reply via email to