Re: Acct-Session-Id in 2.2.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



That's perfectly ok. The session id had to be changed to become more globally unique.
It consists of two parts: 32 bit base (8 hex digits) and 32 bit counter (8 hex digits).
The base is formed from timestamp when the gk has been started, so it changes after
every gk restart. The counter is incremented with each call.
As you can easily calculate, both numbers have to be 32 bit to guarantee uniquess
over long period of time.

----- Original Message ----- 
From: "Kompnet" <kompnet@aaanet.ru>
Sent: Wednesday, January 28, 2004 8:24 AM


Whether there was a real necessity to increase quantity of signs 
in field Acct-Session-Id from 8 (version 2.0.7) up to 16 (version 2.2.3)? 
How it could improve work of GNUGK? 
If it was REAL necessity, why there were no preventions of this change?
I have defined this field as varchar (12) and thought, that such stock will suffice. 
As a result of this change only successful calls enter the name in the table RadAcct.
Work of GNUGK has really "improved"!



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux