IWF RAS Registration Failure Code Mapping
For calls that require interworking between H.323 and SIP, the Oracle® Enterprise Session Border Controller supports IWF response code mapping. This feature enables the Oracle® Enterprise Session Border Controller to support configurable SIP response codes for IWF calls that fail during RAS, when the Oracle® Enterprise Session Border Controller has been unable to register with a gatekeeper; this allows a wider range of more accurate response codes to be communicated.
When this feature is not enabled, the Oracle® Enterprise Session Border Controller generates a 404 Not Found when a SIP-to-H.323 call fails as a result of the stack’s failure to register with a gatekeeper.
When the condition noted above takes place, the response code can be any of the ones listed in this table. The code values listed in the table are used to specify the code to which you want to map.
Code | Description |
---|---|
403 | Forbidden |
406 | Not Acceptable |
408 | Request Timeout |
410 | Gone |
420 | Bad Extension |
480 | Temporarily Unavailable |
486 | Busy Here |
487 | Request Terminated |
500 | Server Internal Error |
503 | Service Unavailable |
504 | Server Time-out |
600 | Busy Everywhere |
603 | Decline |
To enable IWF RAS registration failure code mapping: