I'd not recommend dropping calls by sending a DRQ. This may not always work (especially, when NAT comes into play). Instead, enable DropCallsByReleaseComplete and similar options in the config and modify SendReleaseComplete and/or call CallRec::SetDisconnectCause/CallRec::SetReleaseSource before sending ReleaseComplete and clearing the call. ----- Original Message ----- From: "Amir Hossein Shenavandeh" <shenavandeh@xxxxxxxxx> Sent: Monday, February 12, 2007 2:16 AM Subject: Re: Returned causeCode > Sorry .. > As I understood DRQ does not carry any H225 cause Code and the Code is > reported by endpoints . > But how do an Openh323 endpoint reacts by reciving each of e_forcedDrop, > e_normalDrop, e_undefinedReason ? > and is SendReleaseComplete used when calls are NATed ? > Am I totaly wrong ?! ;) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
