Age | Commit message (Collapse) | Author |
|
Addresses returned from a transport module were always used to populate
Host-IP-Address AVP's in an outgoing CER/CEA, which precluded the
sending of a VIP address. Transport addresses are now only used if
Host-IP-Address is unspecified.
In other words, respect any configured Host-IP-Address, regardless of
the physical addresses returned by the transport. To use the physical
addresses, don't configure Host-IP-Address.
|
|
A transport module can return a local address list from its start/3
function in order to specify addresses to be used as Host-IP-Address
during capabilities exchange. Now allow addresses to be communicated in
a 'connected' message in the case of a connecting transport, so that
diameter_tcp (in particular) can make local address configuration
optional, communicating the gen_tcp default after connection
establishment instead.
|
|
|
|
|
|
|
|
Callback makes sending of DPR configurable.
|
|
|
|
|
|
|
|
Type references enclosed in <c></c>.
|
|
|
|
|
|
Diameter node/peer having been the most vicious terminology blunder.
|
|
|
|
Added an introductory chapter to the User's Guide as well as more
detailed release notes.
|
|
The application provides an implementation of the Diameter protocol
as defined in RFC 3588.
|