Mercurial > hg > freeDiameter
view doc/rt_busypeers.conf.sample @ 1517:9e233ef0b07e
Add 3GPP TS 29.283 V15.1.0 (2019-09)
Add AVPs:
- MCPTT-ID, UTF8String, code 4500, section 7.3.2
- Data-Identification, Grouped, code 4501, section 7.3.3
- Data-Identification-Prefix, Unsigned32, code 4502, section 7.3.11
- Data-Identification-Flags, Unsigned64, code 4503, section 7.3.12
- DPR-Flags, Unsigned32, code 4504, section 7.3.13
- DPA-Flags, Unsigned32, code 4505, section 7.3.14
- DUR-Flags, Unsigned32, code 4506, section 7.3.15
- DUA-Flags, Unsigned32, code 4507, section 7.3.16
- NDR-Flags, Unsigned32, code 4508, section 7.3.17
- NDA-Flags, Unsigned32, code 4509, section 7.3.18
- User-Data-Id, Unsigned32, code 4510, section 7.3.19
- MC-Service-User-Profile-Data, Grouped, code 4511, section 7.3.20
- Sequence-Number-29.283, Unsigned32, code 4512, section 7.3.21
- Data, Grouped, code 4513, section 7.3.22
- MCVideo-ID, UTF8String, code 4514, section 7.3.24
- MCData-ID, UTF8String, code 4515, section 7.3.25
Note: Name conflict with 3GPP TS 29.140 Sequence-Number (1107).
and 3GPP TS 29.329 Sequence-Number (716).
3GPP TS 29.140 V6.1.0 (2005-06) allocated Sequence-Number (1107).
3GPP TS 29.329 V10.0.0 (2010-09) CR 0163 added Sequence-Number (716).
3GPP TS 29.283 V13.1.0 (2016-06) allocated Sequence-Number (4512).
Fix: Sequence-Number (4512) renamed to Sequence-Number-29.283 (4512).
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Thu, 09 Apr 2020 10:32:09 +1000 |
parents | 7ee7b95701c9 |
children |
line wrap: on
line source
# This file contains information for configuring the rt_busypeers extension. # To find how to have freeDiameter load this extension, please refer to the freeDiameter documentation. # # The rt_busypeers extension has two purposes. # - when the local peer receives an error DIAMETER_TOO_BUSY from a peer, # this extension catchs this error and attempts to retransmit the query to another peer if it makes sense, i.e.: # * the peer issuing the error is not the peer referenced in the Destination-Host AVP of the message, # * we have a direct link with the peer that issued the error (see parameter RetryDistantPeers below) # # - When a request is forwarded by the local peer, start a timer and if the corresponding answer/error has # not been received within RelayTimeout seconds, either send to another peer or return a DIAMETER_TOO_BUSY # error, depending on the RetryMaxPeers parameter. # # This extension is mainly useful for Diameter agents, for Diameter clients it is recommended to # implement this logic directly in the client application. # Parameter: SkipTooBusyErrors # If defined, this parameter disables the handling of Diameter Errors message with a Result-Code set to DIAMETER_TOO_BUSY in this extension. # When this parameter is defined, the parameter RetryDistantPeer has no effect. # Default: parameter is not defined. #SkipTooBusyErrors; # Parameter: RetryDistantPeers # By default, the extension only retries to send messages if the peer that issued the DIAMETER_TOO_BUSY error is directly connected to # the local peer (not through a Diameter agent). This avoids the situation where the message is sent to a different relay that will deliver # to the same busy peer afterwards. If the parameter is defined, then the extension will also retry sending messages for errors generated in # distant peers. This should increase the chance that the message is delivered, but also can increase the load of the network unnecessarily. # Default: parameter is not defined. #RetryDistantPeers; # Parameter: RetryMaxPeers # This parameter specifies the limit on the number of times a request can be re-sent to a different peer, before the local relay gives up and # forwards the error to upstream. # Default: 0, meaning all possible candidates are attempted before give up. #RetryMaxPeers=0; # Parameter: RelayTimeout # If the value of this parameter is not 0, it specifies the number of milliseconds (1/1000 s) that the local relay waits for an answer to a # forwarded request before considering the remote peer is busy and taking corrective action (similar as if that relay had returned TOO_BUSY status). # Note: this parameter does not apply for requests issued locally. In that case, the extension issuing the request should directly specify the timeout. # Default: 0, meaning that there is no timeout parameter. #RelayTimeout=0;