Take a look at a pcap of the traffic, I suspect the other side still has media flowing.
On Nov 23, 2009, at 7:00 AM, Maciej Aniserowicz wrote: > > Hello, > I have 2 instances of FS: one controlled by my application (making calls > with TCP commands, recording sessions, listening to events etc) and one > acting as a remote gateway to which all users register. When I leave the > default values of rtp-timeout-sec and brutally kill x-lite during > conversation, the 'hangup' event with 'media_timeout' cause is obviously > sent after the default 5 minutes (and until then, the other leg is still > connected to a 'dead' channel). > The question is: which FS instance is responsible for terminating the > connection after timeout? Only the 'remote' FS instance config seems to > work. I thought that the shortest configured value should cause the timeout, > but it's not the case. Am I missing something, or is this the correct > behavior? _______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
