Reject Action

When you use this action type and a condition matching the manipulation rule arises, the Oracle® Enterprise Session Border Controller rejects the request (though does not drop responses) and increments a counter.

• If the msg-type parameter is set to any and the message is a response, the Oracle® Enterprise Session Border Controller increments a counter to show the intention to reject the message—but the message will continue to be processed.
• If the msg-type parameter is set to any and the message is a request, the Oracle® Enterprise Session Border Controller performs the rejection and increments the counter.

The new-value parameter is designed to supply the status code and reason phrase corresponding to the reject. You can use the following syntax to supply this information: status-code[:reason-phrase]. You do not have to supply the status code and reason phrase information; by default, the system uses 400:Bad Request.

If you do supply this information, then the status code must be a positive integer between 300 and 699. The Oracle® Enterprise Session Border Controller then provides the reason phrase corresponding to the status code. And if there is no reason phrase, the system uses the one for the applicable reason class.

You can also customize a reason phrase. To do so, you enter the status code followed by a colon (:), being sure to enclose the entire entry in quotation marks () if your reason code includes spaces.

When the Oracle® Enterprise Session Border Controller performs the reject action, the current SIP manipulation stops processing and does not act on any of the rules following the reject rule. This course of action is true for nested SIP manipulations that might have been constructed using the sip-manip action type.