Mercurial > hg > freeDiameter
view doc/app_acct.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 | e5010975da35 |
children |
line wrap: on
line source
####################### # This file contains the description of configuration and general information about the # "App_Acct" extension. # This extension provides a simple Diameter Accounting server. # The extension does receive the Accounting-Request message, then # saves the contents of the AVP in a database, as configured here. # The data is not processed at all. The intent is that a dedicated # application will then pull from this database and process the data (consolidate # sessions, ...) # In order to enable this extension, the main freeDiameter configuration file # must contain the following declaration: # LoadExtension = "extensions/app_acct.fdx" : "/path/to/app_acct.conf" ; ####################### ################# ## Part I: AVP ## ################# # Configure here the AVPs that must be stored in the database. # The format is: # "AVP-dictionary-name" = { # field = "db-field-name"; # required; # multi=N; # }; # Where: # AVP-dictionary-name: # The name of the AVP, such as "Session-Id". Only this field is mandatory. # field="...": # The name of the field in the database where is AVP contents will be saved. # The default is that the field is named as the AVP-dictionary-name. # required: # By default, if the AVP is not in the Diameter message, it is not passed in # the INSERT statement (will get NULL). If Required is specified for the AVP, # an error is returned in the Diameter answer, and the data is discarded. # multi=N: # If an AVP may appear several times in a request, you may specify a number of # occurrences to save in the database. The Nth first occurrences of the AVP # will be saved in fields "db-field-name1", "db-field-name2", ... "db-field-nameN" # # In case the default behavior for an AVP is fine, you can use the short syntax: # "AVP-dictionary-name"; # # Note that at the moment, GROUPED AVP are not supported. Also, only the top-level AVPs are # searched. This behavior can be changed quite easily if needed. # You may look at contrib/app_acct_tools/app_acct.conf and database.sql files # for an example of setup. ####################### ## Part II: Database ## ####################### # You must specify the connection information to the database here. # Please note that if the connection is terminated, it will trig the shutdown of the freeDiameter daemon # For this reason, you should as much as possible use a local database. # ConnInfo: # The connection string to the database. See http://www.postgresql.org/docs/8.4/static/libpq-connect.html # Example: ConnInfo = "host=localhost port=5432 dbname=acct user=acct password=freediameter"; # Table: # The name of the table to use. The fields and types in this table must be created accordingly to the Part I configuration in this file. # Example: Table = "incoming"; # Timestamp_field: # Optionally, you can specify a name of a field that will receive the value 'now' when a new record is inserted. # Default: no timestamp is inserted. # Example: Timestamp_field = "recorded_on"; # Server_name_field: # Optionally, you can specify a field which will receive the Diameter Identity of the local server for each record saved. # This is useful especially if you have several Accounting servers and want to check Load-Balancing behavior or so, # after aggregating all the data. # Default: no server name inserted. # Example: Server_name_field = "recorded_serv";