Freeze the failing build, user and filesystem state
Record the symptom, first affected launch, Linphone About version, package name and channel, operating system, signed-in user, executable path and whether the update also changed a profile, package source or wrapper. Preserve likely application-data and configuration roots read-only, but label the documented paths as 4.2 or 4.3 reference points until the running 6.2 process confirms them.
Do not reinstall, clear application data, delete an account, accept a fresh provisioning URL or copy old databases over the current profile. Those actions can rotate credentials, migrate schemas, replace the effective owner or erase the evidence that distinguishes a different path from lost data.
Prove the directories and files the running process uses
Correlate the executable, process owner and open-file or freshly modified evidence with the effective storage and configuration directories. Inventory linphonerc, linphone.conf, linphone.db, call-history.db, friends.db, any older message-history.db, database companions and the logs directory. Retain size, modification time, hash and permissions.
A file in the legacy location is not proof that 6.2 opened it. A new empty database may indicate another profile or a completed migration rather than deletion. Stop before merging files when the schema, journal set or owning process is uncertain.
Separate account, configuration, contacts, history and messages
Check the visible account and non-secret identity fields against the proved configuration source. Then compare contacts, call history and messages independently with the corresponding database evidence. A registered account can coexist with missing local history; recovered contacts do not establish that the selected SIP identity, audio settings or provisioning state is correct.
Protect database copies and configuration as sensitive assets. Do not publish passwords, SIP addresses, phone numbers, IP addresses, domains, message content or unrelated call records while asking for help.
Determine whether provisioning or defaults reapplied state
Preserve the configured provisioning URL, last retrieval result, XML hash, next-start timing, supported key and whether transient provisioning was enabled. Compare those with the effective runtime value after a controlled restart. The Linphone reference says remote configuration can overwrite proxy and authentication information, so a value that returns can be an ownership result rather than a failed local save.
Do not disable TLS, overwrite authentication data or remove the managed URL until the first mismatched layer is known. If provisioning is responsible, correct the authorized source and test one bounded client before a fleet change.
Create a sanitized reproduction before sharing logs
Use the desktop 6.x Help and Troubleshooting flow only after deciding who may receive the result. Clear debug logs, reproduce one incident, stop collection and preserve the exact interval. Review the original locally and create the smallest redacted extract or approved upload needed for support.
Record the upload or link separately from the underlying log and recipient access. A successful share action is not evidence that secrets were absent or that the support copy includes the failure.
Restore one object and retest the complete boundary
After proving the version, owner and schema, restore only the approved configuration, database or contact set from a verified copy. Keep rollback material and never replace files while Linphone is writing them. Restart under the normal user and confirm account selection, registration, contacts, history, messages, devices and logging.
Then run an authorized inbound and outbound call and required DTMF, hold or transfer, two-way audio, clean release and another restart. Record each result separately. No workstation, file, database, provisioning source, credential, PBX, packet, media stream, support exchange or call 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.
- Linphone stable Windows application archive ↗
- Linphone Desktop application files tree ↗
- Linphone Desktop linphonerc configuration reference ↗
- Linphone troubleshooting and support-log collection ↗
- Linphone remote provisioning ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.