Difference between revisions of "OpenScape Endpoint Management"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
Hans.zeiner (talk | contribs) (Created page with "{{Breadcrumb}} [[File:OSEM-Dashboard-screen.jpg|250px|thumb|OSEM dashboard] The '''OpenScape Endpoint Managment''' (OSEM) is an integrated or stand-alone management applicat...") |
Hans.zeiner (talk | contribs) |
||
Line 1: | Line 1: | ||
{{Breadcrumb}} | {{Breadcrumb}} | ||
− | [[File:OSEM-Dashboard-screen. | + | [[File:OSEM-Dashboard-screen.png|250px|thumb|OSEM dashboard] |
The '''OpenScape Endpoint Managment''' (OSEM) is an integrated or stand-alone management application for central administration of the following IP Devices (both [[SIP]] and [[HFA]]) in VoIP networks: | The '''OpenScape Endpoint Managment''' (OSEM) is an integrated or stand-alone management application for central administration of the following IP Devices (both [[SIP]] and [[HFA]]) in VoIP networks: | ||
Latest revision as of 11:12, 30 October 2024
[[File:OSEM-Dashboard-screen.png|250px|thumb|OSEM dashboard] The OpenScape Endpoint Managment (OSEM) is an integrated or stand-alone management application for central administration of the following IP Devices (both SIP and HFA) in VoIP networks:
- IP Phones:
- IP Gateways and HiPath/OpenScape platforms:
- HiPath 4000 V5 and V6,
- HiPath 3000 (through HG1500) V8 and V9,
- OpenScape Office MX/LX V3 (subject to a Project Specific Release),
- OpenScape Voice V5, V6 and V7
OSEM is the central component with which devices and QoS parameters of IP devices are administered for the customer's entire OpenScape solution.
The latest released version is OpenScape Endpoint Management V1 R1.
OSEM is designed as a containerized server application. Currently two deployment scenarios are supported
- OpenScape 4000 integrated
- Standalone Installations for small and medium installations
The Graphical User Interface is scalable and browser based. No local installation on the client is needed.
In addition to standard GUI based operation, all OSEM functions can be used by a built-in REST API.
Contents
OSEM System Requirements
OpenScape 4000
- Eco Server V2
- VM installation as standalone or on Branch
Standalone
- Minimum hardware requirements for the OSEM standalone installation:
OSEMStandalone | |
CPU | x64 CPU |
RAM | 2 GB |
Ethernet | 100 MBit (1 GBit is recommended) |
Disk Space | 50 GB |
Most important OSEM features
- Device Management: Management of devices in groups
- Configuration: Configure all parameters of the supported devices
- Mobility: Mobility for SIP & HFA devices
- Security: Certificate management and secure connection
- Software: Deploy device software based on predefined rules
- Templates: Definition of a set of configurations parameters into a template
- Groups: Combining Templates into groups and assign groups to a set of devices
- Monitoring: Monitor devices whether they are online
- Backup & Restore: Backup and Restore of all OSEM parameters
- Migration from OpenScape Deployment Service: Easy migration path from DLS to OSEM
Customer Benefits
- User Mobility to allow anyone to log into any guest phone in any location and instantly receive all their phone settings and customizations.
- Easy device installation or replacement using Plug&Play without the need for an on-site tech which lowers install and support costs.
- Scheduled software updates minimize disruptions to the business.