Mercurial > hg > freeDiameter
view doc/test_netemul.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 | 083317a4e947 |
children |
line wrap: on
line source
# This file contains information for configuring the test_netemul extension. # To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation. # # The test_netemul extension implements a Diameter proxy that behaves like simple forwarding agent, # with the exception that it can introduce delay in the forwarding of the messages and generate duplicates # of messages, as can be expected from a real Diameter network. It can also generate routing errors when # connected to more than 2 peers. # LATENCY: # Two parameters are used to control the delay introduced in the messages. # - latency_average: # This is the average delay introduced in the packets. # Set to 0 to not add any latency (beyond the normal processing time). # The value is expressed as an integer followed by a unit which can # be 's' (seconds) or 'ms' (milliseconds). Example: # latency_average = 700 ms; # # - latency_deviation: # This parameter controls the variance in the latency. It is expressed # as a value between 0 % and 100 %. When set to 0 %, all messages will be delayed # by exactly latency_average. Otherwise, it represents the width of the interval # "around" the average where "most" of the latency will be chosen (the distribution # has a Gaussian shape). Example: # latency_deviation = 25 %; # # The default values give an added latency "mostly" between 0.4 and 0.6 seconds: # latency_average = 500 ms; # latency_deviation = 20 % ; # REORDERING: # There is no special control over the reordering of messages. It may simply happen # as a result of the latency. If you want to get a lot of reordering, set the # latency_variance to a high value. # DUPLICATES: # Duplicate messages are expected in the Diameter protocol by design, as a consequence # of the failover mechanism that provides the protocol's reliability. # - dupl_proba: # This value gives the probability of producing a duplicate of a forwarded message. # The value is comprized between 0 (no duplicates) and 1 (duplicate all messages). # Duplicates are created for requests, but may result in duplicate answers # received by your Diameter client(s), depending on your server(s)'s behavior. # In the case of freeDiameter client, the duplicate answer is automatically filtered out # because the hop-by-hop id has already been used. # Note that each duplicate copy is an independent message, # which receives a different latency, and might be routed to a different server if you # use for example load-balancing. # The parameter can take several forms: # dupl_proba = 0 ; # Disables the generation of duplicate messages completely. # dupl_proba = 1 / 10000 ; # dupl_proba = 0.0001 ; # Around 1 messages over ten thousands will be duplicated. # # Default value: # dupl_proba = 1 / 100 ;