SIP Local Response Code Mapping

The SIP local response code mapping feature enhances the SIP response code mapping. The SIP response code map feature lets you establish a table that maps SIP response-received messages (entries) to response-to-send messages (entries).

SIP local response code mapping is used with the SIP responses generated by the Oracle® Enterprise Session Border Controller towards a specific SIP session agent. This feature lets you provision the mapping of the response codes used by the Oracle® Enterprise Session Border Controller when it generates the responses towards a session agent.

You create the SIP local response code map using the existing mapping functionality, and then assigning that map to a session agent or to a SIP interface.

Note:

The configured response map is not used when the Oracle® Enterprise Session Border Controller is acting as proxy for the responses to this session agent.

The parameters method and register-response-expires enable a SIP registration response mapping feature that allows you to configure the Oracle® Enterprise Session Border Controller to remap a SIP failure response—which it receives from another network device or that it generates locally—to a 200 OK. You might want the Oracle® Enterprise Session Border Controller to perform this type of mapping for circumstances where non-malicious endpoints continually attempt registration, but will stop (and still not be registered) when they receive a 200 OK. This response mapping does not actually register the client with the Oracle® Enterprise Session Border Controller, meaning that there is neither a registration cache entry or a CAM ACL for it.

For the 200 OK it generates, the Oracle® Enterprise Session Border Controller removes any Reason or Retry-After header in the 200 OK and sets the expires time. By default, the expires time is the Retry-After time (if there is one in the response) or the expires value in the Register request (if there is no Retry-After expires time). You can also set this value using the register-response-expires parameter, but the value you set should never exceed the Register request’s expires time.