As of LCOS version 9.10, the RADIUS server is capable of managing volume budgets in excess of 4GByte.
Important: The RADIUS server now interprets existing volume budgets as a value in MBytes (previously in bytes). By updating to LCOS version 9.10, the device converts existing values and rounds them up to full MBytes. For example, the entry "1000000" (byte) converts to "1" (MByte).
This extension affects the Public Spot module. The specification of the volume budget via the Public Spot web API can also include a unit:
- volumebudget
- Volume budget
- The following entries are allowed:
- k or K: Specified in kilobytes (kB), e.g. volumebudget=1000k.
- m or M: Specified in megabytes (MB), e.g. volumebudget=1000m.
- g or G: Specified in gigabytes (GB), e.g. volumebudget=1g.
This extension affects the XML interface. The specification of the volume budget at the login request and the login response can also include a unit:
- TRAFFICEXPIRE
-
The maximum data volume for a user account. The user can use this data volume until a relative or absolute expiry time (if set) is reached.
The following entries are allowed:
- k or K: Specified in kilobytes (kB), e.g. <TRAFFICEXPIRE>1000k</TRAFFICEXPIRE>.
- m or M: Specified in megabytes (MB), e.g. <TRAFFICEXPIRE>100m</TRAFFICEXPIRE>.
- g or G: Specified in gigabytes (GB), e.g. <TRAFFICEXPIRE>1g</TRAFFICEXPIRE>.