|
•
|
|
3.
|
Create a new project by clicking the My Projects > New Project selection, provide a name within Enter Project Name field, and then click the Create Project button.
|
|
4.
|
Select the Start tab and provide (or update) the following details that are useful for management / control over the specific OpenScape Enterprise Express configuration project.
|
|
•
|
|
5.
|
Click into the Start tab and set the Deployment Architecture to OpenScape Enterprise Express. The UC Deployment default value may be kept.
|
|
6.
|
Set the product software versions for the Openscape Voice, RG8700, OpenScape UC App, OpenScape Branch and OpenScape SBC.
|
|
7.
|
Select the General tab, click the Edit button and in the General parameters of the OpenScape Voice system section:
|
|
a)
|
Select the Keyboard settings for node.cfg value appropriate for the deployment’s country.
|
|
b)
|
Enter the Company Name. Note that it is recommended to use hyphens (’-’) in place of spaces as this field must use only DNS allowed characters (i.e. [az][AZ][09][-][.]).
|
|
c)
|
Enter the Business Group Name.
|
|
d)
|
Enter the Business Group Default Display Number.
|
|
e)
|
Enter the User Digest Password Generation value that will be used for the security of all the SIP phone connections. Available values are Disable, User Input, and Randomize.
|
|
f)
|
Enter the Subscriber Display Syntax as either ’First Name Last Name’ or ’Last Name, First Name’.
|
|
g)
|
If this is to be a site delta generation (e.g. adding a site to a existing deployment; but modify of a site is not possible), then set Delta generation to ’Delta on OSV configuration’.
|
|
h)
|
If delta’s upon an existing deployment’s subscribers is necessary, then set Subscriber Delta generation to ’Delta on CDC project’.
|
|
i)
|
Trace Manager functionality may be enabled via the field Enable Trace Manager. Default is ’no’.
|
|
j)
|
|
p)
|
|
u)
|
Set the SBC: Enable Remote Endpoints if the central SBC is to handle remote endpoints in remote sites, or handle SSP (SIP Service Providers).
|
|
v)
|
The SBC: Enable Remote Subscribers should be if remote subscribers are to REGISTER towards a central SBC via the WAN (e.g. via the internet) towards an OSV. SUPER IMPORTANT is that the digest authentication is ENABLED in this case, to prevent a major security hole allowing SIP communication via the internet without verifying the credentials of the user via the digest authentication. By default, the "SBC: Enable Remote Subscribers" is disabled for security reasons.
|
|
x)
|
Set the Enable EA Cockpit for EA Groups and Enable CAC Feature values as yes or no as needed (defaults are no).
|
|
y)
|
Set Enable PC port on phone if PCs will be connected behind OpenStage phones.
|
|
aa)
|
In most OpenScape Enterprise Express cases the Special Customer Configuration field may be ignored, but if PBX-Routing is a factor then this field may be used.
|
|
8.
|
While still on the General tab the following items are configured in the OpenScape UC basic configuration section
|
|
9.
|
While still on the General tab the following items are configured in the OpenScape Xpressions basic configuration section
|
|
10.
|
While still on the General tab set Call Admission Control field Enable Feature to yes if CAC will be used in the deployment.
|
|
11.
|
While still on the General tab if OpenScape Mobile is to be in the deployment, then the following fields should be configured:
|
|
a)
|
Enable set to yes
|
|
e)
|
|
g)
|
|
12.
|
Select the Site tab.
|
|
a)
|
The first major block / section of information on this tab collects configuration data that applies only to the Headquarters (main office) site. Enter the Private Extension and Public Numbers for the various Voicemail, Conference, Auto Attendant and Operator functions. Fields that do not require input / are not applicable are shown as ’greyed-out’ cells in the tab.
|
|
b)
|
The next major block on the Site tab supports per site configuration settings. This includes the Headquarters (main office) location as well as the remote Branch Offices (i.e.Site 2, Site3, ...). Fill in the relevant data fields for each site. The input field explanations are available in Section 4.2, “General Tab”. WebCDC also supports helpful field explanations via mouse pointer triggered Tool Tip pop ups.
|
|
13.
|
Select the Endpoints tab.
|
|
b)
|
|
c)
|
Endpoint Type - modify as necessary to the correct OSB or RG 8700 model.
|
|
d)
|
|
h)
|
Administration LAN IP (RG 8700 only).
|
|
i)
|
Administration LAN Netmask (RG 8700 only).
|
|
j)
|
Administration LAN Default GW (RG 8700 only).
|
|
15.
|
The remaining columns within the Endpoints tab require valid data input in order to complete the endpoint configuration data.
|
|
a)
|
|
b)
|
County Code - e.g. 1 for USA, 49 for Germany, etc.
|
|
c)
|
Area Code - Area code for the site.
|
|
d)
|
Subscriber Code / Local Exchange Code - Note that this value will be automatically defaulted to ’123’ when Dial In Number Type in the General tab has been set to ’Any Non-DID Numbers’.
|
|
e)
|
Subscriber DID Extension Range - Telephone numbers in the public network that route directly to stations in the customer’s network.
|
|
g)
|
Presubscribed Carrier Code - some countries require this, e.g. Brazil.
|
|
h)
|
Port and Line Channel Selection - Select the used ports (lines) and the channels of the gateway.
|
|
l)
|
Administration Endpoint IP (RG8700 only)
|
|
m)
|
Administration Endpoint Netmask (RG8700 only)
|
|
n)
|
Administration Endpoint Default GW (RG8700 only)
|
|
o)
|
Virtual IP Address (OSB Only) - generally not used for OSEE
|
|
p)
|
Voice LAN IP (RG 8700 only).
|
|
q)
|
Voice LAN Netmask (RG 8700 only).
|
|
r)
|
Voice LAN Default GW (RG 8700 only).
|
|
s)
|
|
t)
|
|
v)
|
|
x)
|
|
z)
|
|
aa)
|
|
16.
|
If the deployment has any analog adapters, then the next step is to select the Analog Adapters tab. This tab supports the details of which sites have adapters, their type and IP addressing information.
|
|
b)
|
Site Name - select it from the drop down list of site names.
|
|
c)
|
Analog Adapter Type - select the model from the drop down list.
|
|
17.
|
The next tab for OSB 50i - 500i supports input of additional details for OpenScape Branches that are located at the remote sites and which are either the 50i, 500i model or will be acting as a Session Border Controller. If the Openscape Branch is to function as an SBC, then only additional information concerning its WAN IP address, Netmask and Default Gateway are required. If it is a 50i or 500i, then the following must be supplied.
|
|
b)
|
Trunk Group Name - A user assigned name.
|
|
c)
|
Trunk Type - Of the 50i’s port (Normal or Emergency) is set for up to 8 physical ports in consecutive columns.
|
|
d)
|
Physical Port - up to 8 may be specified. A range of channels, individual channels, or ’X’ if all channels are used.
|
|
e)
|
Default Dest - should be in the DID range.
|
|
f)
|
|
g)
|
|
h)
|
|
18.
|
If the deployment will use customer Feature Profiles, then they may be created using the Feature Profile tab and referenced from subscriber entries on the Subscribers tab. Otherwise, WebCDC will assign the pre-cast Feature Profiles by default using its internal rules.
|
|
19.
|
Select the Subscribers tab. Enter a row of input for each subscriber that will be in the target deployment. The following columns / data items may be input:
|
|
a)
|
First Name - Name to show in the phone displays.
|
|
b)
|
Last Name - Name to show in the phone displays.
|
|
c)
|
Site Name - Site where subscriber is located.
|
|
d)
|
Subscriber Dialing Permissions - Scope of the subscriber’s calling capabilities.
|
|
e)
|
Extension - The subscriber’s extension number.
|
|
f)
|
Directory Number - If there is a public number.
|
|
g)
|
External Caller Id - If it needs to be different than DN.
|
|
h)
|
Device Type - The model of the phone. The Profile Only value is required if the number is to be a MLHG.
|
|
i)
|
MLHG Group - The ID number for the MLHG.
|
|
j)
|
MLHG Type - The hunting algorithm used by the MLHG. This should only be set for the pilot number, i.e. the Device Type must also be set to Profile Only.
|
|
k)
|
If the deployment shall have keysets, the information on Line Key Label Digits, Keys Order, Keyset Line, and Keyset Module is entered in consecutive columns. If keysets are not an issue then these columns may be hidden via the Hide Keyset Fields button.
|
|
l)
|
Prompt Language - Language that is used for their media server announcements, e.g. English, German.
|
|
m)
|
Xpressions Language - Language that is used by the Xpressions component, e.g. English, German.
|
|
n)
|
UC Login Id - Users Login Id for UC services.
|
|
p)
|
Email - This email address information configures the Xpressions component to provide eFax support to the subscriber.
|
|
20.
|
If EA Groups shall be deployed in the specific deployment, then select the EA Groups tab. Enter a row of input for each station that shall be in the EA Group. The following columns / data items may be input:
|
|
a)
|
Executive/Assistant Group Name - A meaningful name for the group.
|
|
b)
|
Subscriber (Private) Extension - Must refer to a subscriber in the Subscribers tab.
|
|
d)
|
|
e)
|
Line Type - Applies only for Rollover (Primary, Query, Rollover, Private). Blank is treated as Primary.
|
|
f)
|
Function - The station’s role in the EA arrangement, i.e. which assistant or executive they are within the group.
|
|
g)
|
Executive/Assistant Relationship - For example ’Executive2 - Assistant1’ for Executive2’s primary assistant to be Assistant 1.
|
|
21.
|
If the specific OpenScape Enterprise Express deployment is to have contact center capability, then select the OSCC tab. Details for configuring OSCC is available in 6.7, “Setup of OpenScape Contact Center for Enterprise Express”.
|
|
22.
|
Go to the vApp tab and either use the Assign Default vApp values button or supply values that are unique / specific to the target deployment.
|
|
23.
|
At this point the Express data input is complete. Save the project data via the Save button.
|
|
24.
|
The collected Express data may be (1) exported (to.xml) via the Export Project button and/or (2) you may go directly to the file generation via the Generate Config button.
|