This chapter provides a summary of the Oracle Communications Operations Monitor system settings.
302 Redirected: To-URI suffix length
How many characters of the user part of the Contact: and Request URI must match to merge a call. Use 0 to disable this option.
APID request interval for querying SBCs
Number of seconds interval for retrieving informations about autodiscovered SBCs. It is not recommended to alter this value.
Alerting delay after core restart
The length of time alerts are suppressed after a core restart, in minutes.
Allow regeneration of registration events for user updates
If a user is registered in core once, its realm will not be re-checked until the registration expires and gets renewed. If realms are changed continuously and/or customer needs to have registrations always matched to the current realms configuration, enable this option. Be aware that this has some performance impacts on core registration processing.
Append a string at the end of User Tracking searches
When using User Tracking, also look for aliases that have this suffix appended to the number.
Authentication token (shared secret between MEC and ME)
Secret used by the Mediation Engine Connector to sign requests proxied to this Mediation Engine.
Auto-refresh interval for grids
Number of seconds between auto-refresh (if enabled) for grids with this feature.
B2B incoming backlog search for merging
The number of seconds to search the outgoing call leg in the past when an incoming leg is received.
B2B outgoing backlog search for merging
The number of seconds to search the incoming call leg in the past when an outgoing leg is received.
Bind user sessions to IP addresses
Bind each session to an IP address.
Bulk counters/KPIs maximum limit
The maximum limit of counters being added in bulk.
This value represents the interval in minutes for which partial Call Detail Record (CDR) data will be created. The allowed range of this interval is from 0 - 10 minutes. If 0 is given then the partial CDR generation feature is turned off. Warning: Turning on this feature has an impact in performance.
The default limit in minutes to cutoff Control Plane Monitor transaction queries. A value of 600 will result in the transactions grid showing transactions in the range of [ NOW(), NOW() - 10 Hours].
Cache time interval in minutes for User Agent statistics
If User Agent Statistics is active, the results are stored in an internal application cache that is refreshed at the interval defined in this system setting. The value is defined in minutes and the default is 60 minutes. There is no upper time limit for this setting and a value less than five minutes disables the cache which is not recommended for performance reasons.
Maximum number of messages to include in the call report messages section.
Additional Cascading Style Sheet (CSS) rules can be defined here that will be included when generating a call report PDF.
Color of the headings and footer on PDF call reports. Can be the name of a color, or a hexadecimal representation of the color: #ff0000.
Call Transfer: Seconds for correlating calls using REFER
The number of seconds the Mediation Engine looks back for calls containing a REFER causing the current call. If 0, correlating the referred and referring call is disabled for the Call Transfer information.
Call Transfer: correlate using Replaces
Set to true to match calls involved in a call transfer using the Replaces header.
The maximum height of the call flow diagram in pixels.
The maximum width of the call flow diagram in pixels.
The maximum number of messages displayed in a call flow.
When set, the in-browser call flow diagrams will be loaded in several stages, with progressively more information for some messages. This might improve rendering performance.
Call flow timestamp for fragmented messages
Use last fragment's timestamp as the timestamp for the message.
Call flow tree's expanded levels
Expanded levels in the popup for a message.
Cleanup Actions Syslog logging facility
Which logging facility should be used for the Mediation Engine's cleanup actions. Leave negative if this should be disabled. Allowed values are zero through to seven.
Custom header for realm definition
Specify a SIP header field name that is used to match the "Custom Pattern" definition for a realm.
Custom SIP headers in CDR file
A space-separated list of custom SIP header fields to be included in the CDR file. The customization of CDR generation uses these fields. For more information, see "Customizing CDR Generation".
Day on which the week should begin
Defines the day at which the week should begin. A page reload is required for this setting to take effect.
Days until inactive account expires
Expire inactive accounts after the given number of days.
Above this number of devices, device counters will be removed.
The time between sending out digests of recurring alerts in minutes.
If enabled, users cannot make logo changes.
If enabled, users cannot make password or logo changes.
The size of the raw buffer in MB. This buffer is used for creating traces starting in the past. Warning: Increasing this setting might require adjusting memory quotas. Please contact Oracle or your system integrator.
Enables publishing periodic call events for established calls. Enable this setting in order to allow the connection between OCOM and OCFM (Fraud Monitor)
Enable if you want the Mediation Engine to generate CDR files. Please see the user manual for details about the format used and how to get the files.
Enables the processing of BGF messages in MEGACO.
If enabled, saved calls can be shared globally. If you run a multi-tenancy setup, this feature should be DISABLED.
If enabled (the default), Operations Monitor can display a real-time map of the configured platform devices and of the interactions between them. Please note that due to browser and backend performance reasons, this map cannot work for a large number of configured device counters. It is therefore recommended to disable this setting when configuring more than 20 devices or realms. In order to configure the maximum number of devices supported, adjust the Device Map Limit setting.
External authentication enabled
Enables or disables HTTP header authentication driven by the reverse proxy (NGINX or Apache).
Enforce stringent password rules
A set of higher security rules for user passwords.
If enabled, non-admin users will be required to change their passwords periodically. This option can be overridden from the Mediation Engine Connector.
Enable to export selected KPIs via the Oracle Communications Data Model file based integration.
Extend calls by hash inspection
During call legs discovery across multiple sites, a neighboring Mediation Engine can be interrogated multiple times, rather than only once.
Find similar aliases in User Tracking by using a suffix of this many characters
If this value is non-zero, the User Tracking page first searches the alias list for similar usernames/phone numbers and then displays the calls and registration events for all of them. To usernames/phone numbers are considered similar if the last N number of characters are identical, where N is the value of this setting.
If enabled, the fronted will query the core process on each request to get the very latest state information. This can increase the delay before the answer is made, but generally makes the information more up to date.
How many hours a database partition should hold. There can be at most 1024 partitions.
Grey out non-preferred numbers
Numbers that haven't been derived from a configured number determination source will be displayed in gray in the calls table.
Group new registrations from the same user
Group new registrations from the same user.
Guarantee sorting of VSI traces
Due to the distributed nature of the Mediation Engine, it is possible that the packets in the traces buffer are out of order. If this option is enabled, the Mediation Engine will re-sort the packets by their timestamp.
HTTP address of the Mediation Engine Connector
HTTP address where to reach the Mediation Engine Connector. This is automatically set from the Mediation Engine Connector.
Headers in which to look for realm URIs
A space separated list of SIP header fields, for example, Diversion P-Asserted-Identity. Realm matching will include these fields (in addition to To and From).
Hide Megaco messages before off-hook
This option helps if the MEGACO transactions IDs are reused very quickly. It will hide the messages that are assigned to the leg before the off-hook event.
Hide active user session info when limit is reached.
Hide hardware addresses input from devices configuration
If set to true, the hardware addresses field will be hidden from the platform devices wizard.
The high threshold for determining the MOS.
If disabled, registrations from inside the platform will be recorded. This might make some REGISTER transactions to be incorrectly considered unauthorized because the 401/407 answer is seen more than once.
Ignore internal registrations for User Devices statistics
If enabled, the internal registrations (starting from a platform device) will be ignored when computing the User Devices statistics.
Ignore mismatch on contact URI (registrations)
Some registrars change the Contact URI in a reply to a REGISTER. This tells the Mediation Engine to ignore mismatching URIs, but might lead to merging multiple registrations into one.
Ignore non RFC 3261 params in SIP URI username
If set to true, the Mediation Engine will remove the parameters appended to the username before matching the SIP URI username.
Ignore plus prefix number when matching realms
By default the "+" number prefix is ignored in realm matching, when turned on, this option will assign numbers containing + only to the default realm.
The initial search range (in seconds) for calls, registrations etc to search before asking if the search should continue. If 'Paging query range' is bigger, that value will be used.
Defines a threshold for jitter KPIs (in ms) based on RTCP. Any jitter value above this threshold is ignored for the KPI computation. 0 means no threshold.
Limit select queries to this many seconds
Stop SELECT queries if they take more than this many seconds. Set to 0 to disable.
Log user authentication failures
Log information when a user fails to login.
A splash page which is shown after login. Removing all content will disable the splash page.
If enabled, when searching users by using the live search feature, the last digits of the number act as wildcards to suggest similar numbers from the same range.
The low threshold for determining the MOS.
Match registration events by comparing a suffix of the username
The Mediation Engine matches the related registration attempts by the SIP username. If this value is zero, then the whole username is used. If more than zero, the number defines how many digits/characters must match.
The maximum number of times a user can login in parallel.
The maximum number of users that can be logged in at the same time.
The maximum number of traces that can be running at the same time.
Maximum frequency for raising alerts
Determines at what point raised alerts that are not read can be raised again. If an alert has been continuously raised for more than this amount of seconds, it is eligible for being raised again.
The maximum number of lines that a CDR file can contain. When this limit is reached, the Mediation Engine automatically creates a new CDR file.
Maximum number of calls exported with bulk export
The maximum number of calls that can be exported with one bulk export.
Maximum number of items returned by each request to the REST interface
Maximum number of items returned by each request to the REST interface.
Maximum number of legs in one call
If a call already has this many calls, the Mediation Engine won't merge new legs in the same call, even if they match according to the merging algorithm. The purpose of setting a maximum is to avoid infinite calls.
Maximum number of lines exported with CSV export
The maximum number of lines that can be exported with one CSV export.
Maximum number of messages per leg
Configure maximum number of messages to be stored per leg.
Maximum number of number alert definitions per user
Maximum number of number alert definitions that a user can create.
The maximum output size by script run in bytes that is shown. It's stored in memory.
Maximum simultaneous script runs
The maximum number of script runs that can run simultaneously.
The maximum number of script runs that are stored. If this number is exceeded the oldest script runs are removed as needed to stay under this limit.
Mediation Engine Connector hash on P-Charging-Vector icid-value parameter
To enable call merging in Mediation Engine Connector, you hash the INVITE message of the corresponding leg. By default, the Mediation Engine hashes the full INVITE message. When enabled, and the INVITE message contains a P-Charging-Vector header with an icid-value parameter, the value of the icid-value parameter is used to find a match instead of a hashing the full INVITE message.
Field | Value |
---|---|
type | Boolean |
flags | Browse |
default | False |
Mediation Engine Connector hash search on all external legs
To enable call merging in Mediation Engine Connector, you hash the INVITE message of the corresponding leg. By default, the mediation engine hashes all the call legs that traverse between neighboring mediation engines. When enabled, a hash is added to all call legs to or from unknown IP addresses. This option exists for backward compatibility: enabling this option is not recommended if you require call correlation.
Field | Value |
---|---|
type | Boolean |
flags | Browse |
default | False |
Note:
Oracle recommends that the Mediation Engine Connector hash search on all external legs system setting is set to disabled.If this setting is enabled, Mediation Engine will merge two legs that have the same Call-ID even if they are not incoming/outgoing to the same device.
The Oracle database connection string to be used for querying Oracle Communications Data Model.
Omit the gray bars in charts.
Time range a query covers in a single paging request (in seconds).
Partitions to display in Recent calls
Number of partitions to display at once in Recent calls.
Partitions to display in User tracking
Number of partitions to display at once in User tracking calls.
If enabled, the users will be required to respect a set of rules for their passwords (minimum 8 characters, one non-lowercase letter character, no reference to the user name).
Passwords expire duration for non-sensitive enabled users
Number of days after which users without access to sensitive information are required to change their password.
Passwords expire duration for sensitive enabled users
The number of days after which users with access to sensitive information are required to change their password.
Choose the RUDP decoding mode: when 'quick push' mode is activated, the data chunks will be processed as soon as they are read, rather then waiting for the corresponding ACK. This allows better operation of the Mediation Engine in cases where ACKs are delayed excessively, but it will also prevent the detection of some malfunctions in the protocol (like lost packets).
Days during which a new alert identical to a raised unread one will not be created.
Refer: Merging calls requires full Contact match
If call merging on REFER is enabled this option controls whether the full Contact URI must match between the INVITEs of the original call and the referred one. If enabled the complete Contact URIs of both INVITEs are compared, if disabled only the user name parts are compared.
Refer: Seconds for merging calls
The number of seconds the Mediation Engine looks back for calls containing a REFER causing the current call. If 0, merging the referred and referring call is disabled.
How many characters of the user part of Refer-To: and To: must match to merge a call. Set to 0 to compare the full user part.
The refresh interval in seconds that overrides the default one in each portlet when the user reloads the dashboard. Set to 0 to use each portlet's default interval.
When a REGISTER transaction occurs and a registration binding is expired, generates 'Expired' registration events for the expired contacts. No messages are associated with this type of event.
This system setting allows you to configure whether or not the expired registration events should be displayed in the Registrations panel. By default, this system setting is enabled.
If enabled, a REGISTER transaction in which not all previous known contacts of the user are seen in the successful answer generates gone events for the missing contacts. Leave disabled if this is expected in your network.
Rotate CDR files every N seconds
If this option is non-zero, the CDR files are rotated every N seconds, where N is the value of the setting.
Choose the SCTP decoding mode: when quickpush mode is activated, the data chunks will be processed as soon as they are read, rather then waiting for the corresponding SACK. This allows better operation of the Mediation Engine in cases where SACKs are delayed excessively, but it will also prevent the detection of some malfunctions in the protocol (like lost packets).
This option sets & enables packet deduplication for SIP on the ME. The value represents the time limit (in ms) for which a packet is considered duplicate. 0 means off. Warning: enabling deduplication has performance impacts.
Choose the default standard for the MTP3/ISUP protocols. Supported are ITUT and ANSI.
SS7: Prefer ported number to callee (in IAM)
If IAM contains GAP for Ported number, display this as callee number. The matching algorithm is not affected by this setting.
Search for matching registration segments
When viewing the diagram of a Registration event, Mediation Engine will search for other registration events that are related. This option controls the time span in which it searches, in seconds. If set to 0, the searching of related registration events is disabled.
The number of seconds the Mediation Engine looks back for related 'redirected by 302' calls. If 0, merging the redirected calls is disabled.
Seconds for remembering INVITE when merging 302 and REFER calls
The number of seconds the Mediation Engine looks forward for an INVITE if merging calls on 302 and REFER messages. Keep this value low. 0 disables just the forward-looking functionality.
The number of seconds after which the Mediation Engine will consider a call as Timed-Out if no SIP messages are received.
Set customer id for VSI FDP module
Specify a customer ID for VSI FDP module.
Show ISUP abnormal termination in details
For certain Q850 codes, add '- abnormal termination' on the details field.
Display data gathered from the Oracle Communications Data Model in the User tracking page.
Strict SIP CSeq handling for unauthorized calls
When unset, some non-RFC-conformant but successful calls will be treated as successful instead of failed.
Stringent passwords expiration duration
Number of days after which passwords expire when the stringent password policy is enabled.
Suffix length (H.248, MGCP, Diameter, ENUM correlation)
Define the suffix length for correlation on DIAMETER Public ID, H.248/Megaco, MGCP, and ENUM. Set to 0 to only remove leading + from the Request URI/the Public ID.
Choose the TCP decoding mode: when 'quick push' mode is activated, the data chunks will be processed as soon as they are read, rather then waiting for the corresponding ACK. In normal operation, you should not activate this option. If Agents see only one half of TCP traffic (and hence no ACKs are received), enable this option.
Enable the Transaction Data Record.
Time difference in probes that will trigger an alert
Time difference in milliseconds between a probe and the ME that will trigger an alert.
Time window for each chunk of records when exporting
Number of seconds defining the interval for sql-querying a chunk of records to be exported.
Time window for records when exporting
Number of seconds (back from the last record) used for limiting the records to export.
Timeout for Mediation Engine querying
Number of seconds to wait for an answer from the Mediation Engine peers. If one of them becomes unavailable, the timeout ensures that the local results are still available.
The time to wait between starting a new trace from the same alert definition, in minutes.
This setting is used when matching a message to an existing call leg. If this setting is 'true', in case the source IP or destination IP of a new message is not configured as a device, Operations Monitor checks the MAC address before matching this packet to an existing call leg. However, if both source and destination IPs of the new packets can be matched to an existing device, this setting will be ignored and the device MAC address configuration will have precedence when matching the packets to the call leg.
This setting is used when matching a message to an existing call leg. If this setting is true, in case the source IP or destination IP of a new message is not configured as a device, Operations Monitor checks that both source and destination MAC addresses are the same before matching this packet to an existing call leg (if one of the endpoints was already matched via device lookups, the MAC address check for that endpoint is skipped). However, if both source and destination IPs of the new packets can be matched to an existing device, this setting will be ignored and the device VLAN configuration will have precedence when matching the packets to the call leg.
Consider ports when comparing packet and device addresses.
Use the hash of preferred number config to link it to Caller/Callee
If Number Determination Sources rules are configured and the calling or called number of a call is determined by one of the rules, a tag identifying the used rule will be stored in the call record in the database. The CDR CSV fields src_user_pref_tag and dst_user_pref_tag contain the tag of the rule used for the calling and called number respectively.
Note:
The tag is not visible in the Session Monitor GUI, the tag is only visible in the database and in CDRs.If the setting is enabled, the tag value of a Number Determination Sources rule does not change if you delete a rule and add it again with the same parameters. This is because the tag is calculated using a hash on the rule parameters.
If the setting is disabled, the tag value of a Number Determination Sources rule is based on the Database ID of the Number Determination Sources rule, which may change if the rule is deleted and added again.
Set to true to match users based on the SIP URI (domain name), in addition to the user name (number). Changing this value restarts the core process.
Refers whether or not the Mediation Engine's user action should belogged into the dedicated file logging facility. By default, the Linux operating system provides the custom logging from local0 to local7. The number in the setting corresponds to which local syslog facility you want to use. For more information on syslog, refer to the link,
http://docs.oracle.com/cd/E52668_01/E54670/html/ol7-log-sec.html
User Actions Syslog logging facility
Refers to which logging facility should be used for the Mediation Engine's user action. By default, the Linux operating system provides the custom logging from local0 to local7. The number in the setting corresponds to which local syslog facility you want to use. For more information on syslog, refer to the link, http://docs.oracle.com/cd/E52668_01/E54670/html/ol7-log-sec.html
Assign users roles containing predefined permissions.
Assign newly created users this locale.
User devices chart history limit
Fetches only calls not older than specified number of seconds.
User tracking paging query range for
Time range a query covers in a single paging request (in seconds) for user tracking. Should typically be larger than the normal paging query range.
Voice Quality Chart scale in minutes/minute
If true, the Voice Quality Chart scale will be minutes/minute instead of minutes/15 minutes.