Ascend-Event-Request
Andrey Nikolaev <[email protected]>
| Newsgroups | gmane.comp.gnu.radius.general |
|---|---|
| Message-ID | <[email protected]> |
Hi!
Im using gnu-radius 1.3.
Always in log write message:
(Ascend-Event-Request max 35 ""): неизвестный код запроса 33
(Ascend-Event-Request max 36 ""): неизвестный код запроса 33
(Ascend-Event-Request max 77 ""): неизвестный код запроса 33
(Ascend-Event-Request max 78 ""): неизвестный код запроса 33
users:
...
Ascend-Event-Type = Ascend-Session-Event
dictionary include ascend.vs
But ascend site :
Classifying user sessions in RADIUS
The Class and Ascend-Number-Sessions attributes enable access providers to classify their user sessions, such as for the purpose of billing clients depending on the service option they choose.
If you include the Class attribute in the RADIUS user profile, the RADIUS server sends it to the MAX in the Access-Accept packet when the session begins. Class then appears in Accounting-Request packets the MAX sends to the RADIUS accounting server whenever a session starts and whenever a session stops (as long as the Auth parameter on the MAX is not set to RADIUS/LOGOUT). The accounting entries give the class on a per-user and per-session basis.
The Ascend-Number-Sessions attribute reports information on all user sessions-that is, on the number of current sessions of each class. The attribute has a compound value. The first part specifies a user-session class. The second part reports the number of active sessions in that class. In the case of multichannel calls, such as MP+ calls, each separate connection counts as a session.
On the MAX, you can set the Sess Timer parameter in the Ethernet>Mod Config>Accounting menu to send accounting requests at regular intervals. At the specified interval, the MAX reports the number of open sessions by sending an Ascend-Event-Request packet (code 33). This packet contains the NAS-Identifier attribute, followed by a list of Ascend-Number-Sessions attributes.
Only RADIUS daemons you customize to recognize packet code 33 respond these request packets from the MAX. Other accounting daemons ignore it. Therefore, the standard Livingston RADIUS daemon and the Ascend accounting daemon both ignore this attribute.
When modifying the daemon, make sure that it recognizes an Ascend-Event-Request packet in this format:
Code (8-bit)=33
Identifier (8-bit)
Length (16-bit)
Authenticator (48-bit for an accounting server, 64-bit for an
authentication server)
What do ?
Thank you
--
Andrey Nikolaev +380652-511616
+380652-276405
[email protected] AN1035-RIPE