...
We can also blend in exports from Voicemail systems such as unity or 3rd party voicemail if it contains a list of users with voicemail configured. This allows for identification of voicemail users in the LLD reports for replication on the hosted voice or system that is being migrated to.
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 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 | 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 Switch, Port and Last Seen values |
Recorder | NICE NTR | Primary Extension Name | If the "Primary Extension Name" matches Line1DN, then the "Recorder" column is set to "Yes" |
Voicemail | Unity | FirstName | Will set "Personal" voicemail if found, or "Group" if set |
Low-Level/Migration Plan Export Formats
...