Difference between revisions of "OpenScape Business"
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.
(→Integration in business application and processes) |
Claus.rist (talk | contribs) (→Security Bulletins) |
||
| (407 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Breadcrumb|||Unified Communications}} | {{Breadcrumb|||Unified Communications}} | ||
| − | [[Image: | + | [[Image:OSBizX1Rcloudlogo.png|right|250px|]] |
| − | |||
| − | + | Unify '''OpenScape Business''' is based on future-proof technologies and offers small to medium-sized enterprises everything they need for their individual and diverse communication requirements, unified in a single flexible, scalable and secure solution with various deployment (on-premise, hosted, private cloud based or combined) and purchase models (CAPEX and OPEX). The Unify '''OpenScape Business''' architecture allows use independently of the existing telephony infrastructure – regardless of whether this is classic telephony, IP or DECT. Unify OpenScape Business always provides enterprises with up to 500 subscribers, or 2000 subscribers in one network, with the right solution | |
| − | |||
| − | |||
| + | From extended telephony to a feature-rich set Unified Communication (UC) solution, Unify '''OpenScape Business''' is easily scalable and can be enhanced with the cloud-based UC Softphone solution Unify Phone as business grows and the telephony and communications needs change. | ||
| + | |||
| + | Unify Phone provides unprecedented flexibility for organizations of all sizes by enabling them to benefit from the advantages of cloud collaboration while allowing them to leverage their on-premise investments for best in class hybrid-working experiences. Unify Phone is the perfect solution, not only for mobile employees. | ||
| + | |||
| + | <br> | ||
| + | '''OpenScape Business''' offers the following highlights: | ||
| + | <br> | ||
| + | * Best in Class and Award winning Voice & UC Solution for SMB | ||
| + | * Scalable from 2-2000 Users for Standalone and Multisite environments | ||
| + | * All-In-One Solution incl. feature rich Voice, Presence, Conferencing, Contact Center, Messaging, IM, Mobility, Fax | ||
| + | * Support of any given end-customer infrastructure (on-premise, hybrid, private cloud) incl.comprehensive virtualization-options for Voice & UC | ||
| + | * Easy-to-order & pre-packaged, easy-to-install | ||
| + | * Software Upgrades and Service included for 1,3 or 5 years | ||
| + | * Ready for new All-IP / ITSP based Services (SIP Provider) | ||
| + | * Unify Phone for OpenScape Business providing powerful telephony services (connector) either as a stand alone client or embedded in Microsoft Teams | ||
| + | |||
| + | <br> | ||
== Overview == | == Overview == | ||
| + | '''OpenScape Business''' offers small and medium-sized enterprises everything they need for their individual and diverse communication requirements, unified in a single flexible and scalable solution. The OpenScape Business architecture allows use independently of the existing telephony infrastructure regardless of whether this is classic telephony, IP or DECT. From powerful telephony to a feature-rich set Unified Communication (UC) solution, '''OpenScape Business''' always provides with the right solution. With Unify Phone as a cloud based solution secure connected to OpenScape Business, even powerful telephony for office workers, mobile employees or remote worker can be offered. | ||
| − | + | As standalone system up to 1500 subscribers and in networked systems up to 2000 subscribers can be connected. | |
| − | |||
| − | [[Image:OSBiz-overview.png| | + | [[Image:OSBiz-overview.png|800px]] |
== New Features == | == New Features == | ||
| + | Since market introduction the feature set of OpenScape Businsse has been continuously enhanced and improved.<br> | ||
| + | The following link contains an overview about the SW versions and the enhancements. <br> | ||
| + | <br> | ||
| + | [[OpenScape Business Feature Enhancements]] | ||
| + | |||
| + | == OpenScape Business Deployment Options == | ||
| + | Different models are available for the use of telephony and UC functionality. <br> | ||
| − | + | [[Image:OpenScape_Business_Picture_X1_Rack_mounted.png|right|250px|]] | |
| − | + | *'''OpenScape Business X1R''' | |
| + | **For rack and wall-mounting | ||
| + | **Up to 50 UC User | ||
| + | **Up to 500 extensions (number of IP, analog and digital subscribers) | ||
| + | **Max. 8 digital (UP0/E) , max. 4 analog (FXS) | ||
| + | **Max. 7 DECT Base Stations, up to 16 DECT Handsets" | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''' | + | [[Image:OSBiz_X3R_V3.png|right|250px|]] |
| − | * | + | |
| − | + | *'''OpenScape Business X3R''' | |
| − | + | **For rack and wall-mounting | |
| − | + | **Up to 500 UC User | |
| − | + | **Up to 500 extensions (number of IP, analog and digital subscribers) | |
| − | + | **Max. 20 digital (UP0/E) , max. 24 analog (FXS) | |
| − | + | **Max. 15 DECT Base Stations, up to 64 DECT Handsets" | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | [[Image:OSBiz_X5.png|right|250px|]] | |
| − | + | ||
| − | + | *'''OpenScape Business X5R''' | |
| − | + | **For rack and wall-mounting | |
| − | + | **Up to 500 UC User | |
| − | + | **Up to 500 extensions (number of IP, analog and digital subscribers) | |
| − | + | **Max. 56 digital (UP0/E) , max. 68 analog (FXS) | |
| + | **Max. 15 DECT Base Stations, up to 64 DECT Handsets" | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[Image:OSBiz_X8.png|right|150px|]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''' | + | *'''OpenScape Business X8''' |
| − | * | + | **Installation as a standalone unit or mounted in a 19-inch rack |
| − | ** | + | **Modular system with base box and expansion box |
| + | **Up to 500 UC User | ||
| + | **Up to 500 extensions (number of IP, analog and digital subscribers) | ||
| + | **Max. of 384 TDM User (number of digital, analog, DECT subscribers) | ||
| + | **Max. 64 DECT Base Stations, up to 250 DECT Handsets | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | [[Image:OSBizS3.png|right|150px|]] | ||
| − | + | *'''OpenScape Business S''' | |
| − | + | **Pure software solution, server based, as a virtual appliance or hosted as a private cloud solution in a datacenter for up to 1500 IP / UC User" | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | |||
=== Hardware Platforms === | === Hardware Platforms === | ||
| − | OpenScape Business | + | OpenScape Business X1R, X3R, X5R or X8 are "All-In-One" HW platforms with onboard IP access and support for up to 500 subscribers with IP, digital (UP0E), analog (a/b), cordless (DECT) devices. With the new OpenScape Business X1R, X3,X5 and X8 V3 Mainboard full UC capabilities and applications are embedded. Connection to public WAN is done via SIP/ITSP (LAN), ISDN (BRI and PRI) or analog trunks. For X1R one mainboard deployment (basic, no BRI) is available, X3 and X5 two V3 Mainboard deployments (basic and advanced) are available, while for OpenScape Business X8 the advanced Mainboard can be used. |
| − | + | An Advanced mainboard is needed in case the system has more than 50 UC users and/or Contact Center and/or connection to external DB’s and/or higher trunk/feature capacities. | |
| − | |||
| − | * | + | *Basic Mainboard capacities |
| − | * | + | **Up to 50 UC / Unify Phone User |
| + | **Up to 60 SIP trunk channels | ||
| − | + | *Advanced Mainboard capacities | |
| − | * | + | **Up to 500 UC / Unify Phone User |
| − | * | + | **Up to 120 SIP trunk channels |
| − | * | + | **Multimedia Contact Center |
| + | **Connectivity to external databases | ||
| + | **Enhanced feature capacity limits, e.g. group call members" | ||
=== Software Platforms === | === Software Platforms === | ||
| − | OpenScape Business S is the server-based "All-In-One" telefony and UC platform, which supports up to | + | OpenScape Business S is the server-based "All-In-One" telefony and UC platform, which supports up to 1500 IP subscribers and IP (SIP) connection to the public network (WAN). It is designed for Linux (Novell SLES) operating system and can be operated either on a physical or on virtual machines with VMware vSphere, Microsoft Hypervisor, KVM (project-specific) or Google Cloud. OpenScape Business S can be networked with OpenScape Business X1R, X3R, X5R or X8 as gateway for ISDN or analog trunks or TDM / analog devices. |
== Features == | == Features == | ||
| − | '''OpenScape Business''' | + | '''OpenScape Business''' offers a unified software solution architecture based on modern and innovative communication technologies. |
* All-In-One Unified Communication solution for small and medium enterprises | * All-In-One Unified Communication solution for small and medium enterprises | ||
| − | ** Integrated voice services | + | ** Integrated powerful voice and telephony services |
** Presence management (presence status) | ** Presence management (presence status) | ||
| + | ** Status based call forwarding | ||
| + | ** Call Journal | ||
| + | ** Call Recording | ||
| + | ** Favorites list | ||
| + | ** Dialing by mouse click / Hotkey Dialing | ||
| + | ** Visual voicemail | ||
** Drag and Drop Conference | ** Drag and Drop Conference | ||
| − | |||
| − | |||
| − | |||
** Directory access with database connection | ** Directory access with database connection | ||
| + | ** Mobility support | ||
** Fax support | ** Fax support | ||
** Integration into business processes | ** Integration into business processes | ||
| + | ** Instant Messaging (IM) | ||
** etc. | ** etc. | ||
| − | |||
* Multichannel Contact Center | * Multichannel Contact Center | ||
| − | + | * Integration of OpenScape Web Collaboration (Video Conferencing, Screenshare, File Upload) | |
| − | * Integration of OpenScape Web Collaboration | + | * Unify Phone as a WebRTC based cloud telephony service for mobile and desktop |
| − | + | * Interworking with Microsoft Teams (via SBC, Direct Routing) | |
| + | * Integration in Microsoft Teams (myPortal for Teams plugin, Unify Phone for Microsoft Teams) | ||
* Multiple Sites support | * Multiple Sites support | ||
| − | |||
* Unified solution architecture | * Unified solution architecture | ||
** Scalable and flexible HW / SW and licensing | ** Scalable and flexible HW / SW and licensing | ||
| − | ** Easy to handle migration from HiPath 3000 to OpenScape Business | + | ** Easy to handle migration from HiPath 3000 to OpenScape Business (System box and almost all existing devices can be reused only the motherboard and the SW has to be replaced) |
| − | System box and almost all existing devices can be reused only the motherboard and the SW has to be replaced | ||
<br> | <br> | ||
| − | For | + | For detailed feature descriptions have a look into the OpenScape Business datasheet, feature description or Sales Information which is accessible for Mitel/Unify Partners. |
| Line 226: | Line 164: | ||
=== Supported phones and devices === | === Supported phones and devices === | ||
| − | * ''' | + | * '''OpenScape Desk Phone CP (IP/HFA, SIP)'''<br> |
| − | ** | + | ** [[OpenScape Desk Phone CP]] 100, 200/205, 400, 600/E, 700<br> |
| − | * '''OpenScape Desk Phone (SIP)'''<br> | + | * '''OpenScape Desk Phone CP Key Modules'''<br> |
| − | **[[OpenScape Desk Phone | + | ** [[OpenScape Desk Phone CP]] KM400, KM600<br> |
| − | * ''' | + | * '''OpenScape Desk Phone CP G2(IP/HFA, SIP)'''<br> |
| − | **[[ | + | ** [[OpenScape Desk Phone CP G2]] 110,210,410, 710<br> |
| − | * | + | * '''OpenScape Desk Phone CP G2 Key Modules'''<br> |
| − | **[[ | + | ** [[OpenScape Desk Phone CP G2]] KM410, KM710<br> |
| + | * '''OpenScape Desk Phone CP accessories'''<br> | ||
| + | ** [[OpenScape Desk Phone CP G2]] WiFi Stick CP10 for CP210, CP410, CP710 | ||
| + | |||
| + | * '''Mitel Phone Family'''<br> | ||
| + | ** Mitel Phone Series 6800/6900 (connected via SIP) | ||
| + | ** Mitel SIP DECT Solution (connected via SIP) | ||
| + | |||
* ''' Cordless CMI/DECT - IP/DECT telephones '''<br> | * ''' Cordless CMI/DECT - IP/DECT telephones '''<br> | ||
| − | **[[ | + | **[[OpenScape DECT Phone SL5]], [[OpenScape DECT Phone S5]], [[OpenStage SL4 professional]], [[Gigaset S4 professional]], [[OpenStage M3]], [[OpenScape DECT Phone S6]], [[OpenScape DECT Phone SL6]], [[OpenScape DECT Phone R6]]<br> |
| − | * '''PC Clients | + | |
| + | * '''PC / mobile Clients''' <br> | ||
| + | **Unify Phone for OpenScape as a cloud based WebRTC softphone for mobile/desktop operation (hybrid approach via telephony connector to OpenScape Business. | ||
**OpenScape Personal Edition (including Video support for SIP)<br> | **OpenScape Personal Edition (including Video support for SIP)<br> | ||
* '''SIP phones (UC Suite) / AP adapter''' <br> | * '''SIP phones (UC Suite) / AP adapter''' <br> | ||
| Line 245: | Line 192: | ||
<br> | <br> | ||
* '''WLAN phones''' | * '''WLAN phones''' | ||
| − | **[[ | + | **[[OpenScape WLAN Phone WL4]] |
* '''Analog and ISDN phones''' | * '''Analog and ISDN phones''' | ||
**Analog (a/b) phones <br> | **Analog (a/b) phones <br> | ||
| Line 252: | Line 199: | ||
'''Please note''': <br> | '''Please note''': <br> | ||
| − | + | Devices, which are no longer part of the current product portfolio of Unify, (such as optiPoint 410/420/500; Gigaset Handsets: SL3/S4/M2; OpenStage 5/10/20/30/60/80) can still be connected and operated with OpenScape Business. In case of technical problem no support is given by Unify if the milestone "End od Support" has been reached. For further details such as the required software versions for each device, refer to the respective technical release notes. | |
| − | Optiset E devices cannot be operated. | + | Optiset E devices cannot be operated in general. |
=== Unified Communications === | === Unified Communications === | ||
| Line 260: | Line 207: | ||
<br> | <br> | ||
'''UC Smart'''<br> | '''UC Smart'''<br> | ||
| − | UC Smart SW is fully embedded within the OpenScape Business SW running on the | + | UC Smart SW is fully embedded within the OpenScape Business SW running on the V3 Mainboard of OpenScape Business X1/X3/X5/X8 or OpenScape Business S. It comprises the following Unified Communications and Collaborations features.<br> |
| − | comprises the Unified Communications and Collaborations features | ||
* Presence incl. status based announcements <br> | * Presence incl. status based announcements <br> | ||
| − | * Favorites incl. Call Status <br> | + | * Conference planned/adhoc |
| + | * Favorites List incl. Call Status <br> | ||
| + | * Directories <br> | ||
| + | * Call Journals incl. Reminder <br> | ||
| + | * Status based Call Forwarding | ||
| + | * Call Control (CTI) incl. dialing by hotkey <br> | ||
* Visual VoiceMail Control <br> | * Visual VoiceMail Control <br> | ||
| − | * | + | * Instant Messaging (Chat) |
| − | + | * Web Collaboration <br> | |
| − | |||
| − | * | ||
| − | The UC Smart solution offers | + | The UC Smart solution offers two clients: |
| − | * myPortal | + | * myPortal @work (WebRTC based UC and telephony) |
| − | * | + | * Unify Phone for OpenScape (cloud based WebRTC Client for mobile/Desktop) |
| − | |||
<br> | <br> | ||
'''UC Suite'''<br> | '''UC Suite'''<br> | ||
| − | UC Suite | + | UC Suite SW is fully embedded within the OpenScape Business SW running on the V3 Mainboard of OpenScape Business X1/X3/X5/X8 or OpenScape Business S . |
| − | |||
| − | + | It comprises the following extensive Unified Communications and Collaborations features.<br | |
| − | |||
| − | + | * Presence incl. status based announcements <br> | |
| + | * Conference planned/adhoc | ||
| + | * Favorites List incl. Call Status <br> | ||
| + | * Directories, opt. with ext. database connection<br> | ||
| + | * Call Journals incl. reminder <br> | ||
| + | * Status based Call Forwarding | ||
| + | * CallMe! | ||
| + | * Personal Auto Attendant | ||
| + | * Call Control (CTI) incl. dialing by mouse click or hotkey <br> | ||
| + | * Voice Message Box <br> | ||
| + | * Fax Message Box | ||
| + | * Notifications | ||
| + | * Instant Messaging (Chat) | ||
| + | * Voice Recording | ||
| + | * Multichannel Contact Center | ||
| + | * Web Collaboration <br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | The UC Suite solution offers several Unified Communications clients: | |
| − | The | ||
| − | + | * myPortal @work (WebRTC based UC and telephony soft client) | |
| + | * myPortal for Desktop (UC and CTI) | ||
| + | * myPortal for Outlook as Add On for Microsoft Outlook (UC and CTI) | ||
| + | * myAttendant (Attendant Console) | ||
| + | * myAgent (Contact Center Client, Advanced Mainboard required) | ||
| + | * Unify Phone for OpenScape (cloud based WebRTC Client for mobile/Desktop) | ||
| − | + | === Multichannel Contact Center === | |
| + | The Multichannel Contact Center option is available for OpenScape Business UC Suite with the new V3 Mainboard (Advanced) or OpenScape Business S. | ||
| − | The Contact Center | + | The embedded Contact Center solution offers two clients for use within the contact center environment: |
* myAgent as agent and supervisor desktop application | * myAgent as agent and supervisor desktop application | ||
* myReports as client for report creation | * myReports as client for report creation | ||
| + | |||
| + | The features of the Contact Center are described within the following document: | ||
| + | |||
| + | * {{File-DL|OpenScape Business Contact Center Whitepaper EN|pdf|en}} | ||
| + | * {{File-DL|OpenScape Business Contact Center Whitepaper DE|pdf|de}} | ||
| + | * {{File-DL|OpenScape Business Contact Center Reports|pdf|en}} | ||
| + | |||
| + | The following tutorials contain specific contact center configuration advices: | ||
| + | * {{File-DL|OpenScape Business CC Branch on Data Tutorial|pdf|en}} | ||
| + | |||
| + | |||
| + | |||
| + | '''Note:'''<br> | ||
| + | The information provided in these documents contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. | ||
=== Mobility options for mobile employees === | === Mobility options for mobile employees === | ||
| Line 311: | Line 285: | ||
* Integration of smartphones of mobile workers | * Integration of smartphones of mobile workers | ||
* Support of cordless and WLAN telephones within the office | * Support of cordless and WLAN telephones within the office | ||
| − | * DeskSharing | + | * DeskSharing solution |
* Teleworking solution | * Teleworking solution | ||
OpenScape Business Mobility provides features like: | OpenScape Business Mobility provides features like: | ||
| − | * | + | * Mobile Application for PC/Desktop, mobile/Tablet, Apple Car Play Operation |
* One Number Service regardless of location and used device | * One Number Service regardless of location and used device | ||
| − | * Dual mode telephony ( | + | * Dual mode telephony (4G/5G/WiFi) incl. seamless handover between networks |
| + | * Move Calls "call swipe" from one device to another seamlessly | ||
* Mobile Logon | * Mobile Logon | ||
* CallMe function | * CallMe function | ||
| Line 323: | Line 298: | ||
* etc. | * etc. | ||
| + | === OpenScape Business clients === | ||
| − | |||
| − | + | '''myPortal @work'''<br> | |
| − | + | is the common UC desktop (UC and telephony) client for the UC Smart and UC Suite solution. | |
| − | + | * is available for Microsoft Windows and Apple MAC OS.<br> | |
| − | + | * manages and shows presence status of contacts, set connection control of your office extension, and access to directories, favorites, voicemail and journals. | |
| − | + | * offers an integrated WebRTC based VoIP client as an option.<br> | |
| − | + | Additional information can be found within this Wiki using the following link: <br> | |
| − | + | [[myPortal @work | myPortal @work]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | |||
| − | |||
<br> | <br> | ||
<br> | <br> | ||
| − | '''myPortal | + | '''myPortal for Teams'''<br> |
| − | is | + | is a pure web based CTI Client and offers UC and call control features. It can be used as a stand-alone client or embedded in Microsoft Teams as an plugin to enrich Microsoft Teams with powerful telephony and UC features |
| − | |||
| − | |||
| − | |||
<br> | <br> | ||
<br> | <br> | ||
| Line 379: | Line 317: | ||
presents the full suite of OpenScape Business UC features from a single window <br> | presents the full suite of OpenScape Business UC features from a single window <br> | ||
Additional information can be found within this Wiki using the following links:<br> | Additional information can be found within this Wiki using the following links:<br> | ||
| − | [[myPortal | myPortal for Desktop]] | + | [[myPortal for Desktop | myPortal for Desktop]] |
<br> | <br> | ||
<br> | <br> | ||
| Line 386: | Line 324: | ||
*enables users to access all of their communications - voice, conferencing, voicemail, fax, IM, email, and contacts - directly from within MS Outlook | *enables users to access all of their communications - voice, conferencing, voicemail, fax, IM, email, and contacts - directly from within MS Outlook | ||
*Users can click to dial any number from any Microsoft application <br> | *Users can click to dial any number from any Microsoft application <br> | ||
| + | |||
Additional information can be found within this Wiki using the following link: <br> | Additional information can be found within this Wiki using the following link: <br> | ||
[[myPortal for Outlook |myPortal for Outlook]] | [[myPortal for Outlook |myPortal for Outlook]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<br> | <br> | ||
<br> | <br> | ||
| Line 432: | Line 348: | ||
<br> | <br> | ||
<br> | <br> | ||
| − | + | '''Unify Phone for OpenScape / Unify Phone for Microsoft Teams'''<br> | |
| − | + | is the cloud based WebRTC softphone for desktop and mobile operation connected via a telephony connector (hybrid approach) in a single solution. It offers values from the cloud and is the mobile client for OpenScape Business. Unify Phone for Microsoft Teams offers a deep integration in MS Teams including bidirectional presence synchronisation | |
| − | OpenScape | + | <br> |
| − | + | <br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== General configuration == | == General configuration == | ||
| Line 460: | Line 362: | ||
=== Networked System === | === Networked System === | ||
| − | Networking "OpenScape Business" OpenScape Business offers the opportunity to build networks with up to | + | Networking "OpenScape Business" OpenScape Business offers the opportunity to build networks with up to 2000 participants. Within an OpenScape Business Network a broad range Unfified communcation feature are available for all useres beneath the normal telephony features e.g: |
* Presence management with voice support(visibility of presence status) | * Presence management with voice support(visibility of presence status) | ||
| Line 472: | Line 374: | ||
* Integration in the Microsoft Exchange calendar and in the public directory | * Integration in the Microsoft Exchange calendar and in the public directory | ||
* Forwarding of voicemails in the network | * Forwarding of voicemails in the network | ||
| − | + | ||
An OpenScape Business network is controlled by the so called Master Node, which does not require necessarily additional HW/SW depending on the size of the network. An administrator can access all network subscribers via the Single Point of Administration within the Master Node. When changes are made within the Master Node administration, the databases of the individual network nodes are automatically synchronized. | An OpenScape Business network is controlled by the so called Master Node, which does not require necessarily additional HW/SW depending on the size of the network. An administrator can access all network subscribers via the Single Point of Administration within the Master Node. When changes are made within the Master Node administration, the databases of the individual network nodes are automatically synchronized. | ||
| Line 478: | Line 380: | ||
<br> | <br> | ||
A LAN/WAN based IP network is required as prerequisite for networking. | A LAN/WAN based IP network is required as prerequisite for networking. | ||
| − | OpenScape Business systems can be networked | + | OpenScape Business systems can be networked via IP or via digital trunks. Both S0 as well as S2M lines with QSIG protocol can be used for the connection. |
<br> | <br> | ||
<br> | <br> | ||
| − | Within the following some essentiall networking scenarios are shown. Details, prerequisites and even more scenarios are decribed within the administration manual of OpenScape Business | + | Within the following some essentiall networking scenarios are shown. Details, prerequisites and even more scenarios are decribed within the administration manual of OpenScape Business. |
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
| − | '''Networking Multiple OpenScape Business X3/X5/X8 Systems''' <br> | + | '''Networking Multiple OpenScape Business X1/X3/X5/X8 Systems''' <br> |
Up to 32 OpenScape Business communication systems can be networked with each other. | Up to 32 OpenScape Business communication systems can be networked with each other. | ||
| Line 493: | Line 395: | ||
<br> | <br> | ||
'''Networking OpenScape Business and OpenScape Business S (Single Gateway)''' <br> | '''Networking OpenScape Business and OpenScape Business S (Single Gateway)''' <br> | ||
| − | Up to 32 OpenScape Business X3/X5/X8 | + | Up to 32 OpenScape Business X1/X3/X5/X8 and S communication systems can be networked with one another. Multiple OpenScape Business S systems are allowed in an internetwork. Single Gateway means that all IP stations registered at OpenScape Business S only use ONE gateway to the PSTN. |
[[Image:OSBiz_Net_single_gate.png|450px|OpenScape Business systems with single gateway]] | [[Image:OSBiz_Net_single_gate.png|450px|OpenScape Business systems with single gateway]] | ||
| Line 500: | Line 402: | ||
<br> | <br> | ||
'''Networking OpenScape Business and OpenScape Business S (Multi Gateway)''' <br> | '''Networking OpenScape Business and OpenScape Business S (Multi Gateway)''' <br> | ||
| − | Up to 32 OpenScape Business X3 | + | Up to 32 OpenScape Business X1(W)/X3/X5/X8 and S communication systems can be networked with one another. Multi-gateway means that every IP station registered at OpenScape Business S is assigned to exactly one specific gateway. |
[[Image:OSBiz_Net_multi_gate.png|450px|OpenScape Business systems with multiple gateway]] | [[Image:OSBiz_Net_multi_gate.png|450px|OpenScape Business systems with multiple gateway]] | ||
| + | |||
| + | === Data Center and Private Cloud Deployments === | ||
| + | |||
| + | * {{File-DL|OpenScape Business S in private cloud deployments|pdf}} | ||
| + | * {{File-DL|OSBiz S in Data Center and Cloud Depoyments Technical Overview and Details|pdf}} | ||
| + | * Further Informations can be found in the [http://wiki.unify.com/wiki/How_to_collection_and_tutorials_for_OpenScape_Business How to collection and tutorials for OpenScape Business] | ||
== SIP / ITSP Connectivity == | == SIP / ITSP Connectivity == | ||
| − | Information about connection of SIP devices | + | |
| + | === Configuration of LAN/WAN interface for VoIP === | ||
| + | * {{File-DL|OpenScapeBusiness_How_To_Configure_LAN_WAN_Interface_for_VoIP|pdf|en|Configure LAN/WAN Interface for VoIP}} | ||
| + | |||
| + | === SIP Devices === | ||
| + | |||
| + | Information about connection of and SIP devices can be found within the following link | ||
* [[Features and Configuration of SIP Devices]] | * [[Features and Configuration of SIP Devices]] | ||
| + | |||
| + | === SIP Trunks and certified ITSP === | ||
| + | |||
| + | Information about connection of SIP trunks and certified VoIP service providers can be found within the following link | ||
| + | |||
* [[Collaboration with VoIP Providers]] | * [[Collaboration with VoIP Providers]] | ||
| − | |||
| − | |||
| − | + | === Integrated Session Border Controller === | |
| − | * {{File-DL| | + | |
| − | * {{File-DL|OSBiz SIP Attack Protection|pdf}} | + | * {{File-DL|OSBiz_Integrated_SBC|pdf|en}} |
| + | |||
| + | === Miscellaneous SIP related topics === | ||
| + | |||
| + | * {{File-DL|OSBiz SIP Attack Protection|pdf|en}} | ||
| + | |||
| + | === Diagnostics and Configuration Hints === | ||
* [[Network Configuration for VoIP Providers]] | * [[Network Configuration for VoIP Providers]] | ||
| − | |||
== Integration in business application and processes == | == Integration in business application and processes == | ||
| − | + | OpenScape Business supports many interfaces, protocols and standards for integration into business process or connection to 3rd party applications. Details are listed in the the datasheet or feature description. Within the following section only the most relevant interfaces and integrations are described. Nearly all connections, except TDM telephony, uses the Ethernet LAN interface of OpenScape Business. | |
| + | |||
| + | {{Info| | ||
| + | Please note, latest supported operating systems, virtualization platforms and applications can always be found in the official Sales Information provided by Unify and it´s authorized resellers. | ||
| + | }} | ||
| + | |||
| + | |||
| − | === Citrix support === | + | === Windows Terminal Server and Citrix support === |
| − | The following document describes how to operate OpenScape Business client within Citrix XenApp environment | + | The following document describes how to operate OpenScape Business client within Windows Remote Desktop Services and Citrix XenApp environment |
* {{File-DL|OSBiz_V1_CitrixXENApp_6.5_Win2008R2|pdf}} | * {{File-DL|OSBiz_V1_CitrixXENApp_6.5_Win2008R2|pdf}} | ||
| Line 528: | Line 456: | ||
<!-- | <!-- | ||
=== Microsoft Windows Terminal Server support === | === Microsoft Windows Terminal Server support === | ||
| − | The following document describes how to operate OpenScape Business | + | The following document describes how to operate OpenScape Business clients within Microsoft Windoe Terminal Server environment |
* {{File-DL|OSBiz_V1_CitrixXENApp_6.5_Win2008R2|pdf}} | * {{File-DL|OSBiz_V1_CitrixXENApp_6.5_Win2008R2|pdf}} | ||
| Line 550: | Line 478: | ||
The following documents describe how to connect OpenScape Business to “Microsoft Exchange" | The following documents describe how to connect OpenScape Business to “Microsoft Exchange" | ||
| − | * {{en}} {{File-DL| | + | * {{en}} {{File-DL|OSBizV2_MSExchange_2016|pdf}} |
| − | * {{en}} {{File-DL| | + | * {{en}} {{File-DL|OpenScape_Business_OAuth2_HowTo|pdf|en|configuration of OAuth 2.0}} |
| − | + | ||
| + | Further information can also be found in the OpenScape Business Administration Manual within the Mitel/Unify Partner Portal | ||
=== Microsoft Office 365 === | === Microsoft Office 365 === | ||
| Line 568: | Line 497: | ||
* [[OpenScape Office Interaction with 3rd Party Applications]] | * [[OpenScape Office Interaction with 3rd Party Applications]] | ||
--><br> | --><br> | ||
| + | Please check the current required Microsoft licenses before the installation. | ||
=== Access to external directories and data sources === | === Access to external directories and data sources === | ||
| Line 574: | Line 504: | ||
* Open Directory Service | * Open Directory Service | ||
* LDAP | * LDAP | ||
| − | * CSV | + | * Data replication via CSV file import |
| − | |||
<br> | <br> | ||
'''Open Directory Service''' <br> | '''Open Directory Service''' <br> | ||
is fully embedded within OpenScape business. It allows access to internal User Data, Speed Dials and the UC-Suite Directory as well as to following external SQL database servers:<br> | is fully embedded within OpenScape business. It allows access to internal User Data, Speed Dials and the UC-Suite Directory as well as to following external SQL database servers:<br> | ||
| − | |||
* Microsoft SQL server, | * Microsoft SQL server, | ||
* Postgres SQL server, | * Postgres SQL server, | ||
* Sybase SQL server | * Sybase SQL server | ||
| − | More information is given within the link: | + | More information is given within the link:<br> |
| − | + | * [[How to connect a SQL database to Open Directory Service (ODS)]] | |
| − | [[How to connect a SQL database to Open Directory Service (ODS)]] | + | * {{File-DL|OSBizV2_ODBC_to ODBC_Bridge|pdf|en}} |
| − | + | <br> | |
| − | + | <br> | |
| − | < | ||
| − | |||
'''LDAP - Lightweigt Data Access Protocol''' | '''LDAP - Lightweigt Data Access Protocol''' | ||
| − | allows direct data querey from external LDAP capable directories. | + | allows direct data querey from external LDAP capable directories. <br> |
| − | |||
The administration of the LDAP interface within OpenScape Business is described within the link: | The administration of the LDAP interface within OpenScape Business is described within the link: | ||
| − | * [[How to | + | * [[How to connect OpenScape Business to LDAP Server]] |
| − | + | <br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === Open Interfaces === | |
| + | Information about OpenScape Business and its interfaces for business process integration can be found here | ||
| + | * [[OpenScape Business Interfaces]] | ||
== CTI - Computer Telephony Integration == | == CTI - Computer Telephony Integration == | ||
| Line 611: | Line 534: | ||
The descriptions of the CTI interfaces are provided within the following link: <br> | The descriptions of the CTI interfaces are provided within the following link: <br> | ||
| − | [[OpenScape Business | + | * [[OpenScape Business Interfaces]] |
| − | |||
=== TAPI Service Provider === | === TAPI Service Provider === | ||
| Line 626: | Line 548: | ||
* OpenScape Business TAPI 120 and TAPI 170 are new software components that were developed exclusively for OpenScape Business. The software versioning begins with Version 1. | * OpenScape Business TAPI 120 and TAPI 170 are new software components that were developed exclusively for OpenScape Business. The software versioning begins with Version 1. | ||
| + | |||
* The OpenScape Business TAPI 120 or 170 software and the licenses can only be used in conjunction with OpenScape Business. | * The OpenScape Business TAPI 120 or 170 software and the licenses can only be used in conjunction with OpenScape Business. | ||
* The connection to OpenScape Business takes place exclusively via the LAN. | * The connection to OpenScape Business takes place exclusively via the LAN. | ||
| Line 631: | Line 554: | ||
* The licensing is station based and no longer distinguishes between OpenScape Business TAPI 120 or TAPI 170 stations. The licensing requirement begins with the first TAPI station. | * The licensing is station based and no longer distinguishes between OpenScape Business TAPI 120 or TAPI 170 stations. The licensing requirement begins with the first TAPI station. | ||
* Existing HiPath TAPI 120 or 170 user licenses cannot be used in conjunction with OpenScape Business TAPI 120 or 170 | * Existing HiPath TAPI 120 or 170 user licenses cannot be used in conjunction with OpenScape Business TAPI 120 or 170 | ||
| + | |||
| + | |||
| + | == Device@Home == | ||
| + | === System(HFA)Device@Home === | ||
| + | The feature "System Device @ Home" allows the connection of system telephones as OpenStage or OpenScape Deskphone with HFA protocol over the Internet to OpenScape Business and as to operate them e.g. in the home office. | ||
| + | |||
| + | *{{File-DL|How To Configure System Device@Home|pdf|en}} | ||
| + | |||
| + | === SIP Device@Home === | ||
| + | OpenScape Business supports the STUN protocol (Session Traversal Utilities for NAT). This enables the connectivity of STUN capable SIP devices to OpenScape Business via the Internet. | ||
| + | * {{File-DL|OSBiz SIP Endpoint Configuration for SIP@Home|pdf|en}} | ||
| + | |||
| + | == Integration of Vertical Solutions == | ||
| + | |||
| + | === Hotel / Hospitality Solutions === | ||
| + | OpenScape Business can be connected to Hospitality Solutions. Certified solutions are listed within Unify´s "Technology Partner Programm". | ||
| + | |||
| + | == Unify Phone == | ||
| + | |||
| + | Unify Phone is a cloud based telephony connector for OpenScape Business. This section describes the connectivity of Unify Phone to OpenScape Business and how this can be configured. | ||
| + | |||
| + | * {{File-DL|How To connect Unify Phone to OpenScape Business|pdf|en}} | ||
| + | |||
| + | == Circuit == | ||
| + | |||
| + | '''Please note:''' Circuit has reached end of life. As a successor solution we offer a migration path to Unify Video with Unify Phone or Unify Office. Please get in contact with your Unify representative. | ||
| + | |||
| + | == MS Skype for Business Interworking == | ||
| + | |||
| + | This section describes the Telephony Voice Interworking capabilities between OpenScape Business and MS Microsoft Skype for Business an how this can be configured | ||
| + | |||
| + | * {{File-DL|How To Configure OSBiz Skype for Business Interworking|pdf|en}} | ||
| + | * {{File-DL|OpenScape Business - Skype for Business MS Interworking Use Cases and Hints|pdf|en}} | ||
| + | |||
| + | == MS Teams Interworking and Integration == | ||
| + | |||
| + | This section describes the Telephony Voice Interworking and integration capabilities between OpenScape Business and MS Teams (Direct Routing Plan via SBC, myPortal for Teams plugin) based on customer experiences | ||
| + | |||
| + | * {{File-DL|OpenScape Business - MS Teams Interworking|pdf|en}} | ||
| + | * {{File-DL|How To Configure OSBiz MS Teams Interworking|pdf|en}} | ||
== Capacities == | == Capacities == | ||
| Line 636: | Line 599: | ||
{| {{DefaultTable}} | {| {{DefaultTable}} | ||
|- | |- | ||
| − | ! | + | ! |
| + | ! OpenScape Business X1R/W | ||
! OpenScape Business X3 | ! OpenScape Business X3 | ||
! OpenScape Business X5 | ! OpenScape Business X5 | ||
| Line 643: | Line 607: | ||
|- | |- | ||
|'''BRI Trunks''' | |'''BRI Trunks''' | ||
| + | | 0 | ||
| 20 | | 20 | ||
| 52 | | 52 | ||
| Line 651: | Line 616: | ||
| 0 | | 0 | ||
| 30 | | 30 | ||
| − | | | + | | 30 |
| + | | 180 | ||
| N/A | | N/A | ||
|- | |- | ||
| Line 658: | Line 624: | ||
| 60 | | 60 | ||
| 60 | | 60 | ||
| − | | | + | | 60 |
| + | | 180 | ||
|- | |- | ||
<!-- | <!-- | ||
|'''Max.# of Trunks''' | |'''Max.# of Trunks''' | ||
| + | | 250 | ||
| 250 | | 250 | ||
| 250 | | 250 | ||
| Line 669: | Line 637: | ||
|- | |- | ||
|'''Analog Stations''' | |'''Analog Stations''' | ||
| − | | 20 Rack system<br> | + | | 4 |
| + | | 20 Rack system<br>20 Wall system | ||
| 56 Rack system<br>68 Wall system | | 56 Rack system<br>68 Wall system | ||
| 384 | | 384 | ||
| Line 675: | Line 644: | ||
|- | |- | ||
|'''Digital Phones''' | |'''Digital Phones''' | ||
| + | | 8 | ||
| 24 | | 24 | ||
| 56 | | 56 | ||
| Line 685: | Line 655: | ||
| 500 | | 500 | ||
| 500 | | 500 | ||
| + | | 1500 | ||
|- | |- | ||
|'''Cordless/DECT Phones''' | |'''Cordless/DECT Phones''' | ||
| + | | 16 | ||
| 32 | | 32 | ||
| 32 Rack system<br>64 Wall system | | 32 Rack system<br>64 Wall system | ||
| Line 697: | Line 669: | ||
| 500 | | 500 | ||
| 500 | | 500 | ||
| + | | 1500 | ||
|- | |- | ||
|} | |} | ||
Remarks: Figures are subject to change. For actual figures refer to the latest version of OpenScape Business Sales Information and Datasheet. | Remarks: Figures are subject to change. For actual figures refer to the latest version of OpenScape Business Sales Information and Datasheet. | ||
| − | |||
== Administration == | == Administration == | ||
| Line 754: | Line 726: | ||
| ||Fax Printer, User Guide||This document describes the installation, configuration and operation of Fax Printer ||e-Docu||System, {{Partner Portal}} | | ||Fax Printer, User Guide||This document describes the installation, configuration and operation of Fax Printer ||e-Docu||System, {{Partner Portal}} | ||
|- | |- | ||
| − | | ||myPortal | + | | ||myPortal to go, User Guide||This document describes the configuration and operation of myPortal for Mobile||e-Docu||System, {{Partner Portal}} |
|- | |- | ||
| ||myAgent, User Guide||This document describes the installation, configuration and operation of the myAgent application||e-Docu||System, {{Partner Portal}} | | ||myAgent, User Guide||This document describes the installation, configuration and operation of the myAgent application||e-Docu||System, {{Partner Portal}} | ||
| Line 796: | Line 768: | ||
The required operating system (Suse Linux Enterprise system (SLES)) can be obtained also from Unify. <br> | The required operating system (Suse Linux Enterprise system (SLES)) can be obtained also from Unify. <br> | ||
In case, that the SLES SW is ordered from Unify, an registration key for a 3 year SW update period, granted by Novell, is included. | In case, that the SLES SW is ordered from Unify, an registration key for a 3 year SW update period, granted by Novell, is included. | ||
| + | |||
| + | OpenScape Business S SW (incl. SLES) is also available as .OVA Image for virtualized machines via the software Supply Server. | ||
== Licensing == | == Licensing == | ||
| Line 815: | Line 789: | ||
Details are described within the OpenScape Business Sales Information and the Administration Manual | Details are described within the OpenScape Business Sales Information and the Administration Manual | ||
| + | |||
| + | == Security == | ||
| + | === Security Checklist === | ||
| + | Instructions for hardening of OpenScape Business are described within the <br> | ||
| + | OpenScapeBusiness Security Checklist <br> | ||
| + | which can be downloaded from the {{Partner Portal}}. | ||
| + | |||
| + | === Security Bulletins === | ||
| + | The following documents contain descriptions of security improvements. | ||
| + | <br> | ||
| + | <br> | ||
| + | <!-- | ||
| + | * {{File-DL|OSBiz V2R2 SQL database password change|pdf|en}} | ||
| + | --> | ||
| + | |||
| + | * {{File-DL|OSBiz V2R2 Measures against toll fraud|pdf|en}} | ||
| + | |||
| + | <br> | ||
| + | |||
| + | == Discontinued Applications == | ||
| + | |||
| + | Up from OpenScape Business V3 the following applications will be discontinued and be replaced by successor solutions. More informations can be found in the current OpenScape Business Sales Information within our UNIFY Partner Portal | ||
| + | |||
| + | * [[myPortal Smart]] replaced by [[myPortal @work]] | ||
| + | * [[myPortal for OpenStage]] replaced by UC Integration for [[OpenScape Desk Phone CP]] 400 and 600/E | ||
| + | * [[OpenStage Gate View]] replaced by Video Streaming for [[OpenScape Desk Phone CP]] 600/E and 700/X | ||
| + | * Xpressions Compact replaced by integrated or UC Voicemail application | ||
| + | * OpenScape Business integrated VPN solution | ||
| + | * XMPP Protocol | ||
| + | * PPP over ISDN on new V3 hardware | ||
== Further Technical Information / Links == | == Further Technical Information / Links == | ||
| Line 828: | Line 832: | ||
'''IP/Routing''' <br> | '''IP/Routing''' <br> | ||
* RFC 768 UDP | * RFC 768 UDP | ||
| − | * RFC 791 IP | + | * RFC 791 IP (updated by: RFC 1349, RFC 2474, RFC 6864) |
| − | * RFC 792 ICMP | + | * RFC 792 ICMP (updated by: RFC 950, RFC 4884, RFC 6633, RFC 6918) |
| − | * RFC 793 TCP | + | * RFC 793 TCP (updated by: RFC 1122, RFC 3168, RFC 6093, RFC 6528) |
| − | * RFC | + | * RFC 826 ARP (updated by: RFC 5227, RFC 5494) |
| − | * RFC | + | * RFC 1332 The PPP Internet Protocol (updated by: RFC 3241) |
| − | * RFC 2131 DHCP | + | * RFC 1918 IP Addressing (updated by: RFC 6761) |
| − | * RFC | + | * RFC 2131 DHCP (updated by: RFC 3396, RFC 4361, RFC 5494, RFC 6842) |
| − | * RFC | + | * RFC 2822 Internet Message Format (obsoleted by RFC 5322) |
| + | * RFC 5322 Internet Message Format (updated by: RFC 6531, RFC 6532, RFC 6854) | ||
'''Control Protocol (IPCP)''' <br> | '''Control Protocol (IPCP)''' <br> | ||
| − | * RFC 1334 PPP Authentication Protocols | + | * RFC 1334 PPP Authentication Protocols (obsoleted by: RFC 1994) |
* RFC 1618 PPP over ISDN | * RFC 1618 PPP over ISDN | ||
| − | * RFC 1661 The Point-to-Point Protocol (PPP) | + | * RFC 1661 The Point-to-Point Protocol (PPP) (updated by: RFC 2153) |
* RFC 1877 PPP Internet Protocol Control Protocol | * RFC 1877 PPP Internet Protocol Control Protocol | ||
* RFC 1990 The PPP Multilink Protocol (MP) | * RFC 1990 The PPP Multilink Protocol (MP) | ||
| − | * RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP) | + | * RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP) (updated by: RFC 2484) |
* RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE) | * RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE) | ||
* RFC 3544 IP Header Compression over PPP | * RFC 3544 IP Header Compression over PPP | ||
| Line 870: | Line 875: | ||
'''QoS''' | '''QoS''' | ||
* IEEE 802.1p Priority Tagging | * IEEE 802.1p Priority Tagging | ||
| − | * RFC 1349 Type of Service in the IP Suite | + | * RFC 1349 Type of Service in the IP Suite (obsoleted by: RFC 2474) |
| − | * RFC 2475 An Architecture for Differentiated Services | + | * RFC 2474 Type of Service in the IP Suite (updated by: RFC 3168, RFC 3260) |
| − | * RFC 2597 Assured Forwarding PHB Group | + | * RFC 2475 An Architecture for Differentiated Services (updated by: RFC 3260) |
| − | * RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior) Services | + | * RFC 2597 Assured Forwarding PHB Group (updated by: RFC 3260) |
| + | * RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior) | ||
| + | |||
| + | '''Services''' | ||
* RFC 2597 Assured Forwarding PHB Group | * RFC 2597 Assured Forwarding PHB Group | ||
* RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior) | * RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior) | ||
| Line 885: | Line 893: | ||
* TAPI Service Provider for TAPI 2.1 | * TAPI Service Provider for TAPI 2.1 | ||
| − | ''' | + | '''SIP'''<br> |
| − | * RFC 2198 RTP Payload for Redundant Audio Data | + | The table below indicates which RFCs are implemented on the SIP interfaces of the system: |
| − | + | * ITSP: Internet Telephony Service Provider interface | |
| − | + | * SIP SUB: SIP interface for connection of SIP- phones | |
| − | + | * SIP TRK: SIP interface for connection to external SIP servers | |
| − | + | * SIP-Q: SIP interface for connection of OpenScape Business systems | |
| − | + | ||
| − | + | Within the SIP interface columns following information are given: | |
| − | + | * yes: The main content of the RFC is implemented in the system. There might be options in the RFC which are not implemented. No details are given in the list | |
| − | + | * no RFC is NOT implemented on that interface | |
| − | + | * n/a RFC is not applicable to that interface | |
| − | + | ||
| − | + | The information applies to OpenScape Business Version V2R3 | |
| − | + | ||
| − | + | {| {{DefaultTable}} | |
| − | + | | align="center" style="background:#f0f0f0;"|'''RFC number''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''Title''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''Remarks''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''ITSP''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''SIP-SUB''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''SIP-TRK''' | |
| − | + | | align="center" style="background:#f0f0f0;"|'''SIPQ''' | |
| − | + | |- | |
| − | + | | RFC 1889||RTP: A Transport Protocol for Real-Time Applications ||Obsoleted by RFC3550 ||yes||yes||yes||yes | |
| + | |- | ||
| + | | RFC 2198||RTP Payload for Redundant Audio Data||Used in conjunction with RFC 2833||no||no||no||no | ||
| + | |- | ||
| + | | RFC 2246||The TLS Protocol Version 1.0 ||Obsoleted by RFC4346, Updated by RFC3546 ||no||no||no||no | ||
| + | |- | ||
| + | | RFC 2327||SDP: Session Description Protocol (obsoleted by RFC4566)||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 2396||Uniform Resource Identifiers (URI): Generic Syntax ||Obsoleted by RFC3986||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 2560||X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 2617||HTTP Authentication: Basic and Digest Access Authentication||||yes||yes||no||no | ||
| + | |- | ||
| + | | RFC 2782||DNS RR for specifying the location of services (DNS SRV)||||yes||n/a||yes||yes | ||
| + | |- | ||
| + | | RFC 2833||RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals||Obsoleted by 4733 ||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 2976||The SIP INFO Method||Used for SIPQ trunking only||no||no||no||yes | ||
| + | |- | ||
| + | | RFC 3204||MIME media types for ISUP and QSIG Objects||QSIG only||no||no||no||yes | ||
| + | |- | ||
| + | | RFC 3261||SIP: Session Initiation Protocol||SIP Core RFC||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3262||Reliability of Provisional Responses in the Session Initiation Protocol (SIP)||provisional Response Acknowledgement (PRACK) Early Media||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3263||SIP Locating Servers||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3264||An Offer/Answer Model with SDP||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3265||Session Initiation Protocol (SIP)-Specific Event Notification||used for MWI and GroupPickup||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3268||Advanced Encryption Standard (AES) Cipher suites for Transport Layer Security (TLS)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3280||Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3310||HTTP Digest Authentication||||yes||yes||no||no | ||
| + | |- | ||
| + | | RFC 3311||Session Initiation Protocol (SIP) UPDATE Method||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3312||Integration of Resource Management and Session Initiation Protocol (SIP)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3323||A Privacy Mechanism for the Session Initiation Protocol (SIP)||||yes||yes||no||no | ||
| + | |- | ||
| + | | RFC 3324||Short Term Requirements for Network Asserted Identity ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3325||Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks||||yes||yes||yes||no | ||
| + | |- | ||
| + | | RFC 3326||The Reason Header Field for the Session Initiation Protocol (SIP)||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3327||Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3329||Security Mechanism Agreement for the Session Initiation Protocol ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3389||Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3420||Internet Media Type message/sipfrag||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3428||Session Initiation Protocol (SIP) Extension for Instant Messaging||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3489||STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)||||yes||yes||no||no | ||
| + | |- | ||
| + | | RFC 3515||The Session Initiation Protocol (SIP) Refer Method||||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3550||RTP: Transport Protocol for Real-Time Applications||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3551||RTP Profile for Audio and Video Conferences with Minimal Control||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 3581||An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing||rport||yes||yes||yes||no | ||
| + | |- | ||
| + | | RFC 3605||Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3665||Session Initiation Protocol (SIP) Basic Call Flow Examples ||||yes||yes||yes||N/A | ||
| + | |- | ||
| + | | RFC 3666||Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows ||||yes||yes||yes||N/A | ||
| + | |- | ||
| + | | RFC 3680||A Session Initiation Protocol (SIP) Event Package for Registrations ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3711||The Secure Real-time Transport Protocol (SRTP)||||yes||no||no||yes | ||
| + | |- | ||
| + | | RFC 3725||Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) ||||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3761||The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3830||MIKEY: Multimedia Internet KEYing||MIKEY0 only||no||no||no||yes | ||
| + | |- | ||
| + | | RFC 3842||A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)||||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3891||The Session Initiation Protocol (SIP) Replaces Header||passive usage only||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3892||The Session Initiation Protocol (SIP) Referred-By Mechanism ||||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 3959||The Early Session Disposition Type for the Session Initiation Protocol (SIP) ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3960||Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 3966||The tel URI for Telephone Numbers ||||yes||no||no||no | ||
| + | |- | ||
| + | | RFC 3968||The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) ||As this RFC describes rules for assigning new parameters etc. it is not applicable for a certain product||N/A||N/A||N/A||N/A | ||
| + | |- | ||
| + | | RFC 3969||The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) ||As this RFC describes rules for assigning new parameters etc. it is not applicable for a certain product||N/A||N/A||N/A||N/A | ||
| + | |- | ||
| + | | RFC 4040||RTP Payload Format for a 64 kbit/s Transparent Call||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 4028||Session Timers in the Session Initiation Protocol (SIP)||||yes||yes||no||yes | ||
| + | |- | ||
| + | | RFC 4119||A Presence-based GEOPRIV Location Object Format||XML based location definition for emegancy calls||yes||no||no||no | ||
| + | |- | ||
| + | | RFC 4123||Session Initiation Protocol (SIP)-H.323 Interworking Requirements ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 4235||An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol||Used for GroupPickup||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 4244||An Extension to the Session Initiation Protocol (SIP) for Request History Information||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 4320||Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 4504||SIP Telephony Device Requirements and Configuration ||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 4538||Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 4566||SDP: Session Description Protocol; M. Handley, V. Jacobson.(obsoletes RFC 2327)||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 4568||Session Description Protocol (SDP) Security Descriptions for Media Streams ||||yes||no||no||no | ||
| + | |- | ||
| + | | RFC 4733||RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 4856||Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences||Obsoletes RFC3555||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 4967||Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 5009||Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media||P-Early-Media header||yes||no||no||no | ||
| + | |- | ||
| + | | RFC 5031||A Uniform Resource Name (URN) for Emergency and Other Well-Known Services||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 5139||Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)||XML based location definition for emegancy calls||yes||no||no||no | ||
| + | |- | ||
| + | | RFC 5245||Interactive Connectivity Establishment (ICE):A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 5246||The Transport Layer Security (TLS) Protocol Version 1.2||||yes||yes||yes||yes | ||
| + | |- | ||
| + | | RFC 5280||Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 5589||Session Initiation Protocol Call Control – Transfer||||no||yes||no||no | ||
| + | |- | ||
| + | | RFC 5806||Diversion Indication in SIP||Diversion header field||yes||yes||no||no | ||
| + | |- | ||
| + | | RFC 5876||Updates to Asserted Identity in the Session Initiation Protocol (SIP)||||no||no||no||no | ||
| + | |- | ||
| + | | RFC 5923||Connection Reuse in the Session Initiation Protocol||||no||no||no||yes | ||
| + | |- | ||
| + | | RFC 6140||Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)||SIP connect registration||yes||no||no||no | ||
| + | |- | ||
| + | | | ||
| + | |} | ||
'''VoIP Security''' | '''VoIP Security''' | ||
| − | |||
* RFC 2459 X.509 PKI Certificate and CRL Profile | * RFC 2459 X.509 PKI Certificate and CRL Profile | ||
| − | + | ||
| − | + | ||
'''XMPP''' | '''XMPP''' | ||
| Line 924: | Line 1,084: | ||
* RFC 1305 NTPv3 | * RFC 1305 NTPv3 | ||
* RFC 1951 DEFLATE | * RFC 1951 DEFLATE | ||
| − | |||
| − | |||
| − | |||
=== Supported Server based Hardware === | === Supported Server based Hardware === | ||
| Line 932: | Line 1,089: | ||
Unify does not provide any Server based Hardware platform for deploying OpenScape Business S Server and/or OpenScape Business UC Booster Server applications. | Unify does not provide any Server based Hardware platform for deploying OpenScape Business S Server and/or OpenScape Business UC Booster Server applications. | ||
| − | All necessary Server based Hardware (especially in a customer scenario without any suitable Virtualization environment) must be purchased and installed separately according to the Operating System's requirements and restrictions which is requested to deploy OpenScape Business S Server and/or OpenScape Business UC Booster Server applications (actually this Operating System is SuSE Linux Enterprise Server | + | All necessary Server based Hardware (especially in a customer scenario without any suitable Virtualization environment) must be purchased and installed separately according to the Operating System's requirements and restrictions which is requested to deploy OpenScape Business S Server and/or OpenScape Business UC Booster Server applications (actually this Operating System is SuSE Linux Enterprise Server 12 SP5 64 bit up from OpenScape Business V3). |
| − | |||
| − | |||
| − | |||
=== How To Collection === | === How To Collection === | ||
| Line 953: | Line 1,107: | ||
With the technical newsletter you get essential service related information for our products, such as information about technical functionalities, configuration hints and service related issues. | With the technical newsletter you get essential service related information for our products, such as information about technical functionalities, configuration hints and service related issues. | ||
| − | + | To register, please use the registration form in Unify Partner Portal, which can be found there in “Learn / News & Newsletters / Technical Newsletter”. | |
| + | * {{Partner Portal}} (login required). | ||
=== Marketing Information === | === Marketing Information === | ||
| Line 965: | Line 1,120: | ||
[[osbiz/schema/csta]] | [[osbiz/schema/csta]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
== End User License Agreement (EULA) == | == End User License Agreement (EULA) == | ||
[[OpenScape Business EULA]] | [[OpenScape Business EULA]] | ||
Latest revision as of 09:41, 30 September 2024
|
You are here: |
 Home Unified Communications OpenScape Business
|
Unify OpenScape Business is based on future-proof technologies and offers small to medium-sized enterprises everything they need for their individual and diverse communication requirements, unified in a single flexible, scalable and secure solution with various deployment (on-premise, hosted, private cloud based or combined) and purchase models (CAPEX and OPEX). The Unify OpenScape Business architecture allows use independently of the existing telephony infrastructure – regardless of whether this is classic telephony, IP or DECT. Unify OpenScape Business always provides enterprises with up to 500 subscribers, or 2000 subscribers in one network, with the right solution
From extended telephony to a feature-rich set Unified Communication (UC) solution, Unify OpenScape Business is easily scalable and can be enhanced with the cloud-based UC Softphone solution Unify Phone as business grows and the telephony and communications needs change.
Unify Phone provides unprecedented flexibility for organizations of all sizes by enabling them to benefit from the advantages of cloud collaboration while allowing them to leverage their on-premise investments for best in class hybrid-working experiences. Unify Phone is the perfect solution, not only for mobile employees.
OpenScape Business offers the following highlights:
- Best in Class and Award winning Voice & UC Solution for SMB
- Scalable from 2-2000 Users for Standalone and Multisite environments
- All-In-One Solution incl. feature rich Voice, Presence, Conferencing, Contact Center, Messaging, IM, Mobility, Fax
- Support of any given end-customer infrastructure (on-premise, hybrid, private cloud) incl.comprehensive virtualization-options for Voice & UC
- Easy-to-order & pre-packaged, easy-to-install
- Software Upgrades and Service included for 1,3 or 5 years
- Ready for new All-IP / ITSP based Services (SIP Provider)
- Unify Phone for OpenScape Business providing powerful telephony services (connector) either as a stand alone client or embedded in Microsoft Teams
Contents
- 1 Overview
- 2 New Features
- 3 OpenScape Business Deployment Options
- 4 Features
- 5 General configuration
- 6 SIP / ITSP Connectivity
- 7 Integration in business application and processes
- 8 CTI - Computer Telephony Integration
- 9 Device@Home
- 10 Integration of Vertical Solutions
- 11 Unify Phone
- 12 Circuit
- 13 MS Skype for Business Interworking
- 14 MS Teams Interworking and Integration
- 15 Capacities
- 16 Administration
- 17 Documentation
- 18 Software Delivery / Deployment
- 19 Licensing
- 20 Migration
- 21 Security
- 22 Discontinued Applications
- 23 Further Technical Information / Links
- 24 Useful Tools
- 25 Other Information Sources
- 26 End User License Agreement (EULA)
Overview
OpenScape Business offers small and medium-sized enterprises everything they need for their individual and diverse communication requirements, unified in a single flexible and scalable solution. The OpenScape Business architecture allows use independently of the existing telephony infrastructure regardless of whether this is classic telephony, IP or DECT. From powerful telephony to a feature-rich set Unified Communication (UC) solution, OpenScape Business always provides with the right solution. With Unify Phone as a cloud based solution secure connected to OpenScape Business, even powerful telephony for office workers, mobile employees or remote worker can be offered.
As standalone system up to 1500 subscribers and in networked systems up to 2000 subscribers can be connected.
New Features
Since market introduction the feature set of OpenScape Businsse has been continuously enhanced and improved.
The following link contains an overview about the SW versions and the enhancements.
OpenScape Business Feature Enhancements
OpenScape Business Deployment Options
Different models are available for the use of telephony and UC functionality.
- OpenScape Business X1R
- For rack and wall-mounting
- Up to 50 UC User
- Up to 500 extensions (number of IP, analog and digital subscribers)
- Max. 8 digital (UP0/E) , max. 4 analog (FXS)
- Max. 7 DECT Base Stations, up to 16 DECT Handsets"
- OpenScape Business X3R
- For rack and wall-mounting
- Up to 500 UC User
- Up to 500 extensions (number of IP, analog and digital subscribers)
- Max. 20 digital (UP0/E) , max. 24 analog (FXS)
- Max. 15 DECT Base Stations, up to 64 DECT Handsets"
- OpenScape Business X5R
- For rack and wall-mounting
- Up to 500 UC User
- Up to 500 extensions (number of IP, analog and digital subscribers)
- Max. 56 digital (UP0/E) , max. 68 analog (FXS)
- Max. 15 DECT Base Stations, up to 64 DECT Handsets"
- OpenScape Business X8
- Installation as a standalone unit or mounted in a 19-inch rack
- Modular system with base box and expansion box
- Up to 500 UC User
- Up to 500 extensions (number of IP, analog and digital subscribers)
- Max. of 384 TDM User (number of digital, analog, DECT subscribers)
- Max. 64 DECT Base Stations, up to 250 DECT Handsets
- OpenScape Business S
- Pure software solution, server based, as a virtual appliance or hosted as a private cloud solution in a datacenter for up to 1500 IP / UC User"
Hardware Platforms
OpenScape Business X1R, X3R, X5R or X8 are "All-In-One" HW platforms with onboard IP access and support for up to 500 subscribers with IP, digital (UP0E), analog (a/b), cordless (DECT) devices. With the new OpenScape Business X1R, X3,X5 and X8 V3 Mainboard full UC capabilities and applications are embedded. Connection to public WAN is done via SIP/ITSP (LAN), ISDN (BRI and PRI) or analog trunks. For X1R one mainboard deployment (basic, no BRI) is available, X3 and X5 two V3 Mainboard deployments (basic and advanced) are available, while for OpenScape Business X8 the advanced Mainboard can be used.
An Advanced mainboard is needed in case the system has more than 50 UC users and/or Contact Center and/or connection to external DB’s and/or higher trunk/feature capacities.
- Basic Mainboard capacities
- Up to 50 UC / Unify Phone User
- Up to 60 SIP trunk channels
- Advanced Mainboard capacities
- Up to 500 UC / Unify Phone User
- Up to 120 SIP trunk channels
- Multimedia Contact Center
- Connectivity to external databases
- Enhanced feature capacity limits, e.g. group call members"
Software Platforms
OpenScape Business S is the server-based "All-In-One" telefony and UC platform, which supports up to 1500 IP subscribers and IP (SIP) connection to the public network (WAN). It is designed for Linux (Novell SLES) operating system and can be operated either on a physical or on virtual machines with VMware vSphere, Microsoft Hypervisor, KVM (project-specific) or Google Cloud. OpenScape Business S can be networked with OpenScape Business X1R, X3R, X5R or X8 as gateway for ISDN or analog trunks or TDM / analog devices.
Features
OpenScape Business offers a unified software solution architecture based on modern and innovative communication technologies.
- All-In-One Unified Communication solution for small and medium enterprises
- Integrated powerful voice and telephony services
- Presence management (presence status)
- Status based call forwarding
- Call Journal
- Call Recording
- Favorites list
- Dialing by mouse click / Hotkey Dialing
- Visual voicemail
- Drag and Drop Conference
- Directory access with database connection
- Mobility support
- Fax support
- Integration into business processes
- Instant Messaging (IM)
- etc.
- Multichannel Contact Center
- Integration of OpenScape Web Collaboration (Video Conferencing, Screenshare, File Upload)
- Unify Phone as a WebRTC based cloud telephony service for mobile and desktop
- Interworking with Microsoft Teams (via SBC, Direct Routing)
- Integration in Microsoft Teams (myPortal for Teams plugin, Unify Phone for Microsoft Teams)
- Multiple Sites support
- Unified solution architecture
- Scalable and flexible HW / SW and licensing
- Easy to handle migration from HiPath 3000 to OpenScape Business (System box and almost all existing devices can be reused only the motherboard and the SW has to be replaced)
For detailed feature descriptions have a look into the OpenScape Business datasheet, feature description or Sales Information which is accessible for Mitel/Unify Partners.
Voice features
- Making calls: Setting up a connection, e.g., via speed dialing or directories
- Call Signaling, Calling Line ID: CLIP, CLIR, COLP und COLR.
- Functions during the call: Holding, redirecting and transferring calls
- Controlling availability: Call forwarding and call forwarding - no answer
- Conferencing: Different types of application-controlled and phone-controlled conferences
- Optimizing communication: Handling calls more efficiently and sending texts to internal subscribers
- Easy Operation: Resetting activated features, Direct Inward System Access (DISA) and multilingual text output
- Working in a team (groups): Multiple subscribers and phones can be reached under one station number
- UCD (Uniform Call Distribution): Uniform distribution of incoming calls to a group of subscribers (UCD group).
- Emergency Calls: Hotline/Hotline after timeout or an emergency service
- etc.
Supported phones and devices
- OpenScape Desk Phone CP (IP/HFA, SIP)
- OpenScape Desk Phone CP 100, 200/205, 400, 600/E, 700
- OpenScape Desk Phone CP 100, 200/205, 400, 600/E, 700
- OpenScape Desk Phone CP Key Modules
- OpenScape Desk Phone CP KM400, KM600
- OpenScape Desk Phone CP KM400, KM600
- OpenScape Desk Phone CP G2(IP/HFA, SIP)
- OpenScape Desk Phone CP G2 110,210,410, 710
- OpenScape Desk Phone CP G2 110,210,410, 710
- OpenScape Desk Phone CP G2 Key Modules
- OpenScape Desk Phone CP G2 KM410, KM710
- OpenScape Desk Phone CP G2 KM410, KM710
- OpenScape Desk Phone CP accessories
- OpenScape Desk Phone CP G2 WiFi Stick CP10 for CP210, CP410, CP710
- Mitel Phone Family
- Mitel Phone Series 6800/6900 (connected via SIP)
- Mitel SIP DECT Solution (connected via SIP)
- Cordless CMI/DECT - IP/DECT telephones
- PC / mobile Clients
- Unify Phone for OpenScape as a cloud based WebRTC softphone for mobile/desktop operation (hybrid approach via telephony connector to OpenScape Business.
- OpenScape Personal Edition (including Video support for SIP)
- SIP phones (UC Suite) / AP adapter
- SIP phones with RFC 3725 support.
- Mediatrix 4102S (for connecting 2 Analog phones or G.3 FAX devices)
- SIP phones with RFC 3725 support.
More information about supported features of SIP phones and their configurations are available could be found by reading Features and Configuration of SIP Devices page.
- WLAN phones
- Analog and ISDN phones
- Analog (a/b) phones
- Digital (S0) ISDN phones
- Analog (a/b) phones
Please note:
Devices, which are no longer part of the current product portfolio of Unify, (such as optiPoint 410/420/500; Gigaset Handsets: SL3/S4/M2; OpenStage 5/10/20/30/60/80) can still be connected and operated with OpenScape Business. In case of technical problem no support is given by Unify if the milestone "End od Support" has been reached. For further details such as the required software versions for each device, refer to the respective technical release notes.
Optiset E devices cannot be operated in general.
Unified Communications
OpenScape Business provides two alternativ flavours of Unified Communications, depending on the needs:
UC Smart
UC Smart SW is fully embedded within the OpenScape Business SW running on the V3 Mainboard of OpenScape Business X1/X3/X5/X8 or OpenScape Business S. It comprises the following Unified Communications and Collaborations features.
- Presence incl. status based announcements
- Conference planned/adhoc
- Favorites List incl. Call Status
- Directories
- Call Journals incl. Reminder
- Status based Call Forwarding
- Call Control (CTI) incl. dialing by hotkey
- Visual VoiceMail Control
- Instant Messaging (Chat)
- Web Collaboration
The UC Smart solution offers two clients:
- myPortal @work (WebRTC based UC and telephony)
- Unify Phone for OpenScape (cloud based WebRTC Client for mobile/Desktop)
UC Suite
UC Suite SW is fully embedded within the OpenScape Business SW running on the V3 Mainboard of OpenScape Business X1/X3/X5/X8 or OpenScape Business S .
It comprises the following extensive Unified Communications and Collaborations features.<br
- Presence incl. status based announcements
- Conference planned/adhoc
- Favorites List incl. Call Status
- Directories, opt. with ext. database connection
- Call Journals incl. reminder
- Status based Call Forwarding
- CallMe!
- Personal Auto Attendant
- Call Control (CTI) incl. dialing by mouse click or hotkey
- Voice Message Box
- Fax Message Box
- Notifications
- Instant Messaging (Chat)
- Voice Recording
- Multichannel Contact Center
- Web Collaboration
The UC Suite solution offers several Unified Communications clients:
- myPortal @work (WebRTC based UC and telephony soft client)
- myPortal for Desktop (UC and CTI)
- myPortal for Outlook as Add On for Microsoft Outlook (UC and CTI)
- myAttendant (Attendant Console)
- myAgent (Contact Center Client, Advanced Mainboard required)
- Unify Phone for OpenScape (cloud based WebRTC Client for mobile/Desktop)
Multichannel Contact Center
The Multichannel Contact Center option is available for OpenScape Business UC Suite with the new V3 Mainboard (Advanced) or OpenScape Business S.
The embedded Contact Center solution offers two clients for use within the contact center environment:
- myAgent as agent and supervisor desktop application
- myReports as client for report creation
The features of the Contact Center are described within the following document:
-
OpenScape Business Contact Center Whitepaper EN -
OpenScape Business Contact Center Whitepaper DE - OpenScape Business Contact Center Reports
The following tutorials contain specific contact center configuration advices:
Note:
The information provided in these documents contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products.
Mobility options for mobile employees
OpenScape Business offers embedded mobility services and solutions for any enterprise. These comprise:
- Integration of smartphones of mobile workers
- Support of cordless and WLAN telephones within the office
- DeskSharing solution
- Teleworking solution
OpenScape Business Mobility provides features like:
- Mobile Application for PC/Desktop, mobile/Tablet, Apple Car Play Operation
- One Number Service regardless of location and used device
- Dual mode telephony (4G/5G/WiFi) incl. seamless handover between networks
- Move Calls "call swipe" from one device to another seamlessly
- Mobile Logon
- CallMe function
- VPN support
- etc.
OpenScape Business clients
myPortal @work
is the common UC desktop (UC and telephony) client for the UC Smart and UC Suite solution.
- is available for Microsoft Windows and Apple MAC OS.
- manages and shows presence status of contacts, set connection control of your office extension, and access to directories, favorites, voicemail and journals.
- offers an integrated WebRTC based VoIP client as an option.
Additional information can be found within this Wiki using the following link:
myPortal @work
myPortal for Teams
is a pure web based CTI Client and offers UC and call control features. It can be used as a stand-alone client or embedded in Microsoft Teams as an plugin to enrich Microsoft Teams with powerful telephony and UC features
myPortal for Desktop
presents the full suite of OpenScape Business UC features from a single window
Additional information can be found within this Wiki using the following links:
myPortal for Desktop
myPortal for Outlook
- all of the functionality in myPortal for Desktop available as an MS Outlook toolbar!
- enables users to access all of their communications - voice, conferencing, voicemail, fax, IM, email, and contacts - directly from within MS Outlook
- Users can click to dial any number from any Microsoft application
Additional information can be found within this Wiki using the following link:
myPortal for Outlook
myAttendant
- presence-aware switchboard application used by administrators, dispatchers or supervisor
- presents a single, consolidated view of all of the company’s users and their presence status, making it easy to transfer calls to employees when they are available
Additional information can be found within this Wiki using the following link:
myAttendant
myAgent
Presents the full suite of contact center features from a single desktop view (call queue information, relevant customer information pop-ups accompany incoming calls, access customer data and call history)
Additional information can be found within this Wiki using the following link:
myAgent
myReports
myReports provides over 100 predefined standard reports. The historical reports are provided as graphs and/or table views.
Additional information can be found within this Wiki using the following link:
myReports
Unify Phone for OpenScape / Unify Phone for Microsoft Teams
is the cloud based WebRTC softphone for desktop and mobile operation connected via a telephony connector (hybrid approach) in a single solution. It offers values from the cloud and is the mobile client for OpenScape Business. Unify Phone for Microsoft Teams offers a deep integration in MS Teams including bidirectional presence synchronisation
General configuration
Single Node
Networked System
Networking "OpenScape Business" OpenScape Business offers the opportunity to build networks with up to 2000 participants. Within an OpenScape Business Network a broad range Unfified communcation feature are available for all useres beneath the normal telephony features e.g:
- Presence management with voice support(visibility of presence status)
- Network-wide call status (e.g. subscriber is being called, subscriber has an active call)
- Call pickup via myPortal for Desktop
- Instant messaging with Multi-User-Chat
- Drag&Drop conferences in the network
- Network-wide Web Collaboration (for example, desktop sharing and video)
- myAttendant – change the presence status for all users in the network
- Integrate external directories with OpenScape Office Directory Services
- Integration in the Microsoft Exchange calendar and in the public directory
- Forwarding of voicemails in the network
An OpenScape Business network is controlled by the so called Master Node, which does not require necessarily additional HW/SW depending on the size of the network. An administrator can access all network subscribers via the Single Point of Administration within the Master Node. When changes are made within the Master Node administration, the databases of the individual network nodes are automatically synchronized.
A LAN/WAN based IP network is required as prerequisite for networking.
OpenScape Business systems can be networked via IP or via digital trunks. Both S0 as well as S2M lines with QSIG protocol can be used for the connection.
Within the following some essentiall networking scenarios are shown. Details, prerequisites and even more scenarios are decribed within the administration manual of OpenScape Business.
Networking Multiple OpenScape Business X1/X3/X5/X8 Systems
Up to 32 OpenScape Business communication systems can be networked with each other.
Networking OpenScape Business and OpenScape Business S (Single Gateway)
Up to 32 OpenScape Business X1/X3/X5/X8 and S communication systems can be networked with one another. Multiple OpenScape Business S systems are allowed in an internetwork. Single Gateway means that all IP stations registered at OpenScape Business S only use ONE gateway to the PSTN.
Networking OpenScape Business and OpenScape Business S (Multi Gateway)
Up to 32 OpenScape Business X1(W)/X3/X5/X8 and S communication systems can be networked with one another. Multi-gateway means that every IP station registered at OpenScape Business S is assigned to exactly one specific gateway.
Data Center and Private Cloud Deployments
-
OpenScape Business S in private cloud deployments - OSBiz S in Data Center and Cloud Depoyments Technical Overview and Details
- Further Informations can be found in the How to collection and tutorials for OpenScape Business
SIP / ITSP Connectivity
Configuration of LAN/WAN interface for VoIP
SIP Devices
Information about connection of and SIP devices can be found within the following link
SIP Trunks and certified ITSP
Information about connection of SIP trunks and certified VoIP service providers can be found within the following link
Integrated Session Border Controller
Diagnostics and Configuration Hints
Integration in business application and processes
OpenScape Business supports many interfaces, protocols and standards for integration into business process or connection to 3rd party applications. Details are listed in the the datasheet or feature description. Within the following section only the most relevant interfaces and integrations are described. Nearly all connections, except TDM telephony, uses the Ethernet LAN interface of OpenScape Business.
|
Please note, latest supported operating systems, virtualization platforms and applications can always be found in the official Sales Information provided by Unify and it´s authorized resellers. |
Windows Terminal Server and Citrix support
The following document describes how to operate OpenScape Business client within Windows Remote Desktop Services and Citrix XenApp environment
Microsoft Exchange Server
The following documents describe how to connect OpenScape Business to “Microsoft Exchange"
Further information can also be found in the OpenScape Business Administration Manual within the Mitel/Unify Partner Portal
Microsoft Office 365
The following document describes how to connect a local OpenScape Business to “Microsoft Office 365”
Please check the current required Microsoft licenses before the installation.
Access to external directories and data sources
OpenScape Business can access data within external directories or databases via:
- Open Directory Service
- LDAP
- Data replication via CSV file import
Open Directory Service
is fully embedded within OpenScape business. It allows access to internal User Data, Speed Dials and the UC-Suite Directory as well as to following external SQL database servers:
- Microsoft SQL server,
- Postgres SQL server,
- Sybase SQL server
More information is given within the link:
LDAP - Lightweigt Data Access Protocol
allows direct data querey from external LDAP capable directories.
The administration of the LDAP interface within OpenScape Business is described within the link:
Open Interfaces
Information about OpenScape Business and its interfaces for business process integration can be found here
CTI - Computer Telephony Integration
OpenScape Business offers several protocols and API´s to application programmers to integrate telephony and UC functions of OpenScape Business into their applications.
Interface Description
The descriptions of the CTI interfaces are provided within the following link:
TAPI Service Provider
Due to the importance of TAPI two new and powerful TAPI Service Providers (TSP) have been developed for OpenScape Business in addition to the existing CallBridge Collection.
Differences between OSBiz TAPI 120/170 and HiPath TAPI 120/170
In contrast to the handling of the HiPath TAPI 120/170 V2 TAPI Service Providers for HiPath 3000, the following changes apply in the OpenScape Business environment:
- OpenScape Business TAPI 120 and TAPI 170 are new software components that were developed exclusively for OpenScape Business. The software versioning begins with Version 1.
- The OpenScape Business TAPI 120 or 170 software and the licenses can only be used in conjunction with OpenScape Business.
- The connection to OpenScape Business takes place exclusively via the LAN.
- Additional hardware and software components such as the CSTA Message Dispatcher (CMD), CSTA Service Provider (CSP), HG 1500 board or HiPath 5000 RSM System are no longer required for OpenScape Business TAPI 120/170.
- The licensing is station based and no longer distinguishes between OpenScape Business TAPI 120 or TAPI 170 stations. The licensing requirement begins with the first TAPI station.
- Existing HiPath TAPI 120 or 170 user licenses cannot be used in conjunction with OpenScape Business TAPI 120 or 170
Device@Home
System(HFA)Device@Home
The feature "System Device @ Home" allows the connection of system telephones as OpenStage or OpenScape Deskphone with HFA protocol over the Internet to OpenScape Business and as to operate them e.g. in the home office.
SIP Device@Home
OpenScape Business supports the STUN protocol (Session Traversal Utilities for NAT). This enables the connectivity of STUN capable SIP devices to OpenScape Business via the Internet.
Integration of Vertical Solutions
Hotel / Hospitality Solutions
OpenScape Business can be connected to Hospitality Solutions. Certified solutions are listed within Unify´s "Technology Partner Programm".
Unify Phone
Unify Phone is a cloud based telephony connector for OpenScape Business. This section describes the connectivity of Unify Phone to OpenScape Business and how this can be configured.
Circuit
Please note: Circuit has reached end of life. As a successor solution we offer a migration path to Unify Video with Unify Phone or Unify Office. Please get in contact with your Unify representative.
MS Skype for Business Interworking
This section describes the Telephony Voice Interworking capabilities between OpenScape Business and MS Microsoft Skype for Business an how this can be configured
- How To Configure OSBiz Skype for Business Interworking
- OpenScape Business - Skype for Business MS Interworking Use Cases and Hints
MS Teams Interworking and Integration
This section describes the Telephony Voice Interworking and integration capabilities between OpenScape Business and MS Teams (Direct Routing Plan via SBC, myPortal for Teams plugin) based on customer experiences
Capacities
| OpenScape Business X1R/W | OpenScape Business X3 | OpenScape Business X5 | OpenScape Business X8 | OpenScape Business S | |
|---|---|---|---|---|---|
| BRI Trunks | 0 | 20 | 52 | 128 | N/A |
| PRI Trunks | 0 | 30 | 30 | 180 | N/A |
| ITSP Trunks | 60 | 60 | 60 | 60 | 180 |
| Analog Stations | 4 | 20 Rack system 20 Wall system |
56 Rack system 68 Wall system |
384 | N/A |
| Digital Phones | 8 | 24 | 56 | 384 | N/A |
| IP Phones | 500 | 500 | 500 | 500 | 1500 |
| Cordless/DECT Phones | 16 | 32 | 32 Rack system 64 Wall system |
250 | N/A |
| Max.# of Phones | 500 | 500 | 500 | 500 | 1500 |
Remarks: Figures are subject to change. For actual figures refer to the latest version of OpenScape Business Sales Information and Datasheet.
Administration
Administration of OpenScape Business is done mainly via Web Based Management (OpenScape Business Assistant). Manager E tool, known from HiPath 3000, can also be used for administration alternatively.
Documentation
Documentation is available from different sources depending on the type of documentation.
Main source for technical documentation and user guides is the OpenScape Business systems itself. Documents are available either as download from the system SW via the administration tool or can be accessed direcly as file on the SW storage media.
All available documents can be obtained via the Partner Portal.
The following table gives an overview about the provided documents.
| Target Group | Documentation | Content | Medium | Source of supply |
| Sales and Project Planners | Data Sheet | System Overview | e-Docu | Partner Portal |
| Feature Description | This document describes all features | e-Docu | Partner Portal | |
| Planning Guide | This document provides guidelines for planning | e-Docu | Partner Portal | |
| Administrators and Technicians | Installing the Hardware, Service Documentation | This document describes the hardware for OpenScape Business X3/X5/X8 (including the hardware installation) | e-Docu | Partner Portal |
| Installing OpenScape Business X3/X5/X8 | This document describes the installation of OpenScape Business X3/X5/X8 | e-Docu | Partner Portal | |
| Installing the Linux Server | The document describes how to install Linux on a separate server PC as a platform for the OpenScape Business S Softswitch and the Application Server OpenScape Business UC Booster Server | e-Docu | Partner Portal | |
| Installing OpenScape Business S | This document describes the installation of the communication software for the OpenScape Business S Softswitch (incl. UC Suite) on a separate Linux server | e-Docu | Partner Portal | |
| Installing the OpenScape Business UC Booster Server | This document describes the installation of the communication software for the Application Server OpenScape Business UC Booster Server (incl. UC Suite) on a separate Linux server | e-Docu | Partner Portal | |
| Administrator Documentation | This document describes the installation, configuration, operation, administration and features of OpenScape Business | e-Docu | System, Partner Portal | |
| Manager E, Administrator Documentation | This document describes the configuration of features using Manager E | e-Docu | Partner Portal | |
| Users, Technicians, Administrators | myPortal Smart, User Guide | This document describes the configuration and operation of the myPortal Smart application | e-Docu | System, Partner Portal |
| myPortal for OpenStage, User Guide | This document describes the configuration and operation of myPortal for OpenStage | e-Docu | System, Partner Portal | |
| myPortal for Desktop, User Guide | This document describes the installation, configuration and operation of the myPortal for Desktop application | e-Docu | System, Partner Portal | |
| myPortal for Outlook, User Guide | This document describes the installation, configuration and operation of the myPortal for Outlook application | e-Docu | System, Partner Portal | |
| Fax Printer, User Guide | This document describes the installation, configuration and operation of Fax Printer | e-Docu | System, Partner Portal | |
| myPortal to go, User Guide | This document describes the configuration and operation of myPortal for Mobile | e-Docu | System, Partner Portal | |
| myAgent, User Guide | This document describes the installation, configuration and operation of the myAgent application | e-Docu | System, Partner Portal | |
| myReports, User Guide | This document describes the installation, configuration and operation of the myReports application | e-Docu | System, Partner Portal | |
| myAttendant, User Guide | This document describes the installation, configuration and operation of the myAttendant attendant console | e-Docu | System, Partner Portal | |
| OpenScape Business Attendant, User Guide | This document describes the installation, configuration and operation of the attendant console OpenScape Business Attendant | e-Docu | System, Partner Portal | |
| UC Smart Telephone User Interface (TUI), Quick Reference Guide | This document describes the phone menus of the voicemail box (UC Smart) | e-Docu | System, Partner Portal | |
| UC Suite Telephone User Interface (TUI), Quick Reference Guide | This document describes the phone menu of the voicemail box (UC Suite) | e-Docu | System, Partner Portal | |
Software Delivery / Deployment
SW deployment depends on the OpenScape Business models. SW is either deployed as embedded SW or has to be ordered separately on a storage media. SW corrections are available at the Central Software Download Server of Unify, which can be accessed via the Partner Portal.
OpenScape Business X models
The SW of OpenScape Business X models is delivered on a SDHC card together with the main board. SW needs not be ordered separately.
In case that a UC Booster Card is required the SW is delivered on its internal storage device.
OpenScape Business UC Booster Server or OpenScape Business S
The SW of OpenScape Business Booster Server or OpenScape Business S has to be ordered separately. The SW is delivered on DVD as data media.
The required operating system (Suse Linux Enterprise system (SLES)) can be obtained also from Unify.
In case, that the SLES SW is ordered from Unify, an registration key for a 3 year SW update period, granted by Novell, is included.
OpenScape Business S SW (incl. SLES) is also available as .OVA Image for virtualized machines via the software Supply Server.
Licensing
Use of OpenScape Business features is licensed. Starting with the basic system licence, additional features can be easily added, by importing appropriate license keys. License keys are providedby the Central License Server order dependent and are managed by the administration tools of OpenScape Buisness.
Activation Period
OpenScape Business supports a Licence Activation Period with full feature functionality for a time period of 30 days after first installation. After 30 days system functionality is restricted to emergency operation in case that no valid license keys have been uploaded to the system.
Evaluation Licenses
If specific functions should be tested for a time period of 90 days, so called Evaluation Licenses can be ordered.
Migration
OpenScape Business offers an easy migration path from HiPath 3000 to OpenScape Business.
Depending on the HW / SW version of HiPath 3000 existing housing, power supply and also many peripherial boards and devices can be reused.
Within many migration cases only the mainboard, System SW and license file need to be replaced by OpenScape Business components.
Conversion of system configuration data is also supported.
Details are described within the OpenScape Business Sales Information and the Administration Manual
Security
Security Checklist
Instructions for hardening of OpenScape Business are described within the
OpenScapeBusiness Security Checklist
which can be downloaded from the Partner Portal.
Security Bulletins
The following documents contain descriptions of security improvements.
Discontinued Applications
Up from OpenScape Business V3 the following applications will be discontinued and be replaced by successor solutions. More informations can be found in the current OpenScape Business Sales Information within our UNIFY Partner Portal
- myPortal Smart replaced by myPortal @work
- myPortal for OpenStage replaced by UC Integration for OpenScape Desk Phone CP 400 and 600/E
- OpenStage Gate View replaced by Video Streaming for OpenScape Desk Phone CP 600/E and 700/X
- Xpressions Compact replaced by integrated or UC Voicemail application
- OpenScape Business integrated VPN solution
- XMPP Protocol
- PPP over ISDN on new V3 hardware
Further Technical Information / Links
Supported Standards
Ethernet
- RFC 894 Ethernet II Encapsulation
- IEEE 802.1Q Virtual LANs
- IEEE 802.2 Logical Link Control
- IEEE 802.3u 100BASE-T
- IEEE 802.3ab Gigabit Ethernet
- IEEE 802.3X Full Duplex Operation
IP/Routing
- RFC 768 UDP
- RFC 791 IP (updated by: RFC 1349, RFC 2474, RFC 6864)
- RFC 792 ICMP (updated by: RFC 950, RFC 4884, RFC 6633, RFC 6918)
- RFC 793 TCP (updated by: RFC 1122, RFC 3168, RFC 6093, RFC 6528)
- RFC 826 ARP (updated by: RFC 5227, RFC 5494)
- RFC 1332 The PPP Internet Protocol (updated by: RFC 3241)
- RFC 1918 IP Addressing (updated by: RFC 6761)
- RFC 2131 DHCP (updated by: RFC 3396, RFC 4361, RFC 5494, RFC 6842)
- RFC 2822 Internet Message Format (obsoleted by RFC 5322)
- RFC 5322 Internet Message Format (updated by: RFC 6531, RFC 6532, RFC 6854)
Control Protocol (IPCP)
- RFC 1334 PPP Authentication Protocols (obsoleted by: RFC 1994)
- RFC 1618 PPP over ISDN
- RFC 1661 The Point-to-Point Protocol (PPP) (updated by: RFC 2153)
- RFC 1877 PPP Internet Protocol Control Protocol
- RFC 1990 The PPP Multilink Protocol (MP)
- RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP) (updated by: RFC 2484)
- RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE)
- RFC 3544 IP Header Compression over PPP
NAT
- RFC 2663 NAT
IPsec
- RFC 2403 IPsec Authentication - MD5
- RFC 2404 IPsec Authentication - SHA-1
- RFC 2404 IPsec Authentication - SHA-2
- RFC 2405 IPsec Encryption 3DES
- RFC 2407 IPsec DOI
- RFC 2408 ISAKMP
- RFC 2409 IKE
- RFC 2410 IPsec encryption - NULL
- RFC 2411 IP Security Document Roadmap
- RFC 2412 OAKLEY
- RFC 3602 IPSec encryption with AES
- RFC 4301 Security Architecture for the IP
- RFC 4303 IP Encapsulating Security Payload (ESP)
SNMP
- RFC 1213 MIB-II
QoS
- IEEE 802.1p Priority Tagging
- RFC 1349 Type of Service in the IP Suite (obsoleted by: RFC 2474)
- RFC 2474 Type of Service in the IP Suite (updated by: RFC 3168, RFC 3260)
- RFC 2475 An Architecture for Differentiated Services (updated by: RFC 3260)
- RFC 2597 Assured Forwarding PHB Group (updated by: RFC 3260)
- RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)
Services
- RFC 2597 Assured Forwarding PHB Group
- RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)
Codecs
- G.711
- G.729
CTI
- CSTA Phase III
- TAPI Service Provider for TAPI 2.1
SIP
The table below indicates which RFCs are implemented on the SIP interfaces of the system:
- ITSP: Internet Telephony Service Provider interface
- SIP SUB: SIP interface for connection of SIP- phones
- SIP TRK: SIP interface for connection to external SIP servers
- SIP-Q: SIP interface for connection of OpenScape Business systems
Within the SIP interface columns following information are given:
- yes: The main content of the RFC is implemented in the system. There might be options in the RFC which are not implemented. No details are given in the list
- no RFC is NOT implemented on that interface
- n/a RFC is not applicable to that interface
The information applies to OpenScape Business Version V2R3
| RFC number | Title | Remarks | ITSP | SIP-SUB | SIP-TRK | SIPQ |
| RFC 1889 | RTP: A Transport Protocol for Real-Time Applications | Obsoleted by RFC3550 | yes | yes | yes | yes |
| RFC 2198 | RTP Payload for Redundant Audio Data | Used in conjunction with RFC 2833 | no | no | no | no |
| RFC 2246 | The TLS Protocol Version 1.0 | Obsoleted by RFC4346, Updated by RFC3546 | no | no | no | no |
| RFC 2327 | SDP: Session Description Protocol (obsoleted by RFC4566) | yes | yes | yes | yes | |
| RFC 2396 | Uniform Resource Identifiers (URI): Generic Syntax | Obsoleted by RFC3986 | yes | yes | yes | yes |
| RFC 2560 | X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP | no | no | no | no | |
| RFC 2617 | HTTP Authentication: Basic and Digest Access Authentication | yes | yes | no | no | |
| RFC 2782 | DNS RR for specifying the location of services (DNS SRV) | yes | n/a | yes | yes | |
| RFC 2833 | RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals | Obsoleted by 4733 | yes | yes | yes | yes |
| RFC 2976 | The SIP INFO Method | Used for SIPQ trunking only | no | no | no | yes |
| RFC 3204 | MIME media types for ISUP and QSIG Objects | QSIG only | no | no | no | yes |
| RFC 3261 | SIP: Session Initiation Protocol | SIP Core RFC | yes | yes | yes | yes |
| RFC 3262 | Reliability of Provisional Responses in the Session Initiation Protocol (SIP) | provisional Response Acknowledgement (PRACK) Early Media | no | yes | no | no |
| RFC 3263 | SIP Locating Servers | yes | yes | yes | yes | |
| RFC 3264 | An Offer/Answer Model with SDP | yes | yes | yes | yes | |
| RFC 3265 | Session Initiation Protocol (SIP)-Specific Event Notification | used for MWI and GroupPickup | no | yes | no | no |
| RFC 3268 | Advanced Encryption Standard (AES) Cipher suites for Transport Layer Security (TLS) | no | no | no | no | |
| RFC 3280 | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile | no | no | no | no | |
| RFC 3310 | HTTP Digest Authentication | yes | yes | no | no | |
| RFC 3311 | Session Initiation Protocol (SIP) UPDATE Method | yes | yes | yes | yes | |
| RFC 3312 | Integration of Resource Management and Session Initiation Protocol (SIP) | no | no | no | no | |
| RFC 3323 | A Privacy Mechanism for the Session Initiation Protocol (SIP) | yes | yes | no | no | |
| RFC 3324 | Short Term Requirements for Network Asserted Identity | no | no | no | no | |
| RFC 3325 | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | yes | yes | yes | no | |
| RFC 3326 | The Reason Header Field for the Session Initiation Protocol (SIP) | yes | yes | yes | yes | |
| RFC 3327 | Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts | no | no | no | no | |
| RFC 3329 | Security Mechanism Agreement for the Session Initiation Protocol | no | no | no | no | |
| RFC 3389 | Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) | no | no | no | no | |
| RFC 3420 | Internet Media Type message/sipfrag | no | no | no | no | |
| RFC 3428 | Session Initiation Protocol (SIP) Extension for Instant Messaging | no | no | no | no | |
| RFC 3489 | STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) | yes | yes | no | no | |
| RFC 3515 | The Session Initiation Protocol (SIP) Refer Method | no | yes | no | no | |
| RFC 3550 | RTP: Transport Protocol for Real-Time Applications | yes | yes | yes | yes | |
| RFC 3551 | RTP Profile for Audio and Video Conferences with Minimal Control | yes | yes | yes | yes | |
| RFC 3581 | An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing | rport | yes | yes | yes | no |
| RFC 3605 | Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) | no | no | no | no | |
| RFC 3665 | Session Initiation Protocol (SIP) Basic Call Flow Examples | yes | yes | yes | N/A | |
| RFC 3666 | Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows | yes | yes | yes | N/A | |
| RFC 3680 | A Session Initiation Protocol (SIP) Event Package for Registrations | no | no | no | no | |
| RFC 3711 | The Secure Real-time Transport Protocol (SRTP) | yes | no | no | yes | |
| RFC 3725 | Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) | no | yes | no | no | |
| RFC 3761 | The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) | no | no | no | no | |
| RFC 3830 | MIKEY: Multimedia Internet KEYing | MIKEY0 only | no | no | no | yes |
| RFC 3842 | A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) | no | yes | no | no | |
| RFC 3891 | The Session Initiation Protocol (SIP) Replaces Header | passive usage only | no | yes | no | no |
| RFC 3892 | The Session Initiation Protocol (SIP) Referred-By Mechanism | no | yes | no | no | |
| RFC 3959 | The Early Session Disposition Type for the Session Initiation Protocol (SIP) | no | no | no | no | |
| RFC 3960 | Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) | no | no | no | no | |
| RFC 3966 | The tel URI for Telephone Numbers | yes | no | no | no | |
| RFC 3968 | The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) | As this RFC describes rules for assigning new parameters etc. it is not applicable for a certain product | N/A | N/A | N/A | N/A |
| RFC 3969 | The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) | As this RFC describes rules for assigning new parameters etc. it is not applicable for a certain product | N/A | N/A | N/A | N/A |
| RFC 4040 | RTP Payload Format for a 64 kbit/s Transparent Call | yes | yes | yes | yes | |
| RFC 4028 | Session Timers in the Session Initiation Protocol (SIP) | yes | yes | no | yes | |
| RFC 4119 | A Presence-based GEOPRIV Location Object Format | XML based location definition for emegancy calls | yes | no | no | no |
| RFC 4123 | Session Initiation Protocol (SIP)-H.323 Interworking Requirements | no | no | no | no | |
| RFC 4235 | An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol | Used for GroupPickup | no | yes | no | no |
| RFC 4244 | An Extension to the Session Initiation Protocol (SIP) for Request History Information | no | no | no | no | |
| RFC 4320 | Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction | no | no | no | no | |
| RFC 4504 | SIP Telephony Device Requirements and Configuration | no | no | no | no | |
| RFC 4538 | Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) | no | no | no | no | |
| RFC 4566 | SDP: Session Description Protocol; M. Handley, V. Jacobson.(obsoletes RFC 2327) | yes | yes | yes | yes | |
| RFC 4568 | Session Description Protocol (SDP) Security Descriptions for Media Streams | yes | no | no | no | |
| RFC 4733 | RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals | yes | yes | yes | yes | |
| RFC 4856 | Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences | Obsoletes RFC3555 | yes | yes | yes | yes |
| RFC 4967 | Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier | no | no | no | no | |
| RFC 5009 | Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media | P-Early-Media header | yes | no | no | no |
| RFC 5031 | A Uniform Resource Name (URN) for Emergency and Other Well-Known Services | no | no | no | no | |
| RFC 5139 | Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) | XML based location definition for emegancy calls | yes | no | no | no |
| RFC 5245 | Interactive Connectivity Establishment (ICE):A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols | no | no | no | no | |
| RFC 5246 | The Transport Layer Security (TLS) Protocol Version 1.2 | yes | yes | yes | yes | |
| RFC 5280 | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile | no | no | no | no | |
| RFC 5589 | Session Initiation Protocol Call Control – Transfer | no | yes | no | no | |
| RFC 5806 | Diversion Indication in SIP | Diversion header field | yes | yes | no | no |
| RFC 5876 | Updates to Asserted Identity in the Session Initiation Protocol (SIP) | no | no | no | no | |
| RFC 5923 | Connection Reuse in the Session Initiation Protocol | no | no | no | yes | |
| RFC 6140 | Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) | SIP connect registration | yes | no | no | no |
VoIP Security
- RFC 2459 X.509 PKI Certificate and CRL Profile
XMPP
- RFC 3920 Extensible Messaging and Presence Protocol (XMPP): Core
- RFC 3921 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
Others
- RFC 959 FTP
- RFC 1305 NTPv3
- RFC 1951 DEFLATE
Supported Server based Hardware
Unify does not provide any Server based Hardware platform for deploying OpenScape Business S Server and/or OpenScape Business UC Booster Server applications.
All necessary Server based Hardware (especially in a customer scenario without any suitable Virtualization environment) must be purchased and installed separately according to the Operating System's requirements and restrictions which is requested to deploy OpenScape Business S Server and/or OpenScape Business UC Booster Server applications (actually this Operating System is SuSE Linux Enterprise Server 12 SP5 64 bit up from OpenScape Business V3).
How To Collection
How to collection and tutorials for OpenScape Business
Useful Tools
Other Information Sources
Technical Newsletter
With the technical newsletter you get essential service related information for our products, such as information about technical functionalities, configuration hints and service related issues.
To register, please use the registration form in Unify Partner Portal, which can be found there in “Learn / News & Newsletters / Technical Newsletter”.
- Partner Portal (login required).
Marketing Information
Sales and marketing oriented documents and presentations can be obtained using the following links:
- Partner Portal (login required).
CSTA schema
