view doc/rt_ereg.conf.sample @ 1502:515421a9ac5e

Add 3GPP TS 29.154 V15.3.0 (2019-09) Add AVPs: - Network-Area-Info-List, OctetString, code 4201, section 5.3.2 - Number-Of-UEs, Unsigned32, code 4209, section 5.3.10 - Reference-Id, OctetString, code 4202, section 5.3.3 - Transfer-Request-Type, Unsigned32, code 4203, section 5.3.4 - Time-Window, Grouped, code 4204, section 5.3.5 - Transfer-End-Time, Time, code 4205, section 5.3.6 - Transfer-Policy, Grouped, code 4207, section 5.3.8 - Transfer-Policy-Id, Unsigned32, code 4208, section 5.3.9 - Transfer-Start-Time, Time, code 4206, section 5.3.7 - Access-Network-Reports, Grouped, code 4210, section A.6.3.2 - Event-Configuration, Grouped, code 4211, section A.6.3.3 - Event-Configuration-State, Unsigned32, code 4212, section A.6.3.4 - Event-Configuration-Status, Grouped, code 4213, section A.6.3.5 - Event-Reporting-Results, Unsigned32, code 4214, section A.6.3.6 - Event-Reports, Grouped, code 4215, section A.6.3.7 - Extended-SCEF-Reference-ID, Unsigned64, code 4216, section A.6.3.8
author Luke Mewburn <luke@mewburn.net>
date Fri, 03 Apr 2020 15:33:12 +1100
parents f1b65381c1e7
children
line wrap: on
line source

# This file contains information for configuring the rt_ereg extension.
# To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation.
#
# The rt_ereg extension allows creation of routing rules based on AVP value matching regular expressions.

# This extension supports configuration reload at runtime. Send
# signal SIGUSR1 to the process to cause the process to reload its
# config.

# First, one must indicate which AVP should be used for matching. 
# At the moment, only AVP with OCTETSTRING types are valid.
#  AVP = "User-Name";
# It is possible to specify AVPs below GROUPED AVPs with the by separating AVPs with a colon (':'):
#  AVP = "Grouped-AVP1" : "Grouped-AVP2" : "Octetstring-AVP";
# This parameter is mandatory. There is no default value.

# Then a list of rules follow. A rule has this format:
#  "pattern" : "server" += score ;
# Where:
#  pattern is the quoted-string regex to match, 
#  server is the next hop in the routing list that will receive the
#  score, which can be positive or negative.
# Example:
#  "[[:digit:]]*" : "serverA.example.net" += -3 ;
#    means that if the AVP value is only numeric, the ServerA will have its score decreased by 3 points.
#    (reminder: the server with the peer with the highest score gets the message)
# Note that all rules are tested for each message that contain the AVP, not only the first match.

# There can be multiple blocks of AVPs and rules; just start the next one with another AVP line:
#  AVP = "Other-AVP";
# and continue with rules as above.
"Welcome to our mercurial repository"