SIP over UDP has no way of knowing the other side has lost connectivity (eg wifi down). Sip droid will know the local network is down and be able to hang up the call because of that. FreeSWITCH has no such knowledge, so won't know the call is hung up and will continue sending RTP.

3 possibilities are:
1) Use session timers
2) There is a parameter to hang up a call is no RTP has been received for a certain period of time
3) Use SIP/TCP, keepalives might help (but the default is measured in hours)

Note that all of these are timeouts - you simply won't be able to know the call has ended immediately.

Steve



On 30 Apr 2013, at 08:33, Farrukh Ali <smfarrukh@live.com> wrote:

Hi,

I need some help, there is an issue in Freeswitch with SIP clients, when a call is not hung up properly Freeswitch does not close its RTP channels, and it starts to get load on bandwidth after too many dead channels are generated, Improper hang up means if during call sip client went out of the range of WiFi, the client i.e SipDroid shows call hang up but freeswitch continues to send voice packets. Kindly reply
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.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