> 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-12.md). # SAM 1.12 SAM Version: 1.12.0.xxx.1432 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.0 using Android 13 * Versity 97 Series R13.3 using Android 13 ## Upgrading to SAM 1.12 ### Upgrade paths for SAM 1.12 * \*If you’re running **SAM 1.10** or \*\*1.11\ \*\*\*1.10 or 1.11 → 1.12\ You can upgrade directly to 1.12. * \*If you’re running \*\*SAM 1.9.1 or 1.9.2\ \*\*\*1.9.1 or 1.9.2 → 1.10 → 1.12\ First upgrade to 1.10, then 1.12. * \*If you’re running **SAM 1.9.0**\ \*1.9.0 → 1.9.2 → 1.10 → 1.12\ First upgrade to 1.9.2, then to 1.10, then to 1.12. * \*If you’re running **SAM 1.4.1 to 1.8**\ \*1.4.1 through 1.8.0 → 1.9.0 → 1.9.2 →1.10 → 1.12\ First upgrade to 1.9.0, then to 1.9.2, then to 1.10, then to 1.12. * \*If you’re running a version of **SAM before 1.4.1**\ \*1.4.0 or earlier → 1.4.1 → 1.9.0 → 1.9.2 →1.10 → 1.12\ First upgrade to 1.4.1, then to 1.9.0, then to 1.9.2, then to 1.10, then to 1.12. {% hint style="info" %} **If you need to upgrade to SAM 1.10 before upgrading to 1.12, 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 ### Biz Phone #### Send Tones on Local Call Hold When this setting (in the *SIP Registration 1* section) is enabled, a brief tone will sound every five seconds when a call is placed on hold, to confirm to the party on hold that the call is still active. This is useful when working with call servers that do not provide hold tones or hold music. This setting is disabled by default. (X1-5679) #### Call Park Settings ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-615761e3e562233b894aa83ffdd832df4bd96b69%2Frn-image13.png?alt=media) Call parking lets a user put a call on hold and then retrieve the call from another phone. When a call is parked it is transferred to a call park extension. The parked call can then be retrieved by calling that extension. Call parking is disabled by default. If enabled (by setting *Allow Call Park* to **True**), an administrator can configure up to 5 different call park extensions. The extension number is entered into the *Call Park Extension* field. Some call servers require a prefix to be appended to an extension number in order to retrieve a parked call. In that circumstance the prefix and extension number can be entered into the optional *Call Retrieval Extension* field. (If this field is left blank the Call Park Extension number will be used to retrieve the parked call.) See the *Versity Apps Admin Guide* for more information on configuring and using call park. (APPS-6520) ### SAFE #### Use Multiple Numbers as per Panic Button Press Event (DEMO ONLY) #### Secondary Emergency Dial Number (DEMO ONLY) {% hint style="warning" %} **These are demo features!** Demo features are new capabilities being considered for integration into the Spectralink lineup. They have not been fully tested, so there may be some unexpected behaviors and limits to functionality. {% endhint %} These new settings, found under the *Emergency call* tab of the *SAFE* app, give Versity phones the ability to call 2 different emergency numbers, depending on how the user presses the Panic Button: 1 long press would call one number, while 2 short presses would call a different number. For example: in a hospital setting, a long press might call security while 2 short presses would call for immediate medical assistance. When this demo feature is enabled, its behavior depends on the configuration of the *Panic Button* in the *Panic Alarm* tab, as follows: If the Panic Button is set to **Long press**, then a long press will call the Emergency Dial Number and 2 short presses will call the Secondary Emergency Dial Number. If the Panic Button is set to **Two short presses** or **Two short or one long press**, then 2 short presses will call the Emergency Dial Number and 1 long press will call the Secondary Emergency Dial Number. If the SAFE app has been configured to sound an audible alarm, using the Panic Button in any of the above scenarios will trigger that alarm. This demo feature is disabled by default. To configure it in SAM: * Set *Use Multiple Numbers as per Panic Button Press Event (DEMO ONLY)* to **True** * Enter the desired secondary emergency number in the *Secondary Emergency Dial Number (DEMO ONLY)* field. For more information regarding this feature see the *Demo Features* section of the *Versity Apps Administration Guide*. (SAM-1500) ## Fixed Issues & Minor Enhancements **Key** **Summary** ESCSAAS-147 Fixed a UI issue where columns did not align properly on some pages. SAM-1440 The *Sounds* section of the **Device Settings** app now works as expected if an administrator deletes a sound from the sets of available Ringtone, Notification, or Alarm sounds. SAM-1449 In the **Skeyboard** app the sliders for *Keypress Vibration Duration*, *Keypress Sound Volume*, and *Key Long Press Delay* increment in more manageable units. SAM-1452 Secure LDAP (LDAPS) with an OU is now supported. SAM-1456 Fixed an issue where in certain rare circumstances the SAM instance account number becomes corrupted and invalid. X1-6399 The **Buttons** app setting labeled *Custom* has been renamed *Programmable*, to differentiate it from the *Custom 1-4* settings. (The *Programmable* setting can be used to configure a button’s presses and releases to trigger intents with programmable intent details; the *Custom 1-4* settings are reserved for external app programmers. --- # 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-12.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.