...
Overview
The UCentric ZT (Zero Touch) interface is an SPA (Single Page Application) that provides a “Zero Touch” approach to both auditing and provisioning of voice phone systems.
...
A list of all supported vendors can be found here:
Supported Provisioning Targets
A list of all provisioning targets can be found here:
Using UCentric ZT
Logging In
...
The format for each supported filetype is shown in the 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
Type | Typical export from | Default Field mappings | Info |
|---|---|---|---|
Active Directory | Microsoft AD | Telephonenumber/Phone | Looks for Line1DN |
to |
Supported Export/Methods
Default Field Mappings
Logic/Info/Result
patch telephonenumber/phone, if no match, attempts to match on name. Will map all appropriate fields if it finds a match. |
CDR
For Cisco CDR blending, please refer to https://mittech.atlassian.net/wiki/spaces/MKB/pages/35323905/UCentric+ZT+-+User+Manual#Adding-CDR-to-Cisco-BATs-audit
For all other CDR either from third party systems such as call loggers or accounting systems, please contact us directly to discuss the best approach.
Devices
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 line1DDI number, and the regionName 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 | Generated by you/us if needed | userId | Used primarily for Broadworks exports where device information isn't in the backup; |
Network |
...
Default Field Mappings
Logic/Info/Result
Edge switches | Number | Will try to match on Number, IP or MAC. If found, will set |
LANSwitch, |
LANPort and |
LANLastSeen values |
Recorder |
...
Supported Export/Methods
Default Field Mappings
NICE NTR | Primary Extension Name | If the "Primary Extension Name" matches Line1DN |
, then the |
callRecordingMode column is set to "Yes" |
Voicemail |
...
Default Field Mappings
Logic/Info/Result
Unity | FirstName | Will |
persVoicemail voicemail if found, or |
groupVoicemail if set | |||
CDR | Cisco CUCM | https://mittech.atlassian.net/wiki/spaces/MKB/pages/35323905#Adding-CDR-to-Cisco-BATs-audit |
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.
...
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.
https://mittech.atlassian.net/wiki/spaces/MKB/pages/35323905#Adding-CDR-to-Cisco-BATs-audit
Ensure that the CDR file (NOT CMR) is in CSV format and the filename suffix is .cdr.txt
...
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#Auditing35323905#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.
Index
...