Updates:
        Labels: -Version-1.4.0 -Release-Type-Beta Version-1.3.2 
Release-Type-FINAL
        Status: Fixed

Comment by brainslog:
(No comment was entered for this change.)

Affected issues:
  issue 729: Create Diameter Base performance/soak test
    http://code.google.com/p/mobicents/issues/detail?id=729

issue 1257: Improve sessions and messages with all relevant setter/getters - propagate to RAs if needed
    http://code.google.com/p/mobicents/issues/detail?id=1257

issue 1506: Populate org.jdiameter.api.Avp with application specific AVP Codes
    http://code.google.com/p/mobicents/issues/detail?id=1506

  issue 1945: Isolate MessageParser from Diameter Stack
    http://code.google.com/p/mobicents/issues/detail?id=1945

issue 1946: Verify correct behavior and create jUnit tests for Diameter retransmissions.
    http://code.google.com/p/mobicents/issues/detail?id=1946

  issue 1949: 31st October 2010
    http://code.google.com/p/mobicents/issues/detail?id=1949

issue 1983: Diameter MUX is not correctly clearing listeners when they unregister
    http://code.google.com/p/mobicents/issues/detail?id=1983

  issue 2000: Diameter stack threads leaking, not being released
    http://code.google.com/p/mobicents/issues/detail?id=2000

  issue 2001: Diameter Peer FSM "exitAction" is invoked for wrong state
    http://code.google.com/p/mobicents/issues/detail?id=2001

issue 2060: Create Diameter stack specific messages and sessions for Ro/Rf Applications
    http://code.google.com/p/mobicents/issues/detail?id=2060

issue 2062: Provide Diameter Rf Resource Adaptor with 3GPP grouped AVPs objects
    http://code.google.com/p/mobicents/issues/detail?id=2062

issue 2063: Provide Diameter Rf Resource Adaptor with specific ACR messages
    http://code.google.com/p/mobicents/issues/detail?id=2063

issue 2065: Provide Diameter Ro Resource Adaptor with specific CCR/CCA messages
    http://code.google.com/p/mobicents/issues/detail?id=2065



--
You received this message because you are listed in the owner
or CC fields of these issues, or because you starred them.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

Reply via email to