BT120 Setup and Deployment -

Additional Network Configuration and SIP Option Settings via BT120 Web Console

Alexa built-in

Setting up and Deploying BT120 in a Home or an Office Environment

At this point, you should have completed the setup steps including Prerequisites, Basic Network Access, Amazon Account linking, and SIP Parameter Setup, and Mid-Point Alexa Voice Service Tests, and are ready to proceed to Network Configuration and SIP Account Setup via Web Console. 

Additional Network Configuration and SIP Option Settings via BT120 Web Console

Obtaining the Device's IP Address

In addition to using the BuddyTalk Setup App to activate BuddyTalk WiFi and voice services, a BuddyTalk device can also be managed via its web console for advanced settings.  Connect your PC to the same subnet to which the device connects, and access the web console via a web browser:

Long press the Flash button on the device’s touch panel, and the speaker will announce the device’s IP address.  Or press ***1 on a phone connected to the device’s FXS port, and the IP address will be played through the telephone handset.

Logging in to the Device's Web Console

Type the obtained IP address into the browser and login to the BuddyTalk device:

Note: The user password for the web console access is unique to each device.  You can find the device-dependent factory default user ID and password on the label on the base of the BuddyTalk device, and can change the user ID and password once you log in to the BuddyTalk device’s web console.  You can use the BuddyTalk Mobile App to restore the user ID and password to their factory default values.

Once the login is successful, the Home page of the BT120 web console displays as below:

Configuring Network Interfaces

Login to the BuddyTalk web console to configure advanced network options.

A BuddyTalk device needs access to the public Internet to reach Amazon servers for Amazon Alexa services. In addition, if another VoIP service provider is employed to offer telephony services, the device also requires the access to the voice network.

The voice network may or may not be accessible through the public Internet. To support these different office network connection scenarios, the BuddyTalk device offers the following network options:

  • Redundant mode
  • Dual-homed mode (Isolated voice network)
  • VPN for enterprise network traversal
  • VLAN for traffic segregation

Redundant Mode

The BuddyTalk has two physical network interfaces: Gigabit Ethernet and 802.11n WiFi. In Redundant mode, when WiFi interface is enabled and the Ethernet interface is connected, the Ethernet interface will be the master network interface.  When the Ethernet Interface fails to obtain an IP address or physically loses connection, the device will automatically switch to the WiFi interface for the Internet connection.

To manage network IP address settings, or to enable WiFi access, navigate to Network > Interface:

  • Ethernet Interface: The BuddyTalk device’s Ethernet interface is a DHCP client by default. Configure the settings below if a fixed IP address is required.
  • WiFi: Enable WiFi, select a WiFi SSID by pressing the “Scan” button, then input the WiFi password for the chosen SSID.
Field Name Description
  • DHCP: Automatically acquires IP address from the DHCP server. DHCP is selected by default.
  • Fixed IP: Need to configure the following parameters according to the Router’s network settings.

IPv4 IP address of device| Net Mask | Gateway | MTU (maximum size of an IP packet, in bytes).

  • [Enable|Disable] WiFi. Check or uncheck this box.
  • SSID – Click Scan button to choose the target WiFi AP to connect to.
  • Wireless password: input the password to access the WiFi AP.
  • IPv4 Setting. Choose either DHCP or Fixed IP.
  • Connection Status
    • WiFi—Standby: the WiFi link is enabled and Ethernet is connected.
    • WiFi—Connected: WiFi link is enabled and Ethernet is disconnected or unavailable.

Master Interface

The Master Interface is the current active physical network. Long press the Flash button and the device will play the IP address of the master interface through its speaker.

Dual-Homed Mode

When the voice network is separated from the data network, BuddyTalk devices can be configured into Dual-Home mode, with one interface connected to the data network and the other connected to the voice network. The data network connects to the Internet for Amazon Alexa services.

Before start configuring the dual-homed mode network interface, please confirm that the VoIP network DNS server(s), that is, the DNS server(s) resolving VoIP proxy/server FQDNs is(are) reachable from the voice network. Additionally, if Over-the-Air (OTA) provisioning is required, determine if the OTA provisioning server is reachable from the data network or the voice network, and use such information for proper provisioning binding. 

To manage Dual-Homed network interface, navigate to Network > Dual HomedConfigure the interfaces to their respective networks.

Field Name Description
Enble Dual Homed

[Enable|Disable] Dual Homed. Check or uncheck this box.

When Dual Homed is enabled:

  • VPN must be disabled.
  • VLAN must be disabled.
Data/Voice IF Names

Associate network services to their required networks.

  • WiFi/Ethernet: Data via WiFi; Voice via Ethernet.
  • Ethernet/WiFi: Data via Ethernet; Voice via WiFi.
Provisioning Bind with Voice Interface
Enable this option when the OTA (provisioning) server is only accessible through the voice network.

Master Interface

When Dual-Homed mode is enabled, the Master Interface is the data network. Long press the Flash button and the device will play the IP address of the data network interface.

VPN for Enterprise Network Traversal

The BuddyTalk device includes an embedded VPN client which can be used to perform a network traversal function for VoIP devices. When BuddyTalk devices are deployed behind a firewall which blocks two-way voice communications, the VPN feature can be enabled for voice services. The VPN server may be operated by the BuddyTalk service provider, or the office IT department which manages routing traffic to the VoIP servers.

The BuddyTalk VPN client offers two routing options:

  • All traffic (both data and voice) is routed through the VPN. Choose this option when the firewall blocks both Amazon Alexa and voice services.
  • Only voice traffic (both SIP signaling and RTP/RTCP media) is routed through the VPN, and all other traffic is routed to the default gateway of the office data network..

To manage VPN settings, navigate to Network > VPN Setting.:

Field Name Description
Upload various VPN client related files

The BuddyTalk device is installed with the necessary VPN authentication files for the service provider from the factory.

Replace VPN files to switch to a different VPN service.

Enable VPN

Check this box to enable the VPN connection. When VPN is enabled,

  • VLAN must be disabled.
  • Dual Homed must be disabled.
Route all network traffic through VPN
Check this box to route both data and VoIP traffic through the VPN network.

Master Interface

Long press the Flash button and the device will play the IP address of the current active local physical network, not the virtual IP address for VPN connection.

VLAN for Traffic Segregation

For Quality of Service (QoS), security, and various other considerations, some office networks employ VLANs to segregate traffic. In particular, voice and data packets are often separated using VLAN.  The BuddyTalk devices support VLAN tagging, thereby allowing office VLAN segregation using VLAN switches.

The VLAN feature is applicable to the Ethernet interface only. In addition to the original physical Ethernet network interface, two virtual interfaces are created for signaling and voice respectively.

To manage VLAN settings, navigate to Network > Interface.

Two examples: Example 1 – SIP signaling and SIP media share the same VLAN ID (10) and IP address ( 

Example 2 – SIP signaling and SIP media each has its VLAN ID (10 and 20 respectively) and go to different IP subnets ( and 

Field Name Description
Enable VLAN Tagging

Checked | Unchecked

VLAN tagging is applicable to the device’s Ethernet interface. When VLAN tagging is enabled:

  • VPN must be disabled.
  • Dual Homed must be disabled.
  • Traffic types other than SIP signaling and Voice will not be tagged with a VLAN ID.

Configure VLAN ID(s) for both SIP Signaling traffic and Voice traffic, respectively. (2-4094)

  • When the VLAN ID for signaling and the VLAN ID for voice are different, their respective IP addresses should be from different subnets.
  • When the VLAN ID for signaling and the VLAN ID for voice are the same, their respective IP addresses should be configured to be the same.
VLAN Priority
Assign VLAN priorities to both SIP signaling and Voice traffic types. Priority values are from 0 (low priority) to 7 (high priority).
Signaling Address
Assign an IPv4 address to Signaling Interface. Note that this IP address should be from a different network to that of the physical Ethernet interface.
Voice Address
Assign an IPv4 address to Voice Interface. Note that this IP address assigned should be from a network different from that of the physical Ethernet interface.

Examples of VLAN Configurations

Example 1: SIP signaling and voice traffic are configured with the same IP address and VLAN ID, and separated into a different network from that for the data traffic.

Traffic VLAN ID IP Subnet mask Comment
SIP Signaling
VLAN ID = [2-4094]
VLAN ID = [2-4094]
Other Traffic
No VLAN ID assigned (so, it is the same as having VLAN ID =1, the default VLAN ID)

IP address is the physical IP of this device.


Example 2: SIP signaling, voice and data traffic are separated into three different VLANs and networks.

Traffic VLAN ID IP Subnet mask Comment
SIP Signaling
VLAN ID = [2-4094]
VLAN ID = [2-4094]
Other Traffic
No VLAN ID assigned (so, it is the same as having VLAN ID =1, the default VLAN ID)

IP address is the physical IP of this device.


Master Interface

Long press the Flash button and the device will play the IP address obtained from the data (Other Traffic) subnet.

SIP Account Setup via BT120 Web Console to Enable VoIP Calling

BT120 employs “BuddyTalk Calling” whereby an internal SIP stack on the device allows calling via a subscribed VoIP service. When the BT120 is configured with a phone number provided by the subscribed VoIP service, both outbound and inbound calling are supported within the VoIP service provider’s coverage area. The BT120 may be configured to subscribe to an external VoIP service, or, in an office environment, may be configured as an IP phone extension to the office IP-PBX.

BT120 as an IP Phone Extension to an existing IP-PBX

The BT120 can be configured as an IP phone extension to an existing enterprise IP-PBX, utilizing the IP-PBX’s calling capability to make incoming and outgoing calls.  This will require minimal enterprise voice configuration modifications, and instantly turn the environment into a voice-enabled workplace.  

BT120 Configured with an External VoIP Subscription

An alternative to configuring the BT120 to be an IP phone connected to the existing enterprise IP-PBX is to add an external VoIP subscription to the BT120.  In such a configuration, the BT120 device acts as if a new phone line has been added to the enterprise.  

Follow the steps below to configure SIP Server Profiles and Port Settings:

  1. Configure a SIP Server Profile.  Navigate to page Telephony > Profile Config. SIP Server Profiles specify VoIP service settings such as VoIP proxy server FQDN, port, SIP signaling protocol, and other VoIP/SIP settings such as codec settings, and the digitmap specification.  Four SIP Server Profiles can be defined for each device.

The Edit icon

Click the Edit icon to make changes.

  1. Configure Port Settings for the VoIP Service. Navigate to page Telephony > Port Config.  See Figure 17. BT120 Port Setting.  The Device (Port) Configuration defines device specific parameters or settings for the VoIP service. Such specifics include which SIP Server Profile to use, the account credentials (phone number or extension number, password, authentication ID, etc.), and enabling/disabling of device-based call features, etc.
Field Name Description
1. Enable

Enable/Disable this line.

2. Profile

Choose the Profile Name created under the Profile Config.

3. User ID

The IP-PBX extension number, or the subscribed VoIP service phone number assigned to the device (SIP account).

4. Password
Account password (SIP password).
5. Display Name

Name to be displayed in Caller ID.

6. Authentication ID
Authentication ID if needed.
Field Name Description
1. Profile Name

Give this profile a name as a reference for the port settings.

2. Proxy Server

The FQDN or IP address of the enterprise IP-PBX or the proxy server for the subscribed VoIP service.

3. Preferred Transport Protocol


The BT120 uses this setting to set up the SIP signaling protocol. By default, UDP is selected; unless the VoIP service or IP PBX requires TCP or TLS for more reliable or secure communications.

4. SIP Domain
The BT120 uses this setting to compose the host part of SIP request URI strings. Usually, the SIP Domain is the same as Proxy Server. However, it should follow the exact requirements for the IP PBX, or the instructions for your subscribed VoIP service.
5. Digitmap/Replace Rule

Digitmap is the dialing plan for the analog phone connected to the FXS port of the BT120 device. It defines the patterns of dial strings that the BT120 can send to the IP-PBX or SIP server when the pattern has been met, and not have to wait for the InterDigit Time out or the Critical Timeout.

Refer to Section BuddyTalk Dialing Plan

Replace_Rule is a companion rule to the Digitmap dialing plan employed when voice commands or the BuddyTalk App are used to initiate calls.

Refer to Section BuddyTalk Dialing Plan

Setting up Digitmap and Digit Replacement Rules

A digimap, constructed based on a given dialing plan, is a set of digit matching rules that allows the BuddyTalk device to know when the user has completed dialing, and to send out the dialed number in a timely manner. 

The Digit Replacement scheme allows some pre-determined prefixes to be added to the numbers, or replaces a portion of the digits with other digits. The scheme is useful when the BuddyTalk device is configured as an IP phone extension to an IP-PBX. 

For details about the BuddyTalk Digitmap and Digit Replacement Rules, please see Dialing Rules, Digimaps, and Digit Replacement Rules.

Activating Alexa Voice Service Through BT120 Web Console

The activation of Alexa Voice Service can be done through the BuddyTalk Setup App. Alternatively, it can also be managed from the web console. following the steps below:

  1. Prepare your Amazon Alexa account. See “Obtain an Amazon Alexa Account”.
  2. Navigate to page System > Alexa Setting. Input the required parameters as below.

Alexa Setting

  • Check the AVS Wakeup Sound box to enable the “Start-of-Request” sound when the BT120 detects the wakeword.
  • Check the AVS End of Request Sound box to enable the “End-of-Request” sound at the end of listening to an Alexa request.

Alexa Authentication

  • Click Auth to start the Alexa authentication process using your Amazon Alexa account.
  • Or, if the device is already authenticated, click Logout to remove this device from the Amazon Alexa management console.

Once Auth is clicked, the web page will be directed to the Amazon sign-in page shown in the Redirected Amazon Sign-in Page below. Enter your Amazon account and password to complete the AVS authorization process.

Alexa Settings
Field Name Description
AVS Wakeup Sound

Device responds with a “Start-of-Request” sound in response to the Alexa wake word.

AVS End of Request Sound
Device responds with an “End-of-Request” sound at the end of listening to an Alexa request.
AVS Client Authentication
Field Name Description

De-register the BT1XX from the Amazon Alexa server. (Only shown if device already authenticated).


Register the BT1XX to the Amazon Alexa server. (Only shown if device not currently authenticated).

Redirected Amazon Sign-in Page