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

Pin the stable release, beta lane and architecture

PhonerLite is a Windows SIP softphone. On October 18, 2026, the first-party download page listed 3.46 as the stable release, updated October 12, 2026, and 3.47 as beta. It offers installer and portable ZIP packages for 64-bit and 32-bit Windows and an ARM64 choice. The 3.46 note adds ARM64 downloads for optional Piper and Whisper components and says stability improved.

Keep release lane, processor architecture, installer or portable format, downloaded artifact, signature result and installed executable separate. A higher beta number is not the production default, and a release-note fix is not proof that one workstation, account or call path was exercised.

Resolve the actual data directory before changing files

PhonerLite chooses its configuration location from write access. When the program directory is fully writable, it stores configuration there; otherwise it uses %APPDATA%\PhonerLite. The documented files include PhonerLite.ini for global settings and selected sound devices, sipper.ini for SIP profiles and account information, logbook.csv for call history and phonebook.csv for contacts.

Portable therefore does not mean stateless, and moving the executable can change which directory is writable and which data set loads. Record the running executable, user identity, program-directory permissions, resolved data path, file timestamps and hashes before copying or deleting anything. If Phoner and PhonerLite share one directory, the vendor says they also share sipper.dll and sipper.ini; treat that as another possible owner, not a harmless duplicate.

Keep profile storage, selection and registration distinct

PhonerLite supports multiple SIP profiles but only one is active at a time. The release history records fixes for loading the correct profile in 3.40 and switching profiles from the status bar in 3.44. Those entries are version-scoped vendor notes, not proof that a missing profile was deleted or that 3.46 selected the intended account on a particular PC.

The project warns that sipper.ini contains all profile settings, including reusable encrypted passwords. Protect it as a credential-bearing asset. Preserve the profile name, registrar or proxy, username, authentication name, realm, transport and registration result separately. A visible profile is not an active one, and a successful REGISTER does not prove inbound routing, caller identity, media, transfer or emergency behavior.

Treat PLP provisioning as a controlled import

A .plp file maps values into sipper.ini; the documented example can contain a plaintext Password, or a reusable PWD value copied from an existing profile. The installer associates the file type, while a portable copy can register it using PhonerLite.exe /INIT. File association, opening the wizard, accepting an import, activating a profile and registering remain separate observations.

The vendor says the debug window displays the complete sipper.ini path at startup. Use that path as an observation, not as permission to expose or overwrite the file. Deliver provisioning through an authenticated channel, avoid tickets or chat attachments, and rotate credentials if a profile or recovered file escaped its intended custody.

Preserve global audio state, call history and recording custody

PhonerLite.ini owns global settings such as selected sound devices, while a profile owns SIP settings. The application shows microphone and speaker state separately and lets the user choose among devices; Windows still owns the underlying device ports and mixer behavior. A recovered profile can therefore register while the wrong microphone or speaker remains selected.

The logbook and recording are also different artifacts. PhonerLite stores call history in logbook.csv; starting a recording writes a WAV file and records its filename in the logbook. A row does not prove that the file exists, is complete, decodes or contains the intended call. Recording authorization, WAV creation, filename linkage, transcription, retention and deletion remain separate controls.

Pilot update, move, rollback and restored state

Back up the observed configuration set before an approved update or portable move. Test first launch, active profile, registration, inbound and outbound calls, audio-device selection, DTMF, hold, transfer, sleep and wake, restart, update and rollback. When restoring data, compare files and import only the intended profile, global settings, contacts, history and recording links; do not replace a known-good directory wholesale with unexplained older credentials.

Verify TLS signaling and SRTP or ZRTP media independently on the actual call. Record package, version, architecture, executable path, data directory, active profile, PBX or service, file evidence and timestamps. No PhonerLite installation, update, migration, profile, file, protection, recording, transcription, compatibility, availability, price or call behavior was tested for this guide.

Trace a missing PhonerLite profile from the executable outward

Use the PhonerLite local-state diagnostic to prove the running package, resolved data directory, files, active profile, registration and call state.