brainslog
brainslog
Currently the stack has basic support for SCTP. It should be investigated what (if anything) is required to support SCTP Multi-Homing feature and implement it.
In most SIP+Diameter scenarios it should be required that the related SIP and Diameter messages for the same session are delivered to the same node (colocation). For such behavior it...
Currently the TLS support in Diameter stack is somewhat "proprietary", based mostly on the way RFC 6733 specifies, and it's known to work properly between two jDiameter instances but not...
Currently timeouts are not passed to the application, leaving to the SLEE application to use other ways to detect those (eg, setting timers). A SLEE event type should be implemented...
Using ThreadGroup is not recommended and it has already brought some problems. It's usage should be replaced and references to it (docs, config) removed.
Add support for (re)creating a Diameter lost/non-existing session, for instance, when receiving and UPDATE_EVENT or TERMINATE_EVENT CCR for a non-existing session.
Mobicents Diameter Stack should support the updated Diameter Base Protocol, as of [RFC 6733](http://tools.ietf.org/html/rfc6733). This issue should serve as an umbrella issue for the several changes introduced (for which individual...
For instance, on each message send, the following is performed: `long timeOut = container.getConfiguration().getLongValue(MessageTimeOut.ordinal(), (Long) MessageTimeOut.defValue());` Behaviors like this should be replaced by storing the configuration value in a local...
Mobicents jDiameter Stack has minimal support for functional nodes other than Server or Client, such as Relay, Proxy, Redirect and Translation. This support should be improved and create some tests/examples...
Mobicents jDiameter Stack has minimal support for functional nodes other than Server or Client, such as Relay, Proxy, Redirect and Translation. This support should be improved and create some tests/examples...