...
Data blending is the process of adding additional files to a PBX audit to augment it and add information from other systems such as Active Directory, Voicemail or call data (CDR).
To add files for blending, you can select the “Advanced options” section within the ZT Portal which will provide the options shown below.
...
Click the File upload icon in order to begin uploading additional files.
...
Additional files can then be dropped into this window once you have selected the relevant file from the drop down, once selected and you have added the file, click “Add” to add it to the audit.
Supported formats
All additional files for blending are required to be in CSV format. We can also provide example files for you to compare/check against if required.
The format for each supported filetype is shown in the table below.
...
Type
...
Typical export from
...
Default Field mappings
...
Info
...
Active Directory
sections below, please ensure “Default Field Mappings” match the column names in your csv files.
Active Directory
Active directory exports are used to add useful details such as UPN, display name, department and SIP Address to an LLD. This is particularly important when moving from legacy voice to hosted platforms such as MS Teams as all users will need an UPN for example.
Supported Export/Methods | Default Field Mappings | Logic/Info/Result | |
Microsoft AD via PowerShell (On-Prem) or Azure AD GUI using export users option. | Telephonenumber/Phone | Looks for Line1DN in LLD to patch match telephonenumber/phone, if no match, attempts to match on name. Will map all appropriate fields if it finds a match. | |
DDI | This is generated by us/you on a per-customer basis | EXTNPATTERN | This is used to bulk-map DDI and override locations if needed.In this example, any extension in the form 420xxx will be given an appropriate DDI number, and the location will be overrriden to "Amsterdam" - The RegionId of -1 means "match all locations to find this number in the list"The example 567x will only be overridden if the existing location (RegionID/RegionName) matches. Note: The number of underscores must be the same in the suffix of the 1st two columns for this to work |
Devices
...
Devices
Supported Export/Methods | Default Field Mappings | Logic/Info/Result |
Generated by MIT/client as required | userId | Used primarily for Broadworks exports where device information isn't in the backup; |
Network
...
Supported Export/Methods | Default Field Mappings | Logic/Info/Result |
Exported from Edge Switches/LLDP/CDP | Number | Will try to match on Number, IP or MAC. If found, will set Switch, Port and Last Seen values |
Recorder
Supported Export/Methods | Default Field Mappings | Logic/Info/Result |
NICE NTR | Primary Extension Name | If the "Primary Extension Name" matches Line1DN |
...
in LLD then the "Recorder" column is set to "Yes" |
Voicemail
Supported Export/Methods | Default Field Mappings | Logic/Info/Result |
Cisco Unity | FirstName | Will set "Personal" voicemail if found, or "Group" if set |
...
Vendor Specific Blending
Some vendors have their own formats for files that can be extracted when collecting a backup from a PBX, guides for blending these specific files are shown in this section.
Adding CDR to Cisco BATs audit
CDR files can also be added to the backup that is being imported into UCentric. The guide below explains how to do this for Cisco CUCM BATS files and CDR extracts.
...
Use the ZIP file instead of the tar/tgz for the audit following the https://mittech.atlassian.net/wiki/spaces/MKB/pages/35323905/UCentric+ZT+-+User+Manual#Auditing section of this guide to process the audit and generate reports. Any HLD or LLD you generate will now include the CDR that you processed in this audit.