Filtering Data for Operations Monitor

You can configure the Enterprise SBC to filter the data it sends to a monitor collector to simplify your system monitoring and troubleshooting. You do this by configuring one or more filter-profile elements within the comm-monitor elements.

To configure a filter-profile, you specify the source from which to capture, the destination to which to send the data, and the applicable traffic to capture:

• Source of captured traffic—You specify the sip-interface, realm, and network-interface element(s) from which you capture within each filter-profile. If you do not configure these parameters, the system sources from all sip-interface, realm or network-interface objects that apply.
• For example, if you configure a realm, but not a sip-interface, the system captures from every SIP interface on that realm.

  If the system encounters overlapping profiles during filter processing, it uses a precedence for capturing, choosing the filter-profile for the sip-interface first, then the realm, then network-interface to determine the object from which it captures.

• Destination of captured traffic—You specify filter-profile configurations for each individual communication monitor instance (Mediation Engine). You do this by configuring the filter-profile-list parameters in separate monitor-collector sub-elements, with filter-profile names.
• Applicable traffic—You specify the traffic you want to capture within the filter-profile. You first configure the type and, when applicable, method parameters in each filter-profile. The method values only apply to specific traffic type settings.

Note:

More than two filter-profile-list assignments to single monitor-collector can cause a significant drop in the system performance.

Value descriptions for the captured traffic type and, when applicable, method parameters include:

• SIP—Specifies that this filter captures SIP traffic. For dialog creation methods, the system applies this filter for complete, end-to-end dialogs. You can configure a method to act in conjunction with this type. If you do not set a method, the Enterprise SBC captures all of the method traffic listed below. If you configure the method parameter, the Enterprise SBC further filters the output to include traffic for that method only.

  When you use the SIP traffic type, you can configure one or more of the following method values:

  • INVITE—Filters for INVITE to BYE. The system filters all in-dialog methods other than OPTIONS/MESSAGE/REGISTER/ SUBSCRIBE/NOTIFY.
  • OPTIONS—Filters for transaction-based messages only
  • MESSAGE—Filters for transaction-based messages only
  • REGISTER—Filters for transaction-based messages only
  • SUBSCRIBE-INDIALOG—Filters for INVITE session in-dialog subscribe/notify messages.

    To enable SUBSCRIBE-INDIALOG method filter-profile, you must configure the INVITE/ALL type.

  • SUBSCRIBE-OUTDIALOG—Filters for out-of-dialog (Non-INVITE) subscribe and notify messages.
• DNS—Filters for DNS traffic only. The method parameter does not apply.
• ENUM—Filters for ENUM traffic only. The method parameter does not apply.
• QOS—Filters for QoS Report traffic only. The method parameter does not apply.
• MSRP—Filters for MSRP traffic only.

  For MSRP, the only method that applies is INVITE. This includes end-to-end calls where the INVITE includes SDP. The system then filters for all in-dialog messages subsequent to each INVITE. If the INVITE does not include SDP, the Enterprise SBC does not filter for any of those in-dialog messages.

  Note:

  The Enterprise SBC supports MSRP signaling message filtering for Early Offer Answer deployments only. Filtering is not supported for Late Offer/Answer deployments.
• ALL—The system captures all SIP/DNS/ENUM/QOS/MSRP traffic as specified by your type configuration.

Related Configuration

With respect to filtering data sent to Communications Monitor, additional configuration requirements include:

• You must enable the state parameter on the comm-monitor for your filter-profile configurations to be operational.
• You must enable the MSRP license to use the MSRP type.
• For the QoS type parameter:
  • You must enable the Quality of Service entitlement to use a filter-profile with the QoS type.
  • You must enable the qos-enable parameter on the applicable realm to use a filter-profile with the QoS type.

    ORACLE(realm-config)#qos-enable enabled

  • When you configure a filter-profile for QoS, the filter-profile-list only forwards QOS data. In addition to the filter-profile, however, you can further limit your capture to interim QoS reports when you enable the interim-qos-enable within the applicable realm-config.

    ORACLEORACLE(realm-config)#interim-qos-enable enabled

    Note:

    Prior to this feature, you could only configure the interim-qos-enable parameter in the comm-monitor element.

    Note:

    Additionally, if you have enabled the sip-advanced-logging (feature) within the applicable realm-config in addition to the interim-qos-enable, then the system only forwards IPFIX data to the OCOM server for the calls where conditional logging is set in MBCD.