Load Data to the MiVoice MX-ONE 7.x System
As an example of time to load customer data, tests have shown that the following setup takes approximately 8 minutes to execute on Mitel ASU-Lite:
- 3 Servers (LIMs)
- 130 Analog extensions
- 190 Digital extensions
- 40 IP extensions
- 200 Cordless extensions
- 20 ISDN extensions
- 70 mobile extensions
- 100 PEN
- 40 ACD Agents
- 255 external lines
Prepare the MiVoice MX-ONE 7.x Data
- Zip the target folder in C:\Program Files\Aastra\Service Assistant Manager\PC-Regen\source and name it Target.zip.
- Transfer the Target.zip file to the MX-ONE 7.x system.
- Connect to the MX-ONE 7.x system (secure shell, SSH).
- Log on to the system with user name and password.
- Unzip the Target.zip file. Example: <user>@linux:~>unzip Target.zip
- Go to the Target directory. Example: <user>@linux:~>cd Target
- Convert the files to Unix format. Example:Target>dos2unix *
The following list shows the MML commands, that will be automatically executed to regenerate data:
| Commands |
|---|
| AC: ACBGI, ACFUI, ACGMI, ACGRI, ACPAC, ACTNI |
| AD: ADCOI, ADINI |
| AS: ASPAC |
| CB: CBELI, CBGMI |
| CH: CHCMI, CHGMI |
| CS: CSTLI |
| EX: EXTEI |
| GH: GHGMI*, GHGRI* (* = replaced by extension_group_member). See the note mentioned below this table and see table 3. |
| IC: ICFUC, ICMWC |
| IS: ISEPI, ISFUI |
| IT: ITNUI |
| KS: KSADC, KSANI, KSCHC, KSEXI, KSFKC, KSMDI |
| LC: LCDDI, LCLDI, LCOPI, LCTDI |
| MT: MTSLI, MTSRI, MTSSI, MTSTI |
| NC: NCCOI, NCGMI, NCGRI, NCICI, NCNOI, NCSGI |
| NS: NSCOI |
| OP: OPADC, OPCEI, OPCGS, OPCOI, OPCTS, OPDNC, OPERI, OPISS, OPNEI, OPRSC |
| PA: PAALI, PACHI, PAGII, PASAI |
| PL: PLLNI |
| RA: RACEI, RADSI, RAGAI, RAGMI, RAGPI, RAMDI |
| RI: RIANI |
| RO: ROAPI, ROCAI, ROCDI, RODAI, RODDI, RODII, RODNI, ROECI,ROEQI, RONDI, RORII, RORNI, ROVNI |
| SE: SEMII |
| SP: SPEXI |
| TR: TRDPI, TRRSI |
| VM: VMFUI, VMGEI, VMPOI |
The old CP, GH, ROELx, SU, SY, and TC commands have been replaced by unix style commands (route_data_common, extension_group_member, extension_group, extension_group_profile, global_traffic_data and traffic_matrix).
The list below is showing automatically generated Unix-style commands:
| Commands |
|---|
| account_code_init |
| alarm_action |
| alarm_input |
| alarm_output |
| auth_code_init |
| board_config |
| callinfo_condcode_set |
| call_list |
| call_list_profile |
| csta |
dect_cfp, dect_extension, dect_rfp, dect_system_id |
| diversion |
| diversion_common |
| diversion_system |
| exchange_info |
| extension |
extension_group |
extension_dnd_group |
extension_dnd_group_member |
extension_group_member |
extension_group_profile |
| extension_key |
extension_pickup_group |
extension_pickup_group_member |
| extension_profile |
| extension_text |
global_traffic_data |
| ip_extension |
| ip_gatekeeper |
| media_gateway_config |
| media_gateway_interface |
| name |
| number_conversion_initiate |
| number_data_initiate |
| number_initiate |
| parallel_ringing |
| remote_extension |
route_data_common |
| sec_policy |
| sip_domain |
| sip_route |
| sms_client_initiate |
| sms_server_initiate |
traffic_matrix |
| trsp_connection |
| trsp_synchronization |
If Smooth/stepwise Migration is done, not all, but only the extensions moving in this step shall be initiated in the new system. Then the smooth migration measures are repeated for groups of extensions, until all are moved, and the old system can be shut down. See Operational Directions for SMOOTH MIGRATION.
Manual handling
The following commands require manual input by the operator.
| Commands Not Regenerated |
Corresponding File Name |
| alarm_cfg |
alarm_cfg |
license_reread |
license_reread |
- Check and load the optional units (pu_add)
- Configure synchronization for all Servers (LIMs).
- Configure information computer.
- Reconfigure IP domains.
- Reconfigure IP Route settings, if needed.
- Reconfigure settings for IP-phones, if needed.
- Configure Call Logging.
- Configure Alarm functions.
- Configure Traffic Measurement.
Manually Configure Information Computer
Configure the information computer. Use the command ICFUI.
ICFUI:IFCIND=1,DFMT=5,UPDFCN=YES,FILLER=32,lim=1, ip=130.100.10.40,rport=2555;
ICFUI:ICFIND=2,DFMT=5,UPDFCN=YES,FILLER=64,lim=1, ip=130.100.8.110,rport=800;
Note that EMFUI, Electronic Mail function, is not supported in MX-ONE.
Reconfigure IP Route Settings if needed
If needed, reconfigure the IP Route Settings, see the operational directions forIP NETWORKING, RI.
Reconfigure Gateway Settings if needed
If gateway settings have changed, the configuration file for the IP phones needs to be adjusted, see the description for CONFIGURATION FILE FOR DBC 42X.
Start Loading the Telephony Data to the MiVoice MX-ONE 7.x System
- Start loading data to the MX-ONE 7.x system. Example: <user>@linux:~/Target>source REGENCMD.TXT │ tee TSlog.txt
- Wait until the prompt reappears.
- Check if the data was setup correctly.
- Perform a data backup.