What is Button Builder?

Button Builder is a  feature in the PBX portal that allows users to configure buttons on supported phones using a WYSIWYG UI.  With Button Builder, phone features such as Line Appearance, Shared Line Appearance (on devices that support SLA), Speed Dial, BLF, Park, and DTMF can be setup without using NDP overrides.  The image below depicts an example of the user interface when provisioning a Polycom VVX450.

 

Where can I find Button Builder?

It can be found in the 'Inventory' > 'Phone Hardware' Tab when logged in as a Reseller, then click on the button labeled Button Builder, or click the Gear Icon adjacent to each device in the list.


Why is Button Builder only available to Resellers at this time?

Quality Assurance. Button Builder has passed our internal testing, but we want to make sure Button Builder is solid before exposing to End Users.


When will Button Builder be available to End Users?

After confirming there are no further issues or improvements to be made, we will enable Button Builder for End Users. We have no definitive ETA yet but we are working on getting this enabled at the reseller level soon.


What phone brands does Button Builder Support?

Button Builder will currently Support most models of Yealink and Polycom phones. See the bottom of this page for a complete list.


Can I use NDP Overrides and Button Builder simultaneously?

You can continue to use NDP overrides in combination with Button Builder, but you should NOT configure the same buttons in both NDP and Button Builder. 

Note: You cannot work in NDP and Button Builder in different browser tabs at the same time, you will see unexpected results due to the browser cache.


What will happen to configurations made directly on the phones (WebUI/Physical)?

Buttons that are configured on the phones do not get synchronized to NDP or Button Builder. As a result, any changes made to the buttons via the phone's web UI or physical phone settings will get overwritten when the phone pulls a new config from the PBX. 


Does Button Builder work with the Directory Designer from NDP?

No, Button Builder can automate button configuration by using PBX Contacts (including shared contacts) but does not pull configuration from Directory Designer.


What are the feature options that can be configured with Button Builder?

  • Line Appearance
  • Shared Line Appearance (on devices that support SLA)
  • Speed Dial
  • BLF
  • Park
  • DTMF


I noticed that Button Builder overwrites my Polycom Domain-applied overrides. Is this expected?

Yes, this is expected. With how Polycoms are coded in the back end, Button Builder takes precedence over domain-added override. This is different from other phones that are supported where NDP, regardless of where the overrides are added, will always take precedence over Button Builder.  


When released, how can I prevent my end users from accessing Button Builder?

We can disable and hide the entire feature from specific user scopes by domain. There is also a READ-ONLY mode, which removes actions and replaces them with a read-only substitute. This allows users to see the Button Builder feature but not allow them to make any changes to it.


What procedure do you suggest for setting up a new device?

If special parameters are needed, we recommend creating overrides in NDP (or overrides from the Button Builder Interface) before creating buttons in Button Builder.

Note: You cannot work in NDP and Button Builder in different browser tabs at the same time, you will see unexpected results due to the browser cache.


What is the difference between the Static and Dynamic Directory Options?

The Static Directory means once the directory is applied, it will not change if that directory is updated. The Dynamic Directory will update when changes are made to the Directory.


My DSS Keys are stuck on using Account 1, how can I change this?

You can only control this by manually adding overrides. On the Button Builder page, click the vertical ellipsis -> Additional Phone Settings -> Add the parameters in the Overrides section. The format is linekey.X.line="Y" where X is the DSS line number and Y is the Account number, e.g. linekey.2.line="3", where 2 is DSS key 2 and 3 is the third account in the device.


Polycom Normal vs Automata

Button Builder currently sets BLF for Polycom as 'normal' buttons, while many people prefer to set their BLF as 'automata'. The difference in these types of BLF keys is how the buttons function when you are already on a call and you press a BLF.

Normal - When on an active call, pressing a BLF key puts your current call on hold and places a new call to the BLF target extension.

Automata - When on an active call, pressing a BLF key performs a Blind Transfer to the BLF target extension.

Many people prefer BLF's as Automata. If this is the case you can insert the following overrides on the phone you are configuring (this shows making the first 14 attendant resource buttons automata, you can simply use less or add more depending on the number of buttons that are being configured).

attendant.resourceList.1.type="automata"
attendant.resourceList.2.type="automata"
attendant.resourceList.3.type="automata"
attendant.resourceList.4.type="automata"
attendant.resourceList.5.type="automata"
attendant.resourceList.6.type="automata"
attendant.resourceList.7.type="automata"
attendant.resourceList.8.type="automata"
attendant.resourceList.9.type="automata"
attendant.resourceList.10.type="automata"
attendant.resourceList.11.type="automata"
attendant.resourceList.12.type="automata"
attendant.resourceList.13.type="automata"
attendant.resourceList.14.type="automata"


Why do changing BLF's cause my phone to ring on Polycom?

This is another behavior of the 'normal' BLF, you can use 'automata' to correct it, or you can use the following override to turn off the behavior for 'normal' BLF keys.

attendant.behaviors.display.spontaneousCallAppearances.normal="0"



SUPPORTED MODELS: 

The following models are supported by Button Builder.

BrandModel

Yealink

  • T58V
  • T58A
  • T56A
  • T54S
  • T52S
  • VP-T49G
  • T48S
  • T46S
  • T42S
  • T41S
  • T40G
  • T48G
  • T46G
  • T42G
  • T41P
  • T40P
  • T29G
  • T28P
  • T27G
  • T26P
  • T22P
  • T23G
  • T21P
  • T21P E2

Polycom - Soundpoint

  • 335
  • 450
  • 550
  • 560
  • 650
  • 670

Polycom - VVX

 
  • 101
  • 201
  • 300
  • 301
  • 310
  • 311
  • 400
  • 401
  • 410
  • 411
  • 500
  • 501
  • 600
  • 601

The following models are available by Button Builder but will have limited Support at this time.

BrandModel

Cisco

  • 6841
  • 6851
  • 7811
  • 7821
  • 7841
  • 7861
  • 8811
  • 8841
  • 8845
  • 8851
  • 8861
  • 8865
  • SPA500S (Sidecar)
  • SPA500DS (Sidecar)
  • 8800 Key Expansion Modules (8851, 8861, 8865)

Grandstream

  • GXP2170
  • GXP2160
  • GXP2140
  • GXP2135
  • GXP2130
  • GXP1782
  • GXP1780
  • GXP1760
  • GXP1760w
  • GXP1630
  • GXP1628
  • GXP1625
  • GXP1620
  • GXP1615
  • GXP1610
  • GXP2200EXT (Sidecar)

Htek

  • UC926E
  • UC926
  • UC924E
  • UC924
  • UC923
  • UC912P
  • UC903
  • UC902
  • UC46 (Sidecar)