Supporting Released Flows that are Subsequently Hairpinned back to the OCSBC

The Oracle Communications Session Border Controller (OCSBC) allows you to quickly re-establish media flows for released calls that may be hairpinned back the OCSBC by other network elements.

When the OCSBC releases a media flow, it also deletes information related to that flow by default. For a call that the environment subsequently hairpins back to the OCSBC, there is a delay in determining how to forward it. You can configure the OCSBC to retain IP/port information for all released calls to cause it to quickly process and forward these calls. To do this, you configure the media-manager with the hairpin-released-flows option.

ORACLE(media-manager)# options +hairpin-released-flows

This configuration makes the OCSBC store the IP/port information of the released media port sent out in the SDP. Should a proxy or media server send the media connection with that IP/port back to the OCSBC, the OCSBC recognizes the leg and performs the proper linking between the flows.

Recall that you determine whether the OCSBC releases or manages media using the mm-in-realm, mm-in-network, mm-same-ip and mm-in-system settings in the realm configuration.