view doc/rt_ereg.conf.sample @ 1260:4f6f61e67599

Store redirect information for ALL_SESSION and ALL_USER in a hash. This is a speedup if many of these exist (compared to checking a linked list for matches as before). Refactor a bit while here. Use the uthash code from Troy D. Hanson, http://troydhanson.github.com/uthash/
author Thomas Klausner <tk@giga.or.at>
date Mon, 24 Mar 2014 13:21:41 +0100
parents ecfa089bd29a
children f1b65381c1e7
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.

# First, one must indicate which AVP should be used for matching. 
# At the moment, only AVP with OCTETSTRING types are valid.
#  AVP = "User-Name";
# 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.
"Welcome to our mercurial repository"