2.5.1 Solution Configuration

This workflow requires a minimal amount of data input to build OpenScape solution deployments. It makes extensive use of the default configurations provided by WebCDC:

Step by Step

Select the Start tab.

–

Complete the general project information.

–

Enter the desired Deployment Architecture from one of the following:

–

Standard Solution,

–

Standard Solution / vApp,

–

OpenScape Enterprise Express.

NOTE: Standard Solution / vApp is essentially the same as the Standard Solution workflow with the exception of the additional vApp Settings tab. However, an additional fact to note is that the vApp is deployed as a solution. This makes the Generate Config button’s Select All option to be the only one available. All other options are greyed out.

–

Specify the UC Deployment Architecture per target UC arrangement, e.g. Standard Duplex - Small.

–

Choose the correct versions for OpenScape Voice, RG 8700, OpenScape UC App, OpenScape Branch, OpenScape SBC, Xpressions, Contact Center and Concierge.

–

Select the desired Delta generation option.

Select the General tab to set the switch level configuration values.

Select the IP tab and enter the target deployment’s IP settings and host name(s).

Select the Site tab and enter the various call related, site defaults and other settings for the different sites.

Use the Endpoints tab to enter the data for endpoints located at the remote sites. These endpoints represent gateways, SIP proxies, Proxy ATAs and SBCs. The required information include numbering plan info (e.g. Area Code, DID range) as well as IP addressing for the signaling, administration, voice and VIP (OSB only).

The Subscribers tab is used to enter the "non default users“.

–

If the Site tab field Make default subscribers for the extension range is set to yes, then the default subscribers will automatically be generated (and are not shown in the Subscribers tab).

It is possible to create additional subscribers in the Subscribers tab with hunt group and pickup group settings. If the user in the Subscribers tab overlaps with a default user, then the information from the Subscribers tab will be applied.

The available pre-defined Feature Profiles that are automatically assigned to subscribers may be viewed on the Feature Profiles tab. This tab also allows the user to create new FPs via the empty / free columns at the far right of the screen work area and then setting the associated cells to the appropriate values for the listed feature names. Feature Profiles that are shown on this tab are then available for assignment to subscribers on the Subscribers tab.

If analog adapters are used in one or more of the sites, then this information is entered in the Analog Adapters tab. The information required is primarily the analog adaptor type and its IP addressing information.

10.

For sites where an OpenScape Branch 50i or 500i is used with FXO, BRI, or PRI trunks it is necessary to use the OSB 50i - 500i tab. This tab associates the ports to specific trunk groups.

11.

OSCC tab:

NOTE: This tab will not be displayed if the Contact Center version in the Start tab s set to No OSCC Server.

The OSCC tab is used to configure OpenScape Contact Center which supports contact center / call center arrangements with designated agent and manager roles. In the Standard Solution this will only create the data for the OSV (not the OSCC). For OpenScape Enterprise Express the configuration is predefined and so the OSCC is also provisioned. Because Standard Solution is unlimited the OSCC must be provisioned manually.

12.

The EA Groups tab is used to configure Executive / Assistant arrangements. Predefined arrangements with up to four executives and two assistants exist. The user may also customize this configuration, not to exceed 4 execs and 2 assistants.

13.

Breakout Endpoints tab:

NOTE: This tab is only displayed when the General tab’s Breakout Strategy field is set to Customized.

By default the users at a site are automatically allowed to use their local gateway for PSTN access. This tab is populated from the settings on the Site tab and the user is given the chance to make changes (the 'yes' or 'no' question pops up during generation). This provides flexibility for users at sites to instead breakout via another site(s) gateway. Different gateways can be associated with local, national and international calling. (Note that an international breakout is not allowed in another country). Another capability permits specification of a backup function for each site (e.g. when the normal gateway fails). This tab can be useful for purposes of providing a more cost-efficient access and/or to associate a backup path to the PSTN to enhance the robustness/reliability of the PSTN access.

14.

The Speed Dial Lists tab permits configuration of speed dial data lists for the Business Group.

15.

The tab Class of Restriction may be used to define various Class of Restrictions to different Traffic Types while the Toll and Call Restriction tab supports associating characteristics such as Blocked Call Lists, Switchover Durations, and restriction Day / Date Schedules with the Class of Restrictions.

16.

UC tab:

NOTE: This tab is only displayed when the Start tab’s UC Deployment Architecture field is NOT set to No UC.

The UC tab supports assignment of Unified Communications (UC Application) data with Subscriber Directory Numbers. The data includes UC Login ID, IM Address, Email/Password, FAX, Mobile and Home Phone information. Prefill UC Subscriber and Prefill IM Address buttons are located on this tab and streamline some of the initial data entry by using information derived from the Subscribers tab to auto-populate rows into this tab. The remaining data elements for the rows are then completed manually.

17.

Xpressions tab:

NOTE: This tab is only displayed when the Start tab’s Xpressions version field is NOT set to No Xpressions Server.

The Xpressions tab is where Subscriber Directory Numbers are assigned voice mailbox data such as PIN, Password and Language. Similar to the OpenScape UC Data tab, there is a Prefill Xpressions Subscriber Data button to auto-populate rows into this table based upon the Subscribers tab entries. The remaining data elements for the rows are then completed manually.

NOTE: The next three tabs are concerned with special types of subscribers and subscriber groupings/arrangements. They only need to be used if the specific deployment is to have such subscribers.

18.

Concierge tab:

NOTE: This tab is only displayed when the Start tab’s Concierge version field is NOT set to No Concierge Server.

The Concierge tab is used to configure the OpenScape Concierge product which supports company operator positions.

19.

The Continuous Tracing Parameters tab allows configuration of the settings necessary for the OpenScape Trace Manager and the OpenScape device types (to be traced). Information such as trace file sizes, database file path, transfer types and time intervals are defined here. The General tab value for Enable data collection for Continuous Tracing must be set to yes for this tab to appear.

20.

vApp tab:

NOTE: This step applies only if the Deployment Architecture of Standard Solution / vApp has been selected on the Start tab. This triggers the presentation of the vApp tab which supports generation of the deployment’s virtual appliance iso file.

Enter the data for the configuration of the deployment’s specific virtual appliance environment. This tab contains sections which address the configuration values for the various OpenScape products that may be included in the virtualized target deployment. It contains helpful buttons and fields which assign default values and starting IP addresses (from which other IP addresses are derived).

NOTE: vApp support for the Standard Duplex Large for the UC with Duplex deployment for OSV is supported (via UC Front End fields). This is in addition to support of the Standard Solution deployments support for Standard Duplex Small for the UC Assistant and Duplex deployment for OSV. For Standard Duplex Small the only sections of the vApp tab that need to be filled in are the Common Config and OSUC Back End. The OSVoice parameters are automatically filled in by WebCDC during configuration generation.

21.

At this point the necessary tabs have been populated. To perform the actual generation of the device configuration files proceed to the next section.

OpenScape Solution Set V10, Customer Data Collection with WebCDC V1, Planning Guide, Issue 2, ID: A31003-S11A0-P100-2-76A9

© 07/2024 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.