AudioCodes MediaPack Series Manual

Onboarding Analog Telephone Adapters to Teams SIP Gateway
Overview
An analog telephone adapter (ATA) is a device for connecting traditional analog devices to a digital
telephone system. In context of SIP GW, it connects these analog devices via SIP GW to Teams.
A single ATA can connect N devices via N ports (RJ11 interface). Each port represents a SIP device from
TAC (Teams Admin Center) perspective and there is no notation for ATA. However, the hardware ID of
each device is composed of the MAC address of the ATA and a port number. For example, "00-90-8F-49-
28-78:001" which represents ATA MAC address 00-90-8f-49-28-78 and port number 001.
TAC (Teams Admin Center) doesn't have a notion of ATA and each ATA port is abstracted as an
independent device. However, ATA onboarding to SIP Gateway is done per ATA instance versus port. In
other words, ATA as a "box" MUST be factory reset and Server URL of ATA MUST be set with appropriate
regional HTTP URL, as documented in Configure SIP Gateway. The capacity (i.e., maximum number of
ports that can be supported per ATA), is a device attribute and documented for each ATA model. In
other words, if ATA has N ports, then the maximum number of ports that can be provisioned to satisfy
SIP GW security requirements (i.e., TLS and SRTP) may be less than or equal to N (please check link to
OEM documentation for exact number of ports that can be onboarded to SIP Gateway for a given ATA
model).
Analog devices are supported only for CAP (Common Area Phone) accounts; hence Admin MUST use
remote sign-in/sign-out from TAC, for analog devices as they would for any other CAP accounts. Before
remote sign-in admin must enroll the port of the ATA by dialing the feature code + verification code
from an analog device connected to that port to validate that it is a trusted device. "Add device" menu
in TAC remote provisioning now includes an option to select in addition to existing MAC address, Analog
device and populate Hardware ID in the MAC + port # format, as described above.
ATA Settings are to be managed via OEM tools or Web interface of ATA. However, user's settings are
sent to the device by SIP GW device manager, similar to every SIP Phone, for each port in case of analog
devices connected to an ATA.
ATA port will be listed as a regular SIP device in TAC. Admin can activate it via OTP and sign in/out, as
done for any other device. However, if admin will try to restart this device, then the command will be
ignored, since there is no option to restart a single port on an ATA, and Admin should use ATA
management tool to perform this command. Furthermore, all accounts that are signed in MUST be
within same region, since there is no option to "transfer" a port to another region due to regulations,
such as EUDB.
Roadmap for Bulk Provisioning
We are aware of challenge to migrate large number of analog ports from another system to Teams,
hence we plan to enable bulk Provisioning that will avoid the need to OTP each port and afterwards
remote sign in manually. Instead, we plan to have a tool that will accept a list of devices (including
Analog ports) as input and will complete the all process with a single transaction.