> 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-14.md).

# SAM 1.14

SAM Version: 1.14.0.xxx.1441

For use with Versity versions:

* Versity 92 Series R1.9 using Android 10
* Versity 95/96 Series R2.9 using Android 10
* Versity 95/96 Series R3.3 using Android 13
* Versity 97 Series R13.5 using Android 13

## Upgrading to SAM 1.14

### Upgrade paths for SAM 1.14

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

*(For example: to upgrade to SAM 1.14 from SAM 1.7, first upgrade to 1.9.0, then to 1.9.2, then to 1.10, and finally to 1.14.)*

{% hint style="info" %}
**If you need to upgrade to SAM 1.10 before upgrading to 1.14, use the same FQDN and IP address used in your prior SAM system**

When upgrading to SAM 1.10, use the same FQDN and IP address configured in your prior SAM system. If for some reason you need to change the IP address during a migration to 1.10 from your previous system, contact Spectralink Support for assistance, because your prior certificates will not work in the new system. (SAM-1419)
{% endhint %}

## Enhancements

### AMIE Agent

#### Use AMIE Gateway Communication

#### Cloud Communication Enrollment ID

#### Cloud Communication URL

These settings are now functional in SAM. If *Use AMiE Gateway Communication* is set to True, the *AMiE Gateway URL* field is visible for configuration; if set to False, the *Cloud Communication Enrollment ID* and *Cloud Communication URL* fields are visible instead.\
(APPS-7351)

### Biz Phone

#### Emergency Location

These new settings, *Emergency HELD Company ID* and *Emergency HELD URL*, support RedSky HELD integration. (SAM-1540)

### Device Settings

#### WPA3 provisioning

WPA3-Personal (PSK-FT-SAE), WPA3-Personal (PSK-SAE), and WPA3-Enterprise-128 Wi-Fi security protocols can now be configured in Wi-Fi Profile with an EMM. (NOTE: This setting is not part of the SAM interface and can only be configured with an EMM.) (APPS-7068)

#### New vibration settings

These 5 new settings, in the *Touch* section, are for 97 Series phones only: *Ringtone Vibration*, *Vibrate First Then Ring Gradually*, *Media Vibration*, *Alarm Vibration*, and *Notification Vibration*. (SAM-1534)

#### Wi-Fi Loss Alarm

The Wi-Fi Loss Alarm will alert a user if their phone has been disconnected from Wi-Fi for a defined period, configurable from 1 to 10 minutes. (The alarm would be triggered, for example, if a user has gone beyond the Wi-Fi footprint of their facility, or if they lose connectivity for some other reason.) (SAM-1542)

## Fixed Issues & Minor Enhancements

| **Key**  | **Summary**                                                                                                    |
| -------- | -------------------------------------------------------------------------------------------------------------- |
| SAM-1301 | SAM’s dropdown menus in the *Replace Control Characters* section of the **Barcode** app now display correctly. |
| SAM-1543 | The *PHY Mode* setting has been removed from the VQO app.                                                      |


---

# 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-14.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.