Deletion

The Oracle Communications Session Border Controller needs to delete dynamic session agents no longer in use. But dynamic session agents should not be deleted too soon, in case they return to service. So, deletion occurs according to the process this section describes.

For each dynamically created session agent, the Oracle Communications Session Border Controller assigns and tracks the last registration expiry time. It determines this time by doubling the registered endpoint’s core side expiry. Where X is the last registration expiry value and Y is the registered endpoint’s core side expiry, the Oracle Communications Session Border Controller performs checks according to this criteria:

X > (2 * Y)

The the system updates the expiry time with the greater value. This way, whenever the dynamic session agent re-registers, it will have an updated expiry timer value.

Timeouts can also cause dynamic session agents to be deleted. Pings, status changes, transaction timeouts, DNS expiries and other system occurrences can trigger timeouts. When the Oracle Communications Session Border Controller detects that a timeout has occurred, the dynamic session agent is deleted.