Mercurial > hg > freeDiameter
view doc/echodrop.rgwx.conf.sample @ 1514:8912a0645645
Add 3GPP TS 29.234 V11.2.0 (2013-06)
Add AVPs:
- 3GPP-WLAN-APN-Id, OctetString, code 100, section 10.1.15
- Authentication-Method, Enumerated, code 300, section 10.1.5
- Authentication-Information-SIM, OctetString, code 301, section 10.1.6
- Authorization-Information-SIM, OctetString, code 302, section 10.1.7
- WLAN-User-Data, Grouped, code 303, section 10.1.8
- Charging-Data, Grouped, code 304, section 10.1.10
- WLAN-Access, Enumerated, code 305, section 10.1.11
- WLAN-3GPP-IP-Access, Enumerated, code 306, section 10.1.12
- APN-Authorized, Grouped, code 307, section 10.1.14
- APN-Barring-Type, Enumerated, code 309, section 10.1.16
- WLAN-Direct-IP-Access, Enumerated, code 310, section 10.1.17
- Session-Request-Type, Enumerated, code 311, section 10.1.23
- Routing-Policy, IPFilterRule, code 312, section 10.1.24
- Max-Requested-Bandwidth, OctetString, code 313, section 10.1.26
- Charging-Characteristics, Integer32, code 314, section 10.1.27
- Charging-Nodes, Grouped, code 315, section 10.1.28
- Primary-OCS-Charging-Function-Name, DiameterIdentity, code 316, section 10.1.29
- Secondary-OCS-Charging-Function-Name, DiameterIdentity, code 317, section 10.1.30
- Maximum-Number-Accesses, Unsigned32, code 319, section 10.1.38
APN-Id (308) OctetString only present from
3GPP TS 29.234 V6.2.0 (2005-03) to 3GPP TS 29.234 V6.4.0 (2005-09)
before being deprecated in 3GPP TS 29.234 V6.5.0 (2005-12).
(Not provided here.)
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Wed, 08 Apr 2020 15:48:08 +1000 |
parents | 4c935aecee6c |
children |
line wrap: on
line source
# Sample configuration file for the echodrop.rgwx plugin of RADIUS/Diameter translation agent. # # This plugin allows to easily specify the following handling of RADIUS attributes # received in a RADIUS request: # - ECHO: the attribute will be copied verbatim in the RADIUS answer. # - DROP: the attribute is discarded. # # In both cases, the attribute is NOT translated in Diameter message. # # The format of this file is: # <action> CODE <code> [ VENDOR <vid> [ TLV <type> | EXT <ext-type> ] ]; # Where: # <action>: is either DROP or ECHO. # <code> : is a (decimal) integer between 0 and 255, and designates the type of the attribute. # # The remaining of the line is optional, and should only be used # with lines containing "CODE 26" (Vendor-Specific Attribute) # <vid> : a Vendor value (32 bit), see RFC2865 section 5.26 for detail. # # <type> : The attribute is interpreted as TLV (rfc3865, section 5.26) # and we match only this "vendor type" value (8 bits). # # <ext-type>: NOTE: THIS OPTION IS NOT SUPPORTED PROPERLY YET!!!! # The attribute is interpreted as extended attribute (draft-ietf-radext-extended-attributes-08) # and we match only this "Ext-Type" value (16 bits). # This option should only be used with "CODE 26 VENDOR 0". # # Note that the Proxy-State (code 33) attribute is handled directly as an ECHO parameter by the gateway core. # Examples: # DROP code 18 ; # Reply-Message attribute, should not be included in requests # DROP code 26 vendor 9 ; # Drop any Cisco-specific attribute # ECHO code 26 vendor 0 ext 256 ; # Echo any extended attribute with the type 256.