Interesting Events
Interesting events on the Oracle® Enterprise Session Border Controller (E-SBC) are those events that are considered “interesting” for the purpose of troubleshooting SIP sessions in your network. You can specify the type of interesting event you want to filter using the object, interesting-events at the path, in the ACLI.
Currently, there are two types of interesting events that the E-SBC can monitor:
- short-session (short session events on the E-SBC)
- local-rejection (local rejection events on the E-SBC)
You can use the following trigger attributes to specify time provisioning for the interesting events:
- trigger-threshold
- trigger-timeout
Note:
You can also set a trigger-window object to support these trigger attributes. For more information, see Configuring a Trigger Window.The following table identifies the attributes you can set for the interesting-events object.
| Filter | Description |
|---|---|
| interesting-events | Allows you to configure trigger attributes that apply to the filters you set on the
E-SBC. You can configure the following interesting-event attributes:
Note: Interesting Events are always enabled on a global-basis on the E-SBC. |
| type | Sets the interesting events to monitor (short-session, local-rejection) |
| trigger-threshold | Sets the number of interesting events that must occur within the time set by the trigger-window value. If the number of events reaches the trigger-threshold during the trigger-window time, monitoring is started. |
| trigger-timeout | Sets the amount of time, in seconds, that the trigger is active once monitoring has started. If no interesting events occur in the time frame set for this value, monitoring never starts. For example, if trigger-timeout is set to 40, and no interesting events occur in 40 seconds, then monitoring never starts. |
The E-SBC considers short session and local rejection interesting events. A session is viewed as a short session if the length of time, in seconds, is equal to or below the short-session-duration value configured at the path . A local rejection can occur when sessions are locally rejected at the E-SBC for any reason (for example, Session Agent (SA) unavailable, no route found, SIP signaling error, etc.)
If a short session or local rejection event occurs, the E-SBC uses the values configured for the trigger attributes to determine when to start filtering the SIP session data.
If a short session event occurs when the E-SBC is NOT monitoring, the event information is taken from the last BYE that occurred in the session; therefore, only some parts of the call flow may display in the GUI. If a local rejection event occurs when the E-SBC is NOT monitoring, it displays only the information in the last rejected transaction.
Use the following procedure to configure interesting events for SIP Monitor and Trace on the E-SBC.
