6.5 How to Setup OpenScape Mobile for Standard Solution

WebCDC has support for configuration of OSMO subscribers.
Prerequisites
The configuration data for the OSMO subscribers and the standard solution deployment are known / available.
Step by Step
1.
Navigate to the General tab and locate the row with ’OpenScape Mobile’ as its text. OpenScape Mobile is disabled by default in the General tab.
2.
Select ’yes’ in the 'Enable Feature' field located under the OpenScape Mobile row. Refer to section General tab in this document for detailed parameter descriptions.
3.
Set Generate OpenScape Mobile Data only accordingly to the following;
•
No (default) - will generate a combined OpenScape Voice database script for ONS number and the OSMO private DNs.
•
Yes - will still require a complete configuration of the WebCDC tabs, but creates only the OSMO related provisioning.
4.
Set the Numbering Plan value.
All OSMO DNs are private and will be created in the Main Office, although the associated ONS DNs can be provisioned in any branch office. With this only one private OSMO numbering plan is needed, and set to NP_OSMO by default, but may be modified.
5.
Select the Digest Authentication method from the drop-down of available values.
OSMO subscribers must authenticate themselves with OSV the same way as any other SIP entity does,. This requires a password. There are three methods to generate the digest authentication password with the WebCDC tool. The default is to inherit the OSMO subscriber SIP password from the associated ONS DN. WebCDC is able to generate a random password or will require the administrator to enter a password for each OpenScape Mobile subscriber.
•
Inherit Desk Phone DA (default)
•
User Input
•
Random
During registration of the OSMO client, additional data, necessary for utilizing OSMO capabilities will be sent to the client. Some of these parameters may be configured in the next three rows of the table (as shown it the next three steps below.
6.
SBC TLS List is a comma separated list of IP Addresses and ports (<IP Address: Port>) of the WAN interfaces of session border controllers protecting the SIP server in the corporate network.
7.
Service Contact Mail may be set. In case of errors on the client OSMO log files can be sent via email to a network administrator. The Service Contact Mail parameter may be used to set the destination email address in the OSMO clients.
8.
Voicemail - The OSMO client inherits the OSV voicemail DN and stores the number in GNF format on the phone in order to reach the voicemail account independent of connectivity. Format: Should be in GNF i.e. +15613391074.
9.
Next the OpenScape Mobile Office Code must be configured. This is performed on the Site tab.
OSMO DNs are private numbers and hidden to the end user. WebCDC generates these DNs by using the extensions of the associated ONS number and prefixes the extensions with the 'OSMO Office Code', which can be between 3 to 8 digits. By double clicking the Office Code for OpenScape Mobile feature field WebCDC creates the same 3 digit codes for all configured sites.
NOTE:  In case extensions in the different sites are overlapping, it is necessary to manually set the office codes in a way that the composed OSMO DN from office code and extension would not overlap with an OSMO DN from another site.
10.
Finally, the OSMO feature must be enabled per subscriber on the Subscribers tab.
The OSMO feature maybe assigned for each subscriber individually by selecting yes in the OpenScape Mobile Feature column of the subscriber. Depending on the previously chosen digest authentication method in the General tab , i.e. User Input, the WebCDC administrator may need to manually enter a password in the under the OpenScape Mobile Digest Password column.
NOTE:  The enabled OSMO feature automatically triggers WebCDC to choose the correct feature profile, i.e. OSMO w/o UC login = FP_Standard_Int, OSMO w/ UC login = FP_UC_Int.
11.
At this point the configuration details for OSMO are complete. Additional tabs for the deployment may be worked, or the user may continue on to save the configuration (as XML) or generate the actual configuration files. Details for these actions are available in this document.
 
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.