> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/allgemeine-losungen-beim-telefonieren-mit-sipgate/sipgate-softphone-fehler-und-loesungen.md).

# sipgate softphone errors and solutions

Solutions for common errors with the sipgate softphone and webphone, e.g. missing microphone access or problems when setting up a call.

{% hint style="warning" %}
**Important**: In general, we recommend our app for Windows, macOS, and Linux: [sipgate app](https://www.sipgate.de/app-download) which gives you access to a range of integrations.
{% endhint %}

Here you'll find solutions to known issues with the sipgate Softphone app and sipgate Webphone. Most testing was done on Windows desktop PCs, not Windows Server environments.

**What should I do if I can't make outgoing calls, or if I get an error message immediately when answering incoming calls?**

In many cases, the sipgate Softphone app **doesn't have permission to access the microphone.**

Below you'll find instructions on how to grant microphone access to both sipgate Softphone and sipgate Webphone.

* [**sipgate Webphone** in **Google Chrome**](#sipgate_webphone_chrome)
* [**sipgate Webphone** in **Mozilla Firefox**](#sipgate_webphone_firefox)
* [**sipgate Softphone** on **Windows 10**](#sipgate_softphone_win10)
* [**sipgate Softphone** on **Windows 11**](#sipgate_softphone_win11)
* [**sipgate Softphone** on ](#sipgate_softphone_macos)[**macOS**](#sipgate_softphone_macos)

## **When using sipgate Webphone**

If you use Webphone directly in your browser instead, the cause of this issue is often the same: the browser used for sipgate Webphone doesn't have permission to access the microphone, rather than the sipgate Softphone app.

| When using **Google Chrome** as your web browser, a red crossed-out microphone icon at the top of the address bar, to the right of the web address, indicates that microphone access may be disabled. | ![Bildschirmfoto\_2023-06-02\_um\_16.27.07.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-0b3ae4b17a2320195d166e8d4c852f90200a9db6%2FBildschirmfoto%202023-06-02%20um%2016.27.07.png?alt=media\&token=a45d03a3-c207-467e-a786-3006d9b6ab31) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Click the padlock icon to the left of the website address to view the site information. From there, you can click to grant microphone access again.

![Bildschirmfoto\_2023-06-02\_um\_16.26.08.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-82710e3d698faaf274a833ad975323b7ca683939%2FBildschirmfoto%202023-06-02%20um%2016.26.08.png?alt=media\&token=3f74cf35-b817-4928-8124-0a3d6908209f)

| When using **Mozilla Firefox** as your web browser, click the settings icon to the left of the website address to view the permission settings. For the option "**Use the microphone**", make sure "**Allow**" is selected. | ![Bildschirmfoto\_2023-06-02\_um\_17.04.26.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-e1588b445ee601aa088974b95d094940e6c9bf38%2FBildschirmfoto%202023-06-02%20um%2017.04.26.png?alt=media\&token=eb4004b4-75f4-4faf-b776-89d18550a322) |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

![Bildschirmfoto\_2023-06-02\_um\_16.51.54.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-f52c8f1d6829073b38e1dee5b7fde328248ea337%2FBildschirmfoto%202023-06-02%20um%2016.51.54.png?alt=media\&token=f90263e9-b035-4cd2-b64e-68be37f95897)

If there's no microphone access option there, or if "**Blocked**" is selected, click the microphone icon ("***Microphone input***") at the bottom of sipgate Webphone to prompt the browser to ask for microphone access again. Then click "**Allow**" to grant access.

![Bildschirmfoto\_2023-06-02\_um\_16.55.19.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-c162df0f440270f945d7e21ea601793454304fb6%2FBildschirmfoto%202023-06-02%20um%2016.55.19.png?alt=media\&token=348e93c0-e23d-4381-8ac8-2235ae89f42f)

## **When using the sipgate Softphone app**

If you're using the installed sipgate Softphone app, make sure in Windows Settings that apps are allowed to access the microphone.

Under **Windows 10** open **START ➔** the **WINDOWS SETTINGS ➔ PRIVACY ➔ APP PERMISSIONS ➔ MICROPHONE**

and enable the following options there:

* Allow apps to access your microphone
* Allow desktop apps to access your microphone (at the very bottom)

![Windows10-Mikrofon1.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-f9a57128072ebcbb2f954719503c084fce6c8f4d%2FWindows10-Mikrofon1.png?alt=media\&token=632a9f6d-0b4f-45e8-9c0f-71f8ba44440a) ![Windows10-Mikrofon2.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-646fa9657b29abd824950bebe42a22ff019a148b%2FWindows10-Mikrofon2.png?alt=media\&token=2a587cdb-04f4-42ab-a68d-7aae7b5a85cc)

Under **Windows 11** open **START ➔** the **WINDOWS SETTINGS ➔ PRIVACY & SECURITY ➔ MICROPHONE**

and enable the following options there:

* Microphone access
* Allow apps to access your microphone
* Allow desktop apps to access your microphone

![Windows11-Mikrofon.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-70136adf2a9e6162304900282961a6bfd779a703%2FWindows11-Mikrofon.png?alt=media\&token=78fb2840-6f16-4125-930d-8ce43c5c237e)

Under **Apple macOS** open **SYSTEM SETTINGS ➔ PRIVACY & SECURITY ➔ MICROPHONE**

* and enable access for the **sipgate Softphone** app

![MacOS-Mikrofon.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-4f2c9e2beba1ccac958afab536e9d5a99fc3c1fd%2FMacOS-Mikrofon.png?alt=media\&token=6bed11cb-4927-4329-a93c-103945a07dde)

## **How can WebRTC errors be tested?**

On [getting-started](https://webrtc.org/getting-started/testing) the test configurations for Firefox and Chrome are explained.

## **How do you export the softphone log?**

In the softphone, go to the "Help Center" menu item and click the Export button. A ZIP file will then open in the Downloads folder.

![FehlerExport.png](https://4045603198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg0qj71PeONPljdPedXLf%2Fuploads%2Fgit-blob-4d9b6cd84bd1b60c80557d46c053a49f783aa19a%2FFehlerExport.png?alt=media\&token=a00cdf22-b3df-4310-a84c-514a9565c21a)

## **Where can you find additional logs if login fails?**

**Windows**: C:\Users\Benutzername\AppData\Roaming\sipgate-softphone\logs\
**Mac 11.4**: The Logs folder may not be present here.\
/Users/USERNAME/Library/Logs/sipgate-softphone\
**Mac 11.5.1**: /Users/USERNAME/Library/Logs/sipgate-softphone

#### [1. Operating system-independent errors](#h_01GM8GW04NVDP7N09MM8EXR8BN)

<details>

<summary><strong>A failed call with a WebRTC error, but no error message in the softphone.</strong></summary>

This is a normal message when the call is ended by hanging up.

</details>

<details>

<summary><strong>For an outgoing call, you hear a busy signal (SIP 486, Analysis Console / Log: Call failed: Busy).</strong></summary>

The number you called rejected the call or was busy.

</details>

<details>

<summary><strong>A number you call reports busy even though it is reachable (Analysis Console: Call failed 503).</strong></summary>

Your PC has various local IP addresses available via "Docker". In this case, the call is routed through a local Docker IP address instead of an internet IP address. To resolve the issue, disable the local virtual network interfaces.

</details>

<details>

<summary><strong>Error message during an outgoing call with the announcement "The number you have dialed is not in service" (Analysis Console/Log: Call failed: unavailable).</strong></summary>

The selected phone number is not in service here. In such cases, please check the number and make sure you haven't misdialed or see if any other phone numbers are available. If the number can only not be reached via sipgate, please contact our support team.

</details>

<details>

<summary><strong>Login does not happen automatically, or the manual code page is displayed.</strong></summary>

In this case, pop-ups are blocked in your browser or browser add-on. Disable the pop-up blocker for app.sipgate.com, or copy the code and log in manually.

</details>

<details>

<summary><strong>When you log in, clicking the "Log in" button takes you to an error page.</strong></summary>

In this case, access to login.sipgate.com is blocked by the firewall. To resolve this, allow access to [login.sipgate.com](https://login.sipgate.com/auth/realms/sipgate-apps/protocol/openid-connect/auth?response_type=token\&client_id=sipgate-app-web\&redirect_uri=https://app.sipgate.com/implicit-auth-redirect?redirect=/) .

</details>

<details>

<summary><strong>Login fails and the message "Invalid code. Request a new code in the browser" is displayed.</strong></summary>

There are several possible explanations and solutions.

1. You pasted the code with spaces or special characters. Paste the code again and remove all spaces and special characters.
2. The code has expired because you copied it from an old browser window. In this case, click "Log in in browser" in the softphone, log in again, and enter the new code.
3. The code has expired. To resolve this, log out of the softphone, log in with your email address and password, and ignore the code that appears. On the code page, generate a link to a new code, click it, and log in with the new code.\
   Alternatively: Click Webphone in your sipgate account and use it temporarily.
4. Login is always rejected when using a VPN. In this case, the VPN changes the address <https://login.sipgate.com/auth/token>. To resolve this, contact your VPN's IT support. Alternatively, you can disable the VPN and make calls without it. Your calls are encrypted via TLS. You can also leave the VPN enabled and configure VoIP apps with your sipgate credentials.

</details>

<details>

<summary><strong>A blank page is displayed, or the sipgate logo spins in a circle.</strong></summary>

1. In the Analysis Console: ERR\_Network\_ACCESS\_DENIED means your firewall is blocking network access. Go to **Software Firewall ➔ Programs ➔ sipgate Softphone** ➔ **Allow network/Internet access**.
2. In the Analysis Console, ERR\_INTERNET\_DISCONNECTED means there is no network connection or the network adapter is disabled. In such cases, log in to the softphone, disconnect from the network, then quit and restart the softphone. Or plug in the network cable, enable the network card/adapter if necessary, and restart the softphone.
3. For the Analysis Console message Failed to load resource: net::ERR\_CONNECTION\_REFUSED, api.sipgate.com is blocked by the firewall or by %windir%\system32\drivers\etc\hosts. To resolve this, allow access to api.sipgate.com in the firewall or hosts file.

</details>

<details>

<summary><strong>The message "No valid phone number" appears even though all the details have been entered correctly.</strong></summary>

sipgate does not support calls to numbers in the 0137, 0138, 01212, 01807, 0185, 0181, 0188, or 0900 number ranges. Please use another service to call these special numbers. Landline numbers are also known for some special numbers. Please visit <https://www.0180.info/> .

</details>

<details>

<summary><strong>Outgoing calls are rejected immediately (Failed to register, status code 408).</strong></summary>

The LAN and/or Wi-Fi network was probably changed, and the softphone did not reconnect. The call attempt is being sent to the wrong public IP address and is rejected.

Simply quit and restart the softphone, or **Softphone ➔ Display ➔ Reload**.

</details>

<details>

<summary><strong>The message "The phone is offline. Please check your internet connection" is displayed ("Failed to register, status code 401").</strong></summary>

For new customers, the SIP ID and SIP password in the phone database are unknown in this case. To resolve this, l**og in to your sipgate account ➔ My Telephony ➔ Telephony ➔ Devices ➔ click VoIP phone ➔ SIP password ➔ click the gear icon and select "generate new password"**.

Testing for new customers: **Softphone ➔ Edit ➔ Developer Tools ➔ Application ➔ Clear Storage ➔ click "Clear site data"** ➔ **Press F5**. You should now be logged out. Log in again; login should now work.

</details>

<details>

<summary><strong>Analysis Console 1: net::ERR_NETWORK_IO_SUSPENDED</strong></summary>

The OS is put into standby/sleep mode for 30–60 minutes, the network connection is disabled for 60 minutes, or the idle softphone cannot be used for 60 minutes. After standby, restart the idle softphone or reconnect via **Display ➔ Reload page** or press CTRL+R or CMD+R to reconnect.

</details>

<details>

<summary><strong>renderer_error.log: sipjs disconnect / Failed to refresh token: 400</strong></summary>

**renderer\_error.log: sipjs: { category: 'sip.transaction.nict', content: 'Not connected.'**\
\&#xNAN;**\[error] disconnect Error: WebSocket closed wss\://sip.sipgate.de (code: 1006)**\
\&#xNAN;**\[error] Failed to refresh token: 400**\
The web password/SIP password was changed, and the softphone did not receive the update correctly. Log out of the softphone, log in again, and check whether registration succeeds.

</details>

<details>

<summary><strong>The software firewall does not allow a connection via wss to sip.spgate.de.</strong></summary>

Please check the software firewall and allow the softphone access to the internet.

</details>

<details>

<summary><strong>The software firewall's NAT allows access to the internet for only a certain number of minutes.</strong></summary>

Allow sipgate Softphone to access the internet in the software firewall, or check the NAT settings.

</details>

<details>

<summary><strong>The router/firewall is blocking the protocol; WSS or an IP filter is active.</strong></summary>

Allow WSS in the router/firewall protocol settings / disable the IP filter.

</details>

<details>

<summary><strong>The router/firewall's NAT allows access to the internet for only a certain number of minutes.</strong></summary>

Check the router/firewall NAT settings and allow the firewall connection for the Softphone.

</details>

<details>

<summary><strong>The VPN connection does not allow WSS, or there is a NAT problem with the VPN.</strong></summary>

Please disable the VPN, quit and restart the Softphone, and check whether it can now sign in.

</details>

<details>

<summary><strong>The call button turns gray and displays the message "The phone is offline. Please check your internet connection" (WebSocket closed unexpectedly).</strong></summary>

The firewall is blocking the sipgate IP ranges 34.64.0.0/10 + 217.0.0.0/8 + 212.0.0.0./8.\
To resolve this, allow the sipgate IP ranges 34.64.0.0/10 + 217.0.0.0/8 + 212.0.0.0./8 in the firewall.\
**Windows Defender approach 1**\
Advanced settings ➔ Outbound Rules ➔ New Rule ➔ Program ➔ Program path ➔ C:\Users\[Username]\AppData\Local\Programs\sipgate-softphone\sipgate softphone.exe\
➔ Allow the connection ➔ Check Domain+Private+Public ➔ Name: "Allow sipgate Softphone calls" ➔ Finish\
**Windows Defender approach 2:**\
First, complete approach 1. Then go to:\
Windows Defender Firewall ➔ Advanced settings ➔ Outbound Rules ➔ New Rule ➔ Custom ➔ Program path ➔ C:\Users\[Username]\AppData\Local\Programs\sipgate-softphone\sipgate softphone.exe\
and select **all protocols** .\
In the **Which remote IP addresses** field, enter the following: 34.64.0.0/10 + 217.0.0.0/8 + 212.0.0.0./8, and click **Next.** Click Allow the connection ➔ Next. Then select Domain+Private+Public and click **Next**. Finally, under **Name**, enter: Allow sipgate Softphone calls to the IP range, and click **Finish.**

</details>

<details>

<summary><strong>"net::ERR_CERT_REVOKED"</strong></summary>

There is a problem with the certificate, which may have expired. Alternatively, the server and client may not match. In this case, contact sipgate Support and restart the Softphone regularly. Alternatively, you can temporarily use your SIP credentials in another VoIP app.

</details>

<details>

<summary><strong>The voicemail answers after just one ring instead of, for example, 20 seconds ("WebSocket closed unexpectedly").</strong></summary>

If the calls are only a few seconds apart, we send two calls to the same Softphone. In this case, the Softphone cannot "call waiting" and rejects the call as busy, so it goes to voicemail. The likely cause is a software firewall or antivirus program disconnecting the internet connection. To resolve this, configure a VoIP app with your sipgate credentials. You can find configuration guides here: [How to connect phones to your account.](https://help.sipgate.de/hc/de/articles/4402636353041-Konfigurationsanleitungen-So-verbinden-Sie-Telefone-mit-Ihrem-Account)

</details>

<details>

<summary><strong>An incoming or outgoing call disconnects: "An error occurred with your call"</strong></summary>

**renderer\_error.log: sipjs: { category: 'sip.Invitation', content: 'Could not start audio source' } \[error] Failed to answer call: Error: Call failed: OTHER**\
No audio device is selected under Softphone ➔ Audio Input / Audio Output, or the Softphone cannot access the audio device. For **Ubuntu** , go to Settings ➔ Sound ➔ Input and select a microphone/headset. For **Windows desktop**: Select an audio input/output device in the Softphone, or set the default output/input devices in the operating system so the Softphone can access and find the "Default" device. For Windows Server 2016, check the privacy settings under "Group Policy". For **macOS**: "Security & Privacy" ➔ Privacy ➔ Microphone ➔ enable sipgate Softphone.

</details>

<details>

<summary><strong>An outgoing call disconnects immediately — "Requested device not found"</strong></summary>

**Error message:** "SessionDescriptionHandler.getDescription failed - NotFoundError: Requested device not found Failed to initiate call: Error: Call failed: OTHER"

In this case, no audio input/output device, or neither, is connected to the PC/laptop. Simply connect a headset or webcam with a microphone to the PC. On Windows 10, go to "Sound" ➔ select a device each for output and input, and under

Softphone ➔ Audio Input and Audio Output, select one device for each.

If you installed the Softphone on a terminal server and no microphone is detected, use an alternative such as the Webphone or another VoIP app, as the sipgate Softphone is not designed for terminal servers.

</details>

<details>

<summary><strong>An incoming call rings, but is immediately disconnected when answered (SIP 480), or the call drops.</strong></summary>

On macOS, go to System Settings ➔ Security ➔ Privacy ➔ Microphone ➔ sipgate Softphone and enable it. Quit and restart the Softphone. Calls should now work again.

**Alternatively**: Kaspersky Internet Security ➔ Settings ➔ Protection ➔ Application Control ➔ Manage applications ➔ search for "sipgate" ➔ sipgate softphone ➔ Restriction: Trusted

</details>

<details>

<summary><strong>An incoming call rings. The Softphone shows that the call has ended, but audio is still active.</strong></summary>

In this case, the softphone is active twice on the PC. If you answer a call, it appears as ended in the second softphone. Therefore, please use the softphone only once per PC.

</details>

<details>

<summary><strong>The softphone displays "Call from own number / to own number".</strong></summary>

In this case, go to sipgate User ➔ Phones ➔ Optimized number display for single-line displays and set it to off.

</details>

<details>

<summary><strong>You hear no ringing, and there is no audio in either direction from the start of the call (NWA).</strong></summary>

Jabra Pro: Set the Bluetooth base station to "PC mode" and make a test call to 10005 to check.

</details>

<details>

<summary><strong>After three hours, there is no audio in one or both directions (OWA/NWA).</strong></summary>

Restart the VPN and the softphone.

</details>

<details>

<summary><strong>You hear the test tone/ringing. From the start of the call, the other person can hear you, but you cannot hear them.</strong></summary>

**Fritz!Box 6490/6590/6591/6660 7.24**: Please restart the Fritz!Box several times, then call 10005 to test the audio.

**Fritz!Box 7590 7.25**: Restart the Fritz!Box twice after the update; one restart is not enough.

</details>

<details>

<summary><strong>For outgoing calls, you hear the test tone/ringing, but there is no audio in either direction from the start of the call (no-way audio).</strong></summary>

**SpeedPort W724V B and SpeedPort Smart 3**: Set up a DMZ for your PC's IP address. [set up with the softphone](https://www.telekom.de/hilfe/downloads/bedienungsanleitung-speedport-w-724v.pdf). Alternatively, configure another VoIP app with your sipgate credentials and use UDP for registration.

**Fritz!Box 6490/6590/6591/6660** Retail models: install Fritz!Box firmware 7.27 and restart the Fritz!Box several times.

**Fritz!Box 6490/6590/6591/6660 7.20–7.23** From Vodafone/KabelDeutschland/UnityMedia:

Unplug the Fritz!Box and restart it. Update 7.27 should be installed, and the firewall should be enabled.

Fritz!Box ➔ Internet ➔ Sharing ➔ Port Sharing ➔ "Add device for sharing"

\- Device: Select PC. IPv4 settings: Allow this device full access to the internet via IPv4 (Exposed Host).

\- Fritz!Box hardware acceleration: In the "Advanced" view, go to Content ➔ Fritz!Box Support ➔ Packet Acceleration ➔ Enable packet acceleration / Disable hardware acceleration.

\- Enable the Firefox browser and Firefox VPN, log in to sipgate, and use the webphone.

\- Enable the Opera browser and Opera VPN, log in to sipgate, and use the webphone.

Sophos XG Firewall: Disable SIP ALG / allow sipgate IPs and RTP ports.

</details>

<details>

<summary><strong>From the eighth minute of the call, you can no longer hear the person you called.</strong></summary>

The person you called has "silence detection" enabled on their phone/app and remains silent for an extended period. They should disable "silence detection" on their phone/app or say something from time to time, at intervals of 30 to 120 seconds.

</details>

<details>

<summary><strong>From the eighth minute, the person you called can no longer hear the caller.</strong></summary>

"Silence detection" is enabled in the headset software. Please disable it in the headset software. **Alternative**: The router/modem uses SIP ALG and has changed the audio port during the call. Please disable SIP ALG.

</details>

<details>

<summary><strong>You can make calls, but cannot receive them.</strong></summary>

In your sipgate account, go to Phones ➔ first phone ➔ set "Do not disturb (DND)" to inactive. **Alternative 1**: In your sipgate account, go to Call forwarding ➔ first connection: set the active "immediate" forwarding destination to an invalid phone number. **Alternative 2**: In your sipgate account, go to Call forwarding ➔ first connection: deactivate it. Alternative 3: Call forwarding ➔ first connection: enter 10–20s and a valid phone number. If you use an IPv6 DS-Lite connection and registration takes place via IPv4, unfortunately there is no solution for the sipgate softphone. Please use an alternative VoIP app that supports IPv6 and enable IPv6. Instructions can be found here: [Configuration guides](https://help.sipgate.de/hc/de/articles/4402636353041-Konfigurationsanleitungen-So-verbinden-Sie-Telefone-mit-Ihrem-Account)

</details>

<details>

<summary><strong>You can receive incoming calls only for about 5–30 minutes after making an outgoing call.</strong></summary>

To do this, disable SIP ALG: [Known models and solutions](https://help.sipgate.de/hc/de/articles/4406496589201-Probleme-mit-dem-Router-?_ga=2.59038189.1938143315.1670416852-1656892818.1659430377).

</details>

<details>

<summary><strong>When calling a bank computer/conferencing system, the keys are recognized incorrectly (DTMF).</strong></summary>

RFC2833 is configured in the softphone, but the destination system expects SIP Info or in-band signaling. In this case, configure a VoIP app (PC/mobile) with your sipgate credentials. [See the software guides](https://help.sipgate.de/hc/de/articles/4402636353041-Konfigurationsanleitungen-So-verbinden-Sie-Telefone-mit-Ihrem-Account). Look for DTMF in the relevant guide, adjust the settings, and call again.

</details>

<details>

<summary><strong>When calling a bank computer/conferencing system, no keys are received (DTMF).</strong></summary>

There is a problem with the carrier handling calls from sipgate.de to the destination number. Either call using another service or wait until the carrier identifies and resolves the problem. **Alternative**: Report the problem to sipgate support with a call example. Support can then open a fault report with the carrier. Wait until the carrier has resolved the problem.

</details>

<details>

<summary><strong>Lenovo audio jack detects audio output but not microphone input</strong></summary>

This affects the Lenovo T460p/T460s/X380 models. In this case, use a USB sound card and a headset with a 3.5 mm jack, or a USB headset.

</details>

<details>

<summary><strong>The softphone cannot find certain contacts.</strong></summary>

If you have more than 5,000 contacts, only contacts 1–5,000 are searched. Update and install softphone version 1.10.28 or later.

</details>

<details>

<summary><strong>The softphone crashes when you try to click a specific contact with the mouse.</strong></summary>

Please contact support and let them know which contact is affected and how it was created or imported. It may also help to delete the contact and create it again.

</details>

<details>

<summary><strong>Clicking a tel: phone number on a website opens the softphone, but no phone number appears in it.</strong></summary>

Phone numbers and links must not contain spaces. Contact the service or website displaying the phone numbers and report that the formatting is incorrect.

</details>

<details>

<summary><strong>Click2Dial does not work with Google Sheets / Google Excel online forms.</strong></summary>

Simply copy the phone numbers (CTRL/CMD+C) and paste them into the softphone (CTRL/CMD+V).

</details>

<details>

<summary><strong>The softphone intercepts the Play/Pause media keys, so music applications such as Spotify can no longer be controlled.</strong></summary>

Update and install version 1.16.3 or later.

</details>

<details>

<summary><strong>Microphone recording is very quiet</strong></summary>

This affects Lenovo P14s / T14 models running Ubuntu 20.x / 21.04.\
In this case, use a separate microphone or headset, or use Windows instead of Ubuntu.

</details>

<details>

<summary><strong>Unable to answer incoming calls; the button does not respond (IPv6 only)</strong></summary>

Cause: sipgate TCP load balancer update + sipgate Softphone uses the ws protocol instead of the ws protocol.

Solution: Disable IPv6 in your network connection so that SIP registration takes place via IPv4. The ws protocol works in this case.

</details>

#### [2. macOS](#h_01GM8H6MFBG42CREZ8EYDR7EPD)

<details>

<summary><strong>Unable to answer calls using the buttons on a Bluetooth headset.</strong></summary>

No event is sent here; Apple only allows the Play/Stop buttons to be used with music applications. Possible solution: use Windows with a headset.

</details>

<details>

<summary><strong>When placing a call, the message "Could not access microphone" / "Call ended: microphone not found" appears.</strong></summary>

On your Mac, go to System Settings ➔ Security ➔ Privacy ➔ Microphone ➔ enable sipgate Softphone, then quit and restart the softphone. You should now be able to make calls.

**Alternative**: Kaspersky Internet Security ➔ Settings ➔ Protection ➔ Program Control ➔ Manage applications ➔ search for "sipgate" ➔ sipgate softphone ➔ Restriction: Trusted.

</details>

<details>

<summary><strong>No notifications or push alerts are received for incoming calls.</strong></summary>

Enable push notifications in the softphone settings or allow notifications in macOS.

</details>

<details>

<summary><strong>You cannot hear an announcement when dialing the phone number 10005.</strong></summary>

Check where audio is normally played in your operating system and adjust the setting.

</details>

<details>

<summary><strong>My voice is not being recorded (wired headset, macOS)</strong></summary>

If the headset is muted, unmute it using the headset or the inline cable switch.

**Alternative 1:** Uninstall the drivers or headset software, then install a newer version. **Alternative 2**: Go to System Settings ➔ Security ➔ Privacy ➔ Microphone ➔ enable the "Browser" app.

**Alternative 3:** Try another headset or switch to the microphone built into your tablet or laptop.

</details>

<details>

<summary><strong>My voice is not being recorded / I cannot hear the caller (Bluetooth headset, macOS)</strong></summary>

Sometimes the headset appears twice: as a speaker and as a "Hands free" communications device. This can cause problems if audio playback is only possible in stereo mode. In this case, select the "Hands free" communications device.

</details>

<details>

<summary><strong>My voice is transmitted in a choppy way, but I can hear the person I called clearly (macOS)</strong></summary>

There is probably not enough upload bandwidth available (60–100 kbit/s). If possible, disable uploads on the network or allocate a specific amount of bandwidth. Otherwise, switch from UMTS / LTE to Wi-Fi / DSL / cable / fiber.

</details>

<details>

<summary><strong>I receive the caller's voice in a choppy way, but they can hear me clearly.</strong></summary>

There is probably not enough upload bandwidth available. At least 60–100 kbit/s is required. If possible, disable uploads on the network or allocate a specific amount of bandwidth. Otherwise, switch from UMTS / LTE to Wi-Fi / DSL / cable / fiber.

</details>

<details>

<summary><strong>My voice is transmitted with a noticeable to severe delay.</strong></summary>

If you use satellite internet, switch to a DSL / cable / fiber / LTE connection if possible. If you are using a VM (HypeV / VirtualBox) and do not need it, disable the VM network controller.

</details>

<details>

<summary><strong>My voice is transmitted, but I cannot hear audio from the caller (macOS)</strong></summary>

Make sure the "correct" output device is selected in the softphone's audio settings.

**Alternative 1**: Turn up the volume in your Mac's audio settings and/or on your headset. **Alternative 2**: Unblock the RTP/audio proxies in the hardware firewall.\
**Alternative 3**: Disable SIP ALG on the [router/modem](https://help.sipgate.de/hc/de/articles/4406496589201-Probleme-mit-dem-Router-?_ga=2.126874061.1938143315.1670416852-1656892818.1659430377).

</details>

<details>

<summary><strong>AirPods: Audio quality decreases as soon as the microphone is active.</strong></summary>

In this case, it’s best not to use the AirPod microphone. Instead, go to

Mac ➔ System Settings ➔ Sound ➔ Output: select AirPods, and Mac ➔ System Settings ➔ Sound ➔ Input: select Mac Microphone. Softphone: Microphone input: Mac Microphone / Audio settings: AirPods

</details>

<details>

<summary><strong>Poor voice quality (choppy audio and crackling)</strong></summary>

This is probably due to insufficient bandwidth when using Wi-Fi with multiple devices. Calls require 100–200 kbit/s, while video streams can use up to 1–2 Mbit/s. It’s best to disable optional Wi-Fi devices that are streaming video or audio. Alternatively, use a LAN/network connection instead of Wi-Fi.

</details>

<details>

<summary><strong>Poor voice quality / choppy audio / crackling due to high latency or packet loss</strong></summary>

One possible cause is an operating system process that was not shut down properly, leaving insufficient storage space to send or receive data correctly. A full restart of the computer should resolve this. If the problem persists after restarting, restart the network devices as well. Changing the Wi-Fi channel may also help resolve the issue. Finally, check network usage. Some routers allow you to prioritize network devices. In this case, prioritize internet telephony.

</details>

<details>

<summary><strong>Mac Finder does not delete all sipgate folders when uninstalling</strong></summary>

Uninstall sipgate Softphone via Finder ➔ Applications. You can then manually delete the following folders:\
com.sipgate.desktop\
com.sipgate.desktop.ShipIt\~/Library/Saved\ Application\ State/\
com.sipgate.desktop.savedState\~/Library/Preferences/\
com.sipgate.desktop.plist\~/Library/Application Support/\
sipgate-softphone\
@web-apps

</details>

<details>

<summary><strong>Softphone reports that it is offline and opens a network path to a local server in Finder</strong></summary>

The Softphone was probably installed from a local server. To fix the issue, uninstall the Softphone and reinstall it from the local Mac hard drive.

</details>

<details>

<summary><strong>Softphone shows network access in Finder / offline when the local server is unreachable</strong></summary>

The Softphone is probably located on a local server and was installed from there. To fix the issue, go to System Settings ➔ Users & Groups ➔ Login Items, check for sipgate startup entries pointing to the local server, and delete the file paths to the local server.

</details>

#### [3. Windows](#h_01GM8H659SEBH3NDPYYZ3CYQZ0)

<details>

<summary><strong>Installation stalls at about 33% and cannot be completed</strong></summary>

First, temporarily disable your antivirus software, then run the installation again. If Symantec is installed, it may also prevent the Softphone from being installed. Temporarily disable Symantec to complete the installation. Alternatively, you can use the webphone in the logged-in area of sipgate or use another [VoIP app ](https://help.sipgate.de/hc/de/sections/4411313184017-Konfigurationsanleitungen)instead.

</details>

<details>

<summary><strong>When starting Softphone, the hourglass spins indefinitely</strong></summary>

The firewall is probably blocking the Softphone’s internet access. Allow the Softphone to access the internet in your firewall settings.

</details>

<details>

<summary><strong>Cannot answer/reject calls using the buttons on a Bluetooth headset (Windows)</strong></summary>

sipgate does not offer Bluetooth button integration. Alternatively, Zoiper with the Pro feature can be used with Jabra/Sennheiser/Plantronics headsets.

</details>

<details>

<summary><strong>When ending a call using a Bluetooth headset, the microphone remains active</strong></summary>

With the Sennheiser MB Pro 2 headset, the microphone remains active after a call, and the headset battery runs out after 2–3 hours instead of 10–15 hours.

Test:

* Sennheiser MB Pro 2: Windows ➔ Sound ➔ Input: possibly two devices named "Speaker / Communication Device Hands free"
* Windows ➔ Sound ➔ Input: Communication Device Hands free
* Softphone ➔ Input: Communication Device Hands free
* Call 10005, hang up, then check whether the microphone is still active or has been deactivated

</details>

<details>

<summary><strong>Mac + Sennheiser MB Pro 1/2: microphone mutes during a call</strong></summary>

During a call, the microphone mutes randomly, while audio continues to play. As a workaround, use the headset with another VoIP app.

</details>

<details>

<summary><strong>When making calls, the message "Could not access microphone" / "Call ended: microphone not found" appears (Windows)</strong></summary>

The following error message appears: "category: 'sip.Inviter', content: 'Could not start audio source" and "error] Failed to initiate call: Error: Call failed: OTHER"

The microphone does not have access to sipgate-softphone. To fix this, go to Windows Settings ➔ Microphone ➔ Let apps access your microphone: ON

If the problem persists, check whether desktop apps have access to the microphone: Windows Settings ➔ Microphone ➔ Let apps access your microphone: ON ➔ Allow desktop apps to access your microphone: ON

Another possible cause is that Kaspersky Internet Security has classified sipgate Softphone as untrusted. In Kaspersky Internet Security, go to Settings ➔ Protection ➔ Application Control ➔ Manage applications ➔ search for "sipgate" ➔ sipgate Softphone ➔ right-click ➔ change the restriction status to "trusted".

</details>

<details>

<summary><strong>Outgoing calls end immediately (Windows)</strong></summary>

The following error message appears: "SessionDescriptionHandler.getDescription failed - NotFoundError: Requested device not found Failed to initiate call: Error: Call failed: OTHER"

This error message means that no connected audio device could be detected.

To fix this, connect a headset or a webcam with a microphone to the PC. Then go to Windows ➔ Manage audio devices and check that at least one device is listed for both the output and input devices. Also, go to

Windows ➔ Sound settings ➔ Output/Input: select an audio device for both output and input. Finally, go to Softphone ➔ Audio input and Audio output and select a device for each.

</details>

<details>

<summary><strong>No push notification appears when Softphone is minimized</strong></summary>

One or more notification settings are disabled. You can re-enable them under

Softphone ➔ Settings ➔ Enable push notifications.

Also check the following settings:

Windows ➔ Notifications & actions

Get notifications from apps and other senders: On

Show notifications on the lock screen: check/uncheck

Show reminders and incoming VoIP calls on the lock screen: recommended

Get notifications from these senders:

sipgate Softphone: On

</details>

<details>

<summary><strong>I don't hear an announcement when dialing 10005 (Windows)</strong></summary>

Check in the operating system where audio is being output and, if necessary, adjust the settings to use the current audio device.

See also "My voice is being recorded, but I can't hear the person I'm calling:"

</details>

<details>

<summary><strong>My voice is not being recorded (wired headset, Windows)</strong></summary>

The **Mute**function is probably enabled. You can disable it using the mute button on the headset or the cable switch. Alternatively, the headset may have been disabled using Lenovo software. Press FN + F4 to activate the microphone. If the microphone still isn't recording, also check whether the headset drivers are up to date. Alternatively, check whether the headset is defective. If so, audio may not be recorded in other applications either.

</details>

<details>

<summary><strong>My voice is not being recorded / I can't hear the caller (Bluetooth headset, Windows)</strong></summary>

The headset is listed twice: once under Speakers and once as Communication Device Hands Free.

In Windows 10: Settings ➔ Sound ➔ Sound Control Panel

Set Bluetooth Headset Communication Device (Hands-Free) as the default device, and under Recording, set Bluetooth Headset Communication Device (Hands-Free) as the default device.

Then restart the softphone. You should now be able to run the call test at 10005.

</details>

<details>

<summary><strong>My voice is transmitted in a choppy way, but I can hear the person I'm calling clearly (Windows)</strong></summary>

There may not be enough bandwidth available. At least 60–100 kbit/s of upload bandwidth is required for smooth transmission. You can disable uploads on the network or assign a specific amount of bandwidth. If possible, switch from UMTS/LTE to Wi-Fi/DSL. You can also check whether an alternative softphone, such as [Phonerlite](https://app.sipgate.com/team/faq/setup/index/id/41), provides better transmission quality.

</details>

<details>

<summary><strong>My voice is transmitted, but I don't receive audio from the caller (Windows)</strong></summary>

Under Softphone ➔ Audio settings, check whether the correct audio device is selected.

If it is, change the volume in the Windows audio settings or directly on the device. If you still don't receive audio from the caller, check whether the hardware firewall is blocking RTP/audio proxies by IP. These can be unblocked manually in the settings. Also check whether SIP ALG on the router/modem is preventing incoming RTP/audio packets from being forwarded. If so, disable SIP ALG on the [router/modem](https://app.sipgate.com/team/faq/setup/index/id/41).

</details>

<details>

<summary><strong>Microphone icon remains active after the call ends</strong></summary>

An update to Windows 2004 may change the microphone privacy settings. In this case, the softphone stops using the microphone after a call, but after a few seconds Windows shows that the softphone is actively using it. The webcam light is on even though no transmission is active, and Windows sounds/music are quiet because Windows thinks a call is in progress. Install the latest softphone version (at least 1.10.27).

</details>

<details>

<summary><strong>With CRM + Click2Dial, clicking phone numbers opens a different app</strong></summary>

A different app is set as the phone app under Default apps. Go to Windows ➔ Default apps ➔ Choose default apps by protocol ➔ TEL:URL:tel ➔ APP XY

and change it as follows: Windows ➔ Default apps ➔ Choose default apps by protocol ➔ TEL:URL:tel ➔ sipgate softphone

{% hint style="info" %}
Note:

\- Only phone numbers linked via HTML are recognized

\- Only phone numbers without spaces can be dialed

TEL:URL:tel is only displayed once the softphone is installed

Example link: \[+492111234567]\(tel:+492111234567)
{% endhint %}

</details>

<details>

<summary><strong>With CRM + Click2Dial, clicking phone numbers does not open an app</strong></summary>

Cause: CRM uses Click2Dial for sip: / phone: / callto:, which is currently not supported

Solution: Use a CRM solution that can call phone numbers via tel:

Windows-> Default apps ➔ Choose default apps by protocol ➔ TEL:URL:tel->sipgate softphone

Workaround: [VoIP app](https://teamhelp.sipgate.de/hc/de/articles/360010454657-Alle-Softphones-im-%C3%9Cberblick) configured with sipgate credentials that supports sip: / phone: / callto:

</details>

<details>

<summary><strong>Error message: "The instruction at 0x00007FF6FC1D431E referenced memory..."</strong></summary>

The following error message appears: "The instruction at 0x00007FF6FC1D431E referenced memory at 0x00000295EF13F000. The read operation could not be performed in the memory."

A second monitor is probably connected, with the softphone open on it. You can resolve the issue by disconnecting the second monitor.

</details>

<details>

<summary><strong>Softphone is installed / not offered for uninstallation under "Apps &#x26; features"</strong></summary>

The softphone version is outdated. Check for updates, or uninstall and reinstall the softphone.

</details>

#### [4. Linux](#h_01GM8H5Q6BY75MMJ4RMQ9A5EDN)

<details>

<summary><strong>FATAL:setuid_sandbox_host.cc(157) — The SUID sandbox helper binary was found, but is not configured correctly.</strong></summary>

The Chrome sandbox requires root privileges. You can grant them as follows:

Open a terminal and enter the following commands

**Ubuntu**:\
sudo chown root chrome-sandbox\
sudo chmod 4755 chrome-sandbox**Debian 10 "Buster"**\
$ chmod +x sipgate.AppImage\
$ ./sipgate.AppImage --no-sandbox\
**Alternatively**: upgrade from Debian 10 to Debian 11.5

</details>

<details>

<summary><strong>Error message in the console: ./sipgate-softphone.AppImage: cannot execute binary file: Exec format error</strong></summary>

This error appears because our application cannot be used with an ARM or x86 chip. Support for this is not currently planned; instead, use the Webphone.

</details>

<details>

<summary><strong>Automatic update downloads, but the new AppImage is not created</strong></summary>

The Softphone image is being used in /usr/local/bin, where permissions are restricted

To fix the error, quit the Softphone and copy the Softphone AppImage to "Downloads". Restart the Softphone; the automatic update should download the new AppImage file. Quit the Softphone and start it again. Then check whether the new version is active under Softphone ➔ Update, and move the new AppImage file to the desired folder. Alternatively, you can download a new AppImage file directly via the link. See the FAQ at the top.

</details>

<details>

<summary><strong>An unknown error aborted your call OK</strong></summary>

Restart the app; the error should no longer occur.

</details>

<details>

<summary><strong>I don't hear an announcement when calling 10005 (Linux)</strong></summary>

Check where audio is normally output in your operating system and adjust the settings if necessary.

-See also "My voice is being recorded, but I can't hear the person I'm calling"

</details>

<details>

<summary><strong>My voice is not being recorded (wired headset, Linux)</strong></summary>

"Mute" may be enabled using the button on your headset or cable. Disable the mute button on the headset or cable switch. If that doesn't work, the headset may be defective. In that case, other applications probably won't be able to record audio either. Try another headset. If your voice still isn't being recorded, the headset is probably not supported by Linux. To resolve the issue, look for a newer version of the driver for your headset.

</details>

<details>

<summary><strong>My voice is not being recorded / I can't hear the caller (Bluetooth headset, Linux)</strong></summary>

The headset is listed twice: once under Speakers and once as the "Hands free" communication device. In stereo mode, only audio playback is possible. Select the "Hands-Free" communication device to resolve the issue.

</details>

<details>

<summary><strong>My voice is transmitted in a choppy way, but I can hear the person I'm calling very well (Linux)</strong></summary>

There isn't enough bandwidth available for uploads: 60–100 kbit/s.

Disable uploads on the network or allocate a specific amount of bandwidth, if possible. Alternatively, switch from UMTS/LTE to Wi-Fi/DSL/cable/fiber, if possible.

</details>

<details>

<summary><strong>The caller's voice is received in a choppy way, but they can hear me very well (Linux)</strong></summary>

There isn't enough upload bandwidth available. Disable downloads on the network or allocate a specific amount of bandwidth, if possible. Alternatively, switch from UMTS/LTE to Wi-Fi/DSL/cable/fiber, if possible.

</details>

<details>

<summary><strong>My voice is transmitted with a slight to severe delay (Linux)</strong></summary>

If you use satellite internet, long transmission distances can cause delays. If possible, switch to DSL/cable/fiber/LTE. On a virtual machine (Hyper-V/VirtualBox), voice data passes through the VM software's network controller and is delayed as a result. If you don't use a VM, disable the VM network controller.

</details>

<details>

<summary><strong>My voice is transmitted, but I don't receive any audio from the caller (Linux)</strong></summary>

Under Softphone ➔ Audio settings, check where audio is being output and select the audio device you're using.

If the correct output device is selected, the volume may be set too low. Increase the volume in the Linux audio settings and/or on the headset. If you still can't receive any audio, check whether the RTP/audio proxies have been blocked by IP address in your hardware firewall. Unblock them if necessary.

Also check whether SIP ALG on your router/modem is preventing incoming RTP/audio packets from being forwarded. If so, [disable SIP ALG on your router/modem](https://basicsupport.sipgate.de/hc/de/articles/115005739225-Router-VPN-LTE-mit-VoIP-Problemen).

Finally, under sipgate Softphone ➔ Edit ➔ Developer tools ➔ Network,

you can check data usage:

Login: approx. 520 KB / per minute: 223 bytes / 60 min: approx. 13–15 KB

</details>


---

# 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://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/allgemeine-losungen-beim-telefonieren-mit-sipgate/sipgate-softphone-fehler-und-loesungen.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.
