> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-essentials/release-notes/sam-1-8-0.md).

# SAM 1.8.0

SAM Version: 1.8.0.xxx.1108

For use with Versity versions:

* Versity 92 Series R1.5 using Android 10
* Versity 95/96 Series R2.5 using Android 10

{% hint style="info" %}
**Only SAM 1.7.1 may be upgraded to SAM 1.8.0**

You must be running SAM 1.7.1 before you upgrade to SAM 1.8.0.
{% endhint %}

{% hint style="info" %}
**SAM compatibility**

SAM 1.8.0 was tested with Versity 92 Series 1.6 and Versity 95/96 Series 2.6. However, this version of SAM should work with any version of the Versity smartphone software. Any options that appear in SAM that are not in the phone menus will be ignored by the phone. Any options that are in the phone but not in SAM will be ignored by SAM, unless programmed through Custom Attributes.
{% endhint %}

## Enhancements

### Barcode

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-66c8b74898ad9b29ff6128367f853d2b22327cc8%2Frn-image30.png?alt=media)

#### Block entry keyboard injection

An administrator can now choose between 2 different types of keyboard injection for barcode scanning: *Character entry* or *Block entry*. Block entry often enables faster scanning.

### Buttons

#### Intent injections capability

The ability to perform intent injections was added, to allow button presses and releases to trigger intents with custom intent details. The intent details vary depending on the app you’re triggering.

**Configuring the new Custom Intent option**

Here’s an example of how to use the new Custom Intent option to program a button on your Versity phones to automatically initiate MS Teams Walkie Talkie Push-to-Talk calls – *without* needing to open the Teams app and navigate to the Walkie Talkie function:

1. ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-3f40197fd7a30dab391083fd4f8c196f6e0a536a%2Frn-image31.png?alt=media) From the Applications list, choose *Buttons*.

   *For the following example we’ll configure the Right button to have MS Teams Walkie Talkie functionality (allowing the user to hold the button to transmit and release the button to stop transmitting):*
2. Click *Right Button* in the Buttons list to expand its configuration menu, then choose *False* for *Enable User Control of Right Button*.
3. In the dropdown menu that appears, select *Custom*. Expand the *Custom Intent Details* section:

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-b4807772047aa844b22a553dac8ab22360f46704%2Frn-image32.png?alt=media)

{% hint style="danger" %}
**Known Issue with Custom Intent Details in SAM 1.8.0**

There is a Known Issue in SAM 1.8.0 where the Custom Intent Details section is visible regardless of a button’s settings.

This section should only be used when you set *Enable User Control* of a button to *False*, and then select the *Custom* option from the resulting dropdown menu.

**The following steps should only be done after you’ve selected the *****Custom***** option (and NOT Custom 1, Custom 2, Custom 3, or Custom 4) from the dropdown menu. *****For any choice other than Custom, leave the fields blank.***

For more information, see the *Known Issues* section below.
{% endhint %}

4. Enter the custom MS Team PTT parameters in the *Button Down Action* and *Button Up Action* fields:

   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-57581d1d146ca89f3fe162341e0047a132ecef24%2Frn-image34.png?alt=media)
5. Once your SAM configurations are sent to your phones, they will have MS Teams Walkie Talkie functionality whenever users press the Right button.

### Device Settings

#### More administrative control over notifications

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-7e1efb5f7e80e26f1b13a0f4f63bee8b2b330003%2Frn-image35.png?alt=media)

An administrator can disable a user’s ability to access the “Alerting”, “Silent”, and “Turn off notifications” options from the long-press menu of a notification.

#### Verbose Wi-Fi logging

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-ba4fa6662c8af557c3490a5361974751ef18ff5c%2Frn-image36.png?alt=media)

Verbose Wi-Fi logging is now available as an option. It is needed to troubleshoot the majority of wireless issues reported by administrators, and is therefore enabled by default to speed up the troubleshooting process. Verbose Wi-Fi logging is controllable via the phone, AMIE Essentials, or an EMM.

### Logging

#### Capture log bundle

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-8b913b5450e35de7086cfb0ba18dace62c4cfd6c%2Frn-image37.png?alt=media)

A new menu option in the advanced logging menu, “Capture log bundle”, behaves the same as “Capture bug report”, but with several enhancements.

In addition to triggering and collecting a bug report, it collects the following logging components (if they are enabled):

* The most recent logcat (if logcat is enabled)
* The most recent slnkdump (if slnkdump is enabled)
* The most recent QXDM logs (if QXDM logging is enabled)
* ANRs (if applicable)

The collected logs are zipped into a zip file that will be 50MB or less, which is then uploaded to the Upload server (if configured).

### SoundStage+

SoundStage+ is a new app replacing the original SoundStage app, offering more administrative control options and an improved user interface. It enables administrators and users to control the volumes of various system and application sounds using five profiles: Normal, Loud, Soft, Silent, and Personal. All profiles are enabled by default; the administrator can disable any profile, which is then hidden from the user.

An administrator can configure each profile with minimum, maximum, and default volume levels for system sounds (alarm, ringer, media, and call) and app sounds (Web API, PTT, Batt Life). The user can change the volume level for the currently active profile only within the minimum and maximum ranges set by the administrator.

The volume levels of the Normal, Loud, Soft, and Silent profiles can be fully or partially controlled by SAM or an EMM. If the Personal profile is enabled by the administrator, its volume levels are set by the user.

Rules can be configured to apply a given profile at a specific time: for example, you can make a rule for the Silent profile to engage from 6 p.m. to 9 a.m., with the Normal profile operating from 9 a.m. to 6 p.m.)

SoundStage+ provides NFC options to scan and associate NFC tags to a profile. When configured, profiles can be switched by tapping the phone to something like a badge on the door of a conference room — a handy way to switch to the Silent profile when entering a meeting.

#### Upgrading to SoundStage\*+\* from SoundStage

{% hint style="danger" %}
**Upgrade to SAM 1.8.0 before upgrading your phones to Versity 2.6/1.6 and SoundStage+**

To avoid losing your previously configured SoundStage settings, you must upgrade to SAM 1.8 and configure SoundStage+ there *before* upgrading your phones to Versity 2.6/1.6 and SoundStage+.
{% endhint %}

*Follow these steps to retain your previously configured settings from SoundStage when upgrading to Versity 2.6/1.6 and SoundStage+:*

1. Upgrade to SAM 1.8.0.
2. Manually configure SoundStage+ in SAM 1.8.0, using your SoundStage settings as a reference.
3. Update your Spectralink phones to Versity 2.6 (1.6 for the V92 series). During the upgrade, Versity will automatically copy your SoundStage settings to SoundStage+.
4. In the Device List in SAM 1.8.0, select all devices. From the “Select actions…” dropdown menu, choose “Re-apply config”.

{% hint style="info" %}
**If you use an EMM to manage your phones**

You’ll need to whitelist SoundStage+, and delist SoundStage. Consult your EMM references or vendor for more information.
{% endhint %}

#### General options

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-a8490c76dac3f4f351933124d8d05a8a608450d9%2Frn-image38.png?alt=media)

**Enable SoundStage+**

|               |                               |
| ------------- | ----------------------------- |
| **Type**      | Radio button                  |
| **Default**   | Disabled                      |
| **Unique?**   | No                            |
| **Required?** | Yes, for SoundStage+ profiles |
| **Level**     | Any                           |
| **Notes:**    |                               |

**Enable Sound Profile Switch**

|               |                                            |
| ------------- | ------------------------------------------ |
| **Type**      | Radio button                               |
| **Default**   | Enabled                                    |
| **Unique?**   | No                                         |
| **Required?** |                                            |
| **Level**     | Any                                        |
| **Notes:**    | Allows the user to switch between profiles |

**Enable Personal Profile**

|               |                                                                                                        |
| ------------- | ------------------------------------------------------------------------------------------------------ |
| **Type**      | Radio button                                                                                           |
| **Default**   | Enabled                                                                                                |
| **Unique?**   | No                                                                                                     |
| **Required?** |                                                                                                        |
| **Level**     | Any                                                                                                    |
| **Notes:**    | Allows the use of a personal profile configurable by the user; if disabled, it is hidden from the user |

**Persist Active Profile Notification**

|               |              |
| ------------- | ------------ |
| **Type**      | Radio button |
| **Default**   | Enabled      |
| **Unique?**   | No           |
| **Required?** | No           |
| **Level**     | Any          |
| **Notes:**    |              |

**Enable NFC Beam**

|               |              |
| ------------- | ------------ |
| **Type**      | Radio button |
| **Default**   | Enabled      |
| **Unique?**   | No           |
| **Required?** |              |
| **Level**     | Any          |
| **Notes:**    |              |

**Enable Normal Profile**

|               |                              |
| ------------- | ---------------------------- |
| **Type**      | Radio button                 |
| **Default**   | Enabled                      |
| **Unique?**   | No                           |
| **Required?** |                              |
| **Level**     | Any                          |
| **Notes:**    | Hidden from user if disabled |

**Enable Loud Profile**

|               |                              |
| ------------- | ---------------------------- |
| **Type**      | Radio button                 |
| **Default**   | Enabled                      |
| **Unique?**   | No                           |
| **Required?** |                              |
| **Level**     | Any                          |
| **Notes:**    | Hidden from user if disabled |

**Enable Soft Profile**

|               |                              |
| ------------- | ---------------------------- |
| **Type**      | Radio button                 |
| **Default**   | Enabled                      |
| **Unique?**   | No                           |
| **Required?** |                              |
| **Level**     | Any                          |
| **Notes:**    | Hidden from user if disabled |

**Enable Normal Profile**

|               |                              |
| ------------- | ---------------------------- |
| **Type**      | Radio button                 |
| **Default**   | Enabled                      |
| **Unique?**   | No                           |
| **Required?** |                              |
| **Level**     | Any                          |
| **Notes:**    | Hidden from user if disabled |

**Enable Silent Profile**

|               |                              |
| ------------- | ---------------------------- |
| **Type**      | Radio button                 |
| **Default**   | Enabled                      |
| **Unique?**   | No                           |
| **Required?** |                              |
| **Level**     | Any                          |
| **Notes:**    | Hidden from user if disabled |

**Switch Profiles Silently**

|               |              |
| ------------- | ------------ |
| **Type**      | Radio button |
| **Default**   | Disabled     |
| **Unique?**   | No           |
| **Required?** |              |
| **Level**     | Any          |
| **Notes:**    |              |

#### Profile options

**Profiles: Normal, Loud, Soft, Silent**

The administrator controls the parameters for the Normal, Loud, Soft, and Silent profiles. Each profile can be configured with minimum, maximum, and default volume levels for system sounds (alarm, ringer, media, and calls), and apps (Web API, PTT, and Batt Life). When a profile is selected on the phone, all of these settings are applied at once.

The screenshot below shows the configuration options for the Normal profile, with all the settings at Default. (The Loud, Soft, and Silent profiles provide the same configuration options, but have different Default settings.)

When the profiles are configured in SAM, they are set for the user in the SoundStage+ app on the phone. The user can change a volume level on their phone only within the minimum and maximum range set by the administrator.

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-34f10e431939dcc3705cf5bae86559b351faf964%2Frn-image39.png?alt=media)

#### Rules options

An administrator can define up to 5 rules. Rule 1 is reserved for the Charging profile, to be used when the phone is in the charger. Rules 2 through 5 are defined by setting a time for a specific profile to be applied.

SoundStage+ changes profile behavior when a phone’s status changes:

1. When the phone is removed from the charger, the profile rule in effect for current time will be applied.
2. If the user changes the current profile manually or by NFC tap, this change will apply until the next scheduled profile rule becomes active.

SoundStage+ will choose an active profile from the enabled rules whenever any of the following happens:

1. The app first starts (on boot, after force-stop and restart, etc.).
2. The phone is placed in the charger.
3. The phone is removed from the charger.
4. A new rule is enabled, or an existing enabled rule is modified.

The screenshot below shows the default settings for Rules 1 and 2. Rules 3, 4, and 5 permit setting times for profiles, like Rule 2, but have different defaults.

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-13c79cf222dad09c9abc8f97e184153ef7e41e18%2Frn-image40.png?alt=media)

**Apply Rule n**

|               |                                                                                                                                                      |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Type**      | Radio button                                                                                                                                         |
| **Default**   | False                                                                                                                                                |
| **Unique?**   | No                                                                                                                                                   |
| **Required?** | No                                                                                                                                                   |
| **Level**     | Any                                                                                                                                                  |
| **Notes:**    | Rule 1 is reserved for the Charging profile, to be used while charging the phone. Rules 2-5 are used for setting times to trigger specific profiles. |

**Select Profile to Switch for Rule n**

|               |                           |
| ------------- | ------------------------- |
| **Type**      | Dropdown menu of profiles |
| **Default**   | Normal                    |
| **Unique?**   | No                        |
| **Required?** | No                        |
| **Level**     | Any                       |
| **Notes:**    |                           |

**Type for Rule n**

|               |                                                                                                                                                    |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Type**      | Rule 1 is reserved for setting the profile to be used while charging the phone. Rules 2-5 are used for setting times to trigger specific profiles. |
| **Default**   | Normal                                                                                                                                             |
| **Unique?**   | No                                                                                                                                                 |
| **Required?** | No                                                                                                                                                 |
| **Level**     | Any                                                                                                                                                |
| **Notes:**    |                                                                                                                                                    |

**Select Time Slot for Rule n**

|               |                                   |
| ------------- | --------------------------------- |
| **Type**      | Dropdown menu of selectable times |
| **Default**   | Normal                            |
| **Unique?**   | No                                |
| **Required?** | No                                |
| **Level**     | Any                               |
| **Notes:**    |                                   |

## Fixes & Minor Enhancements

SAM-1029 The process for generating a self-signed certificate has been improved, to give you more flexibility when setting up the SAM Client app.

While running the application\_init script you will be prompted for various pieces of information, such as the hostname of your SAM appliance. This information will be used to generate a self-signed certificate and/or a Certificate Signing Request (CSR). Both of those specify a Subject Alternative Name field (SAN). The application\_init script will prompt you for a DNS hostname (and other DNS names, if relevant), which will all be placed in the SAN field. Now, by default, the IP address to which the DNS hostname resolves will also be added to the certificate or CSR SAN.

SAM-1076 Fixed an issue where in some circumstances adding more than one license key generated an error message.

## Known Issues

SAM-997 *(For users who followed this upgrade path: SAM 1.6 or 1.7 → 1.7.1 → 1.8.0)*\
In certain rare multiple-group configurations, when the lower-priority group sets an attribute that is not set in the higher-priority group, the phone will receive the default values instead of the configured values from the lower-priority group.

SAM-1004 We are investigating an issue with Auto Generated backup files (files named *backup.zip*, created when an administrator changes app configurations in SAM and saves), and have temporarily disabled the ability to download them.

*Workaround:* Manual backups can still be downloaded and used. Create a manual backup by going to the About page and clicking “Backup Now”. Manual backups in SAM are designated as “User Triggered”, and their file names include the date they were created – for example: backup.2021.04.07-10.18.13.zip.

SAM-1009 In the Buttons app settings, the Custom Intent Details fields (Button Down Action, Button Down Extras, Button Up Action, Button Up Extras) should only be available when “Enable User Control” of the button is set to “False” and “Custom” is selected from the resulting dropdown menu.

Currently the fields are visible regardless of the button’s configuration – however, unless you’ve selected the “Custom” option (and NOT “Custom 1”, “Custom 2”, “Custom 3”, or “Custom 4”), you should leave those fields blank. because except for the “Custom” option any parameters entered in those fields are ignored by the app.

*Workaround:* the Custom Intent Details fields should be left blank unless you do not enable user control and you choose “Custom” from the dropdown menu. *(NOTE: “Custom” only – **NOT** “Custom 1”, “Custom 2”, “Custom 3”, or “Custom 4”)*

SAM-1013 In the Barcode app General settings, while the Decode Session Timeout slider will let you enter any value between 5 and 99, **the value you enter MUST BE an increment of 5** or the handset will stay at the default value.

SAM-1020 Copy Configuration, used to copy device-level settings from one Versity phone to another, is not available in SAM 1.8.0. This functionality will be restored in a future release.\
*Workaround:* Manually configure a new device with another device’s settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spectralink.net/amie-essentials/release-notes/sam-1-8-0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.