Note: It has come to my attention that out of the box, the AudioCodes Mediant Virtual Edition comes with two ESBC licenses that will support two concurrent calls and is available as a download from their support site. This makes it ideal for a Microsoft Lync 2010 or 2013 lab that would mimic a production environment without additional cost. This article steps you through the basic installation of the SBC.
One of the most recent AudioCodes offerings is the Mediant Virtual Edition. This software is aimed at firms who have chosen to virtualize their infrastructure as much as possible and strictly need an SBC (no PRI or other TDM modules). It runs software that is very similar to the physical Mediant series you may be used to running but has the additional resiliency advantages of living on within a virtual environment. At the time of this writing, the latest maintenance release (we’re in 6.8 right now) does not support transcoding. This means that if we’re going to send G.711 to Lync, we’re going to need to receive G.711.
Since these SBCs deal with real time communications, much like Lync, you’ll want to follow virtualization best practices. The documentation from AudioCodes suggests “Each vCPU must correspond to a physical CPU core fully reserved for the SBC VM.” The supported Hypervisors include VMware ESXi version 5.1 or later and Microsoft Hyper-V Server 2012 R2 or later. For our purposes today, I’ll be showing you the install from HyperV. We’ll avoid the virtual machine setup and jump right into the SBC install.
|Low Capacity Specification||High Capacity Specification|
|Virtual CPU||1 virtual CPU||4 virtual CPUs|
|Memory||2 GB||4 GB|
|Disk||10 GB||10 GB|
|Network Interfaces||2 vNICs are recommended, a third can be added for HA configurations||2 vNICs are recommended, a third can be added for HA configurations|
The software is available as an OVF for VMWare, a prepackaged virtual machine for HyperV, or as an ISO. I thought it would be the most interesting to walk through the ISO installation today.
Booting the ISO from our HyperV box shows us this boot screen. I love the colorful ASCII art, it’s rare that I get to see it these days. The SBC actually runs on a CentOS installation which you’ll see parts of as the installation occurs. From the boot screen, hit the Enter key.
You’ll see processes fly by… be patient.
You’ll then be dropped at a screen that’s going to prompt you to wipe the disk you created, hopefully this isn’t a shock or a big deal. Navigate to select the Re-initialize box and hit Enter.
The Linux packages will install, but it doesn’t take long. It will feel almost instant if you’re used to watching SQL Express instances install for Lync.
Once our SBC installation is complete, make sure to eject your virtual DVD or else we’ll be taken right back to the top screen. Once ejected, click the Reboot button.
After a quick boot, up pops our GRUB loader. Hit enter or let it select it as a default.
The next screen should be familiar if you’ve ever used a serial cable or the CLI of an AudioCodes Mediant before. To log in, we’ll use the default user name Admin and password Admin. Please note that I’ve capitalized the A intentionally as the username and password are both case sensitive.
Once we’re in, we can dig and look at the default IP address. To so do, type in “show voip interface network”. If you want to see what commands are available to you, you can download the CLI Reference Guide or type ?. Many of the commands you’ll see may be familiar if you’re familiar with the command line interface on popular routers and switches.
The default IP is 192.168.0.1 with a subnet mask of 255.255.255.0 on the default VLAN. You can either set another machine up with an IP on this network and connect right away, or change the IP now through the CLI. To change the IP from the CLI, we’ll need to enter enable mode by typing “enable”. Now, we need to get into config mode. Since the network settings are found in the VoIP section of a Mediant, we’ll type “configure voip”. We’ll switch to our default network interface by typing “interface network-if 0”. Now we can use the ip-address, prefix-length, and gateway commands to set our IP, subnet, and default route respectively. This can be seen in the image below. Once finished, type activate and hit Enter. You’ll see a note that the configuration won’t take effect until we reset. To reset, type “exit” to get out of config mode, then type “reload now”.
That’s it for getting it accessible from the network. In the screenshot below you can see us using the web interface. If you’re a partner you can use the AudioCodes SBC Wizard to configure it, or set it up from scratch.
Here’s the part I love for the lab: It comes pre-licensed with 2 SBC sessions. That will allow two concurrent calls through the device without additional purchase or licensing. You can then connect this to a trunking provider like Intelepeer or FlowRoute for inexpensive calling over the Internet into Lync!
We’ll stop here because we have our SBC up and running. The configuration is up to you, though if there’s interest I’ll do a basic walkthrough blog of that as well. If you’re new to AudioCodes, they have remote implementation services available as well for a no-fear installation. Please let me know if you have any comments, questions, or corrections and thanks for reading!