VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

PhonerLite profile, history or settings are missing after an update

Trace the running package, write context, resolved data directory, files and active profile before restoring credentials, history, contacts, audio settings or recording links.

Reviewed 2026-10-18Current first-party PhonerLite product, 3.46 stable and 3.47 beta release, profile, configuration-location, provisioning, audio-device, logbook, recording and transcription documentation reviewed October 18, 2026. Executable package, resolved configuration directory, active profile, credential-bearing sipper.ini, registration, call history, recording file, sound device and completed call remain separate evidence. No package, signature, Windows host, profile, credential, PBX, file, recording, transcription, headset, protected session or live call was inspected or testedIntermediateDocumentation based · not lab tested

Freeze the executable and both possible data locations

Record the symptom, first affected launch, Windows user, PhonerLite version and architecture, installer or portable package, executable path, shortcut target, working directory, elevation state and program-directory write access. Preserve the program directory and %APPDATA%\PhonerLite read-only before making changes.

Do not uninstall, rerun /INIT, import a PLP file or copy an old sipper.ini yet. Those actions can change associations, profiles, credentials or evidence while the actual fault is only a different resolved directory.

Prove which directory and files the running process loaded

Use the startup debug window to capture the full sipper.ini path, then correlate that observation with the executable, user and permissions. Inventory PhonerLite.ini, sipper.ini, logbook.csv and phonebook.csv in every candidate directory, retaining size, modified time, hash and access controls.

A file existing in %APPDATA% does not prove the current process opened it. Conversely, a portable folder containing files is not the active data source if write access or the running executable differs. If Phoner is installed in the same directory, record whether it shares the DLL and sipper.ini.

Separate missing profile, inactive profile and failed registration

Compare profile names and non-secret fields without publishing password material. PhonerLite activates one profile at a time, so verify the selected profile after proving its source file. Then preserve the registrar or proxy, username, authentication name, transport, DNS result, REGISTER exchange and response.

A profile can be present but inactive, active but rejected, or registered while inbound routing still points elsewhere. Do not reset credentials, disable TLS or change PBX routing until the first mismatched boundary is known.

Trace global settings, history and recordings independently

If the profile is correct but devices changed, compare PhonerLite.ini and the visible microphone and speaker selections. Device enumeration, Windows mixer or privacy permission, PhonerLite mute state and call media remain different observations.

For lost history or contacts, compare logbook.csv and phonebook.csv rather than inferring deletion from an empty screen. For a missing recording, start with the filename stored in the relevant logbook row, then prove file existence, size, decode, call identity, authorized access and retention separately. Do not recreate a recording or transcript from sensitive production audio merely to test the interface.

Restore only the intended state and protect credentials

After identifying the prior and current owners, back up both sets and restore only the approved profile, global settings, contacts, history or recording links. Treat every sipper.ini, PLP Password and reusable PWD value as a credential. Restrict custody, avoid ad hoc attachments and rotate the SIP password if exposure cannot be ruled out.

Do not merge INI or CSV files while either application is writing them. Preserve the before state, use a non-production copy where possible and keep a rollback path to the exact package and files.

Retest state, registration, calls and the next restart

Restart PhonerLite under the normal user and confirm the executable, resolved data directory, selected profile, visible contacts and history, sound devices and file links. Then run an authorized inbound and outbound call, DTMF, hold or transfer if required, two-way audio, clean release, sleep and wake, another restart and the approved update or rollback path.

Record each outcome separately. One recovered screen or successful REGISTER does not establish file completeness, protected media, recording integrity, future update safety or service compatibility. No workstation, file, credential, PBX, call, recording or recovery was inspected or tested for this diagnostic.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Client research · Current first-party PhonerLite product, 3.46 stable and 3.47 beta release, profile, configuration-location, provisioning, audio-device, logbook, recording and transcription documentation reviewed October 18, 2026. Executable package, resolved configuration directory, active profile, credential-bearing sipper.ini, registration, call history, recording file, sound device and completed call remain separate evidence. No package, signature, Windows host, profile, credential, PBX, file, recording, transcription, headset, protected session or live call was inspected or tested

PhonerLite 3.46: Windows packages, profiles and local-data evidence

Separate the 3.46 stable and 3.47 beta packages, architecture, executable path, resolved configuration directory, active SIP profile, local history, recordings and negotiated calls.

Read guide →
Hub · Primary softphone documentation reviewed through October 10, 2026; app, package, browser, mobile-wrapper, Windows audio and PBX interoperability not lab tested

Softphone research

Choose a desktop, mobile or browser calling client by SIP account, provisioning control, encryption and reliable call delivery.

Explore topic →
Guide · Primary desktop-softphone and operating-system documentation reviewed through October 10, 2026; app, audio-device and PBX interoperability not lab tested

Desktop softphones: SIP accounts and workstation operations

Evaluate installable clients on Windows, macOS and Linux with evidence for audio, registration, encryption and configuration ownership.

Read guide →
Hub · Vendor-neutral endpoint workflow plus Acrobits Cloud Softphone platform provisioning documentation reviewed October 8, 2026; exact parameters and precedence remain product-, service- and deployment-specific and no device or application was tested

Phone provisioning: repeatable endpoint deployment

Build a controlled path from a newly connected phone to the right identity, firmware and calling policy.

Explore topic →
Guide

PBX logs and packet captures: useful evidence with limited exposure

Collect enough to diagnose a call while protecting identities, secrets and audio.

Read guide →
Troubleshooting · RFC 3261 with current Asterisk PJSIP documentation; Asterisk 22 LTS and FreePBX 17 deployment context; no live test

SIP phone will not register: locate the failed evidence state

Separate local account state, REGISTER transport, endpoint identity, digest exchange, AoR binding and contact renewal.

Read guide →
Troubleshooting · Current Microsoft Windows audio-device and per-app routing guidance, Apple macOS input and output guidance and AVAudioSession route-change documentation, Android AudioManager reference, and W3C Media Capture and Audio Output specifications reviewed October 6, 2026; no computer, mobile device, dock, USB interface, Bluetooth device, browser, softphone, operating-system policy, PBX, media path or live call was inspected or tested

Softphone uses the wrong speaker, headset or microphone

Separate the connected device, operating-system defaults, per-app route, softphone selection, browser permission and active call path after docking, Bluetooth or USB changes.

Read guide →