[QuotaProfile.QP2]
packages=2
bucket_sizes=100000
dosage_sizes=5000
aggregation_period=30 minutes
penalty_period=none
penalty_profile=none
#slice_period=

# This file contains the definitions of the Quota Profiles 
# and Quota RDR Server configurations

# Each section contains the definition for a single quota profile
# The Section name is [QuotaProfile.<QUOTA-PROFILE-NAME>]

#[QuotaProfile.QUOTA-PROFILE-1]
# List of SCA-BB's package IDs that use this quota profile
#If the profile is used as penalty profile - only one package
#can be defined below
# Default value: none
#packages=

# Length oft the penalty period in minutes.
# Applicable if the current profile is used as penalty profile
# Must be expressed as a product of the aggregation period
#penalty_period=

# List of bucket sizes
# The bucket sizes are the quota limits for each aggregation period
# The list must be ordered: The first number is for bucket ID 1, 
# the second for bucket ID 2, and so on
# The remaining buckets past the last configured are set to zero
# The quota units are either number of sessions or volume in KBytes
# based on SCA-BB's configuration
# For multiple thresholds scenario this parameter defines the
# threshold on which the subscriber is moved to penalty profile
#For multi bucket with penalty support � the number of penalty profiles  and 
#the number of bucket_sizes should be same.
# Default value: none
#bucket_sizes=

# List of quota dosage sizes per bucket
# In each quota provisioning operation, the Quota Manager fills the bucket 
# in the SCE up to the quota dosage size
# The list must be ordered in the same way as bucket_sizes, 
# and must be of the same length
# Setting this parameter to a very low value will cause high rate of updates
# to and from the SCE
# Setting this parameter to a very high value will cause inaccuracy of quota 
# in an event of a failure
# Default value: none
#dosage_sizes=

# Definition of the aggregation period that is also called sliding window period.
# Possible values: <number> minutes/hourly/daily/weekly/monthly
# For minutes type minimal value is 30 
# The default value is daily
#aggregation_period=daily

# The following three parameters define when the aggregation period start
# day_of_month is only relevant if the aggregation period is monthly. 
# Possible values: 1-31. Default is 1.
#day_of_month=1

# day_of_week is only relevant if the aggregation period is weekly. 
# Possible values: sunday,monday,....,saturday. Default is sunday.
#day_of_week=sunday

# time_of_day is relevant for all aggregation periods
# The format is HH:mm, when the hours are for the 24-hour clock
# If the aggregation period is hourly, only the minutes are relevant
# Possible values: hours 0-23, minutes 0-59
# Default value: 00:00 (midnight)
#time_of_day=00:00

# gap is used to distribute the aggregation period start time 
# between different subscribers. The motivation behind this is 
# to avoid network bursts when new aggregation period starts.
# The distribution is uniform. 
# gap is the distribution range in percentage of the aggregation period.
# gap = 0 means no distribution 
# (aggregation periods start on the same time for all subscribers)
# gap = 100 means full distribution
# For example, suppose the aggregation period is daily and starts on midnight.
# gap = 50 means that the aggregation period falls between midnight and midday
# gap = 25 means that the aggregation period falls between midnight and 6AM.
# Possible values: 0-100. Default is 0
#gap=100

#Penalty parameters
# Name of the Quota Profile that holds the definition of 
# the package and quota for the penalty period
#For multi bucket with penalty support � the number of penalty profiles  and 
#the number of bucket_sizes should be same. Penalty profile list should be 
# comma (,) separated profiles.
#penalty_profile=

#Post-penalty map - defines Quota Profile to which the subscriber
# is moved if his/her usage during the last aggregation period
# is lower than the according threshold
#post_penalty.<threshold>=<Quota Profile Name>
#if multi bucket with penalty support is used then post-penalty configuration should be ,
#post_penalty.[<threshold1>|<threshold2>|<threshold3>]=<Quota Profile Name>
#In multi bucket penalty support , thresholds are treated as % of quota usage for the corresponding quota buckets

#Sliding window parameters
# Define slice period in minutes. Minimal value is 10.
# valid only in case of minutes/hourly/weekly aggregation type
# in other cases monthly and none (infinity) should not be used or 
# set to default.
# default value -1
#slice_period=


# This section contains the Quota RDR server configurations

# [QuotaRDRServer]

# The following parameter determines whether to start the Quota RDR Server or not. 
# Possible values are yes and no. The default value is no.
# start=no

# Defines the IP address of  Quota RDR Server.Use this parameter only in cases where the IP
# address is not the main IP address of the Subscriber Manager machine, for example in cluster
# topologies.
# ip=<ip address>

# Specifies the Quota RDR server port. The default is 32145.
# port=<port>

# Specifies the maximum number of connections accepted by the server. 
# The default is 8.
# max_connections=8

# Specifies the receiver buffer size which is used to scale up TCP receive window 
# to the configured buffer size. The default is 64KB.
# socket_recv_buffer= 65536

# Specifies the requested maximum number of pending connections on the socket. 
# The default is 0.
# server_socket_backlog=0

# Specifies the server socket time out for accepting connections. 
# The default is 0.
# server_socket_timeout=0

# Specifies the Maximum number of RDR stored in internal quota queue before processing. 
# The default is 100000.
# rdr_queue_size=100000

# Specifies the maximum utilization of queue as percent (value between 0-100) 
# before dropping less priority rdr's like periodic and threshold.
# Its not recommented to configure value < 50. The default is 90.
# queue_threshold=90