Differences

This shows you the differences between two versions of the page.

--- usage [2016-09-19 17:22] – [Core] wikiadmin
+++ usage [2016-09-19 19:50] (current) – [Auto-Topups] wikiadmin
@@ Line 44: / Line 44: @@
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Traffic-Notify]]
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Traffic-NotifyTemplate]]
+  * [[mod_feature_capping.pm|SMRadius-AutoTopup-Traffic-Threshold]]
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-Enabled]]
@@ Line 50: / Line 51: @@
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-Notify]]
   * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-NotifyTemplate]]
+  * [[mod_feature_capping.pm|SMRadius-AutoTopup-Uptime-Threshold]]
 ===== Validity ====
@@ Line 70: / Line 72: @@
 Evaluate and set an attribute / attributes based on the results of the evaluation. Syntax: TEST CASE ? TRUE_ATTRIBUTE : FALSE.
+Lets take a real life example:
+. For traffic under 80000Mbyte, we set an attribute
 <code>
 SMRadius-Evaluate ||+= SMRadius_Capping_TotalDataUsage < 80000 ? [14988:Mikrotik-Rate-Limit] = 1m/4m 1m/6m 1m/5m 10/10 1
+</code>
+. For traffic above 80000Mbyte, but below 130000Mbyte, we set the same attribute to something else...
+<code>
 SMRadius-Evaluate ||+= SMRadius_Capping_TotalDataUsage > 80000 && SMRadius_Capping_TotalDataUsage < 130000 ? [14988:Mikrotik-Rate-Limit] = 512k/1m 640k/2m 640k/2m 10/10 4
+</code>
+. For traffic above 130000Mbyte, we set the traffic to a third different value...
+<code>
 SMRadius-Evaluate ||+= SMRadius_Capping_TotalDataUsage > 130000 ? [14988:Mikrotik-Rate-Limit] = 128k/384k 512k/1024k 256k/512k 10/10 8
 </code>
@@ Line 86: / Line 99: @@
 ===== SMRadius-Disable-WebUITopup =====
-Allows one to build web ui's that ignore topups, this attribute is not used internally at all.
+Allows one to build web ui's that ignore topups, this attribute is not used internally.
 ===== SMRadius-Username-Transform =====