> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/user/pascom-app-userguide/linekeys.md).

# Line Key Configuration

In this guide we will show you how to set up the line keys of your hardware phone

## Trainings Video

coming soon

## Overview

Line keys are the speed dial keys with busy lamp field (BLF) on hardware telephones. These keys can be configured and assigned as desired and show different LED colors depending on their status.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-1042a3a11c538b87dd59fbee354c564a6b7f1059%2Flinekey-example.jpg?alt=media" alt="Line Key Example" width="50%"><figcaption></figcaption></figure>

## Where do I find the Line Keys?

The function of the line keys can be found in the **App Settings**.

1. Open the **App Settings** via the PASCOM menu.

![Open App Settings](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-c4a4bcf8655b2611f171482cd10614fb8b2e4052%2Fopen_clientsettings.jpg?alt=media)

2. In the **Settings menu** click on **My devices**. You will then find the button **Configure line keys** for your **hardware phone**.

![Create new Line Key Configuration](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-a86fffeac56b683c4c27f76a9536d9a7e3101892%2Flinekey-add.en.png?alt=media)

## Line Key Configuration

In the **Line Key Settings** overview, you can add new key configurations.

![Line Key Settings](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-8edcd8ceb1cb01d0cfe4aa7c81b69fe36f7feabc%2Flinekey-settings.en.png?alt=media)

2. In the overview you can see already preconfigured **line keys**, which are locked by a **lock symbol**. These keys are globally predefined and cannot be **deleted** or **changed**.

Click the **Add key below** button to create your own new **line key**.

{% hint style="info" %}
**"A new line key cannot be created"**

If you cannot click the **Add key below** button, the function of own **line keys** is blocked by the administrator.
{% endhint %}

## Create a new Line Key

If you add a new **line key**, it will be inserted at the bottom of the list. The key configurations are always consecutive and the order of the list can only be rebuilt afterwards by deleting the last elements.

As you can see in the screenshot below, there are different **types** of **line keys**, which we will explain in more detail in the points below.

![Line Key Types Not used](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-3fb73996ded04389c331b755e24698525b80abcf%2Flinekey-types.en.png?alt=media)

### Line Key - not used

The type **"not used"** blocks or locks a line key so that it cannot be used. This type is often used to create placeholders in the list.

### Line Key - Any Number

![Line Key Types Any Number](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-409a6428d139a9ad634ad0075b879def431a4253%2Flinekey-customnumber.en.png?alt=media)

The type **"any number"** allows to store user-defined phone numbers. These can be **external** as well as **internal** numbers. In addition, you can also use **function codes**, as shown in our example above (PASCOM prompt system \*50).

### Line Key - PASCOM Menu

![Line Key Types PASCOM menu](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-a6b8afe696227d95cc1a8ddc7bb9a14e95ac3f1a%2Flinekey-pascommenu.en.png?alt=media)

The type **"PASCOM menu"** allows to store the PASCOM menu on a **line key**. The PASCOM menu contains further useful functions for hardware telephones.

### Line Key - Open URL

![Line Key Types Open URL](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-477e16a84a5a1ae67a172748e8f4038282aac6ee%2Flinekey-url.en.png?alt=media)

The type **"Call URL"** allows to store **URL addresses**, which will be called when the **Line key** is pressed.

### Line Key - Contact List

![Line Key Type Contact List](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-9734a8cf8dfec76edc432eccee50d4d31f355bfc%2Flinekey-contactlist.en.png?alt=media)

The **"contact list"** type allows you to store phone numbers from your **contact list** and the **private / global phone book**.

### Line Key - Team loggon/ -off

![Leitungstasten Typen Team](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-452034dce29d66e8812eb9b4cc3a591cc4797701%2Flinekey-team.en.png?alt=media)

The type **"team loggon/ -off"** allows you to loggon/ -off to **teams / call queues** You also have the possibility to apply this function to all **teams**, you are a member of.

## Apply Line Key Settings

Once your settings are complete or you have made changes to your **line keys**, you must apply them by clicking the **Save and Apply** button.

1. **Changes** to your line keys are immediately transmitted to your **hardware phone** so you can try them out right away.

<figure><img src="https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-563183dddba8b04dccd53b1ad23d380f98f44884%2Flinekey-example-newkeys.jpg?alt=media" alt="New Line Keys" width="50%"><figcaption></figcaption></figure>

## Remove Line Keys

To remove a **line key** you created yourself, simply click on the small **trash can icon**. Don't forget to apply the change via the **Save and Apply** button.

![remove Line Key](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-670d48167a4867a8b62422cdf1f103d5e0f3c11a%2Flinekey-delete.en.png?alt=media)

1. If you want to undo all changes / button configurations at once, use the link **Reset to default** at the top of the menu.

## Useful Information

1. Is it possible to set the LED colors of the **Busy Lamp Field(BLF)** itself?

No, this is controlled automatically by the PASCOM telephone system, e.g. for busy users, active extension switches or whether one is logged on or off in a team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/user/pascom-app-userguide/linekeys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
