You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Initiate a call via a TAPI oder CSTA Interface #617
currently only "tel:"-Links are available which can only used if a proper handler ist available
Proposed solution
Also implement methods to use a TAPI interface or a direct CSTA MakeCall routine
Alternatives considered
Alternatifly the user could install a extra SW that handles TAPI calls and offers a tel: handler.
As most of these programs are not available open source there would be additional costs for the implementation of the service.
Therefore a direct implementation should be better.
Context
I am using (or intend to use) Lagebuch operationally in a fire brigade
Thanks — parked in the Backlog for now rather than a release milestone, for two reasons:
Which interface comes first depends on the device. Could you check what the Gigaset DL500a actually exposes to a PC: a TAPI service provider (TSP) on Windows, CSTA over TCP, or both? That decides the first slice.
Only you can test it. None of the maintainers has the hardware, so this needs someone who can try a build against the DL500a.
How it would fit: a desktop-only dialling service behind an interface (the way the file dialogs are done), with tel: staying the default and the only path on Android. Nothing in the .fwincident file changes, so it is not tied to the 1.0 file-format freeze and can be moved into a release once the above is clear.
Findings: a separate tel: → TAPI tool instead of TAPI inside Lagebuch
Lagebuch keeps doing one thing well, opening tel: links, and a small dedicated tool turns tel: into a TAPI call on Windows. That keeps Windows telephony, device quirks and a test burden nobody but the hardware owner can carry out of Lagebuch, and it helps every other program in the ELW that opens tel: links too.
1. The DL500A does offer TAPI — via Gigaset QuickSync. QuickSync installs a TAPI driver for the DL500A over the LAN ("CTI over Ethernet"); latest is 9.0 (build 9.0.883, September 2021), 64-bit build listed for Windows 10/11. Outgoing calls only — incoming calls are not signalled, which is fine for click-to-dial. So CSTA is not needed for this device. Caveat: the only user reports found are 2011–2015 forum posts, some saying it did not work reliably.
Sources: TAPICall – Gigaset TAPI drivers, DL500A manual, telefonanlagenforum.de
2. An open-source tool for exactly this already exists, unmaintained.oliversalzburg/TelProtocolHandler (GPL-3.0, archived 2023, last code 2017) and its fork reck1610/click-to-dial (last change 2019) register as the tel: handler and dial on a chosen TAPI line. C#, .NET Framework 4.5, WinForms, JulMar ITAPI3. No release binaries. Nothing maintained turned up.
3. Windows 10/11 detail: an installer can register as a capabletel: handler but cannot make itself the default — the user picks it once under Settings → Apps → Default apps → Choose defaults by link type.
@ChrArlt — could you test click-to-dial against the DL500A?
The zip (click-to-dial-b59ab30-win-x86.zip) follows in the next comment. It is a build of reck1610/click-to-dial at b59ab30, source unchanged, cross-built for .NET Framework 4.5 / x86. It is unofficial and unsigned (SmartScreen will warn), test use only; GPL-3.0 licence included.
SHA-256 of the zip: e9995e988be29040ececdcde393424261a84e672e6ce415185df0ac0d99ac0e6
Prerequisites
Gigaset QuickSync installed, its TAPI line visible (Control Panel → Telefon und Modem)
Unzip to a permanent folder, e.g. C:\Tools\click-to-dial — setup writes that path into the registry.
Start tel.exe without arguments → setup.exe asks for admin (UAC), then pick the DL500A's TAPI line.
Make TelProtocolHandler the default for TEL under Default apps → by link type.
Test with start tel:891234567 in cmd.
Known quirk — please read before testing:tel.exealways prefixes a 0 (an outside-line code for a PBX). tel:891234567 dials 0891234567. A normal number as Lagebuch emits it, tel:0891234567, would dial 00891234567, and tel:+49… becomes 00049…. So for this first test, drop the leading 0. Should the DL500A sit behind a PBX that needs 0 for an outside line, it is exactly right.
What would help most:
Does the TAPI line show up in the selection dialog?
Does start tel:<number without leading 0> make the DL500A dial?
Any error message, plus log-file.txt (next to tel.exe or in the folder it was started from) — remove phone numbers before posting it.
If the line dials, the tool works with this hardware and the next step is a small, maintained CodeForFire tool (configurable prefix, +49 handling, current .NET) — still with no change in Lagebuch. If it does not, we know whether the problem is QuickSync's TAPI driver or the tool.
In general the DL500A supports both methods with a Windows 10 driver. As we will have to update to Windows 11 in the near future we will use TAPI connectivity. Then only CSTA is available for initiating a call.
The above mentioned tools where already found, but as the are quite old SW that are not tested against current windows versions it does not seem to be a proper solution for the first glimpse.
Nevertheless I will check by chance wether this can be an interim solution.
Tested on a real DL500A: dialling works without QuickSync, TAPI or CSTA
QuickSync is not coming back — Gigaset has withdrawn it from download and states it offers "no replacement product or alternative software" (Gigaset support). But QuickSync was only a front end: the DL500A itself accepts AT commands from a "Datengerät" to place outgoing calls (manual, Datengeräte nutzen). That needs no driver at all.
Tested today on a DL500A (firmware 41.173.000) from a Linux laptop over Bluetooth:
The base offers a Serial Port Profile (SPP) on RFCOMM channel 1. Over it:
AT → OK
AT+CGMI → Gigaset Communications GmbH
AT+CGMR → 41.173.000
ATD <number> → OK, CLIP:EXTERN, CONNECT
ATD made the DL500A dial out on its line; the call came through, and it stayed up on the base after the Bluetooth link was closed. Same command set as QuickSync4Linux (GPL-3.0, maintained) uses.
One trap: if the PC also has the DL500A connected as an audio device (the desktop grabs its Hands-Free service automatically after pairing), every connection to the serial port hangs until it times out. Disconnect the audio side first; the serial connection then opens instantly.
About CSTA: I could not find any evidence that the DL500A speaks CSTA — Gigaset's CSTA documentation covers the N670/N870 IP PRO only. @ChrArlt, where did the CSTA information come from? And Windows 11 still ships TAPI 2.x, so "Windows 11 means no TAPI" is not a given either — but with the above, neither is needed.
@ChrArlt — could you repeat this on a Windows 11 PC?
Pair the DL500A with the PC (Bluetooth on at the base; Menü → Bluetooth → Suche Datengerät if the PC side does not find it).
Settings → Bluetooth & devices → More Bluetooth settings → COM Ports: note the outgoing COM port for the DL500A's "SPP" service (add one if none is listed).
Make sure the DL500A is not connected as an audio device on that PC (Bluetooth & devices → DL500A → Disconnect the audio side, or remove it from Sound).
Open the COM port in PuTTY (Serial, 115200 baud), type AT → OK, then ATD <your mobile number>.
If that dials, the next step is a small CodeForFire tel: handler for Windows: register for tel:, normalise the number (+49… → 0…, configurable prefix), connect to the SPP port, send ATD, disconnect. Nothing changes in Lagebuch — it keeps opening tel: links, and every other program in the ELW gets click-to-dial too.
Still open: the LAN ("QuickSync over Ethernet") protocol is undocumented. While a Windows 10 PC with QuickSync is still around, a Wireshark capture of one QuickSync call would show whether it is the same AT commands over TCP — that would remove the Bluetooth range limit.
Activity
ChrArlt commentedon Oct 17, 2026
Information for our special use case can be found when searching after information about Gigaset DL500a
DeepDiver1975 commentedon Oct 17, 2026
Thanks — parked in the Backlog for now rather than a release milestone, for two reasons:
How it would fit: a desktop-only dialling service behind an interface (the way the file dialogs are done), with
tel:staying the default and the only path on Android. Nothing in the.fwincidentfile changes, so it is not tied to the 1.0 file-format freeze and can be moved into a release once the above is clear.DeepDiver1975 commentedon Oct 17, 2026
Findings: a separate
tel:→ TAPI tool instead of TAPI inside LagebuchLagebuch keeps doing one thing well, opening
tel:links, and a small dedicated tool turnstel:into a TAPI call on Windows. That keeps Windows telephony, device quirks and a test burden nobody but the hardware owner can carry out of Lagebuch, and it helps every other program in the ELW that openstel:links too.1. The DL500A does offer TAPI — via Gigaset QuickSync. QuickSync installs a TAPI driver for the DL500A over the LAN ("CTI over Ethernet"); latest is 9.0 (build 9.0.883, September 2021), 64-bit build listed for Windows 10/11. Outgoing calls only — incoming calls are not signalled, which is fine for click-to-dial. So CSTA is not needed for this device. Caveat: the only user reports found are 2011–2015 forum posts, some saying it did not work reliably.
Sources: TAPICall – Gigaset TAPI drivers, DL500A manual, telefonanlagenforum.de
2. An open-source tool for exactly this already exists, unmaintained. oliversalzburg/TelProtocolHandler (GPL-3.0, archived 2023, last code 2017) and its fork reck1610/click-to-dial (last change 2019) register as the
tel:handler and dial on a chosen TAPI line. C#, .NET Framework 4.5, WinForms, JulMar ITAPI3. No release binaries. Nothing maintained turned up.3. Windows 10/11 detail: an installer can register as a capable
tel:handler but cannot make itself the default — the user picks it once under Settings → Apps → Default apps → Choose defaults by link type.@ChrArlt — could you test click-to-dial against the DL500A?
The zip (
click-to-dial-b59ab30-win-x86.zip) follows in the next comment. It is a build of reck1610/click-to-dial atb59ab30, source unchanged, cross-built for .NET Framework 4.5 / x86. It is unofficial and unsigned (SmartScreen will warn), test use only; GPL-3.0 licence included.SHA-256 of the zip:
e9995e988be29040ececdcde393424261a84e672e6ce415185df0ac0d99ac0e6Prerequisites
ITapi3.dllneedsMSVCR90.dllSteps
C:\Tools\click-to-dial— setup writes that path into the registry.tel.exewithout arguments →setup.exeasks for admin (UAC), then pick the DL500A's TAPI line.TELunder Default apps → by link type.start tel:891234567incmd.Known quirk — please read before testing:
tel.exealways prefixes a0(an outside-line code for a PBX).tel:891234567dials0891234567. A normal number as Lagebuch emits it,tel:0891234567, would dial00891234567, andtel:+49…becomes00049…. So for this first test, drop the leading 0. Should the DL500A sit behind a PBX that needs0for an outside line, it is exactly right.What would help most:
start tel:<number without leading 0>make the DL500A dial?log-file.txt(next totel.exeor in the folder it was started from) — remove phone numbers before posting it.If the line dials, the tool works with this hardware and the next step is a small, maintained CodeForFire tool (configurable prefix,
+49handling, current .NET) — still with no change in Lagebuch. If it does not, we know whether the problem is QuickSync's TAPI driver or the tool.DeepDiver1975 commentedon Oct 17, 2026
click-to-dial-b59ab30-win-x86.zip
ChrArlt commentedon Oct 19, 2026
In general the DL500A supports both methods with a Windows 10 driver. As we will have to update to Windows 11 in the near future we will use TAPI connectivity. Then only CSTA is available for initiating a call.
The above mentioned tools where already found, but as the are quite old SW that are not tested against current windows versions it does not seem to be a proper solution for the first glimpse.
Nevertheless I will check by chance wether this can be an interim solution.
DeepDiver1975 commentedon Oct 26, 2026
Tested on a real DL500A: dialling works without QuickSync, TAPI or CSTA
QuickSync is not coming back — Gigaset has withdrawn it from download and states it offers "no replacement product or alternative software" (Gigaset support). But QuickSync was only a front end: the DL500A itself accepts AT commands from a "Datengerät" to place outgoing calls (manual, Datengeräte nutzen). That needs no driver at all.
Tested today on a DL500A (firmware 41.173.000) from a Linux laptop over Bluetooth:
The base offers a Serial Port Profile (SPP) on RFCOMM channel 1. Over it:
ATDmade the DL500A dial out on its line; the call came through, and it stayed up on the base after the Bluetooth link was closed. Same command set as QuickSync4Linux (GPL-3.0, maintained) uses.One trap: if the PC also has the DL500A connected as an audio device (the desktop grabs its Hands-Free service automatically after pairing), every connection to the serial port hangs until it times out. Disconnect the audio side first; the serial connection then opens instantly.
About CSTA: I could not find any evidence that the DL500A speaks CSTA — Gigaset's CSTA documentation covers the N670/N870 IP PRO only. @ChrArlt, where did the CSTA information come from? And Windows 11 still ships TAPI 2.x, so "Windows 11 means no TAPI" is not a given either — but with the above, neither is needed.
@ChrArlt — could you repeat this on a Windows 11 PC?
AT→OK, thenATD <your mobile number>.If that dials, the next step is a small CodeForFire
tel:handler for Windows: register fortel:, normalise the number (+49…→0…, configurable prefix), connect to the SPP port, sendATD, disconnect. Nothing changes in Lagebuch — it keeps openingtel:links, and every other program in the ELW gets click-to-dial too.Still open: the LAN ("QuickSync over Ethernet") protocol is undocumented. While a Windows 10 PC with QuickSync is still around, a Wireshark capture of one QuickSync call would show whether it is the same AT commands over TCP — that would remove the Bluetooth range limit.
DeepDiver1975 commentedon Oct 27, 2026
implemented using: https://github.com/CodeForFire/freizeichen