view doc/rt_ereg.conf.sample @ 1517:9e233ef0b07e

Add 3GPP TS 29.283 V15.1.0 (2019-09) Add AVPs: - MCPTT-ID, UTF8String, code 4500, section 7.3.2 - Data-Identification, Grouped, code 4501, section 7.3.3 - Data-Identification-Prefix, Unsigned32, code 4502, section 7.3.11 - Data-Identification-Flags, Unsigned64, code 4503, section 7.3.12 - DPR-Flags, Unsigned32, code 4504, section 7.3.13 - DPA-Flags, Unsigned32, code 4505, section 7.3.14 - DUR-Flags, Unsigned32, code 4506, section 7.3.15 - DUA-Flags, Unsigned32, code 4507, section 7.3.16 - NDR-Flags, Unsigned32, code 4508, section 7.3.17 - NDA-Flags, Unsigned32, code 4509, section 7.3.18 - User-Data-Id, Unsigned32, code 4510, section 7.3.19 - MC-Service-User-Profile-Data, Grouped, code 4511, section 7.3.20 - Sequence-Number-29.283, Unsigned32, code 4512, section 7.3.21 - Data, Grouped, code 4513, section 7.3.22 - MCVideo-ID, UTF8String, code 4514, section 7.3.24 - MCData-ID, UTF8String, code 4515, section 7.3.25 Note: Name conflict with 3GPP TS 29.140 Sequence-Number (1107). and 3GPP TS 29.329 Sequence-Number (716). 3GPP TS 29.140 V6.1.0 (2005-06) allocated Sequence-Number (1107). 3GPP TS 29.329 V10.0.0 (2010-09) CR 0163 added Sequence-Number (716). 3GPP TS 29.283 V13.1.0 (2016-06) allocated Sequence-Number (4512). Fix: Sequence-Number (4512) renamed to Sequence-Number-29.283 (4512).
author Luke Mewburn <luke@mewburn.net>
date Thu, 09 Apr 2020 10:32:09 +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"