Hi All, I am running into an intermittent problem with outbound calling. I originate calls (using FreeTDM to Sangoma hardware) from a lua script, and every so often (10-50% of the time) the call disconnects just as the endpoints answers the call. I am executing these calls identically and to the same phone number. Here is CLI output for a call that doesn't disconnect: http://pastebin.freeswitch.org/15409 And here is an example of one that does upon answering on the endpoint: http://pastebin.freeswitch.org/15408 I noticed that one difference is that in the disconnected call there is the following output: 2011-02-17 23:11:48.747752 [DEBUG] switch_core_state_machine.c:204 FreeTDM/2:1/09586550654 Standard SOFT_EXECUTE 2011-02-17 23:11:48.747752 [DEBUG] switch_core_state_machine.c:372 (FreeTDM/2:1/09586550654) State SOFT_EXECUTE going to sleep *2011-02-17 23:11:48.747752 [DEBUG] switch_cpp.cpp:981 FreeTDM/2:1/09586550654 destroy/unlink session from object* 2011-02-17 23:11:48.747752 [DEBUG] switch_channel.c:2535 (FreeTDM/2:1/09586550654) Callstate Change ACTIVE -> HANGUP I'm wondering what's triggering that destroy/unlink. I've taken this issue up with Sangoma support, they are saying that there is nothing from the HW side that would trigger this, though freeTDM may possible be passing back some variables in a way that causes this and subsequent callstate change. In case it's useful, pcaps for the normal,connected call and disconnected fault call are attached. Thanks in advance, Neil