1. h323-conf-id should be fine in most cases. 2. You definitelly found a bug. I've just commited a fix to the cvs, thanks! ----- Original Message ----- From: "Razvan Radu" <gnugk@xxxxxxxxxxxxxxxx> Sent: Friday, July 09, 2004 6:15 PM > hello, > > I am trying to unique identify a call in the accounting send by several > equipments in the following configuration: > > originating gw --> gnugk --> terminating gw > > unfortunately I have to process the accounting sent by all of this > equipments and I want to use the h323-conf-id attribute witch the > documentation says that is unique across all traversing devices. > > Is this true ? I am concern about h323-incoming-conf-id attribute on the > cisco gws. Is it possible that some equipments will rewrite this call > parameter ? can I base my accounting scheme on this h323-conf-id ? > > thanks > Razvan Radu > > > P.S. I am using gnugk-2.0-cvs as of 2004-07-08 and I see that my old > configuration regarding explicit authentication on the status port 7000 > does no longer work. Is it possible that the line: > > GkConfig()->GetString(authsec, peer, ""); > > in file GkStatus.cxx, should be: > > val = GkConfig()->GetString(authsec, peer, ""); ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
