Interesting Events
Interesting events on the Oracle® Enterprise Session Border Controller (E-SBC) are used 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, Configure terminal, session-router, sip-monitoring, interesting-events.
The E-SBC can monitor the following types of interesting events:
- short-session events
- local-rejection events
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 | Use to configure trigger
attributes that apply to the filters you set on the
E-SBC.
Note: Interesting Events are always enabled on a global-basis on the E-SBC. |
| type | Use to set the interesting events to monitor, for example, short-session and local-rejection. |
| trigger-threshold | Use to set 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 | Use to 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 as 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 Configure terminal, session-router, session-router-config, short-session-duration. 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, and SIP signaling error.
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 In such a situation, 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.
