OpenScape Desk Phone CP FAQ

You are here:

Home  Devices  OpenScape Desk Phone CP FAQ  OpenScape Desk Phone CP FAQ

In this OpenScape Desk Phone CP FAQ you will find answers to frequently asked questions on the OpenScape Desk Phone CP phone family, divided into various topics.

Advanced Features

Bluetooth

With the OpenScape Desk Phone CP600 phone is Bluetooth available and allows use of Bluetooth headsets. More interesting features are supported using Bluetooth: Proximity Monitoring and Eddystone Beacons.

Audio Scenario, for Bluetooth Headset connection

The so called “classical” Bluetooth Specification 2.1 provides connectivity for a wide range of audio devices, including headsets and hands-free units. Support for high-definition audio devices is new in the OpenScape Desk Phone CP600.

The media player is loading...

Proximity Detection

The OpenScape Desk Phone CP600 phone supports in addition to the "classical" Bluetooth Specification also the new Bluetooth Specification 4.1
One of the new prominent feature is the Bluetooth Proximity Profile (PXP). The Proximity Profile defines the behavior of the OpenScape Desk Phone CP600 when a Bluetooth 4.1 device moves away or come closer together. For example, when workers approach their desks, the OpenScape Desk Phone CP600 phone detects proximity of their Bluetooth 4.1 supported headsets or mobile devices and automatically logs them in into the OpenScape Desk Phone CP600. Access to the phone and personal data can be protected in a comfortable and intuitive manner - smart and simple.
Now workers are able to use a phone no matter at which desks they sit. This is ideal for organizations that have a high number of transient or temporary employees, and it works with the hoteling model.

This YouTube video shows the above use case with a Plantronics Voyager Headset
Together, the Plantronics Voyager Focus UC and the CP600 allow users to manage calls distraction-free with immersive HD audio while protecting privacy, and ensuring security.

Eddystone Beacon

Eddystone Beacon is a technology provided by Google and is supported in the OpenScape Desk Phone CP600.
The Eddystone Beacon is part of the Physical Web initiative, which is about better connecting the real with the virtual world. The basic idea is to fully replicate the real world in the Internet. The challenge is to make all this information accessible in the moment where those are needed.

Beacons are becoming increasingly popular to meet these requirements but can be difficult to manage and maintain, as they require periodic maintenance like changing batteries or updating firmware. Integrating Beacon technology into the desk phones and so with integration into the Enterprise network can increase the number of Beacons without having to deploy standalone ones or to care about batteries.

Those Beacons have become popular in tracking customers, devices, or workers, and enable companies to push information to users automatically. To realize those functionalities, the new Eddystone Beacon support two basic use cases:

1) The OpenScape Desk Phone CP600 transmit Eddystone-URL frames
The OpenScape Desk Phone CP600 provide access to Location Based Services to mobile user. That Location Based Services are services which are relevant at a specific place, for instance pushing advertising and special rates/deal of the day in a shop; providing menu/lunch cards to the workers or simply send access to instruction to the phone.

The media player is loading...

2) The OpenScape Desk Phone CP600 receives Eddystone frames
Consider an enterprise that uses Bluetooth-enabled mobile devices (e.g. hospital with expensive/to be shared mobile heart rate monitor with attached Bluetooth 4.1 sender). This enterprise could use the OpenScape Desk Phone CP600 phones to span a wireless network to track those devices, creating an application to show the exact location of each device to find them fast and simply. The same could be done with humans when they carry Bluetooth 4.1. sender. We used for instance at last CEBIT fair the OpenScape Desk Phone CP 600 on the exhibition both to locate the booth duties.

There are many other use cases for this, ranging from Internet of Things (IoT) applications to security.

Remarks to realization:
Bluetooth devices which would use this service (e.g. smartphones) don´t need a classical Bluetooth pairing. Each Smartphone equipped with Bluetooth 4.1 Low Energy and a newer version of the Chrome browser is able to read and display those URLs.

See also for Eddystone Beacon and Physical Web

• Information

Talk with Scott Jenson about the Physical Web
https://www.youtube.com/watch?v=w8zkLGwzP_4
Background info on what the concept of "Physical Web" is about
https://google.github.io/physical-web/
More information to the concept of Eddystone
https://github.com/google/eddystone
Physical Web information from BKON
https://bkon.com/the-physical-web/

• Configuration

Configuration of Chrome/ Android for the Physical Web
https://www.phy.net/blog/physical-web-arrived-chrome-android/
Configuration of Chrome / iOs for the Physical Web
https://www.youtube.com/watch?v=gxPcPXSE_O0

Near Field Communication (NFC)

NFC support makes the process of pairing a smartphone to the OpenScape Desk Phone CP600 simple, requiring just a single tap - no manual pairing via menus and entering a PIN. The OpenScape Desk Phone CP600 supports that Secure Simple Pairing with smartphones, but not headsets, as these usually carry a NFC tag.

Remarks to realization:
The NFC tag in the OpenScape Desk Phone CP600 is read-only and contains the MAC address of the OpenScape Desk Phone CP600 and the built-in Bluetooth chip. With an additional implementation / service this technology can also be used to automatically login mobile users on OpenScape Desk Phone CP600. An Android application just needs to read the data from the NFC tag and send this together with the user’s E.164 number to the Management Server. This is all the Management Server needs to know to send the user’s personal data to the visited OpenScape Desk Phone CP600. That use cases can be realized with support of the UNIFY Professional Service.

The media player is loading...

Circuit Integration

Circuit, the UNIFY team communication and collaboration tool is now also integrated into the desk phones OpenScape Desk Phone CP400 and OpenScape Desk Phone CP600. The large screen of the desk phones makes it possible to display the conversation information from the Circuit application. This lets workers view and monitor Circuit conversations on their desk phones instead of having to check the mobile app or desktop computer screen. If the user presses the display button next to the conversation at his OpenScape CP Phone, the conversation contact is been called. If workers aren't using Circuit, they will see the standard lists (e.g. missed call list).

Remarks to realization:
The OpenScape Desk Phone CP acts as an IP phone, connected to the OpenScape Voice System. There's neither a Web RTC nor a dedicated Circuit client running on the desk phone. But, a specific "Circuit connector" / Application Interface is being used to exchange information between Circuit and the OpenScape Desk CP Phone, which are Conversation list, contact details, etc. The user has just to enter his Circuit account and password in the user menu of the CP Phone. If the user start to make a call via the Button next to the Circuit conversation, this is treaded as a standard audio call via the OpenScape Voice system and no Advanced Telephony Connector (ATC)/Universal Telephony Connector (UTC) is needed. The phone just grabs the phone number from the Circuit contact details. This is the same when dialing into a group conversation. Using ATC/UTC to enhance this functionality and pull calls from PC/Chrome browser is planned for the future and will be released separately.

The media player is loading...

Administration

Canonical Settings

coming soon

is required for the following functions:

Conversation , Intuitive search function , Real time LDAP , Permanent LDAP Lookup ,

LDAP

Accessing the LDAP server is available on OpenScape Desk Phone CP 20X/400/600

What is the purpose of a LDAP template?

See also: LDAP on OpenScape Desk Phone

A LDAP template has to be downloaded to the phone via local phone menu or WBM, because it contains necessary information about the search attributes and the location of all user data inside the directory.

is required for the following functions:

Intuitive search function , Real time LDAP , Permanent LDAP Lookup ,

Where do I get the template from?

It is a plain txt file and must fit your directory environment. The configuration for a Microsoft Active Directory would look like this:

OpenStage LDAP TEMPLATE (v.1)

SEARCHBASE="OU=Users,DC=microsoft,DC=com"

ATTRIB01="sn"

ATTRIB02="givenName"

ATTRIB03="telephoneNumber"

ATTRIB04="otherTelephone"

ATTRIB05="mobile"

ATTRIB06="homePhone"

ATTRIB07="company"

ATTRIB08="department"

ATTRIB09="l"

ATTRIB10="title"

ATTRIB11="mail"

ATTRIB12="picture"

EOF

Configuration at the phone.

The LDAP template can also be configured without file upload via the WBM (Admin --> Local functions --> LDAP Template) or the DLS IP Devices -> IP Phone Configuration -> Service Integrations -> LDAP Attributes

Besides the template, add the following information in the admin menu of the CP Phone IP: Admin --> Local functions --> Directory Settings

• LDAP server address
• LDAP server port
• LDAP authentication (if Simple, add authentication information below)
• (optional) Permanent LDAP Enabled
• (optional) Avatar server

Circuit

In order to use the Circuit function, a Circuit Server with the corresponding user name and PW must be configured from Admin or User.

Local: User Settings -> Configuration-> Circuit

WBM: User Settings -> Configuration-> Circuit

DLS: IP Devices -> IP Phone Configuration -> Service Integrations -> Circuit

is required for the following functions:

Circuit Mode

Exchange

In order to use the Exchange function, a Exchange Server with the corresponding user name and PW must be configured from Admin or User.

Local: User Settings -> Configuration-> Microsoft® Exchange

WBM: User Settings -> Configuration-> Microsoft® Exchange

DLS: IP Devices -> IP Phone Configuration -> Service Integrations -> Exchange

is required for the following functions:

Exchange

Landing Screen

The Landing Screen can be configured by the user or admin using the following methods:

Local: User Settings -> Phone -> Idle Screen

WBM: User Settings -> Phone -> Idle Screen

DLS: IP Devices -> IP Phone Configuration -> Miscellaneous -> Display / Phone Settings

Idle Screen

The Idle Screen can be configured by the user or admin using the following methods:

Local: User Settings -> Phone -> Idle Screen

WBM: User Settings -> Phone -> Idle Screen

DLS: IP Devices -> IP Phone Configuration -> Miscellaneous -> Display / Phone Settings

is required for the following functions:

Idle Screen

See also

Blog from BeaconZone to the OpenScape Desk Phone CP
https://www.beaconzone.co.uk/blog/ip-telephone-with-eddystone/