Accounting support

[Sergey]

i am trying integrate
FirstSpot with Alepo RBS Billing
by Radius protocol

1) Alepo sucessfule authorize FirtSpot
but when recieving accounting packet
do error

01/25/2005 13:35:44 Dropping Accounting request from 192.168.1.3, User = test : No Session Id

How I can enable Act_Session_id in Firstspot Accounting packets?

[alan]

Currently, FirstSpot only supports Funk and Microsoft IAS RADIUS server.

Nevertheless, we would like to explore further on how we can support your case. What does Act_Session_id exactly stands for? Can you disable Act_Session_id check in your RADIUS server during accounting request?
_________________
~ Patronsoft Limited ~

[Sergey]

The detailed description is
http://www.faqs.org/rfcs/rfc2139.html
RFC 2139 - RADIUS Accounting

5.5. Acct-Session-Id

Description

This attribute is a unique Accounting ID to make it easy to match
start and stop records in a log file. The start and stop records
for a given session MUST have the same Acct-Session-Id. It is
strongly recommended that the Acct-Session-Id be a printable ASCII
string.

For example, one implementation uses a string with an 8-digit
upper case hexadecimal number, the first two digits increment on
each reboot (wrapping every 256 reboots) and the next 6 digits
counting from 0 for the first person logging in after a reboot up
to 2^24-1, about 16 million. Other encodings are possible.

A summary of the Acct-Session-Id attribute format is shown below.
The fields are transmitted from left to right.

0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | String ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type

44 for Acct-Session-Id.

Length

>= 3

String

The String field SHOULD be a string of printable ASCII characters

[Sergey]

Can u implement this in Firstspot ?