Jeff, In my session hanguphook I call: if (Session != null && Session.HookState == switch_channel_state_t.CS_HANGUP) { Session = null; } All calls to the session in my app are as follows: if (Session != null && Session.Ready()) This is to prevent calls to dead FS sessions. Without this, the Session object exists, but calling it on a hungup session (even calling Session.Ready()) causes the object not found error. This is under load. Maybe it is timing issue. I don't need to do this with just a couple of calls. Does that make any sense? Hopefully I am not completely off base here? I read elsewhere in this list that the HangupHook does not fire 100% of the time - Anthony has just pushed change. I will check it with that. Phil On Tue, Jul 27, 2010 at 3:21 PM, Jeff Lenk <jeff@jefflenk.com> wrote:
Are you sure the very thing you are doing by setting the manages session to null is not what is causing the error?
Just a thought :) -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/ERR-switch-cpp-910-object-is-n... Sent from the freeswitch-users mailing list archive at Nabble.com.
_______________________________________________ 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