Configuration · guide

Setting up analog devices and ATAs on Webex Calling

Verified 2026-09-30 · 78 sources · tier 1–2

For Webex Calling administrators and partner engineers deploying analog devices and analog telephone adapters..

Analog telephone adapters (ATAs) connect non-IP hardware such as analog phones, fax machines, and overhead paging systems to Webex Calling 19. The Cisco analog telephone adapters listed as supported for Webex Calling are the ATA191 Multiplatform, ATA192 Multiplatform, VG400 ATA, VG410 ATA, and VG420 ATA 34.

Before you start

Cisco cautions that data devices such as fax machines and modems may not function optimally with an ATA and recommends a dedicated PSTN line for best performance 36.
If you use the Cisco ATA 191 or Cisco ATA 192, each physical unit provides 2 RJ-11 FXS ports (PHONE 1 and PHONE 2) 2829.
For VG4xx models, only FXS ports are supported with Webex Calling; FXO and ISDN interfaces are not supported 63.
Note that onboarding a VG4xx ATA overwrites its existing configuration, including the administrator password, and the unit can only be used with Webex Calling afterward 78.
Users with a Webex Calling Standard license cannot be assigned to VG4xx ATA ports 67.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

What will the analog lines plug into?

Will any of these ports carry a fax machine, and if so how should the fax travel?

Does this site use Webex Calling enhanced emergency calling (E911 with RedSky), or does it rely on the PSTN provider's emergency handling?

Three questions. One permanent page you can send to your manager.

Step 1 Inventory analog lines and separate data endpoints

Do

Identify every analog endpoint at the site intended for connection, including handsets, fax machines, and paging equipment 19. Check modems and fax machines against Cisco's recommendation for dedicated PSTN lines 36. Verify that the required port count matches the capacity of your chosen hardware 2829.

Verify

Suggested check: verify each analog endpoint is listed and assigned to a port plan or kept on an existing line.

Rollback

Suggested rollback: retain existing connections on their original lines.

Step 2 Prepare user accounts and workspaces in Control Hub

Cisco ATA 191 or ATA 192 (two analog ports per unit)

Do

Prepare or identify the user account that will own the ATA in Control Hub 3. For secondary ports, configure device-less workspaces or users, noting that only workspaces without existing devices appear when searching for shared port assignments 3. Note that multi-port ATAs treat each port as a separate device in Control Hub 16.

Verify

Suggested check: verify in Control Hub that the target user exists and any planned secondary workspace has no device assigned.

Rollback

Suggested rollback: delete any newly created workspace in Control Hub.

FXS ports on a Cisco VG400, VG410, or VG420 ATA

Do

Create one workspace or user for each port planned on the VG4xx ATA 57. For each workspace or user, assign an extension of at least 4 digits, because shorter extensions do not register on a VG4xx ATA port 59. Assign a license other than a Webex Calling Standard license to user accounts, as Standard licenses are not supported on VG4xx ATA ports 67. Do not assign virtual lines, which cannot be assigned to a VG4xx ATA 68. Ensure each workspace or user is mapped to only 1 line, as a workspace or user can occupy only 1 line of a given VG4xx ATA 71. Designate the owner for port 1 deliberately, because the workspace or user selected when adding the gateway is permanently assigned to ATA port 1 73.

Verify

Suggested check: verify that each planned owner has a valid non-Standard license and an extension with sufficient digits.

Rollback

Suggested rollback: delete any workspaces created for the gateway ports in Control Hub.

Step 3 Configure network settings and verify firmware

Cisco ATA 191 or ATA 192 (two analog ports per unit)

Do

Configure any site-specific network parameters such as VLAN, IP address, and subnet mask before device activation, as these settings cannot be accessed or altered after activation 15. If using an ATA 192, note that it has an additional ETHERNET LAN port that the ATA 191 does not have 24. For an ATA 191 or ATA 192, the device can be restored to factory defaults by pressing and holding the RESET button on the back panel for about 10 seconds 78. To check IP addressing via the IVR, connect an analog phone, press **** to access the IVR, and dial 110# to hear the assigned IP address 910. Ensure the ATA firmware is at 11-1-0MPP0414-004 or later 1314.

Verify

Suggested check: verify that the device responds on its network address and the firmware meets the minimum version requirement.

Rollback

Restore default settings by holding the RESET button on the back panel for about 10 seconds 78.

FXS ports on a Cisco VG400, VG410, or VG420 ATA

Do

Access the gateway's command-line interface and verify the installed licenses using show license summary 65. Confirm that uck9, securityk9, and webex_calling licenses are present 65. Confirm that the platform is running an approved IOS XE 17.18.1a universalk9 image (vg400-universalk9.17.18.1a.SPA.bin, vg4x0-universalk9.17.18.1a.SPA.bin, or vg420-universalk9.17.18.1a.SPA.bin) 62.

Verify

Confirm with show license summary that uck9, securityk9, and webex_calling appear active 65.

Rollback

Suggested rollback: reload the gateway with its prior system software or configuration file if licensing or images do not match.

Step 4 Provision the adapter to Webex Calling

Cisco ATA 191 or ATA 192 (two analog ports per unit)

Do

Add the ATA under the owning user in Control Hub using the unit's MAC address 3. Once provisioned in Control Hub, the ATA 191 and ATA 192 onboard automatically through EDOS on the initial factory boot or after a factory reset 56. If provisioning manually, access the ATA web configuration utility, navigate to Voice > Provisioning, enter the regional server address into the Profile Rule field (https://cisco.sipflash.com/ for North America or https://cisco.broadcloud.eu/ for Europe), and submit 1718.

Verify

Suggested check: verify that the device completes onboarding and shows an online status.

Rollback

Reset the ATA to factory defaults by pressing and holding the RESET button on the back panel for about 10 seconds 78.

FXS ports on a Cisco VG400, VG410, or VG420 ATA

Do

In the VG4xx ATA command-line interface, enter voice service voip configuration mode and specify the regional device management URL with wxc-dm-url <Device Management URL>, using https://cisco.sipflash.com for the United States 77. In Control Hub, navigate to Devices, add the gateway using its MAC address, and assign port 1 to the designated initial workspace or user 73. Note that onboarding will overwrite the existing configuration and administrator password 78.

Verify

Suggested check: verify that the gateway contacts the device management URL and registers the initial port in Control Hub.

Rollback

Reset the device to Cisco factory default settings to clear the Webex Calling configuration 60.

Step 5 Assign ports and configure line settings

Cisco ATA 191 or ATA 192 (two analog ports per unit)

Do

In Control Hub, go to Management > Users > the user > Devices > the device > Users on this Device > Configure Ports 3. Add a shared port configuration by searching for the target user name or phone number 3. Device-level parameters can be modified under Management > Devices > the device > All Configurations 4. Resync the device from Control Hub or from the unit itself after changing settings to apply them 20.

Verify

Suggested check: place test calls to and from both ports to verify line signaling and dial tone.

Rollback

Suggested rollback: remove the secondary user or workspace assignment from the ATA port in Control Hub.

FXS ports on a Cisco VG400, VG410, or VG420 ATA

Do

In Control Hub, open Devices, select the VG4xx ATA, select Configure ports, and assign the remaining preconfigured users and workspaces 57. Remember that VG4xx ATA ports are numbered starting from 0, whereas other ATA ports are numbered from 1 74. For analog handsets requiring ring-down or instant dial functionality, configure hot-line on the designated port 64. Do not push configuration updates while a port is active; on release 17.18.1a, pushing changes to an active port causes it to deregister after processing the file 55.

Verify

Suggested check: verify that test calls ring on the corresponding physical ports according to zero-based indexing.

Rollback

If a port deregisters due to a push while active, push the configuration again after the port becomes idle 55.

Step 6 Configure fax transmission mode

Cisco ATA 191 or ATA 192 (two analog ports per unit) + No fax machine on these ports

Do

Leave T.38 fax compression unchecked across all ports in Control Hub 21.

Verify

Suggested check: verify that normal voice calls operate correctly on the configured lines.

Rollback

Suggested rollback: leave settings untouched.

Cisco ATA 191 or ATA 192 (two analog ports per unit) + Fax over T.38 relay

Do

Connect the fax machine directly to the ATA phone port without any extension or splitter, using overseas mode if available or a low transmission speed 4647. In Control Hub, open Configure Ports for the device, check the box in the T.38 column for the assigned port, and save 21. The ATA 191 Multiplatform and ATA 192 Multiplatform data sheets list real-time Group 3 fax over IP via T.38 fax relay 2627.

Verify

Suggested check: send and receive a multi-page test fax to confirm transmission reliability.

Rollback

Clear the T.38 checkbox for the port in Control Hub and save 21.

Cisco ATA 191 or ATA 192 (two analog ports per unit) + Fax as ordinary audio (G.711 pass-through), T.38 left off

Do

Connect the fax machine directly to the ATA phone port without any splitter or extension, and configure the machine for overseas mode or low speed 4647. Leave the T.38 option unchecked in Control Hub, using Group 3 fax pass-through via G.711 262721.

Verify

Suggested check: transmit and receive a test document to ensure G.711 pass-through operates reliably.

Rollback

Suggested rollback: if pass-through fails, evaluate enabling T.38 relay on the port 21.

FXS ports on a Cisco VG400, VG410, or VG420 ATA + No fax machine on these ports

Do

Leave T.38 fax compression disabled on the VG4xx ATA port in Control Hub 75.

Verify

Suggested check: verify that normal voice calls operate correctly on the configured lines.

Rollback

Suggested rollback: leave settings untouched.

FXS ports on a Cisco VG400, VG410, or VG420 ATA + Fax over T.38 relay

Do

In Control Hub, access port settings for the VG4xx ATA and enable T.38 compression on the port 75. Enabling T.38 provides SIP-based T.38 fax relay and overrides the default audio codec for that port 6175.

Verify

Suggested check: transmit a test fax across the configured port to confirm negotiation.

Rollback

Disable the T.38 option on the VG4xx ATA port configuration in Control Hub 75.

FXS ports on a Cisco VG400, VG410, or VG420 ATA + Fax as ordinary audio (G.711 pass-through), T.38 left off

Do

Leave T.38 compression disabled on the VG4xx ATA port in Control Hub to use G.711 fax passthrough 6175.

Verify

Suggested check: execute a test fax transmission through the FXS port.

Rollback

Suggested rollback: switch the port to T.38 mode in Control Hub if transmission quality requires relay 75.

Step 7 Configure Emergency Callback Numbers (ECBN)

Do

Configure an Emergency Callback Number (ECBN) for each analog line user or workspace 41. Selectable options are the line's own phone number, the location default ECBN, or another assigned number belonging to a user in the same location 41. For extension-only workspaces or users, select either the location default ECBN or an assigned user number, because the option to use their own phone number does not appear 40.

Verify

Suggested check: open the calling settings for each workspace and confirm that a dialable callback number is assigned.

Rollback

Suggested rollback: reselect the previous ECBN configuration under the workspace calling parameters.

Step 8 Configure emergency location routing

Enhanced emergency calling (E911) is in use for this location

Do

In the RedSky administrative portal, configure a location mapped against the caller ID of each analog line 38. This manual entry is required because ATAs do not communicate with the location service 38. 47 CFR 9.16(b)(3)(i) requires an on-premises fixed telephone associated with a multi-line telephone system to provide automated dispatchable location no later than January 6, 2021 32.

Verify

Suggested check: verify that the caller ID and location entry appear active in the RedSky portal.

Rollback

Suggested rollback: adjust or remove the caller ID entry in the RedSky administration portal 38.

Emergency calls are handled by the PSTN provider using the emergency callback number

Do

Coordinate with your PSTN service provider to verify that the ECBN assigned to the analog lines is associated with the correct physical address on record for emergency dispatch 41.

Verify

Suggested check: verify with the carrier that the address registration matches the device's physical installation location.

Rollback

Suggested rollback: update the registered address record with the provider or reassign the ECBN to an existing verified number.

Step 9 Configure emergency notifications and direct dial

Do

47 CFR 9.16(b)(1) requires a multi-line telephone system to be configured so that a user can directly call 911 from any station equipped with dialing facilities without dialing any additional digit, code, prefix or post-fix 31. Configure emergency call email notifications at Services > PSTN & Routing > Settings > Emergency call notification for the organization, or at Management > Locations > the location > Emergency Calling > Emergency Call Notification 44.

Verify

Suggested check: verify in Control Hub that the designated recipient email address is configured under Emergency Calling.

Rollback

Disable or clear the email address under Emergency Call Notification settings in Control Hub 44.

Step 10 Plan site survivability and failover

Do

If deploying local survivability gateways, verify that your analog adapters are supported 49. The analog endpoints listed as supported with Webex Calling site survivability are the VG400, VG410 and VG420 ATAs and the Cisco ATA 191 and 192 49. VG4xx ATA failover to Webex Calling site survivability is available from VG4xx ATA version IOS XE 17.16.1 52. In Webex Calling survivability mode, E911 calling requires a PSTN circuit or SIP trunk at the site 50. Third-party devices are not supported with the Webex Calling survivability gateway 51.

Verify

Suggested check: verify that the survivability gateway configuration lists the ATA IP addresses and routing parameters.

Rollback

Suggested rollback: remove the survivability gateway assignment if local failover is not implemented.

Step 11 End-to-end device testing

Cisco ATA 191 or ATA 192 (two analog ports per unit)

Do

Perform inbound and outbound test calls on each connected RJ-11 port 2829. If line settings or configurations were altered in Control Hub, resync the device from Control Hub or the unit directly to ensure the changes are active 20.

Verify

Suggested check: place a test call from an external phone to each port's assigned number and verify correct ringing.

Rollback

If testing fails, restore the device to factory defaults by holding the RESET button for about 10 seconds and re-provision 78.

FXS ports on a Cisco VG400, VG410, or VG420 ATA

Do

Perform inbound and outbound calls on each configured port 57. For hot-line ports, lift the handset and confirm automatic routing to the programmed destination 64. Ensure no port configuration pushes were sent while lines were in use to avoid port deregistration on release 17.18.1a 55.

Verify

Suggested check: verify that each line receives dial tone and successfully reaches assigned internal and external destinations.

Rollback

If onboarding or port mapping is irrecoverable, reset the gateway to Cisco factory defaults to exit Webex Calling configuration 60.

Applicability

Applies to: Cisco Webex Calling, Cisco ATA 191 Multiplatform, Cisco ATA 192 Multiplatform, FCC 47 CFR Part 9, Cisco Webex Calling E911, Cisco Webex Calling Site Survivability, Cisco VG4xx ATA, and Cisco VG400 ATA. Deployments: multi-tenant, multi-line-telephone-system, and third-party-call-control. Sources checked 2026-09-30. The Cisco analog telephone adapters listed as supported for Webex Calling are the ATA191 Multiplatform, ATA192 Multiplatform, VG400 ATA, VG410 ATA, and VG420 ATA 34. Supported third-party AudioCodes models include MP-124E, MP-1288, MP-202, MP-204, MP-504, MP-508, MP-516, MP-524, and MP-532 30. Firmware requirements specify a minimum of 11-1-0MPP0414-004 for ATA 191 and ATA 192 devices 1314, IOS XE 17.18.1a universalk9 for VG4xx ATA onboarding 62, and IOS XE 17.16.1 or later for VG4xx ATA site survivability failover 52. Enhanced emergency calling (E911) covers the United States, its territories, and Canada 39.

What remains uncertain

The exact procedure to remove a device record or individual port assignment from Control Hub is not covered by the sources below. Whether hot-line functionality is supported on ATA 191 and ATA 192 models is not covered by the sources below. Emergency location handling procedures for analog endpoints outside the United States and Canada are not covered by the sources below. Third-party ATA configuration workflows, including AudioCodes models and customer-managed devices, are not covered by the sources below. Transmission parameters and port configurations for elevator emergency phones and fire alarm panels on Webex Calling are not covered by the sources below.

Sources

1
Alarm panels and elevator emergency phones that signal with modem-style tones or dialers are data devices in the sense of Cisco's caution, so the recommendation to keep a dedicated PSTN line applies to them at least as strongly as to fax.inferred
Improve fax transmission with your ATA · note on data devices · Checked 2026-09-30
2
An ATA is added to a user in Control Hub from Devices by starting a new device, choosing Existing User, selecting the user, selecting the device type and supplying the MAC address where required.
Add a Desk Phone or Analog Telephone Adapter to a User · numbered procedure · Checked 2026-09-30
3
An ATA's ports are configured in Control Hub at Management > Users > the user > Devices > the device > Users on this Device > Configure Ports, where a shared port configuration is added by searching for a name or phone number; only workspaces without devices appear in that lookup.
Configure and manage Webex Calling devices · section 'Configure an ATA device for a user' · Checked 2026-09-30
4
Cisco ATA device settings can be set in Control Hub at three levels: organization (Services > Calling > Settings > Service > Configure Default Device Settings), location (Management > Locations > Calling tab > Device management) and device (Management > Devices > the device > All Configurations).
Configure and modify device settings in Webex Calling · organization, location and device level procedures · Checked 2026-09-30
5
ATA 191 devices onboard automatically through EDOS when their MAC address is provisioned in Control Hub, and the automatic onboarding runs after the first factory boot or after each factory reset.
Get started with your Cisco ATA 191 and 192 · EDOS automatic onboarding passage · Checked 2026-09-30
6
ATA 192 devices onboard automatically through EDOS when their MAC address is provisioned in Control Hub, and the automatic onboarding runs after the first factory boot or after each factory reset.
Get started with your Cisco ATA 191 and 192 · EDOS automatic onboarding passage · Checked 2026-09-30
7
An ATA 191 is restored to factory defaults by pressing and holding the RESET button on the back panel for about 10 seconds.
Get started with your Cisco ATA 191 and 192 · factory reset procedure · Checked 2026-09-30
8
An ATA 192 is restored to factory defaults by pressing and holding the RESET button on the back panel for about 10 seconds.
Get started with your Cisco ATA 191 and 192 · factory reset procedure · Checked 2026-09-30
9
On an ATA 191, pressing **** on the connected analog phone opens the IVR, and 110# makes it speak the ATA's IP address.
Get started with your Cisco ATA 191 and 192 · sections 'Change configuration utility login' and 'Provision ATA for Webex Calling' · Checked 2026-09-30
10
On an ATA 192, pressing **** on the connected analog phone opens the IVR, and 110# makes it speak the ATA's IP address.
Get started with your Cisco ATA 191 and 192 · sections 'Change configuration utility login' and 'Provision ATA for Webex Calling' · Checked 2026-09-30
11
On an ATA 191, a steady green Power LED means the system booted and is ready, a steady green Phone LED means the port is on-hook, and a Phone LED that flashes fast three times signals a registration failure.
Get started with your Cisco ATA 191 and 192 · top panel LED table · Checked 2026-09-30
12
On an ATA 192, a steady green Power LED means the system booted and is ready, a steady green Phone LED means the port is on-hook, and a Phone LED that flashes fast three times signals a registration failure.
Get started with your Cisco ATA 191 and 192 · top panel LED table · Checked 2026-09-30
13
ATA 191 devices need to be on a minimum firmware of 11-1-0MPP0414-004 for Webex Calling.
Get started with your Cisco ATA 191 and 192 · section 'Your new Cisco ATA 191 and 192' · Checked 2026-09-30
14
ATA 192 devices need to be on a minimum firmware of 11-1-0MPP0414-004 for Webex Calling.
Get started with your Cisco ATA 191 and 192 · section 'Your new Cisco ATA 191 and 192' · Checked 2026-09-30
15
When adding an ATA, all network settings such as VLAN, IP address and subnet mask must be configured before the device is activated, because they cannot be accessed or changed after activation.
Add a Desk Phone or Analog Telephone Adapter to a User · note on ATAs before the activation step · Checked 2026-09-30
16
When an ATA with more than one port is added, each port is treated as a separate device in Control Hub.
Add a Desk Phone or Analog Telephone Adapter to a User · note on multi-port ATAs · Checked 2026-09-30
17
An ATA 191 is provisioned manually by opening its web configuration utility, going to Voice > Provisioning, entering the regional provisioning server address in the Profile Rule field and submitting; the North America address is https://cisco.sipflash.com/ and the Europe address is https://cisco.broadcloud.eu/.
Get started with your Cisco ATA 191 and 192 · section 'Provision ATA for Webex Calling' · Checked 2026-09-30
18
An ATA 192 is provisioned manually by opening its web configuration utility, going to Voice > Provisioning, entering the regional provisioning server address in the Profile Rule field and submitting; the North America address is https://cisco.sipflash.com/ and the Europe address is https://cisco.broadcloud.eu/.
Get started with your Cisco ATA 191 and 192 · section 'Provision ATA for Webex Calling' · Checked 2026-09-30
19
In Webex Calling, ATAs connect non-IP devices such as analog phones, fax machines and overhead paging systems to the network so that they act as Webex Calling devices.
Supported devices for Webex Calling · section 'Analog Telephone Adapters (ATAs)', introductory sentence · Checked 2026-09-30
20
After device settings are changed in Control Hub, devices must be resynced from Control Hub or from the device for the changes to take effect, and devices with custom settings that override organization or location defaults are not updated by a change to those defaults.
Configure and modify device settings in Webex Calling · notes following the organization and location level procedures · Checked 2026-09-30
21
In the ATA Configure Ports view in Control Hub, T.38 fax compression is enabled per port by checking the box in the T.38 column and saving.
Configure and manage Webex Calling devices · section 'Configure an ATA device for a user', final step · Checked 2026-09-30
22
The documented deployment order for an ATA 191 is: install the ATA, reset it to factory settings, change the configuration utility login, upgrade firmware, then provision it for Webex Calling.
Get started with your Cisco ATA 191 and 192 · deployment workflow task list · Checked 2026-09-30
23
The documented deployment order for an ATA 192 is: enable the WAN port, install the ATA, reset it to factory settings, change the configuration utility login, upgrade firmware, then provision it for Webex Calling.
Get started with your Cisco ATA 191 and 192 · deployment workflow task list · Checked 2026-09-30
24
The ATA 192 has an additional ETHERNET (LAN) port that the ATA 191 does not have; both have one NETWORK (WAN) RJ-45 port.
Get started with your Cisco ATA 191 and 192 · hardware and back panel descriptions ('ETHERNET Port (ATA 192 only)') · Checked 2026-09-30
25
On an ATA 192, web access from the NETWORK (WAN) side is disabled by default; it is enabled by connecting to the ETHERNET port, browsing to 192.168.15.1 and turning on Remote Management under Administration > Remote Access.
Get started with your Cisco ATA 191 and 192 · section 'Enable WAN port on ATA 192' · Checked 2026-09-30
26
The ATA 191 Multiplatform data sheet lists both real-time Group 3 fax over IP via T.38 fax relay and Group 3 fax pass-through via G.711.
Cisco ATA 191 Multiplatform Analog Telephone Adapter Data Sheet · specifications table, fax rows · Checked 2026-09-30
27
The ATA 192 Multiplatform data sheet lists both real-time Group 3 fax over IP via T.38 fax relay and Group 3 fax pass-through via G.711.
Cisco ATA 192 Multiplatform Analog Telephone Adapter Data Sheet · specifications table, fax rows · Checked 2026-09-30
28
The Cisco ATA 191 provides two RJ-11 FXS ports (PHONE 1 and PHONE 2) for analog devices.
Get started with your Cisco ATA 191 and 192 · sections 'Your new Cisco ATA 191 and 192' and back panel description · Checked 2026-09-30
29
The Cisco ATA 192 provides two RJ-11 FXS ports (PHONE 1 and PHONE 2) for analog devices.
Get started with your Cisco ATA 191 and 192 · sections 'Your new Cisco ATA 191 and 192' and back panel description · Checked 2026-09-30
30
The supported-devices list for Webex Calling also names AudioCodes ATAs: MP-124E and MP-1288, MP-202 and MP-204, and MP-504, MP-508, MP-516, MP-524 and MP-532.
Supported devices for Webex Calling · section 'AudioCodes ATA devices' · Checked 2026-09-30
31
47 CFR 9.16(b)(1) requires a multi-line telephone system to be configured so that a user can directly call 911 from any station equipped with dialing facilities without dialing any additional digit, code, prefix or post-fix.
47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(1) · Checked 2026-09-30
32
47 CFR 9.16(b)(3)(i) requires an on-premises fixed telephone associated with a multi-line telephone system to provide automated dispatchable location no later than January 6, 2021.
47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(3)(i) · Checked 2026-09-30
33
47 CFR 9.16(b)(2) requires a multi-line telephone system to be configured to send a notification of a 911 call to a central location at the facility or to another person or organization, initiated contemporaneously with the call and without delaying it.
47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication) · 47 CFR 9.16(b)(2) · Checked 2026-09-30
34
The Cisco analog telephone adapters listed as supported for Webex Calling are the ATA191 Multiplatform, ATA192 Multiplatform, VG400 ATA, VG410 ATA and VG420 ATA.
Supported devices for Webex Calling · section 'Analog Telephone Adapters (ATAs)', Cisco model list · Checked 2026-09-30
35
Third-party ATAs can be added to Webex Calling as customer managed devices, for which Webex supplies SIP credentials and outbound proxy details but no configuration file, and Cisco Technical Support does not investigate issues with devices connected through that option.
Add your customer managed device · overview and limitations · Checked 2026-09-30
36
Cisco cautions that data devices such as fax machines and modems may not function optimally with an ATA, and recommends a dedicated PSTN line for best performance.
Improve fax transmission with your ATA · note on data devices · Checked 2026-09-30
37
The enhanced emergency calling article describes 933 as a test number used to check emergency service address routing before full 911 routing is enabled.
Enhanced emergency calling for Webex Calling · passages on 933 test calls · Checked 2026-09-30
38
With Webex Calling enhanced emergency calling, DECT devices and ATAs do not communicate with the location service; their emergency calls route to the emergency service provider, so a location must be configured in the RedSky administrative portal against their caller ID.
Enhanced emergency calling for Webex Calling · note on DECT and ATA devices · Checked 2026-09-30
39
Webex Calling enhanced emergency calling (E911) provides location-based emergency call routing to PSAPs across the United States, its territories and Canada.
Enhanced emergency calling for Webex Calling · overview · Checked 2026-09-30
40
For a user or workspace that has only an extension, the option to use its own phone number as the ECBN does not appear, and extension-only entries are not offered in the assigned-number list.
Emergency callback number · notes on extension-only users and workspaces · Checked 2026-09-30
41
The ECBN for a user or workspace can be its own number, the location default ECBN, or an assigned number belonging to another user in the same location.
Emergency callback number · ECBN options list · Checked 2026-09-30
42
When a Webex Calling user or workspace places an emergency call, the configured emergency callback number (ECBN) is presented to the PSTN provider, which routes the call to the PSAP and maps it to an emergency service address.
Emergency callback number · overview · Checked 2026-09-30
43
A workspace's ECBN is set in Control Hub at Management > Workspace, selecting the workspace, then Calling, then Emergency Callback Number in the Numbers section.
Emergency callback number · workspace ECBN procedure · Checked 2026-09-30
44
Webex Calling can email an administrator when an emergency call is placed; it is enabled for the organization at Services > PSTN & Routing > Settings > Emergency call notification, either for all locations or by allowing individual locations to turn it on, and per location at Management > Locations > the location > Emergency Calling > Emergency Call Notification.
Emergency call notifications · organization-level and location-level procedures · Checked 2026-09-30
45
The fax machine should be set to Fax or Auto Answer Fax mode so that incoming calls are not treated as voice calls.
Improve fax transmission with your ATA · before-you-begin note · Checked 2026-09-30
46
A fax machine must be connected directly to the ATA 191 phone port, without an extension or splitter, and should use overseas mode if available or otherwise a low transmission speed.
Get started with your Cisco ATA 191 and 192 · section 'Devices associated with your ATA', fax machine item, and installation step 2 · Checked 2026-09-30
47
A fax machine must be connected directly to the ATA 192 phone port, without an extension or splitter, and should use overseas mode if available or otherwise a low transmission speed.
Get started with your Cisco ATA 191 and 192 · section 'Devices associated with your ATA', fax machine item, and installation step 2 · Checked 2026-09-30
48
If fax problems persist after T.38 is enabled, Cisco's suggested measures are to restart the fax machine and ATA, check connections and the ATA status in Control Hub, lower the baud rate to 9600 or 2400 bps, adjust Error Correction Mode, and send fewer pages per transmission.
Improve fax transmission with your ATA · troubleshooting list after the setup steps · Checked 2026-09-30
49
The analog endpoints listed as supported with Webex Calling site survivability are the VG400, VG410 and VG420 ATAs and the Cisco ATA 191 and 192.
Site survivability for Webex Calling · supported endpoints table, analog endpoints · Checked 2026-09-30
50
In Webex Calling survivability mode, E911 calling requires a PSTN circuit or SIP trunk at the site.
Site survivability for Webex Calling · emergency calling passage · Checked 2026-09-30
51
Third-party devices are not supported with the Webex Calling survivability gateway.
Site survivability for Webex Calling · supported endpoints, third-party devices note · Checked 2026-09-30
52
VG4xx ATA failover to Webex Calling site survivability is available from VG4xx ATA version IOS XE 17.16.1.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manage VG4xx ATAs in Control Hub', site survivability note · Checked 2026-09-30
53
By default an ATA on Webex Calling sends faxes with T.38 mode disabled, and in that default mode the fax stays encrypted between the ATA and the Webex Calling service.
Improve fax transmission with your ATA · introductory paragraphs · Checked 2026-09-30
54
Enabling T.38 mode for an ATA on Webex Calling can resolve fax transmission problems, but it disables encryption on faxes.
Improve fax transmission with your ATA · introductory paragraphs · Checked 2026-09-30
55
On VG4xx ATA release 17.18.1a, pushing a port configuration change from Control Hub while that port is active causes the port to deregister once the configuration file is processed; the documented remedy is to push the configuration again after the port is idle.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Troubleshoot VG4xx ATA deployment', known issue for release 17.18.1a · Checked 2026-09-30
56
Before onboarding a VG4xx ATA, run 'show version' to confirm the boot image is the Webex-approved version and that the configuration register is 0x2102; if changes are made, save with 'write memory' and reload.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manually configure the VG4xx ATA', boot parameter verification steps · Checked 2026-09-30
57
Remaining VG4xx ATA ports are assigned in Control Hub by opening Devices, selecting the VG4xx ATA, choosing Configure ports and adding the preconfigured users and workspaces.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section on assigning users and workspaces to remaining ports · Checked 2026-09-30
58
A VG4xx ATA is created in Control Hub under Devices > Add device by choosing Shared usage, then Existing workspace, selecting the workspace for port 1, choosing Cisco-managed device and the model, and entering the MAC address.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Create VG4xx ATA in Control Hub' · Checked 2026-09-30
59
For a workspace or user on a VG4xx ATA port to register successfully, its extension must contain at least 4 digits, whether it is extension-only or extension plus PSTN number.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Troubleshoot VG4xx ATA deployment', known limitations, item 1 · Checked 2026-09-30
60
To use a VG4xx ATA outside Webex Calling after onboarding, the device must be reset to Cisco factory default settings.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare VG4xx ATA for onboarding Webex Calling', note after prerequisites · Checked 2026-09-30
61
Cisco's VG400 white paper for Webex Calling states that the VG400 provides SIP-based T.38 fax relay and G.711 fax passthrough.
Webex Calling and Cisco VG400 Analog Telephone Adapter Technical Whitepaper · fax support passage of the white paper · Checked 2026-09-30
62
The firmware images listed as supported for VG4xx ATAs on Webex Calling are IOS XE 17.18.1a universalk9 images: vg400-universalk9.17.18.1a.SPA.bin, vg4x0-universalk9.17.18.1a.SPA.bin (VG410) and vg420-universalk9.17.18.1a.SPA.bin.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare VG4xx ATA for onboarding Webex Calling', supported firmware versions table · Checked 2026-09-30
63
FXO and ISDN interfaces on VG4xx models are not currently supported for use with Webex Calling; only FXS ports are used.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manage VG4xx ATAs in Control Hub', restrictions · Checked 2026-09-30
64
For a VG4xx ATA port connected to an analog handset, hot-line functionality can be configured on the port in Control Hub.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section on assigning users and workspaces to remaining ports, optional port configuration · Checked 2026-09-30
65
'show license summary' on a VG4xx ATA must show three licenses before onboarding: uck9, securityk9 and webex_calling.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manually configure the VG4xx ATA', license verification step · Checked 2026-09-30
66
Before onboarding, a VG4xx ATA is reached by connecting a computer to port GE 0/0/1, where the device presents its management web interface at 192.168.253.253 with an Administration > Command Line Interface page.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manually configure the VG4xx ATA', web interface access steps · Checked 2026-09-30
67
Users with a Webex Calling Standard license cannot be assigned to VG4xx ATA ports.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manage VG4xx ATAs in Control Hub', restrictions · Checked 2026-09-30
68
Virtual lines cannot be assigned to a VG4xx ATA.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare for VG4xx ATA port assignment' · Checked 2026-09-30
69
After the device management URL is set, the VG4xx ATA displays its MAC address; the documented order is to record it, add it to Control Hub, run 'write memory', connect port GE 0/0/0 to a network with DHCP and internet access, and wait about five minutes for the configuration to complete.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manually configure the VG4xx ATA', Webex configuration steps 3 to 7 · Checked 2026-09-30
70
When a VG4xx ATA cannot onboard, the documented checks are the device management URL, that the MAC address in Control Hub matches interface GE 0/0/0, and that all ports are on-hook as shown by 'show voice port summary'.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Troubleshoot VG4xx ATA deployment', row for a device that cannot onboard · Checked 2026-09-30
71
A workspace or user can occupy only one line of a given VG4xx ATA.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare for VG4xx ATA port assignment' · Checked 2026-09-30
72
VG400 ATA models offer two, four, six or eight FXS ports; VG410 ATA models offer 24 or 48 FXS ports; VG420 ATA models offer 84, 132 or 144 FXS ports.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manage VG4xx ATAs in Control Hub', supported models · Checked 2026-09-30
73
The workspace or user selected when a VG4xx ATA is added in Control Hub is permanently assigned to ATA port 1.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare for VG4xx ATA port assignment' · Checked 2026-09-30
74
VG4xx ATA ports are numbered from 0, while other ATA ports are numbered from 1.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section on assigning users and workspaces to remaining ports, port numbering note · Checked 2026-09-30
75
For a VG4xx ATA port connected to a fax machine, enabling T.38 compression on the port overrides the default audio codec.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section on assigning users and workspaces to remaining ports, optional port configuration · Checked 2026-09-30
76
When creating a workspace for a VG4xx ATA port, select 'Add a device later', assign the Webex Calling service with a license, and give it a telephone number or extension.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare for VG4xx ATA port assignment' · Checked 2026-09-30
77
A VG4xx ATA is pointed at Webex Calling by entering 'voice service voip' and then 'wxc-dm-url <Device Management URL>' in its command line interface; the URL is regional and the United States value is https://cisco.sipflash.com.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Manually configure the VG4xx ATA', Webex configuration steps · Checked 2026-09-30
78
After a VG4xx ATA is onboarded it can only be used with Webex Calling, and its earlier configuration, including the administrator password, is overwritten.
Configure your Cisco Voice Gateway VG400, VG410, or VG420 in Control Hub · section 'Prepare VG4xx ATA for onboarding Webex Calling', note after prerequisites · Checked 2026-09-30

Documents

tier 1 standards and regulators

Cite this page

APA

WarmTransfer. (2026, September 30). Setting up analog devices and ATAs on Webex Calling. WarmTransfer. https://warmtransfer.net/guides/webex-calling-analog-ata-setup

BibTeX

@misc{warmtransfer-webex-calling-analog-ata-setup,
  title  = {Setting up analog devices and ATAs on Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/webex-calling-analog-ata-setup},
  note   = {Verified 2026-09-30}
}