Mercurial > hg > freeDiameter
view doc/rt_ereg.conf.sample @ 1504:4dff34cd2d3d
Add 3GPP TS 29.215 V15.2.0 (2019-09)
Add AVPs:
- DRA-Deployment, Enumerated, code 2206, section 5.3.7
- Multiple-BBERF-Action, Enumerated, code 2204, section 5.3.6
- Subsession-Decision-Info, Grouped, code 2200, section 5.3.1
- Subsession-Enforcement-Info, Grouped, code 2201, section 5.3.2
- Subsession-Id, Unsigned32, code 2202, section 5.3.3
- Subsession-Operation, Enumerated, code 2203, section 5.3.4
- DRA-Binding, Enumerated, code 2208, section 5.3.x
- PCRF-Address, DiameterIdentity, code 2207, section A.7.3.1.1
- UE-Local-IPv6-Prefix, OctetString, code 2205, section A.8.3.1
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Fri, 03 Apr 2020 16:50:00 +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.