Mercurial > hg > freeDiameter
view doc/app_redirect.conf.sample @ 1513:73e563165594
Add 3GPP TS 29.468 V15.8.0 (2019-12)
Add AVPs:
- BMSC-Address, Address, code 3500, section 6.4.2
- BMSC-Port, Unsigned32, code 3501, section 6.4.3
- Common-Tunnel-Endpoint-Identifier, OctetString, code 3524, section 6.4.26
- FEC-Request, OctetString, code 3525, section 6.4.27
- FEC-Result, Unsigned32, code 3531, section 6.4.33
- Local-M1-Information, Grouped, code 3518, section 6.4.20
- Local-MB2-U-Information, Grouped, code 3519, section 6.4.21
- MB2U-Security, Unsigned32, code 3517, section 6.4.19
- MBMS-Bearer-Event, Unsigned32, code 3502, section 6.4.4
- MBMS-Bearer-Event-Notification, Grouped, code 3503, section 6.4.5
- MBMS-Bearer-Request, Grouped, code 3504, section 6.4.6
- MBMS-Bearer-Response, Grouped, code 3505, section 6.4.7
- MBMS-Bearer-Result, Unsigned32, code 3506, section 6.4.8
- MBMS-eNB-IP-Multicast-Address, Address, code 3520, section 6.4.22
- MBMS-eNB-IPv6-Multicast-Address, Address, code 3521, section 6.4.23
- MBMS-GW-SSM-IP-Address-29.468, Address, code 3522, section 6.4.24
- MBMS-GW-SSM-IPv6-Address-29.468, Address, code 3523, section 6.4.25
- MBMS-Start-Time, Time, code 3507, section 6.4.9
- Radio-Frequency-29.468, Unsigned32, code 3508, section 6.4.10
- ROHC-Full-Header-Periodicity, Float32, code 3527, section 6.4.29
- ROHC-Max-CID, Unsigned32, code 3532, section 6.4.34
- ROHC-Profile, Unsigned32, code 3528, section 6.4.30
- ROHC-Request, Grouped, code 3526, section 6.4.28
- ROHC-Result, Unsigned32, code 3530, section 6.4.32
- TMGI-Allocation-Request, Grouped, code 3509, section 6.4.11
- TMGI-Allocation-Response, Grouped, code 3510, section 6.4.12
- TMGI-Allocation-Result, Unsigned32, code 3511, section 6.4.13
- TMGI-Deallocation-Request, Grouped, code 3512, section 6.4.14
- TMGI-Deallocation-Response, Grouped, code 3513, section 6.4.15
- TMGI-Deallocation-Result, Unsigned32, code 3514, section 6.4.16
- TMGI-Expiry, Grouped, code 3515, section 6.4.17
- TMGI-Number, Unsigned32, code 3516, section 6.4.18
- Userplane-Protocol-Result, Grouped, code 3529, section 6.4.31
Note: Name conflict with 3GPP TS 29.061 MBMS-GW-SSM-IP-Address (924).
3GPP TS 29.061 V10.4.0 (2011-09) CR 0355 added MBMS-GW-SSM-IP-Address (924).
3GPP TS 29.468 V14.0.0 (2016-12) CR 0021 added MBMS-GW-SSM-IP-Address (3522).
Fix: MBMS-GW-SSM-IP-Address (3522) renamed to MBMS-GW-SSM-IP-Address-29.468 (3522).
Note: Name conflict with 3GPP TS 29.061 MBMS-GW-SSM-IPv6-Address (925).
3GPP TS 29.061 V10.4.0 (2011-09) CR 0355 added MBMS-GW-SSM-IPv6-Address (925).
3GPP TS 29.468 V14.0.0 (2016-12) CR 0021 added MBMS-GW-SSM-IPv6-Address (3523).
Fix: MBMS-GW-SSM-IPv6-Address (3523) renamed to MBMS-GW-SSM-IPv6-Address-29.468 (3523).
Note: Name conflict with 3GPP TS 32.299 Radio-Frequency (3462).
3GPP TS 29.468 V12.0.0 (2014-09) added Radio-Frequency (3508).
3GPP TS 32.299 V13.1.0 (2015-06) CR 0638 added Radio-Frequency (3462).
Fix: Radio-Frequency (3508) renamed to Radio-Frequency-29.468 (3508).
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Tue, 07 Apr 2020 19:38:33 +1000 |
parents | 8d7201a747eb |
children |
line wrap: on
line source
# This file contains the configuration for the app_redirect extension of freeDiameter. # # This extension provides configurable Redirect messages. # Lines starting with a # are comments and ignored. # Spaces and newlines are not meaningful, except inside quoted areas. ######################################################################################### # See Diameter RFC for a detailed explanation on Redirects semantics # ######################################################################################### ## default_redirect_cache_time # Specify the default value for Redirect-Max-Cache-Time. # This value can be overwritten for each rule as specified below. # If this value is not specified, the default is: #default_redirect_cache_time = 86400; ## => 1 day # The remaining of this file contains a list of RULE elements. # Each RULE consists in three parts: # - a CRITERIA that specifies which messages the RULE applies to. # - a REDIRECT_TYPE that specifies what type of redirect is to be sent, and its duration. # - a TARGET_HOSTS list that specifies the host(s) to send the message to. # # The rules are matched in the order they appear in this file. Once a rule has matched, the # remaining rules are not processed. # # The basic format of a rule is: # REDIRECT_TYPE : CRITERIA to TARGET_HOSTS ; # These are a few examples. The definition of each term follows. # # 1) REALM_AND_APPLICATION : app=3 "Destination-Realm"="myrealm.net" to "aaas://acct1.myrealm.net" "aaas://acct2.myrealm.net"; # will ask all peers sending a Base Accounting message for realm "myrealm.net" to send # this message directly to either 'acct1.myrealm.net' or 'acct2.myrealm.net'. # # 2) ALL_SESSION 3600 : "Origin-AAA-Protocol"=1 "Destination-Realm"="myrealm.net" to "aaas://raddiam.myrealm.net"; # Will ask any peer sending messages translated from RADIUS and targeted to this realm # to address all the messages from the same session to 'raddiam.myrealm.net'. The # redirect entry should be stored for 1 hour. # # 3) ALL_HOST : from.realm=[".*\.(fr|de|es)"] to "aaas://relay-EU.myrealm.net"; # ALL_HOST : from.realm=[".*\.(cn|jp|vn)"] to "aaas://relay-ASIA.myrealm.net"; # Redirect messages to different relays depending on where they come from. # # 4) ALL_HOST : to "aaas://newserv.myrealm.net"; # This server was relocated, tell all peers to go directly to the new one. # This rule should appear last because it matches all messages, so further rules will never be used. # # REDIRECT_TYPE # # The redirect_type is one of the following (see Redirect-Host-Usage AVP definition in RFC for semantics): # DONT_CACHE # ALL_SESSION # ALL_REALM # REALM_AND_APPLICATION # ALL_APPLICATION # ALL_HOST # ALL_USER # In addition, an integer can follow. If specified, it overwrites the default_redirect_cache_time # value for this rule. The value is always specified in seconds. # # CRITERIA # # Each RULE can contain 0 or more criteria. # If no criteria is specified, all messages are assumed to match (wildcard). # If more than one criteria is specified, an "AND" relationship is assumed. # If you need to specify "OR", just create separate rules. # # In the following definitions, "STR/REG" stands for: # - a quoted string "some.peer" that will match exactly this string (case-insensitive), or # - a bracket-quoted string ["some regex"] that will be interpreted as a POSIX extended regular expression (case-sensitive), and attempt to match the string. # # A criteria is one of the following: # from.id="STR/REG" -> matches messages received from peer with this Diameter Identity. # from.realm="STR/REG" -> matches messages received from peer with this Realm. # app=U32_VALUE -> matches messages with this Diameter Application-Id value in its header. # "AVP-name"=U32_VALUE -> matches messages that contain an avp "AVP-name" (replace with the realm name) with this value. # "AVP-name"="STR/REG" -> matches messages that contain an avp "AVP-name" (replace with the realm name) with this . # # TARGET_HOSTS # # This is a simple list of DiameterURI that must be sent back. # See the RFC for valid format of Diameter URI: # "aaa://" FQDN [ port ] [ transport ] [ protocol ] # "aaas://" FQDN [ port ] [ transport ] [ protocol ] ######################################################################################