view doc/rt_rewrite.conf.sample @ 1504:4dff34cd2d3d

Add 3GPP TS 29.215 V15.2.0 (2019-09) Add AVPs: - DRA-Deployment, Enumerated, code 2206, section 5.3.7 - Multiple-BBERF-Action, Enumerated, code 2204, section 5.3.6 - Subsession-Decision-Info, Grouped, code 2200, section 5.3.1 - Subsession-Enforcement-Info, Grouped, code 2201, section 5.3.2 - Subsession-Id, Unsigned32, code 2202, section 5.3.3 - Subsession-Operation, Enumerated, code 2203, section 5.3.4 - DRA-Binding, Enumerated, code 2208, section 5.3.x - PCRF-Address, DiameterIdentity, code 2207, section A.7.3.1.1 - UE-Local-IPv6-Prefix, OctetString, code 2205, section A.8.3.1
author Luke Mewburn <luke@mewburn.net>
date Fri, 03 Apr 2020 16:50:00 +1100
parents b0401251d8c0
children
line wrap: on
line source

# This file contains information for configuring the rt_rewrite extension
# To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation.
#
# The rt_rewrite extension allows moving data from one AVP into another one, or dropping AVPs altogether.

# This extension supports configuration reload at runtime. Send
# signal SIGUSR1 to the process to cause the process to reload its
# config.

# The config consists of MAP for AVP pairs of source/target, or DROP for a source.
#
#  MAP = "Source-AVP" > "Destination-AVP";
#
# It is possible to specify AVPs below GROUPED AVPs with the by separating AVPs with a colon (':'):
#  MAP = "Grouped-AVP1" : "Octetstring-AVP1" > "Grouped-AVP2" : "Grouped-AVP3" : "Octetstring-AVP2";
# Intermediate destination grouped AVPs will be created automatically.
#
# NOTE: you can not move grouped AVPs as a unit, you have to move each separate AVP.
# i.e., this will not work:
#  MAP = "Grouped-AVP1" > "Grouped-AVP2";
#
# For removing AVPs, use DROP:
#  DROP = "Grouped-AVP1" : "Octetstring-AVP1";
"Welcome to our mercurial repository"