view doc/rt_ereg.conf.sample @ 1514:8912a0645645

Add 3GPP TS 29.234 V11.2.0 (2013-06) Add AVPs: - 3GPP-WLAN-APN-Id, OctetString, code 100, section 10.1.15 - Authentication-Method, Enumerated, code 300, section 10.1.5 - Authentication-Information-SIM, OctetString, code 301, section 10.1.6 - Authorization-Information-SIM, OctetString, code 302, section 10.1.7 - WLAN-User-Data, Grouped, code 303, section 10.1.8 - Charging-Data, Grouped, code 304, section 10.1.10 - WLAN-Access, Enumerated, code 305, section 10.1.11 - WLAN-3GPP-IP-Access, Enumerated, code 306, section 10.1.12 - APN-Authorized, Grouped, code 307, section 10.1.14 - APN-Barring-Type, Enumerated, code 309, section 10.1.16 - WLAN-Direct-IP-Access, Enumerated, code 310, section 10.1.17 - Session-Request-Type, Enumerated, code 311, section 10.1.23 - Routing-Policy, IPFilterRule, code 312, section 10.1.24 - Max-Requested-Bandwidth, OctetString, code 313, section 10.1.26 - Charging-Characteristics, Integer32, code 314, section 10.1.27 - Charging-Nodes, Grouped, code 315, section 10.1.28 - Primary-OCS-Charging-Function-Name, DiameterIdentity, code 316, section 10.1.29 - Secondary-OCS-Charging-Function-Name, DiameterIdentity, code 317, section 10.1.30 - Maximum-Number-Accesses, Unsigned32, code 319, section 10.1.38 APN-Id (308) OctetString only present from 3GPP TS 29.234 V6.2.0 (2005-03) to 3GPP TS 29.234 V6.4.0 (2005-09) before being deprecated in 3GPP TS 29.234 V6.5.0 (2005-12). (Not provided here.)
author Luke Mewburn <luke@mewburn.net>
date Wed, 08 Apr 2020 15:48:08 +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"