It probably means that there's a mutex that's been locked by something but not rleaseed. First, upgrade your version to the latest git. It's possible it's a bug that's already been fixed. If you can reproduce it on the new version, install gcore and collect a corefile while FS is hung: http://wiki.freeswitch.org/wiki/Debugging_Freeswitch#Simple_bash_script_to_m... and open a Jira ticket with the results at http://jira.freeswitch.org/browse/FS -Steve On 27 October 2010 10:27, Khurram Shafi <khurram@breezecom.ae> wrote:

Hello,

I am having strange behavior of FS Sofia profile being locked up after running 1200+ calls for 2-3 hours.

There is nothing in logs. FS internal profile which is set on port 5060 simply stops listening on port 5060 and accepts no calls on it.

I m running FreeSWITCH Version 1.0.head (git-b834a0e 2010-09-19 16-59-58 -0500)

Regards

_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org