It is not present, since there is no "connect" event for unconnected calls. I know Cisco gateways send h323-connect-time everytime, but we do not send also other attributes the gateways send - so we are not 100% Cisco compatible either. With the new h323-connect-time present/not present rule it is easy (and 100% reliable) to separate unconnected calls from connected calls. Also h323-setup-time is not always sent - if the call is admitted (ACF) but signalling channel has not been opened, only h323-disconnect-time will be sent. This behaviour gives finer call flow details. I am considering to write a small patch (or a small derived authenticator - OnSendPDU overriden) for those who need the old behaviour (all h323-xxx-time attributes always sent) - if there are many such gk users. ----- Original Message ----- From: "Oleg Ustinov" <Oleg.Ustinov@nectis.com> Sent: Tuesday, September 30, 2003 5:10 PM > Just one question more. > In new release 2.0.6, if call is not connected gnugk sends RADIUS no > h323-connect-time. > Can you check it, please? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
