6.6. Motorola Dimetra AIS Interface¶
6.6.1. Motorola Dimetra AIS Interface Introduction¶
The purpose of this document is to describe the requirements for a successful integration between the Eventide NexLog DX-Series 740/840 recorders and the Motorola DimetraIP, DimetraIP Compact or DimetraIP Micro via the Motorola MCC 7500 Archiving Interface Server (AIS), Voice Processing Module (VPM) and CRAM. The CRAM is a CORBA based software that provide an interface between the AIS and the NexLog DX-Series recorder.
Required Personnel
Eventide dealer/reseller Technician
Motorola Field or Systems Engineer
Customer Network Administrator
Eventide support/deployment engineer
License Required
This feature must be licensed to be used. Contact your Eventide Communications Dealer for assistance.
6.6.2. Install and configure AIS and CRAM¶
The Archiving Interface Server (AIS) is Motorola provided software tool used to deliver audio and metadata to third party recording solutions, such as the Eventide NexLog DX-Series products. In a Dimetra environment the AIS is effectively “wrapped” by the CRAM and the CRAM in turn presents an interface to the recording solution over the IP network. Detailed configuration details surrounding the AIS and CRAM are outside the scope of this document. However, the details of what is needed from the AIS/CRAM to properly configure the NexLog DX-Series are outlined here.
Install the AIS application and CRAM application on Motorola provided or specified workstation
Configure the CRAM parameters via the “Remote API Configurator”, example screen shown below
Fig. 6.71 CRAM Configuration¶
Using the “SSL keys and certificates” tab in the “Remote API Configurator”, Generate the Common name (cert.), Common name (keys) and supply password.
Note
the files generated here will be used later to configure the NexLog DX-Series Dimetra recording board.
6.6.2.1. Add Virtual Recording Interface¶
Select the number of IP channels/number of talk paths, then select the “Motorola Dimetra AIS Interface” Template
Fig. 6.72 Add Interface¶
Note
this is the maximum number of talk paths between the NexLog DX-Series and the AIS that can be recorded. Not to be confused with “Talk Groups”, multiple Talk Groups can be on one “Talk Path”.
6.6.2.2. Motorola Dimetra AIS Interface Template Fields¶
The following figure has the fields populated for illustrative purposes, the actual values in each installation will most likely be different. Verify each value with the Motorola Field Engineer or the Customer Network Administrator.
Fig. 6.73 Interface Configuration¶
Template Field Details
Recorder IP: IP address of the NIC device on the NexLog DX-Series that has access to the AIS
Typical Source: Customer Network Administrator
Recorder Base Port: 35000 when configuring primary AIS, 37000 when configuring secondary AIS
Typical Source: Customer Network Administrator or Motorola Field Engineer
AIS IP: IP address of the AIS that will be serving the NexLog DX-Series calls
Typical Source: Customer Network Administrator or Motorola Field Engineer
AIS Hostname: Host name of the AIS on the network
Typical Source: Customer Network Administrator
AIS Username and password: Credentials that can log into the AIS and access Dimetra resource information
Typical Source: Customer Network Administrator or Motorola Field Engineer
AIS CRAM type: Select either SSL or non-SSL. As of the writing of this document, Eventide is of the understanding that Motorola does not support the non-SSL version
Typical Source: Customer Network Administrator or Motorola Field Engineer
AIS CRAM Port: UDP port that will connect the NexLog DX-Series Recorder and AIS/CRAM
Typical Source:Customer Network Administrator or Eventide Communications Dealer/Reseller
Upload CA CERT File: This file will have been previously generated using the Motorola provided “Remote API Configurator”, see “Install and configure AIS and CRAM”
Typical Source: Customer Network Administrator or Motorola Field Engineer
Upload Client KEY File: This file will have been previously generated using the Motorola provided “Remote API Configurator”, see “Install and configure AIS and CRAM”
Typical Source: Customer Network Administrator or Motorola Field Engineer
Upload Client CERT File: This file will have been previously generated using the Motorola provided “Remote API Configurator”, see “Install and configure AIS and CRAM”
Typical Source: Customer Network Administrator or Motorola Field Engineer
6.6.2.3. Apply the template¶
After filling in all the fields, select “Save”. The NexLog DX-Series will now attempt to save the template data and initialize for recording.
Note
After selecting “Save”, it could take up to 30 seconds or more to complete the communication to the AIS/CRAM. When the process completes, you will be returned to the main recording boards page, example shown below
6.6.2.4. Select Talk Groups and Re-Apply the Template¶
Select the newly created “Local IP Recording (dimetra template), the template will now be populated with the same information initially entered, with the addition of lists of Group Calls and Private calls that could be setup to record. You can select the Group Call group name and Private call units to be recorded by selecting on the “record” checkbox. The priority of recording for that resource can also optionally be changed. Note, the lists can be large, so filters and select all options are provided as a convenience to the user. Once you have selected all the resources to be recorded, select the Re-apply Template button and Save the template.
After the system indicates successful saving of the template, the system should be ready to record.
6.6.2.5. Check for Alerts¶
Check the NexLog DX-Series front panel and/or configuration manager (figure below) for any system alerts or Tait Radio specific alerts. There will be alerts specific to the Tait Radio integration if there are problems with downloading talk groups, managing crypto keys and OTAR.
6.6.2.6. Verify Recording¶
Place a series of test calls between radios on both encrypted and unencrypted talk groups. Use MediaWorks DX or the front panel display to verify recording of all test calls. Following is an example of Diemtra test calls and some of the associated metadata available.
6.6.2.7. Verify Recording after Restart¶
Reboot the NexLog DX-Series and verify that recording resumes automatically, this will verify that the system will continue to record after a power failure or shutdown.
6.6.2.8. Ensure the NexLog DX-Series has a Time Synchronization source¶
It is important that the NexLog DX-Series have a time synchronization source set to the same source as the AIS. It has been seen in the field that when the NexLog DX-Series’s time drifts from the that of the AIS the AIS can stop sending calls to the NexLog DX-Series. The Time Sychronization settings on the NexLog DX-Series can be found in the System>>Date Time section of Web Config.