blob: fbcb370d792ff8869b62e92e1fd613457ca1fe6a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
# 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.
|
