As a fully managed device on the Webex Calling platform, the VG420/VG400 ATA offers:

  • A higher capacity 8-port option from the standard 2-port device, for Webex Calling customers

  • A direct migration path for UCM customers moving to Webex Calling.

  • Use for legacy PBXs that don't work with SIP trunking.

Hardware specifications

The Cisco VG420 Voice Gateway supports the following interfaces:

  • 2-Gigabit Ethernet (GE) interfaces, one for LAN and the other for configuration

  • RJ45 Console Port

  • FXS Ports

The Cisco VG420 Voice Gateway has these components:

  • Micro USB Console Port
  • FXO Ports
  • Network Interface Module (NIM)

The Cisco VG400 Voice Gateway has these components:

  • Eight RJ11 FXS ports for analog station devices

  • FXO ports aren’t supported on any VG400 models when connected to the Webex Calling platform.

Add an ATA device in Control Hub

Before you begin

  • Add the VG400 as a device in the Control Hub and create the workspace at the same time.

  • When adding an ATA, configure all network settings before activating the device.

    Configure network settings before activating the device in Control Hub. After you activate the device, you can't access VG through the Web GUI or SSH. This is because you configured the device in Control Hub and have limited access. You can’t configure network settings such as VLAN, IP address, and subnet mask.

Use the same steps to add a VG400, VG410, or VG420 device.

Configure the ATA device for users and workspaces

Before you begin

Add VG400, VG410, or VG420 to a workspace to use for fax and overhead paging service.

Configure the ports on the VG400 ATA device to a user within Control Hub

1

From the customer view in https://admin.webex.com, go to Users.

2

Select the user to modify and scroll to Devices.

3

Select the device that you would like to add or modify.

4

Under Users on this Device, click Configure Ports.

5

To add a shared port configuration, click the + icon.

6

Enter the name or phone number and select from the options displayed.

7

Click Save.

You see workspaces without devices, user lines, and empty workspaces in the lookup.

If the device requires T.38 fax compression, check the box in the T.38 column under Customized Behaviors. Else you can override the user-level compression option and then click Save.

To assign a number to a port, create an empty workspace and assign a number to the workspace, then add it to the Voice Gateway device.

Onboard the ATA device for Webex Calling

Under certain circumstances, you may need to manually reconfigure the Cisco VG420, VG410, or VG400 ATA for it to connect to the Webex Calling platform.

Before you begin

Make sure you have the following equipment:

  • A computer with an Ethernet interface

  • An Ethernet cable to connect to your network, and another to connect to your PC.

  • An analog phone, butt set, or other device along with an RJ-11 phone cable to test the analog ports.

  • Uninterruptible power supply (UPS) to provide backup power.

After you onboard the ATA to the Control Hub, any prior configuration settings on the voice gateway are overridden, including the administrator password. Also, the device is usable only with Webex Calling.

To use the device on any network other than the Webex Calling, reset the device to the Cisco factory default configuration.

The supported firmware for a VG420/VG410/VG400 ATA to connect with the Webex platform is as follows:

Voice Gateway device modelSupported firmware
VG400

vg400-universalk9.17.12.02.SPA.bin

VG410

vg4x0-universalk9.17.12.02.SPA.bin

VG420

vg420-universalk9.17.12.02.SPA.bin

The following sections show the reconfiguration steps for the VG400/VG410/VG420 to work with Webex. Perform the Section A to E on VG400/VG410/VG420 that is loaded with Webex supported firmware and with a preinstalled Webex Calling license. If the VG400/VG410/VG420 doesn’t have Webex supported firmware and preinstalled Webex Calling license, then first go to Section F.

Manually reconfigure the VG420/VG410/VG400 ATA

Section A: Log in to the VG420/VG410/VG400 through Web GUI

  1. Connect a computer to the Ethernet port labeled ‘GE 0/0/1’ on the VG420/VG410/VG400 with an Ethernet cable.

    • The ‘GE 0/0/1’ port is the management port of VG. Its default IP address is 192.168.253.253.

    • The computer should get the IP address 192.168.253.254 automatically from DHCP from the VG420/VG410/VG400.

  2. From the computer, browse to the Web GUI of the VG420/VG410/VG400 using http://192.168.253.253. Login with the default username cisco and password cisco2. If the Webex supported firmware isn’t installed on VG400/VG410/VG420, go to Section F

Section B: Verify and configure the VG420/VG400/VG410 for Boot parameters (Optional)

  1. From the VG420/VG400/VG410 web GUI, go to Administration > Command Line Interface page.

  2. Select the Exec mode and input the show version command. Click Run Command to check the boot image and register setting.

  3. In the output of the show version command, the line starting with “System image file” shows the current boot image. Make sure you configure the Cisco Webex approved image. If not, select Configure mode, run the command boot system flash <boot image name> to set boot image.

    ModelBoot system flash command example

    VG400

    boot system flash:vg400-universalk9.17.12.02.SPA.bin

    VG410

    boot system flash:vg4x0-universalk9.17.12.02.SPA.bin

    VG420

    boot system flash:vg420-universalk9.17.12.02.SPA.bin

    Example: The command boot system flash:vg400-universalk9.17.12.02.SPA.bin sets boot image to vg400-universalk9.17.12.02.SPA.bin

  4. The last line of the output starting with “Configuration register” shows the register setting. Make sure the value 0x2102 is configured here. If not, select Configure mode and run config-register 0x2102 command to set the value.

  5. If the Register configuration gets changed at Step 2, select Exec mode and run the command write memory to save the changes.

  6. If the boot image configuration gets changed at Step 2, go to the Administration > Reload page, select the Save Configuration and Reload option, and click Apply to reboot the VG420/VG410/VG400 with the new image. It takes the VG420/VG410/VG400 about 10 minutes to bootup.

Section C: Verify VG420/VG410/VG400 for required licenses (Optional)

  1. From the VG400/VG410/VG420 web GUI, go to Administration > Command Line Interface page.
  2. Select Exec mode, input the show license summary command, then click Run Command to check the installed licenses.
  3. In the output of show license summary command, the section starting with “License Usage” shows the current installed licenses. Make sure that these three required licenses are in use: “uck9”, “securityk9”, “webex_calling”. If not, go to Section F.

Section D: Configure VG420/VG410/VG400 for Webex license report (Optional)

  1. From the VG420/VG400/VG410 web GUI, go to Administration > Command Line Interface page.

  2. Select Configure mode and input the following commands to set smart license reporting parameters:

    license smart transport smart

    license smart url default

  3. Select Exec mode and run the following commands to trigger smart license reporting:

    — license smart trust idtoken <token> local force

    — license smart sync local

    You can find the token at Smart Software Manager from the https://software.cisco.com/ website with a valid user account.

Section E: Configure VG420/VG410/VG400 for Webex

Make sure to perform the procedures in sections A, B, C, and D before starting this step.

  1. From the VG420/VG400/VG410 web GUI, go to Administration > Command Line Interface page.

  2. Select Configure mode and input the following commands to set the local SRTP port and Webex Device Management URL:

    — voice service voip

    — wxc-dm-url <Device Management URL>

    The valid setting for <Device Management URL>:

    U.S

    https://cisco.sipflash.com

    UK https://cisco-uk.bcld.webex.com/

    EU

    https://cisco.broadcloud.eu

    EUN

    https://cisco-eun.bcld.webex.com

    AU

    https://cisco.broadcloud.com.au

    CA

    https://cisco-ca.bcld.webex.com

    JP

    https://cisco-jp.bcld.webex.com

    For example, use the wxc-dm-url https://cisco.sipflash.com command for VG420/VG410/VG400 devices installed in the U.S. region.

  3. Click Run Command.

  4. Write down the VG420/VG410/VG400’s MAC address shown at the output screen after running the commands.

  5. Add the VG420/VG410/VG400 MAC address in the Control Hub.

  6. Select Exec mode and input the command write memory. Click Run Command button to save the configuration.

  7. Connect ‘GE 0/0/0’ port on VG400 to the internet through DHCP.

Wait about five minutes after Step 7. The VG420/VG410/VG400 is configured and ready for use with the Cisco Webex network.

Section F. Convert an existing customer owned non-Webex VG420/VG410/VG400 to work with the Webex platform

  1. Upgrade the VG420/VG410/VG400 to the Webex approved image (example: vg400-universalk9.17.12.02.SPA.bin).

  2. From the VG420/VG410/VG400’s console port, run the below commands to add the Webex Calling license:

    conf t

    license boot level uck9

    license boot level securityk9

    end

  3. Run the command to make uck9 and securityk9 license take effect on the next boot and reboot:

    write memory

    reload

  4. From the VG420/VG410/VG400’s console port, run the below commands to add uck9 and securityk9 licenses:

    conf t

    voice service pots

    webex-calling license

    end

  5. Run the write memory command to ensure that the license boot is applied during the next boot-up.

  6. Run the following commands to erase all existing config and reboot the VG400:

    write erase

    reload

  7. After the VG420/VG400 boots up, follow sections A, B, C, D, and E to configure the VG420/VG400 device.

Troubleshooting

If the device is unable to accept Webex Calling configuration or is unable to register with Webex Calling, perform these steps:

  1. Verify that the device MAC address is correct in the Control Hub.

  2. Verify that the device MAC address is assigned to a user/phone in the Control Hub.

  3. Before downloading configuration from Webex Calling, use the show voice port summary command and make sure that all the ports are in onhook state. If any port is in the offlhook state, the Voice Gateway won't process the configuration file downloaded from the Webex Calling.

For the VG410 only, if the device still can't register using the two steps, verify the “vdsp” application is running with the following steps:

  1. From the VG410 console port, run show app-hosting list command and verify that the “vdsp” is in RUNNING state.
  2. If not, run voice vdsp removecommand to remove the “vdsp” application.
  3. Run show app-hosting list command repeatedly and verify that the “vdsp” application is removed.
  4. Run voice vdsp install command to install the “vdsp” application.
  5. Run show app-hosting list command repeatedly and verify that the “vdsp” is in RUNNING state.

If the device still experiences issues, contact your technical support team for assistance.

Troubleshoot the deployment of your Cisco Voice Gateway

Issue

Action

Can’t onboard a device:

Verify the initial setup by local login to the ATA device Web GUI.

  • Connect to the device to enter the DM-URL

No dial-tone on FXS ports:

Verify network settings and connectivity to the internet

Wrong DN provisioned to a FXS port:

Check setup in Control Hub