From 14e8bfe73c15ce4a9cfd85179d1d0e9a5fbfcbd1 Mon Sep 17 00:00:00 2001
From: Erlang/OTP
+ The possibility of choosing a handler process for an + incoming Diameter request with a configured MFA was + documented in OTP 20.0, but counters (with + {traffic_counters, true}) were not incremented when this + process was on a remote node. Counters are now + incremented on the node that configures the transport in + question.
++ Introduced in OTP 21.3.
++ Own Id: OTP-16457
++ Transport options differing from those passed to + diameter:add_transport/2 were used in several situations: + when starting a transport process after connect_timer + expiry after an initial connection attempt has failed, + when starting a transport process after a connection has + been accepted, when sending events, when returning + options in diameter:service_info/2, and possibly more. In + particular, the following configuration options to + diameter:add_transport/2 were dropped: avp_dictionaries, + incoming_maxlen, spawn_opt, strict_mbit.
++ Moreover, any service options mistakenly passed to + diameter:add_transport/2 were interpreted as such, + instead of being ignored as the documentation states, + with the consequence that outgoing and incoming requests + saw different values of some options, some were always + taken from transport options, and others from service + options.
++ diameter:add_transport/2 must be called in new code for + the fix to have effect.
++ Introduced in OTP 20.1.
++ Own Id: OTP-16459
+