> 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-9-1.md). # SAM 1.9.1 SAM Version: 1.9.1.xxx.1211 For use with Versity versions: * Versity 92 Series R1.8 using Android 10 * Versity 95/96 Series R2.8 using Android 10 * Versity 97 Series R13.1 using Android 13 ## Upgrading to SAM 1.9.1 You must be running SAM 1.9.0 to upgrade to SAM 1.9.1. (If you haven’t upgraded to SAM 1.9.0 yet, see [Upgrading to SAM 1.9.0](/amie-essentials/release-notes/sam-1-9-0.md#upgrading-to-sam-1-9-0).) 1. {% hint style="info" %} **Regarding PHY Mode in the VQO app** ***Administrators should not change this setting*** except under the guidance of a Spectralink representative. This parameter will be supported in a future release. (SAM-1286, X1-4946) {% endhint %} ## Enhancements ### Active Directory (AD) Enhancements #### Multiple UPN suffixes SAM 1.9.1 allows administrators to login using multiple User Principal Name (UPN) suffixes. When using AD, SAM now requires the entire UPN to be entered (not just the username) at the login dialog to authenticate with the AD server. This means users can login as, for example, ** if the AD server has users set up with those UPN suffixes. {% hint style="info" %} **If you’re using Active Directory for authentication in SAM 1.9.1, you need to type your full User Principal Name (UPN) at login** When using Active Directory authentication with SAM 1.9.1 (either after upgrading or in a new installation) administrators need to type their full UPN (for example, **) instead of just the username at login. This is a new requirement in SAM 1.9.1 that differs from previous SAM versions. (SAM-962) (If you’re using standard local database authentication, you can log in as with previous versions of SAM, without providing the full UPN.) {% endhint %} For more information regarding additional UPN suffixes, see [https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc756018(v=ws.10)](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc756018\(v=ws.10\)?redirectedfrom=MSDN) #### Organization Unit (OU) SAM 1.9.1 supports an optional Organization Unit (OU). If an OU is configured during SAM setup, SAM will authenticate users within that OU. If a user is not part of that OU, that user will not successfully authenticate. Example AD setup using an Organization Unit (OU) ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-d7d00df70f1b361f5559f80ad56e6a432618f60b%2Frn-image26.png?alt=media) {% hint style="info" %} **Do not use Secure LDAP (LDAPS) if using an OU** Secure LDAP (LDAPS) with an OU is not supported in SAM 1.9.1. Please contact Spectralink support if you have any questions regarding this. {% endhint %} At login after the setup above, the administrator needs to enter their full UPN – in the example below, instead of amieadmin: Login using the full UPN in SAM 1.9.1 ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-c07f4e5f037eb0c6334b1ce0d463fe2c6b638661%2Frn-image27.png?alt=media) ## Fixes & Minor Enhancements **Key** **Summary** SAM-997 Settings from lower hierarchy groups in multiple group configurations are now applied correctly. SAM-1268 Backup files now append SAM version information to the file name. SAM-1276 In Advanced Logging in the Logger app *Enable Logcat* set to true is shown to be the default setting. SAM-1279 New or updated app parameters are now handled correctly. SAM-1286 The new PHY mode setting in the VQO app is successfully integrated into SAM. SAM-1287 Device info settings in the Device Settings app are now handled correctly. --- # 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-9-1.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.