IR.92 Multiple Emergency Numbers
The Oracle Communications Session Border Controller expands compliance with the IR.92 standard by including an alternative service and message for emergency traffic.
The Oracle Communications Session Border Controller can be configured with multiple emergency services based on the dialed number match. Custom messages can be configured through the sip-380-reason parameter.
When an emergency call is received at the Oracle Communications Session Border Controller Proxy Call Session Control Function, the system checks any Network Management Control (NMC) rules that are enabled for the ingress realm. If the call matches a rule's destination-identifier parameter and fails with a 380 response, then that rule's sip-380-reason will be used in the response. Conversely, if the matching rule's sip-380-reason is empty or no matching NMC rule is found, then the value of the sip-interface's send-380-response will be used as the reason. If the send-380-response is also empty, the default reason "priority calls not allowed" will be used. This logic also applies if the call fails and no matching network management control rule is found. The Oracle Communications Session Border Controller will use the value of the sip-interface's send-380-response as the reason or the default message if the value is empty. The valid values for send-380-response are any string. It is not required.
This functionality is configured through the sip-380-reason parameter in the net-management-ctrl object.
