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?
Regards, Maciej Aniserowicz -- View this message in context: http://n2.nabble.com/Question-about-rtp-timeout-sec-variable-tp4050650p4050650.html 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
