Supported Voice Devices
Refer to Server Requirements for a SaaS deployment
VoiceConsole On Prem Deployment Supported Talkman Devices
The following voice devices are supported:
- A700XP
- A700x
- A700
- A500
Legacy devices such as the Talkman T5 or older may function, but are not tested with current software and are therefore unsupported. For these devices, Honeywell Technical Support considers any issues encountered and reported under "best effort" support.
VoiceConsole SaaS Deployment Supported Talkman Devices
The A700XP is supported. It requires VoiceCatalyst 5.0 or later.
The A700x is supported. It requires VoiceCatalyst 4.7 or later.
VoiceConsole Android Support
DevKit based applications are built from DevKit and may be referred to as Guided Work Solutions or branded for a specific solution such as a WMS. These applications run on multiple device types including A700x, A700XP, and Android devices.
-
Applications must be built from DevKit 1.15 or later. DevKit 2.1 or later is recommended.
The following table compares the features supported on each type of device.
For more information see the list of Guided Work Solutions Supported Devices.
Administration
| Talkman Device Feature | Android Device Support? |
Note |
|---|---|---|
| Device Licensing | ü |
Operator Management
| Talkman Device Feature | Android Device Support? |
Note |
|---|---|---|
| Operators | ü | |
| Operator Templates | ü | |
| Operator Teams | ü | Android device limitation: Do not use single letters (A-Z) as Team Spoken Name. When selecting an Operator Team from the Android device, selecting one with a single letter spoken name can result in the following message: "Error in voice dialogue, please report problem. Use screen to complete current task and continue" |
| Operators Associated With a Task Package or Voice |
X | Available in Talkman devices. For Android devices, either an APK developed from DevKit and/or the necessary GWS Connector components (these are equivalent to a Task Package) must be installed manually or with an MDM. The voice is selected from the Android device or application. |
| Send Message | ü | Android application must be build from DevKit 2.3 or later. |
| Load Operator by Number |
X |
A user can pre-assign an operator to Talkman devices. For Android devices an operator logs on the device directly to receive the assignment. |
Device Management
| Talkman Feature | Android Device Support? |
Note |
|---|---|---|
| Export VRG / Device Profile Configuration |
X |
VoiceConsole SaaS deployments use Android Device Config to export a OnetimeStartupSettings.config file. This config file contains settings to connect an Android device to the VoiceConsole SaaS deployment. Other profile items included in a Talkman profile are not present for Android. |
| Report a Problem | ü |
|
| Device Groups | X |
Device groups are groups of devices that you can work with as a unit, making any device-based actions easier to perform. Device groups are for Talkman devices only. They provide functionality such as loading device profiles, task packages, and operators. |
| Accessory Configurations / Battery Management Reports |
X |
For Talkman devices, the Export Headset Report provides a list of all active headsets. The Battery Management Report is currently available only for SRX3 headsets and SRX3 batteries or Talkman batteries. View Android battery information through the Android device settings. |
| Bluetooth Pairing |
X |
Use VoiceConsole to pair Talkman devices with Bluetooth devices. For Android, pair Bluetooth devices through the Android device settings. |
| Display Dialog | ü |
Android application must be build from DevKit 2.1 or later. |
| Device Logging | ü |
Talkman devices provide logging details in addition to the information found in the application logs. For Android this enables GWS application logs, not device-specific logs. |
| Site Support in Device Config File | ü |
Android application must be build from DevKit 2.3 or later. Applications built from earlier versions do not include the Site ID and place all Android devices in the Default site. |
There may be a delay before action items start in a VoiceConsole SaaS deployment. See Device Communications for details on the Call Home delay.