Egress Transaction Management

The main functions of egress transaction management are:

• Support DRL controlled RADIUS compliant retransmissions of requests
• Creating, monitoring, and closing of source ports
• RADIUS ID acquisition and release
• Store information for conversion of a RADIUS Response message to a Diameter Answer message

Egress transaction management uses an egress pentransaction manager to support creation, lookup, extraction, and expiration of egress transaction record to support RADIUS compliant retransmission.

Egress transaction management uses a port number and a RADIUS ID to allocate and release RADIUS IDs for use in egress request messages.

The Local Node associated with RADIUS client connections are configured with client port ranges. RADIUS source ports are opened when any client connection associated with a Local Node needs a RADIUS ID and one is not already available. RCL shall create as many source ports as needed to cater to the number of RADIUS IDs required - that are in use (outstanding) waiting for a response.