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.

The Cisco VG420 Voice Gateway supports the following interfaces:

  • Gigabit Ethernet (GE)

  • Micro USB Console Port

  • RJ45 Console Port

  • FXS Ports

  • FXO Ports

  • Network Interface Module (NIM)

The VG400 ATA is made up of these components:

Two interfaces

  • Eight RJ11 FXS ports for analog devices.

    FXO ports are not supported on any VG400 models when connected to the Webex Calling platform.

  • WAN and LAN Ethernet ports.

  • The ATA has LEDs to provide status of the device.

Before you begin

  • Users and workspaces must be added to the organization in Control Hub before you can add a device to them.

  • When adding an ATA with more than one port, each port is treated as a separate device in Control Hub.

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

    Note: After the device is activated, you can’t access or change these network settings. A few examples of available network settings are: VLAN, IP address and subnet mask.

See steps to add an ATA device in Control Hub

Before you begin

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


From the customer view in, go to Users.


Select the user to modify and scroll to Devices.


Select the device you would like to add or modify.


Under Users on this Device, click Configure Ports.


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


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


Click Save.


Only workspaces without devices appear in the lookup.

If the device requires T.38 fax compression, check the box in the T.38 column or override user-level compression options, and then click Save.

A workspace can have an ATA (for example, used for fax machines).

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

Before you begin

Make sure you have the following equipment:

  • Ethernet cable to connect to your network.

  • Analog phone or fax machine to connect to your ATA.

  • Phone cable to connect your phone.

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

Once the ATA is manually reconfigured, any prior configuration settings on the device are overridden. Including the administrator password. Also, the device is usable only on the Cisco Webex network.

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

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

VG400: vg400-universalk9.17.06.03a.SPA.bin

VG420: vg420-universalk9.17.06.03a.SPA.bin

Manually reconfigure the VG420/VG400 ATA

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

  1. Connect the computer to the ethernet port marked ‘GE 0/0/1’ on the VG420/VG400 with an Ethernet cable.

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

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

  2. From the computer, to the web GUI of VG420/VG400 with default username cisco and password cisco2. If the Webex supported firmware is not installed on VG400/VG420 go to

    Section F. Convert an Existing Customer Owned Non-Webex VG420/VG400 to Work with the Webex Platform

Section B: Reset the VG420/VG400 to Factory Defaults

  1. From the VG420/VG400 web GUI, go to Administration > Reload.

  2. Select the Reset to Factory Default and Reload and click Apply button to reset the VG420/VG400 to factory default.

Section C: Verify and Configure the VG420/VG400 for Boot Parameters (Optional)

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

  2. Select Exec mode, input command show version, then click Run Command button to check the boot image and register setting.

    In the output of 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 command boot system flash <boot image name> to set boot image.

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

    The command boot systemboot system flash:vg420-universalk9.17.06.03a.SPA.bin sets boot image to vg400-universalk9.17.06.03a.SPA.bin

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

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

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

Section D: Configure VG420/VG400 for Webex License Report (Optional)

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

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

    license smart transport smart

    license smart url default

  3. Select Exec mode and run below 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 site through the valid user account.

Section E: Configure VG420/VG400 for Webex

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

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

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

    — voice service voip

    — rtp-port range 19560 19660

    — wxc-dm-url<Device Management URL>

    The valid setting for <Device Management URL>:

    Table 1.







    For example, use command wxc-dm-url for VG420/VG400 devices installed in the U.S. region.

  3. Click Run Command.

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

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

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

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

Section F. Convert an Existing Customer Owned Non-Webex VG420/VG400 to Work with the Webex Platform

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

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

    conf t

    voice service pots

    webex-calling license


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

    conf t

    license boot level uck9

    license boot level securityk9


  4. Run command to make license boot take effect on next boot:

    write memory

  5. Next, run commands to erase all existing config and reboot the VG400:

    write erase


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

Section G: Troubleshooting

If the device doesn’t come back or there are issues, perform these steps:

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

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

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



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