Service-Type=Login-User is always used for RRQ. ARQ will trigger either Service-Type=Login-User or Service-Type=Call-Check. Login-User is send for ARQ from call originator, Service-Type=Call-Check is for answer ARQ. This makes possible to separate "originate the call" requests from "answer the call" requests. ARQ request can be distinguished from RRQ request by the presence of Calling-Station-Id and/or Called-Station-Id - these are never present inside Access-Request triggered by RRQ. ----- Original Message ----- From: "Razvan Radu" <razvan.radu@coretech.ro> Sent: Monday, September 22, 2003 5:47 PM Subject: Radius (Service-Type = Call-Check) > I have a small question about how radius modules (RadAuth, RadAliasAuth) > make the difference between RRQ and ARQ features ? > > Is it correct to assume that for RRQ uses Service-Type = Login-User and > for ARQ uses Service-Type = Call-Check ? > > If so why when I call out I get a "Service-Type = Login-User" instead of > "Service-Type = Call-Check" when I call local (both parties registered > on the same gk) I get one Login-User and one Call-Check instead of two > Call-Check and, the correct one (in my opinion) is when I receive an > outside call and get one Call-Check. > > Is it safe to assume that attributes "Calling-Station-Id and > Called-Station-Id" appear only in a request for an ARQ ? ------------------------------------------------------- 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/
