Fixed defaults

The fixed defaults refer to the settings that must be configured on the default MiVoice Business Platform database to ensure proper interaction between Management Portal and the MiVoice Business Platform.

When a user, hotdesk phone (IP device only), or call group is created using Management Portal, there are specific settings that Management Portal applies, and these must match those on the MiVoice Business Platform, to ensure it responds correctly (i.e. when a hunt group is created, Management Portal sets the Class of Service to COS 6).

See Fixed Defaults Table for the default values that Management Portal users. The values must be identical to the values configured on the default MiVoice Business database.

Flexible defaults

The flexible defaults refer to the settings that must be configured on the default MiVoice Business Platform database to ensure proper interaction between Management Portal and the MiVoice Business Platform instance corresponding to the bundle and dial plan assignments.

A bundle and dial plan are assigned to each newly created user. A bundle includes a Feature Profile, which is Management Portal's view of a Class of Service (COS). When a user is assigned a bundle, the COS number affiliated with the bundle gets assigned to the user on the MiVoice Business Platform.

Similarly, a dial plan in Management Portal corresponds to a Class of Restriction (COR) on the MiVoice Business Platform. When a user is assigned a dial plan, the COR that is registered to the dial plan gets assigned to the user on the MiVoice Business Platform.

To ensure that proper services (COS options and ARS routes) are available to an end user, it is essential to set the Flexible Defaults appropriately.

If any of the User features that affect the MiCollab Client are modified either through Management Portal or directly on the MiVoice Business System Administration Tool, then the changes will not be reflected on the MiCollab Client until it has been synchronized with those MiVoice Business instances affected.

Create the golden MiVoice Business database

To create the MiVoice Business database for the first time, it is necessary to use the fixed and flexible defaults listed above, and any other additional customer requirements that may arise. Once this information has been collected, the default database can be created and then applied to each MiVoice Business Platform instance, using one of the following methods:

• Platform Manager - If you are using Platform Manager, this is the easiest way to create golden database. See the Platform Manager Help for details.

• MiVoice Business Import Spreadsheets

• Configure an initial MiVoice Business, then Backup and Restore on other MiVoice Business instances

To create the Default Database using MiVoice Business Import Spreadsheet

1. Export the 3300ICPImportSpreadsheet.tar.gz using the Embedded System Manager (ESM) from a form that has the Export button.

2. Unzip the file to get the 3300ICPImportSpreadsheet.tar file.

3. Unzip the 3300ICPImportSpreadsheet.tar to get the 3300ICPImportSpreadsheet.xls file.

   Ensure that the filename extension is ".xls". Filename extensions with ".xlxs" are not supported.

4. Open the spreadsheet, enable macros, and create the following spreadsheets for the default MiVoice Business database:

   1. Default CESID

   2. Class of Service Options

   3. VM Ports

   4. Station Attributes

   5. Hunt Groups

   6. Hunt Groups - Hunt Group Members

   7. Call Rerouting Always Alternative

   8. Call Rerouting

   9. Class of Restriction Groups

   10. Trunk configuration forms (eg. SIP Peer Profile, IP/XNET Trunk Profiles, and any additional forms that may be required)

   11. ARS Routes

   12. ARS Dialed Digits

   13. ARS Leading Digits

   14. ARS Digit Modification Plans

   15. Trunk Attributes

   16. Embedded UM Settings

   17. System Options

5. Enter the following appropriate information into spreadsheets:

   1. Required Management Portal defaults (voicemail, COS, COR, Default CESID, DID trunk).

      Make sure your COS values are set up correctly. If you create a Ring Group with Voicemail and use it in a Call Flow, the call will route to Voicemail instead of the selected Overflow Point. This happens because the COS Call Forward No Answer Timer is set to 15 seconds while the default Overflow timer in the Ring Group is set to 20 seconds. The COS option will trigger before the Overflow Point thus routing the call to Voicemail.

   2. To enable Customer Administrators to create call flows that do not follow business hours, set the following COS values:

      1. Third Party Call Forward Follow Me Accept = Yes

      2. Third Party Call Forward Follow Me Allow = Yes

      3. Use Held Party Device for Call Re-routing = Yes

   3. Business requirements (COS - Feature Profiles, ARS - Dial Plans)

   4. Go to the Shared Options form and set "DPNSS/QSIG Diversion Enabled" to Yes.

6. For each sheet completed in Step 4 above, check the Data Format and Save For Import.

7. Use the output spreadsheet file to configure each MiVoice Business instance with this default database.

8. Follow these guidelines:

   • DID Configuration: Set the number of DID digits to absorb or insert for an incoming DID call (ensure that the DID trunk is set to absorb or insert all digits required to allow for ten digits to pass into the MiVoice Business instance).

   • Hardware Defaults: If the hardware defaults to not fit deployment requirements, refer to System Maintenance.

   • Call Rerouting: 6080 - 6099 will be used as pilot numbers in MiVoice Business.

   • Rows 20 - 39 (inclusive) in Call Rerouting Always and Call Rerouting 1st Alt forms are reserved for Management Portal. Any changes to Call Rerouting in Management Portal will change the values in these rows of these two forms.

   • Configuration Changes: Any changes to the default MiVoice Business database may require substantial reconfiguration of the Management Portal application to ensure that there are no discrepancies across the entire service offering.

   • Do not attempt to perform multiple loading tasks at the same time as the Import. Those tasks being loaded at the same time as the Import will fail. It will be necessary to retry those loading tasks independently.

To create an Initial MiVoice Business, then Backup and Restore on other MiVoice Business instances:

1. Use the MiVoice Business Embedded System Manager (ESM) to configure the initial MiVoice Business instance.

2. Test to ensure that the configuration was performed successfully.

3. Backup the MiVoice Business database.

4. Use the saved database backup file to configure each MiVoice Business with this default database.

Because Management Portal allows for programming Embedded Unified Messaging in user mailboxes, and Forward to Email in user mailboxes, the system programming requirements for these should be part of the default MiVoice Business database programming requirements.

Embedded Unified Messaging needs to be enabled on a system-wide MiVoice Business basis in the Embedded UM Settings form. For Forward Voicemail to Email, the SMTP server needs to be configured in the System Options form on the MiVoice Business instance(s).

To set up Embedded Unified Messaging:

1. Go to the Embedded UM Settings form on the MiVoice Business instance(s).

2. Program the following fields:

   1. Enable Embedded UM: Yes

   2. IMAP Server: The IP address of your IMAP server

   3. IMAP Server Connection Type: Either CLEARN, SSL, or STARTTLS

   4. IMAP Server Port: The port used by your IMAP server (typically 143)

   5. IMAP Server SSL Port: The port used by your IMAP server (typically 993)

3. Go to the System Options form.

4. Program the following fields:

   1. Email Server - The IP address of the SMTP server

   2. Email - Sender's Address - Enter an email address