| Brian Waters | 13d9601 | 2017-12-08 16:53:31 -0600 | [diff] [blame^] | 1 | # This file contains information for configuring the rt_ereg extension. |
| 2 | # To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation. |
| 3 | # |
| 4 | # The rt_ereg extension allows creation of routing rules based on AVP value matching regular expressions. |
| 5 | |
| 6 | # First, one must indicate which AVP should be used for matching. |
| 7 | # At the moment, only AVP with OCTETSTRING types are valid. |
| 8 | # AVP = "User-Name"; |
| 9 | # This parameter is mandatory. There is no default value. |
| 10 | |
| 11 | # Then a list of rules follow. A rule has this format: |
| 12 | # "pattern" : "server" += score ; |
| 13 | # Where: |
| 14 | # pattern is the quoted-string regex to match, |
| 15 | # server is the next hop in the routing list that will receive the |
| 16 | # score, which can be positive or negative. |
| 17 | # Example: |
| 18 | # "[[:digit:]]*" : "serverA.example.net" += -3 ; |
| 19 | # means that if the AVP value is only numeric, the ServerA will have its score decreased by 3 points. |
| 20 | # (reminder: the server with the peer with the highest score gets the message) |
| 21 | # Note that all rules are tested for each message that contain the AVP, not only the first match. |