Button Configuration

Setting up buttons on the phones is a very useful feature of TruePBX. It makes it very easy and intuitive to set up buttons on the phones that it serves.

 

Provisioning Buttons

Provisioning buttons on snom phones is very easy.

On the TruePBX you can set buttons for each snom phone as default.

To do that:

    • Go to your selected domain in TruePBX PBX web interface.
    • Go to Buttons page.

    • You can select any of the default profiles named after the snom phone model to set the buttons as you want for that phone. You may also select any other profile you may have created.

    • When you select a profile, you can map the buttons in it. For example if you select snom710, its buttons appear as shown below which you can then change if you want and press Save.

    • You can also create new buttons profiles (in case you want to assign a particular profile to an extension instead of automatic selection based on phone type). On the buttons profiles page, just provide a name for the profile and press Create. The new profile will appear in the list, which you can then edit to add and map buttons.

When a snom phone is provisioned by the PBX, the PBX will automatically pick the right phone model and provision it with the default button profile of that phone, set in the PBX domain.

You can also choose not to use the automatic option and instead assign a particular button profile to an extension for more customization.

Assigning Button Profile to an Extension

In case you want to force a particular button profile to an extension, instead of automatic selection by the PBX according to the phone type, you can do so as follows:

    • Go to your selected domain in TruePBX PBX web interface.
    • Go to the extension to which you want to assign a particular button profile.
    • Go to the Buttons tab of the extension found at the top.

    • In the Choose Profile dropdown, select the profile you want to assign to that extension, which can be any of the phone defaults or any other profile you might have created, as described above.

  • Press Save.
  • Furthermore, you can make changes to that chosen profile as it appears below on that page, in order to customize it for that extension. Simply make the modification within the existing profile and click Save as Custom.
  • This customized profile (not Automatic) will also now appear in the user mode when the user logs in, where he/she can also customize it if needed in Buttons Setup page.

Please remember, if you want to go back to automatic detection of the phone type for button provisioning, make sure to select the “Automatic” option in the “Choose Profile” dropdown and press Save.

Mapping Buttons

How do you map the buttons once you have chosen a button profile to edit. This of course is pretty straight forward.

    • Choose the button Type which is a drop down list from which to choose.

  • Enter a value in the parameter field. This value will generally consist of an account on the system or an extension.
  • Note Label is used only for the snom870 and snom821 virtual keys.

Button Types

Following is a list and explanation of some of the button types:

Button Type Parameter
Private: Multiple lines can be configured on IP phones. No parameter
Shared Line: Shared lines can best be compared to physical lines between the system and the central office of the old PBX days, when users had to seize a line before placing outbound calls. The Shared Line button emulates this mode. When a user picks up a shared line, other users also sharing this line see the LED go on. Users can place calls on hold by pressing the button, and other users sharing this line can pick the call up by pressing the button again on their end. This is sometimes referred to as “key system” functionality. Before this type of button will work, the CO lines must be configured on the trunk. The setting is made in the trunk itself, so you’ll need to click the Trunks tab, then scroll down to CO lines. Click the image to view this configuration. The names that are assigned to CO-lines must be unique across the domain. For example, you can set up three CO-lines on Trunk1 with the names “co1 co2 co3” and more CO lines on Trunk2 with different names like “co4 co5 co6”. co1 co2 co3
Speed Dial: When buttons are used as speed dials, the phone will simply dial the programmed number (the LED next to the button will not light). Speed dials can be used for phone numbers, extensions, star codes, and other numbers. For example, if you want to transfer a ringing call to the voicemail of a specific extension, the parameter would need to include the following:

  • The “transfer” star code (*77)
  • The direct dial prefix (e.g., 8)
  • The number of the extension (e.g., 40)

Example: *77840.

9781234567
Cell Phone: This mode allows you to pull a call from your cell phone and push a call back to your cell phone, depending on where the call is. No parameter
Service Flag: This mode allows you to change the status of a service flag. (This button affects only service flags that can be changed manually; it will have no impact on automatic, time-dependant service flags.) Service flag number
Park Orbit: Use this mode if you want to assign a button to a park orbit. Once this button has been configured, calls can be parked and retrieved by pressing this button. A parked call is indicated by a blinking light.Important: Before you can use this button, the star codes for Call Park and Call Park Retrieve must match (e.g., *85/*85). Park orbit number
Do not disturb: This mode shows that extension’s DND status. The LED will light when DND is in active mode. No parameter
Agent login/logout: This mode shows an agent’s login/logout status. This button can be used in a number of ways:

  • If the agent needs to log in and out of all agent groups at the same time (or if the agent belongs to only one agent group), use a single Agent login/logout button and do not specify a parameter (leave it blank).
  • If the agent belongs to numerous agent groups and needs to log in and out of a specific agent group before logging into another agent group, use multiple Agent login/logout buttons and in the parameter field, enter the agent group number. Do this for each agent group.

Once this button has been configured, the LED will light when the agent is logged in.

Important: Before you can use this button, the star codes for Agent Log in/Agent Log out must match (e.g., *64/*64).

Agent group account
Redirect: This mode allows you to redirect calls to a predefined extension or number. To use this mode, enter the redirection target into the parameter field. Pressing the button activates redirection and lights the LED. Pressing the button deactivates redirection. This mode is useful when an executive assistant should take over calls. Extension or external number
Busy Lamp Field (BLF): This mode shows when the specified extensions are in use. When the extension is connected, the LED will be solid; when the extension is ringing, the light will blink fast; and when the extension is holding a call, the light will blink slowly. This mode is similar to the monitor extension mode; however, it does not support the picking up of calls. When the user presses the button, the phone always dials the programmed extension. Extension
Agent Group: This button allows users to monitor the status of an agent group. When a caller is waiting in the group, the LED will blink quickly. Users can then press the button to pick up the call.. Agent group number
Message Waiting Indicator (MWI): This button indicates when a message has arrived for the account that is entered into this field. The MWI button can be especially useful in situations where it is necessary to send the same voicemail to more than one extension. In this case, a group mailbox must be created, and the phones must subscribe to MWI for the extension of the groupmail account. (This button can also be used for older phones that do not have a Message button on the telephone keypad.) Group mailbox