view doc/rt_ereg.conf.sample @ 1515:8430dabbc637

Add 3GPP TS 29.109 V15.0.0 (2017-06) Add AVPs: - GBA-UserSecSettings, OctetString, code 400, section 6.3.1.1 - Transaction-Identifier, OctetString, code 401, section 6.3.1.2 - NAF-Id, OctetString, code 402, section 6.3.1.3 - GAA-Service-Identifier, OctetString, code 403, section 6.3.1.4 - Key-ExpiryTime, Time, code 404, section 6.3.1.5 - ME-Key-Material, OctetString, code 405, section 6.3.1.6 - UICC-Key-Material, OctetString, code 406, section 6.3.1.7 - GBA-U-Awareness-Indicator, Enumerated, code 407, section 6.3.1.8 - BootstrapInfoCreationTime, Time, code 408, section 6.3.1.9 - GUSS-Timestamp, Time, code 409, section 6.3.1.10 - GBA-Type, Enumerated, code 410, section 6.3.1.11 - UE-Id, OctetString, code 411, section 6.3.1.12 - UE-Id-Type, Enumerated, code 412, section 6.3.1.13 - UICC-App-Label, OctetString, code 413, section 6.3.1.14 - UICC-ME, Enumerated, code 414, section 6.3.1.15 - Requested-Key-Lifetime, Time, code 415, section 6.3.1.16 - Private-Identity-Request, Enumerated, code 416, section 6.3.1.17 - GBA-Push-Info, OctetString, code 417, section 6.3.1.18 - NAF-SA-Identifier, OctetString, code 418, section 6.3.1.19 - Security-Feature-Request, OctetString, code 419, section 6.3.1.20 - Security-Feature-Response, OctetString, code 420, section 6.3.1.21 Note: 3GPP TS 29.109 table 6.1 row GBA_U-Awareness-Indicator (407) has an underscore in the name (contrary to RFC 6733 section 4.1). Fix: GBA_U-Awareness-Indicator (407) renamed to GBA-U-Awareness-Indicator (407).
author Luke Mewburn <luke@mewburn.net>
date Thu, 09 Apr 2020 00:34:15 +1000
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"