> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/virtual-numbers/devices.md).

# Devices

Take calls in your browser, on a desk phone or on a softphone app.

Open **Settings → Devices**.

Choose where your calls actually ring.

## Ring in browser

Calls ring in the LimeCall dashboard and you speak through your computer.

Nothing to install, but it requires:

* the dashboard open in a tab,
* microphone permission granted to the browser,
* a stable connection.

Best for people working at a desk all day. Use a headset — laptop microphones pick up the room and produce echo.

{% hint style="info" %}
If the browser never rings, microphone permission is the usual cause. Check the padlock icon in the address bar and confirm microphone access is allowed for app.limecall.com.
{% endhint %}

## Forward to a phone

Calls ring an ordinary phone number — typically a mobile.

The most reliable option, because it uses the normal phone network rather than your internet connection. Best for people who are out, on site, or driving.

Your mobile number stays private; the caller sees your LimeCall caller ID.

## Desk phone or softphone (SIP)

Connect a SIP device — a physical desk phone, or a softphone app on a computer or mobile.

This suits teams with existing handsets, and anyone who wants a real phone on the desk rather than a browser tab.

Setting one up requires connecting the device to your LimeCall SIP credentials. The Devices page generates these and can show a QR code that provisions a softphone app directly, which avoids typing a long string of settings by hand.

{% hint style="warning" %}
SIP credentials let a device place calls billed to your account. Treat them like a password: do not share them, and regenerate them if a device is lost or a person leaves.
{% endhint %}

## Using more than one

You can have several devices. Calls can ring them together, so you answer wherever you are, or in order.

Ringing your browser and your mobile at once is a common and effective setup — you answer at your desk when you are there, and on your mobile when you are not.

## Personal availability

Whichever device you use, calls only reach you during your personal hours, set under **Settings → My hours**.

## Audio quality

If calls sound poor:

* Use a wired headset rather than laptop speakers, which cause echo.
* Prefer a wired network connection to wi-fi for browser calling.
* Close other applications using bandwidth — video calls and large uploads especially.
* For SIP handsets, confirm the device is on the same network you configured and not behind a restrictive firewall.

If quality is consistently poor in the browser but fine on a forwarded mobile, the problem is your local network rather than the platform.

## Testing

Make a test call to each device you have configured. Check it rings, that both sides can hear each other, and that the call appears under **Calls** afterwards.


---

# 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 by asking a question.

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

```
GET https://docs.limecall.com/virtual-numbers/devices.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 `automate deployments from our CI pipeline` 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.