NexLog Recorder User Manual v2.2.0 85
their membership in a user group, and by configuring it here you can narrow
those permissions down to the desired set by deleting the set granted by default
and recreating it with just the resources needed. Conversely, a user may have a
specific permission to access resources outside the normal scope of their user
group, in which case these resources can be added individually.
4.6.5. Custom Fields
By Default the NexLog Recorder Database stores several pieces of information
about each Record, such as the Channel Number and Name it was recorded on,
the Date/Time it started, and it’s Duration. In addition to these standard fields,
some optional features and custom integrations can fill in additional
information. Since there is no preset field in the database to hold this
information, you must configure a Custom Field to store the info. These fields
are populated by various optional and standard subsystems, or by custom
integrations. For example, upon a fresh installation, three custom fields are
automatically added: DTMF, Calling_Party and Caller_Id. These fields are
automatically filled in for calls which enter the system via certain board tasks.
For example, a call received on an Analog card which contains DTMF Tones will
have those tones automatically processed and the corresponding numbers
entered into the database record for that recording as long as the DTMF custom
field has not been deleted. If you are not using those fields they may be deleted
for your convenience.
In addition to the three preset Custom Fields, Certain optional features, both
licensed and base, may utilize a preset custom field and for those features to
operate, a custom field by the indicated name must be added. Examples of such
custom fields are MF_ANI for storing the MFR2 ANI Number transmitted on
some analog CAMA trunks, and RadioID for the ANI transmitted via MDC1200
on some analog Radio systems. Custom Metadata Integrations may require
additional custom fields, for example, an ANI/ALI Spill for a 911 Call Center
may contain information such as Customer_Name and Street_Address. These
custom fields could be added to the system, and the Metadata Integration
configured to populate them. Note that just adding a new custom field without
an integration to populate it will not provide a useful function, just empty fields.
Custom Fields can be enabled as columns in the Front Panel's Replay screen
and MediaWorks / MediaAgent clients to view the metadata associated with a
call.
To Next Page
Loading...
