Exceptional Cases

When the relevant option in enabled, the Oracle® Enterprise Session Border Controller can handle properly the following cases of codec change:

• When the H.323 side rejects the request mode change, the Oracle® Enterprise Session Border Controller response to the SIP side with a 488 Not Acceptable. Session description and state remain unchanged, and the call continues using the original session description.
• When the H.323 side does not respond to the request mode change within the timeout limitation, the Oracle® Enterprise Session Border Controller releases the call on both sides.
• When the SIP side does not respond to the ReINVITE within in the timeout limitation, the Oracle® Enterprise Session Border Controller releases the call on both sides.
• When the intersection of codec is empty, the Oracle® Enterprise Session Border Controller rejects the codec change on the SIP side with a 488 Not Acceptable and on the H.323 side with an H.245 RequestModeReject. Session description and state remain unchanged, and the call continues using the original session description.
• If the Oracle® Enterprise Session Border Controller does not receive any of the LogicalChannel request or acknowledgement messages, the Oracle® Enterprise Session Border Controller releases the call on both sides.

Note that for protocol timeout errors, the preferred behavior is to release the call on both sides. Timeout errors usually indicate network problems, such as an endpoint being unreachable.