> 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-4.md). # SAM 1.4 SAM Version: 1.4.0.xxx.708 For use with all Versity versions: * Versity 92 Series R1.2 using Android 10 * Versity 95/96 Series R2.1 using Android 10 {% hint style="info" %} **SAM compatibility** SAM 1.4 was tested with Versity 92 Series 1.2 and Versity 95/96 Series 2.1. However, this version of SAM should work with any Versity smartphone software version. Any options that appear in SAM and 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 %} {% hint style="info" %} **What does the “xxx” stand for?** You will notice an “xxxx” in the version number. It signifies the build version of the VM the SAM software is installed on. When the SAM version is loaded at your site, the number will reflect the VM version in use at your site. The version number will replace the “xxxx” after install as displayed on the SAM About page. {% endhint %} {% hint style="info" %} **Updating SAM to the current release** You will see two files for this and future releases. The upgrade version is an incremental release used to update code to the next released version. It is a smaller file with a faster download time and recommended for incremental updates. Always use the appropriate incremental file for your current release. i.e. Do not skip versions. Use the next released version. The New install file contains the full code for a new SAM VM and software deployment. {% endhint %} {% hint style="warning" %} **The full release version will install a new instance of SAM on the VM** The New install version will install a new instance of SAM with an empty database. If SAM is already deployed in your facility, do not try to “upgrade” with the New install version. Use the upgrade version unless you intend to start over. {% endhint %} {% hint style="warning" %} **Your account number is critical to SAM setup** Due to repeated situations where the SAM server was installed with a phony customer account number, a caution note is added here to help all installers understand that the correct customer account number will prevent future configuration and installation problems. Spectralink assigns a unique account number to each customer which is linked to your SAM license. If a different number is used to configure the SAM server and it is not the assigned number, the SAM license will fail and the entire server must be reinstalled. {% endhint %} ## New Features ### Improved UI Continuing improvements in the UI to enhance legibility and option organization. ### Activate Beta features Beta features can be displayed in the SAM UI. In the banner, navigate to \[username]> Preferences> Enable Beta Features. s![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-62321d792e60d6961f3ef041c47f21c6e37cceaa%2Frn-image44.png?alt=media) ### Use of QR code to associate smartphones Currently offered as a Beta feature, SAM displays a QR code that can be used to associate a Versity smartphone running R2.1or above. The QR code can be printed or directly scanned by a phone using the same Wi-Fi network as SAM. On the Versity smartphone, activate the QR scan by opening the SAM Client app. Tap the Spectalink logo five times in rapid succession and the scanner will open. Point the scanner at the QR code. The phone will begin to associate with SAM. Note that the phone should not be controlled by an EMM when using this feature. ### Apps Enhancements The Versity Applications Administration Guide details new and improved enhancements made to Spectralink applications. The Release Notes for Versity 95/96 R2.1 and Versity 92 R1.2 provides more information about the changes to these apps: * Barcode * Batt Life * Biz Phone * Buttons * Device Settings * Logging * Sound Stage ## Fixes and Minor Enhancements Key Summary SAM-709 Copying configuration from one approved phone to another is working correctly. Copy an approved phone's configuration to a mac address is not. This mechanism is used for copying a configuration from a broken phone to a future phone, provided the mac address is known. Once the configuration is copied and a phone is approved with the same mac address, the configuration is automatically applied to it. There seems to be some validation used for the source phone since it is displaying this icon: . After entering a target mac address and selecting a category, and either entering a reason or not, the "COPY CONFIG" button fails to produce any result. No config is copied. ## Known Issues Admin Tip: FT and CCKM temporarily disabled To prevent inadvertent enabling of FT and CCKM these options have been disabled in the SAM 1.4 version. If FT/CCKM has been enabled previously, it will be disabled automatically by SAM during the upgrade to 1.4. Contact your service representative for assistance. Custom attributes can be used to program FT and CCKM in SAM. Refer to the *Versity Applications Administration Guide* and the *SAM Administration Guide* for complete information. --- # 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-4.md?ask=&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.