Mercurial > hg > freeDiameter
view doc/rt_ereg.conf.sample @ 1508:eb19aa48829f
Add 3GPP TS 29.343 V15.1.0 (2019-09)
Add AVPs:
- Origin-App-Layer-User-Id, UTF8String, code 3600, section 6.4.2
- Target-App-Layer-User-Id, UTF8String, code 3601, section 6.4.3
- ProSe-Function-ID, OctetString, code 3602, section 6.4.4
- ProSe-Request-Type, Unsigned32, code 3603, section 6.4.5
- PDUID, OctetString, code 3604, section 6.4.6
- Application-Data, UTF8String, code 3605, section 6.4.7
- Allowed-Suffixes-Number, Unsigned32, code 3606, section 6.4.8
- Monitor-Target, Grouped, code 3607, section 6.4.9
- ProSe-Code-Suffix-Mask, Grouped, code 3608, section 6.4.10
- Suffix-Code, OctetString, code 3609, section 6.4.11
- Suffix-Mask, OctetString, code 3610, section 6.4.12
- Banned-User-Target, Grouped, code 3611, section 6.4.17
- Metadata-Indicator, Unsigned32, code 3612, section 6.4.18
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Sat, 04 Apr 2020 21:28:45 +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.