...
Type | Typical export from | Default Field mappings | Info |
---|---|---|---|
Active Directory | Microsoft AD | Telephonenumber/Phone | Looks for Line1DN to patch 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 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 | Edge switches | Number | Will try to match on Number, IP or MAC. If found, will set LANSwitch, LANPort and LANLastSeen values |
Recorder | NICE NTR | Primary Extension Name | If the "Primary Extension Name" matches Line1DN, then the callRecordingMode column is set to "Yes" |
Voicemail | 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 |
...
Use the ZIP file instead of the tar/tgz for the audit following the https://mittech.atlassian.net/wiki/spaces/MKB/pages/35323905#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
Table of Contents |
---|