-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Labels
nethvoiceBug or features releted to the NethVoice projectBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)The issue is related to NethLink (NethVoice Web client)
Milestone
Description
Description:
After releasing the new app, manual login works correctly, but scanning the QR‑code generated by the CTI no longer auto‑fills fields or triggers login.
Steps to Reproduce:
- Generate the QR‑code via CTI using the current string (e.g.
csc:vittorio@nethvoice.nethesis.it:3662ae06…@qrcode). - Launch the new app.
- Scan the QR‑code.
Current Behavior:
- The scanner reads the QR‑code but leaves the form empty and does not trigger login.
Expected Behavior:
- Upon scanning, all fields should be auto‑populated and the app should automatically log in.
Background & Context:
- In the previous version, the QR‑code included the
@qrcodemarker to distinguish the token‑based authentication flow. - With the new app, the trailing parameter must be the project’s CloudID (e.g.
@NETHVOICE), but replacing@qrcodewith@NETHVOICEremoves the marker and causes the token to be ignored.
Proposed Solution:
- Update the CTI QR‑code generator to produce strings in this format:
e.g.
csc:<username>@<domain>@qrcode:<password>@<CLOUDID>csc:vittorio@domain@qrcode:36....80aef3c2198ad5eb@NETHVOICE - Extend the generation logic so that for installations of the VOIPIU (rebrand) app, the CLOUDID used is
VOIPIUinstead ofNETHVOICE.
Notes:
- Ensure the in‑app parser always recognizes
@qrcode:and the correct CloudID segment.
Metadata
Metadata
Assignees
Labels
nethvoiceBug or features releted to the NethVoice projectBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)The issue is related to NethLink (NethVoice Web client)
Type
Projects
Status
Done