Unsuccessful Transfer Scenarios

The Oracle® Enterprise Session Border Controller does not successfully handle the following failed, unusual, and unexpected transfer scenarios:

• The new INVITE to the Referred-To party gets challenged, the Oracle® Enterprise Session Border Controller does not answer the challenge. It is treated with the 401/407 response just as any other unsuccessful final response.
• The header of the REFER message contains a method other than INVITE or contains URI-parameters or embedded headers not supported by the Oracle® Enterprise Session Border Controller.
• The Oracle® Enterprise Session Border Controller shall allow the Referred-To URI that happens to resolve to the same next-hop as the original INVITE went to, to do so.
• The Oracle® Enterprise Session Border Controller ignores any MIME attachment(s) within a REFER method.
• The Oracle® Enterprise Session Border Controller recurses (when configured to do so) when the new INVITE sent to the Referred-To party receives a 3xx response.
• The transferee indicated support for 100rel, and the original two parties agreed on using it, yet the Referred-To party does not support it.
• The original parties negotiated SRTP keys.
• The original parties agreed on a codec using a dynamic payload type, and the Referred-To party happens to use a different dynamic payload number for that codec.