Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

Backup support

The backup mechanisms and tools vary from vendor to vendor. This page details which systems UCentric supports auditing via backup for along with the supported backup formats and methods for each.

Please click one of the vendor logos below to go directly to the section for that vendor or select them from the table of contents below.

New ‘backup’ methods are being added all the time. Please return to this page to find the latest information and compatibility.

Alcatel/Lucent

There are two Alcatel systems we can audit OXE and OXO (OmniPCX Enterprise and Office), these systems may use the OXO Connect Management Console or OmniVista (4760 or 8770) tools to export data. The method used will depend on the tool the partner or customer has access to.

Asterisk/FreePBX (and derivatives)

Cisco (& Broadworks)

Avaya

Avaya BCM

Microsoft Teams, Lync/Skype for Business

Mitel

Aastra MX-One

Aastra MX-One backups/exports should contain the most if not all of the files listed in the below table, some files may be empty or missing if the related config doesn’t exist on the PBX.

Files should be zipped up into a single file for processing in the the UCentric ZT or Web portal.

Description

Filename

Notes

System details

ts_about

 

Exchange details

exchange_info

 

Media Gateways / LIMS

trsp_connection

 

Board list

board_list

 

DECT boards

dect_cfp

 

Board versions

board_sw

 

Speedials

ADCDP

 

Personal Speedials

ADIDP

 

Analog Extensions

EXDDP

 

IP Extensions

ip_extension_info

 

Key System Directory

KSDDP

 

ISDN Directory

ITDAP

 

Keys

KSFKP

 

Extension list

extension

 

Key System Categories

KSCAP

 

Directory names

name1

Main directory file

Directory names

NIINP1

Read in addition to name1 as different systems split directory files

Directory names

NIINP2

Read in addition to name1 as different systems split directory files

Directory names

NIINP3

Read in addition to name1 as different systems split directory files

Directory names

NIINP4

Read in addition to name1 as different systems split directory files

Directory names

NIINP5

Read in addition to name1 as different systems split directory files

Directory names

NIINP6

Read in addition to name1 as different systems split directory files

Diversion (Call forward)

diversion

 

Hunt Groups

GHDAP

 

Pickup Groups

GPDAP

 

Licenses

license

 

Bridged Extensions

parallel_ringing

 

Trunks

ROEDP

 

Voicemail Pilot

VMGEP

 

DECT Extensions

dect_extension

 

MiCollab / MiCC

Backups are achieved through importing standard ‘backups’ downloaded through the MiVoice Connect, MiCollab and MiCC application web portals.

MiVoice Connect (Previously Shoretel)

You will need to be a MiVoice Connect System Administrator and have the credentials to login to the MiVoice Connect System

 

Procedure 1:

  • Login to the MiVoice Connect HQ server either directly or using Remote Desktop Connection 

  • Navigate to "Drive:\Shoreline Data\Database\SnapShot"

  • Sort the view by "Date Modified" and take the "SnapShotMM-DD-YYYY XXXXXX.sql.gz" file that is most recent.

Alternatively:

Procedure 2: (Run Backup on Demand)

  • Navigate to C:\program files<x86>\ shoreline communications\ shoreware server\MySQL\MySQL server\Examples

  • Run the backup config.bat file. This will create a new “.sql” file under C folder

  • Get the “.sql” file for generating audit and migration reports

Mitel 3300 / Legacy MiVB

Backups are achieved through manually exporting the following forms manually, and exporting them from the Mitel Application portal to a CSV file (one for each section) – then zipping them up into a single file for processing

System Options

System Capacity

Users and Services Configuration

Feature Access Codes

System Speed Calls

Personal Ring Groups

Hunt Groups

Ring Groups

Pickup Groups

Paging Groups

Call Forwarding Profile

DND

Default Account Codes

Independent Account Codes

System Account Codes

Inward Dialling Modification

Outward Dialling Modification

Trunk Attributes

ICP/PBX Network Elements

IP/XNET Trunk Groups

All IP Telephones

Hardware Modules

Hardware Compute Cards

System IP Properties

Network Elements

ACD Agents IDs

ACD Agent Skill Groups

ACD Express Groups

ACD paths

ACD Path interflow dialling lists

ACD Remote Agent Subgroups

Default CESID

L2 to CESID

CESID Assignment

ARS Call Progress Tone Detection

ARS Digit Modification

ARS Maximum Dialled Digits

ARS Routes

ARS Route Lists

ARS Route Plans

ARS Digits Dialled

ARS Leading Digits

ARS Node Identities

Analog Trunks + Trunk Groups

Digital Trunks

DID Ranges for CPN Substitution

Then import the file into UCentric from within the site manager, Zero-Touch SPA or using the following command line:

Audit.exe Live MiVB2 -S 123 -d 127.0.0.1 -f “relative\path\to\myfile.zip”

A full guide for this can be found here: Auditing a Mitel 3300 using CSV backups

Unify (& Siemens)

Siemens/Unify HiPath/HiCom

Siemens/Unify HiPath’s can be audited from what is called a “Regen” or “LastLoad” file. Both are .txt files and look something like this:-

Then import the file into UCentric from within the site manager, Zero-Touch SPA or using the following command line:

Audit.exe Live HiPath -S 123 -d 127.0.0.1 -f “relative\path\to\myfile.txt

Unify OpenScape OSV

OSV can be imported from a ZIP file that contains .cfg and .csv files for the OSV configuration. It needs at a minimum:-

uc_users.csv UC Users

mediatrix.csv Mediatrix Servers

????_bgl_????.txt Main location devices

DLS-export.csv SIP + Keys

mlhg_??????.csv Hunt groups

export_all.txt Main configuration file

In addition the .cfg files for each gateway will enable UCentric to accurately audit the entire solution.

Then import the zip file into UCentric from within the site manager, Zero-Touch SPA or using the following command line:

Audit.exe Live OSV -S 123 -d 127.0.0.1 -f “relative\path\to\myfile.zip


OpenScape Business (OSBiz)

OSBiz can be imported from a standard OSBiz XML input/export file.

It should appear in this form:

<?xml version="1.0" encoding="UTF-8"?>
<osbiz>
    <general>
        <xml_file_version>1.0</xml_file_version>
        <system_type>OSBiz S</system_type>
        <system_mode>UC Suite</system_mode>
        <system_in_network>false</system_in_network>
    </general>

    <basic>
        <gateway>
            <customer_name>Test In House</customer_name>
            <contract_number/>
            <system_name>Test</system_name>
            <gateway_location/>
            <contact_address/>
            <system_country>United Kingdom</system_country>
            <brand>OpenScape Business</brand>
            <international_prefix>00</international_prefix>
            <national_prefix>0</national_prefix>
            <country_code>44</country_code>
            <local_area_code/>
            <pabx_number/>
            <node_id>0</node_id>
            <continuous_tone>true</continuous_tone>
        </gateway>

NEC

NEC NEAX systems can be imported from a Standard XLSX backup that has the following tabs:-

You can import the XLSX file into UCentric from within the site manager, Zero-Touch SPA

NEC/Philips Sopho/IS3000

IS3000/Sopho systems can be audited via a backup import with some additional pre-import steps. The backup file supported is usually a rar file that contains .POM files.

A .POM file viewer app must be used to carry out the steps below before importing the file into UCentric.

  1. Extract the “.POM” files from an archive into their own folder.

  2. Open the LLxxxx.POM file in the POM view program

  3. Click “File”, “Report” and select “Full Report”, “Report in XML” and “all in one file (is3000.xml)”

NOTE: The iS3000.xml file will be created in the XML subdirectory of wherever your POM file is located.

Once you have the XML file, you can use the UCentric Zero Touch (SPA) interface or standard web interface to add a new site/import the file like any other audit.

Index

Version Date Comment
Current Version (v. 35) Sept 12, 2024 21:17 Sean Millar
v. 43 Oct 16, 2024 17:05 Sean Millar
v. 42 Oct 16, 2024 17:02 Sean Millar
v. 41 Oct 09, 2024 14:35 Sean Millar
v. 40 Sept 13, 2024 13:43 Sean Millar
v. 39 Sept 13, 2024 13:41 Sean Millar
v. 38 Sept 13, 2024 13:37 Sean Millar
v. 37 Sept 12, 2024 21:38 Sean Millar
v. 36 Sept 12, 2024 21:34 Sean Millar
v. 35 Sept 12, 2024 21:17 Sean Millar
v. 34 Sept 12, 2024 20:47 Sean Millar
v. 33 Sept 12, 2024 20:43 Sean Millar
v. 32 Sept 12, 2024 20:38 Sean Millar
v. 31 Aug 28, 2024 17:54 Sean Millar
v. 30 Aug 28, 2024 17:49 Sean Millar
v. 29 Aug 28, 2024 17:46 Sean Millar
v. 28 Aug 28, 2024 13:42 Sean Millar
v. 27 Aug 28, 2024 13:41 Sean Millar
v. 26 Aug 28, 2024 13:40 Sean Millar
v. 25 Aug 22, 2024 15:12 Liam McGuinness
v. 24 Aug 05, 2024 08:56 Paul McGuinness
v. 23 Aug 01, 2024 13:53 Liam McGuinness
v. 22 Aug 01, 2024 09:50 Paul McGuinness
v. 21 Jul 31, 2024 11:33 Liam McGuinness
v. 20 Jul 01, 2024 16:29 Paul McGuinness
v. 19 Feb 15, 2024 17:14 Sean Millar
v. 18 Dec 12, 2023 14:35 Paul McGuinness
v. 17 Dec 05, 2023 18:08 Sean Millar
v. 16 Nov 22, 2023 17:17 Sean Millar
v. 15 Nov 22, 2023 17:16 Sean Millar
v. 14 Oct 25, 2023 11:35 Paul McGuinness
v. 13 Oct 25, 2023 11:25 Paul McGuinness
v. 12 Sept 28, 2023 10:55 Sean Millar
v. 11 Aug 23, 2023 11:26 Paul McGuinness
v. 10 Aug 22, 2023 09:31 Paul McGuinness
v. 9 Aug 07, 2023 16:21 Sean Millar
v. 8 Jul 18, 2023 15:58 Paul McGuinness
v. 7 Jan 27, 2023 14:44 Sean Millar
v. 6 Jan 27, 2023 14:43 Sean Millar
v. 5 Jan 13, 2023 17:35 Sean Millar
v. 4 Oct 06, 2022 16:31 Sean Millar
v. 3 Oct 06, 2022 13:59 Sean Millar
v. 2 Oct 06, 2022 13:29 Sean Millar
v. 1 Oct 06, 2022 10:26 Sean Millar
  • No labels