Not applicable to SBC SWe Edge.
The Application Solution Module (ASM) module is a separate, fully-functional server installed inside the SBC 1000/2000 chassis. Features of this ASM are managed from the SBC 1000/2000 Web Interface via the SBC 1000/2000 Communication Service.
An operating ASM has two software partitions:
- The Live partition, from which the system actively runs. Unlike the SBC 1000/2000 application partitions, this partition is always active on a running ASM.
- The Recovery partition, which contains a spare software image. You have the ability to re-initialize the ASM from this partition; an operation which replaces the live partition with the recovery image. This partition can also be updated directly as needed; refer to Updating the ASM Recovery Partition.
Software application support on the Application Solution Module (ASM) is limited:
- Microsoft Teams/Skype Survivable Branch Appliance (SBA)
- Microsoft Teams/Skype Resilient Branch Appliance (RBA) communicating with the Teams/Skype Front End
- Quality of Experience (QoE) Agent Server Gateway
Software must be provided by Ribbon and configured via the Ribbon-provided provisioning and management interface.
ASM Modes and Ribbon Support
The ASM operates in either of two modes, Appliance or Server.
- Appliance mode, in which the SBA utilizes Ribbon's security solution and the SBA default offering.
- Server mode, in which the SBA relies on the software you installed to provide alternative security/firewall protection or enhanced SBA operation. Operating in Server mode is valid.
By default, all ASMs are shipped in Appliance mode.
Server Mode
There are three actions that you can take to switch an ASM into Server mode:
- Installing third-party software that is not approved by Ribbon.
- Changing the Windows Role and Feature installed on the ASM in order to support additional Windows functionality. Using Remote Desktop or any other source.
- Running Windows Update without using the Ribbon UI or API (for example, using GPO or automatic Windows Update).
You can choose to operate in Server mode if:
- You want to follow their own internal security and update processes rather than the Ribbon standard processes regarding the Windows Server OS and/or the SBA application, or
- You want to deploy a firewall or antivirus solution not supplied by Ribbon, or
- You wish to use a third-party application (Call Recording, Auto Attendant, or IP PBX for example) that is not currently approved for use with the ASM. This includes common open-source IP PBX applications such as those offered by Asterisk.
Note on Server Mode and Ribbon Support
If you deploy in Server mode, Ribbon will continue hardware and software support to the base SBC, and all call flows and operations that do not involve the ASM. However, support for the ASM will be confined to hardware and ASM connectivity.
Third-Party Applications Supported in Appliance Mode
When the ASM is deployed in Appliance mode, Ribbon will provide support for the selected ("approved") third-party applications. Ribbon has approved select applications from the following vendors for use in Appliance mode.
Installing Unsupported Third-Party Applications
- Please contact your Ribbon service representative before installing any unsupported third-party applications.
- If you install third-party applications that Ribbon has not explicitly approved, and if you request ASM OS and application support (vs. hardware support only), Ribbon reserves the right to request that the ASM be re-initialized and returned to Appliance mode.
Windows Status Panel
The Support Mode value of Server in the Windows Status panel indicates that unsupported software has been installed on the ASM.
The only way to switch back to Appliance mode is to re-initialize the ASM.
Support Mode Definitions
Appliance Certified Mode: The ASM image contains v3.2 SbcComms or later and no third-party software has been installed.
Appliance Controlled Mode: The original ASM image was a version previous to 3.2 and has been upgraded.
Server: A third-party software installation has been detected by the ASM. Operating in Server mode is valid.
Additional Topics
- Viewing ASM Operational Status
- Powering the ASM ON and OFF
- Installing an ASM Package
- Approved Partner Solutions for ASM
- Installing Unsupported Third-Party Applications on the ASM via VM
- Viewing the Installed Packages on the ASM
- ASM Security
- Configuring the ASM IP Settings
- How to Enable and Provide Log Files From SBC and SBA
- Updating the ASM Recovery Partition
- Enabling and Disabling Remote Desktop on the ASM
- Changing the ASM Admin Password
- Rebooting and Resetting the ASM
- Re-initializing the ASM
- Viewing and Exporting Windows Event Logs on the ASM
- Managing the Windows Firewall on the ASM
- Managing ASM Virtual Machines
- Managing the SBC Communication Service
- Remote Update of ASM Recovery Partition
- Best Practice - Repurposing the Ribbon Cloud Link ASM for Skype for Business Server 2015 Standard Edition
- Best Practice - Common Use Cases for Repurposing the ASM for Third-Party Applications and Server Mode
- Upgrading the ASM Image From Windows-Only to Lync SBA
- Best Practice - Repurposing the Ribbon Cloud Link as a Lync/Skype SBA Device