> 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-2.md). # SAM 1.2 SAM Version: 1.2.0.xxx.591 For use with all Versity versions. {% hint style="info" %} **SAM compatibility** SAM 1.2 was tested with Versity 1.7. 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" %} 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. Caution: Your account number is critical to SAM setup 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 Please refer to the *Spectralink Application Administration Guide* for complete information about all features mentioned here. ### Support added for AMiE and SSO The AMiE Analytics system enables administrators to keep track of real time device metrics on a management console. Single sign-on is an authentication system that allows one Versity smartphone to be shared by multiple users, each with their own login. ### Remove security vulnerabilities Spectralink conducted a comprehensive security scan to identify and correct any security vulnerabilities. E-1159 ### Add support for encrypted Active Directory integration Installations can now specify the SSL port and the associated encryption used for Active Directory. E-1212 ### Add support for SAN Installations can specify one or more Subject Alternative Names (SAN) as part of the SAM setup process. When the CSR is generated, the SAN names are included. S-317 ### Add support for wildcard certificates Wildcard certificates are now supported for domain certificates allowing use of a single certificate for all servers in the environment. E-1313 ### Barcode app—add support for setting supplemental options A conflict between EAN and UPC values prompted a new value for EAN supplementals. S-277 ### Add support for Cisco advanced contact search in Biz Phone S-457 Add Cisco Contact Search and Advanced contact search enable to the Cisco Solution Partner Program settings. ### Add ability to export MAC addresses from Holding Area (.csv) As a workflow improvement, the ability to export the device list as CSV file. The following values are included for each device. (S-266, S-301) * * MAC address * Device serial * Last heartbeat * Groups * SIP extension * Device Info 1 * Device Info 2 * Device Info 3 * Device Info 4 * Status * Device model * Software * AP SSID ### Device Settings rearrangement, Quick Settings tiles support User restriction settings (S-348) are added and grouped to support quick settings and other user restriction options. Several admin settings added: Edit device name (S-464), Application battery optimization whitelist (S-374), Allow battery saver (S-379), SKeyboard and Google Voice Typing (S-375), Sleep, Touch, Emergency, Camera and Network settings to align with Versity. ### PTT Edits to remove deprecated settings including Emergency and Priority channel designations and transmit audio frame size. S-483, 485, 486 ### Sys Updater Add ability to update LTE models over a metered network by adding the “allow OTA over metered network” option. This option enables Versity to use a metered network to contact the facility system over a VPN connection in order to download a code update. Such service may be quite expensive and you should be aware of what data charges will be incurred before enabling this option. S-476 Revert last upgrade. Introduced in R1.6, Revert last upgrade allows an administrator to revert to a previous upgrade. S-380 ## Fixes and Minor Enhancements Key Summary [SAM-216](https://jira.spectralink.com/browse/SAM-216) Implement backup strategy - take backup nightly when config changes [SAM-240](https://jira.spectralink.com/browse/SAM-240) Add Custom Apps tab to support new apps being tested SAM-299 Add reason fields for copy config (for future use) [SAM-305](https://jira.spectralink.com/browse/SAM-305) Enhance SAM Security: Postgres SAM-343 Add custom intents to Buttons app options [SAM-349](https://jira.spectralink.com/browse/SAM-349) Password for database recovery (postgres) may not use special characters SAM-351 Add ability to disable call waiting [SAM-352](https://jira.spectralink.com/browse/SAM-352) Add new string to list package names for the "battery optimization" whitelist to SAM's device settings tab [SAM-353](https://jira.spectralink.com/browse/SAM-353) SAM Custom Attribute shows correct values on upgrade [SAM-365](https://jira.spectralink.com/browse/SAM-365) Document how to backup, retrieve backup and restore to a new SAM [SAM-374](https://jira.spectralink.com/browse/SAM-374) Default value for new setting app\_battery\_opt\_whitelist is now sent after upgrade [SAM-375](https://jira.spectralink.com/browse/SAM-375) Spectralink secure keyboard key(s) SAM-433 Add capability to manage SlnkSSO settings SAM-451 Add support for full state name when generating certificate --- # 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-2.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.