SIP Monitor and Trace Filter Configuration Objects
The Oracle® Enterprise Session Border Controller (E-SBC) provides configuration objects you can set on the E-SBC to customize filters for SIP Monitor and Trace. The system can monitor and filter specific SIP session data and display it to the GUI. The filter objects you can configure include:
| Filters | Description |
|---|---|
| filter-config | Use to create custom filters for
SIP Monitor and Trace. You can configure session agents (SA) and realms to use
such filters, or set sip-monitoring to use the filters on a global basis.
For more information, see Creating Custom Filters . |
| sip-monitoring | Use to configure SIP Monitor and
Trace features.
Note: You must configure the sip-monitoring object to enable filtering. You must also configure a session agent or realm, or you must set filtering on a global basis for Monitor and Trace to occur. |
| state | Use to enable and disable SIP
Monitor and Trace.
For more information, see Enabling Disabling SIP Monitoring & Tracing . |
| monitoring-filters | Use to specify the name of the
custom filter to use on a global basis. This value is based on the filter
created in “filter-config.” You can also specify an asterisk (*) as a value for
this attribute, which monitors all session data on the
E-SBC.
For more information, see Using Filters to Monitor on a Global-Basis . |
| interesting-events | Use to configure the following
attributes:
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 monitoring starts. 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. Note: Interesting Events are always enabled on a global-basis on the E-SBC. For more information, see Configuring Interesting Events . |
| trigger-window | Use to specify the amount of time,
in seconds, for the window of time that the trigger-threshold value must reach
before monitoring begins. For example, if type is set to short-session,
trigger-threshold is set to 2, and trigger-window is set to 60, monitoring
begins when the
E-SBC discovers 2
short-session events in a 60 second window.
For more information, see Configuring a Trigger Window . |
