Before creating a customer and allowing a customer administrator to perform self-service operations, you need to setup a default MiVoice Business Platform database that can be applied to each MiVoice Business Platform instance.
The default MiVoice Business Platform database is based upon the information gathered during the system planning phase. It is a combination of configurations to satisfy system requirements for feature profiles (COS), bundles, dial plans, and default settings. The template is then applied to every MiVoice Business Platform instance to provide the same level of features and services to all customers.
Note: The Platform Manager installation includes some reference golden database files. You can find them on the Platform manager server, under the linux directory /opt/dist_oria-bim-setup/reference.
Prior to performing any configuration operations on the default MiVoice Business Platform database, it is necessary to ensure that all requirements have been satisfied and included in the default database. There are two parts of the default database that can be defined as follows:
• Fixed Defaults - Oria Default Configurations (these are fixed in Oria and cannot be changed)
• Flexible Defaults - Business Requirements Configurations
The fixed defaults refer to the settings that must be configured on the default MiVoice Business Platform database to ensure proper interaction between Oria and the MiVoice Business Platform.
When a user, hotdesk phone (IP device only), or call group is created using Oria, there are specific settings that Oria applies, and these must match those on the MiVoice Business Platform, to ensure it responds correctly (i.e. when a hunt group is created, Oria sets the Class of Service to COS 6).
The table below shows the default values that Oria uses, and these values must be identical to that configured on the default MiVoice Business database. Use this table to plan and configure the default database.
Important: There are several pre-configurations that must be performed on the MiVoice Business before it can be provisioned by Oria. It is important to read the Oria Engineering Guidelines first, before configuring MiVoice Business in Oria.
Notes:
Index #1 in the Call Rerouting Always Alternatives and the Call Rerouting First Alternatives forms must be blank (or will be overwritten by Oria).
Index #2 in the Call Rerouting Always and First Alternative #2 must be set to DN configured through the Oria Portal.
| operation | setting | value | description |
|---|---|---|---|
| COS Defaults | Hotdesk Phones | 1/1/1 | Day/Night1/Night2 |
| Standard Phones | Any | MiCW default is 11. Recommendation is to use COS 11 for the MiCollab environment | |
| Hunt Groups | 6/6/6 (MiVoice) 25/25/25 (MiCollab) | Day/Night1/Night2 MiCW default value is 25. | |
| Ring Groups | 6/6/6 (MiVoice) 26/26/26 (MiCollab) | Day/Night1/Night2 Will need to override the MiCW default value of 26. | |
| EHDU Extensions | 11/11/11 | Day/Night1/Night2 MiCW default value is 11. | |
|
COR Defaults |
Hot Desk Phones | 1/1/1 | Day/Night1/Night2 |
| DID Trunk Attributes | DID Digits to Absorb | Value that will generate a 7 digit number string. | Oria requires a 7 digit local number after the process of absorbing the DID digit string. For example, in North America, the digits to absorb will be 3 if the regional dialing plan is 10 digits and 0 if the regional dialing plan is 7 digits. |
| Voicemail (EMEM) Configuration | Voicemail COS | *Any | Enable options: - COV/ONS/E&M Voicemail Port - Message Waiting - Voicemail Softkey *Use any available COS for voicemail (ports/hunt group) |
| Vmail Ports | *Any | Assign Voicemail COS *Create as many vmail ports as necessary | |
| Vmail Hunt Group | *Any | Assign: - Voicemail COS - Vmail ports *This is a configurable value (in the Settings tab when creating a Platform Group), and once assigned to a customer it cannot change. | |
| Call Rerouting First Alternative | 2 | Set as 'THIS' for all options to forward to voicemail hunt group (6000). | |
| Call Rerouting Always | 2 | Set as 'THIS' for all options to forward to voicemail hunt group (6000). | |
| Voicemail (NuPoint) Configuration | Voicemail COS | Any | Use any available COS for voicemail. The MiCW default value is 82. |
| Voicemail MWI COS | Any | Use any available COS for voicemail. The MiCW default value is 84. | |
| Voicemail Ports | Any | Assign Voicemail COS. Create as many voicemail ports as necessary. The MiCW default is to choose port numbers incrementally after the Voicemail Hunt Group number (eg. if the Voicemail Hunt Group number is 6000, the default is to start from 6001). | |
| Voicemail Hunt Group | 6000 (MiCollab) 7000 (vUCC) | Assign: • Voicemail COS • Voicemail ports | |
| Call Rerouting First Alternative | 2 | Set as 'THIS' for all options to forward to voicemail hunt group (eg. 6000). | |
| Speech Auto Attendant Configuration | Speech Auto Attendant COS | Any | Use any available COS for Speech Auto Attendant. The MiCW default value is 85. |
| Mitel Collaboration Advanced Configuration | Mitel Collaboration Advanced COS | Any | Use any available COS for MCA. The MiCW default value is 86. |
| Default CESID | Enable Automatic CESID | True | Allows user and hotdesk phone creation to occur successfully |
| Registration Access Code Configuration | Set Registration Access Code | Enter a string from 3 to 10 characters long to use when registering a new IP telephone. The access code followed by the DN constitutes the PIN and can include the characters # and/or *. |
Is required for creating a MiCollab Client Tenant in a platform group. If not set (blank), Oria displays the error message "MCD does not have the registration code set" when you try to save the platform group. |
The flexible defaults refer to the settings that must be configured on the default MiVoice Business Platform database to ensure proper interaction between Oria 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 Oria'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 Oria 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 Oria 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.
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:
• MiVoice Business Import Spreadsheets
• Configure an initial MiVoice Business, then Backup and Restore on other MiVoice Business instances
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 containing the 3300ICPImportSpreadsheet.tar file.
3 Unzip the 3300ICPImportSpreadsheet.tar to get the containing 3300ICPImportSpreadsheet.xls file.
Note: 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 De- fault MiVoice Business database:
• Default CESID
• Class of Service Options
• VM Ports
• Station Attributes
• Hunt Groups
• Hunt Groups - Hunt Group Members
• Call Rerouting Always Alternative
• Call Rerouting
• Class of Restriction Groups
• Trunk configuration forms (eg. SIP Peer Profile, IP/XNET Trunk Profiles, and any additional forms that may be required)
• ARS Routes
• ARS Dialed Digits
• ARS Leading Digits
• ARS Digit Modification Plans
• Trunk Attributes
• Embedded UM Settings
• System Options
5 Enter all of the following required and appropriate information into spreadsheets:
• Required Oria defaults (voicemail, COS, COR, Default CESID, DID trunk).
Note: 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.
• To enable Customer Administrators to create call flows that do not follow business hours, set the following COS values:
a Third Party Call Forward Follow Me Accept =Yes
b Third Party Call Forward Follow Me Allow =Yes
c Use Held Party Device for Call Re-routing =Yes
• Business requirements (COS - Feature Profiles, ARS - Dial Plans)
• 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 Oria. Any changes to Call Rerouting in Oria 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 Oria 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.
1 Use the MiVoice Business Embedded System Manager (ESM) to configure the initial Mi- Voice 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.
Since Oria 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).
1 Go to the Embedded UM Settings form on the MiVoice Business instance(s).
2 Program the following fields:
• Enable Embedded UM: Yes
• IMAP Server: The IP address of your IMAP server
• IMAP Server Connection Type: Either CLEARN, SSL, or STARTTLS
• IMAP Server Port: The port used by your IMAP server (typically 143)
• 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:
• Email Server:- The IP address of the SMTP server
• Email - Sender's Address: - Enter an email address