view doc/rt_rewrite.conf.sample @ 1512:f98e2b6e8f42

Add 3GPP TS 29.368 V15.1.0 (2019-09) Add AVPs: - Device-Action, Grouped, code 3001, section 6. 4.2 - Device-Notification, Grouped, code 3002, section 6.4.3 - Trigger-Data, Grouped, code 3003, section 6.4.4 - Payload, OctetString, code 3004, section 6.4.5 - Action-Type, Enumerated, code 3005, section 6.4.6 - Priority-Indication, Enumerated, code 3006, section 6.4.7 - Reference-Number, Unsigned32, code 3007, section 6.4.8 - Request-Status, Enumerated, code 3008, section 6.4.9 - Delivery-Outcome, Enumerated, code 3009, section 6.4.10 - Application-Port-Identifier, Unsigned32, code 3010, section 6.4.11 - Old-Reference-Number, Unsigned32, code 3011, section 6.4.12 - Feature-Supported-In-Final-Target, Unsigned32, code 3012, section 6.4.13
author Luke Mewburn <luke@mewburn.net>
date Tue, 07 Apr 2020 16:04:36 +1000
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"