Record the 3.22.19 package before assigning a regression
On October 17, 2026, MicroSIP’s current-version pointer and primary download table listed 3.22.19 for both the regular and Lite editions with an October 3 release date. The table offered installer and portable ZIP forms. Preserve retrieval time, exact filename, edition, package form, installed executable version and software-distribution record; a managed catalogue, portable directory or cached page can retain another build.
The publisher notes improved DTMF tone playback while suppressing local tones during calls, a microphone-muted fix, corrected outgoing calls where P-Asserted-Identity replaced the dialed extension, PAI visibility in Call Manager, call-state and timer improvements, and detection of memory corruption associated with problematic audio devices or drivers. These are release notes, not proof that one installation has the defect, receives the fix or is compatible with its PBX, headset, driver or security policy.
Separate regular, Lite, installer and portable custody
The official table distinguishes the regular build, which lists video support, from Lite, which does not, and supplies installer and portable ZIP forms. Linux, macOS and BSD are described through Wine rather than native packages. A package name does not establish support for one operating-system build, enterprise control, audio device or emergency workflow.
Portable configuration can reside with the executable in an INI file. The 3.22 series also records account and settings export, shortcut and call-log export, and migration of call history to a database. Inventory the executable, configuration, account secrets, contacts, call history, recordings, logs, exports and update owner separately. Encrypt and restrict retained copies, and rotate credentials after workstation or archive loss.
Trace dialed target, SIP identity and asserted identity
MicroSIP account fields separate SIP server, proxy, username, domain, login and password, while its dial plan can transform or block entered digits. Preserve the entered value, post-dial-plan Request-URI, From identity, authorization username and any P-Asserted-Identity on the actual leg before assigning a routing or caller-ID failure.
The 3.22.19 notes say outgoing calls no longer replace the originally dialed extension with P-Asserted-Identity and that outgoing PAI is shown in Call Manager technical information. A displayed value or publisher fix note is not proof that the installed build generated the right request, or that the PBX accepted, trusted, forwarded or presented that identity. Treat the dialed destination, asserted identity, Hide Caller ID control and final presentation as separate evidence.
Verify signaling and media protection independently
MicroSIP documents UDP, TCP and TLS signaling plus disabled, optional SRTP, mandatory SRTP, DTLS-SRTP with SRTP fallback and DTLS-SRTP without that fallback. Record the configured policy, certificate validation result, negotiated SIP transport, accepted media profile, keying method and any fallback on the exact call.
The documentation scopes media protection to the softphone-to-PBX leg and notes that the PBX can access the media. A PBX, SBC, recorder or carrier can create another leg with a different policy. TLS registration does not prove SRTP, and an SRTP setting does not prove a trusted TLS connection or end-to-end confidentiality. Do not lower certificate or media policy simply to make one call connect.
Keep local DTMF playback, transmitted digits and remote action separate
The 3.22.19 notes describe improved DTMF tone playback and say local DTMF tones are not played during calls. The help page separately documents Auto, in-band, RFC2833 and SIP INFO choices, with Auto using the RTP event method by default and falling back to in-band when the peer does not advertise support in SDP. Preserve the exact configured label, offer and answer, payload mapping or INFO message, transmitted event and remote application result.
Local audible feedback is not the transmitted digit, and the presence of an RTP event is not proof that an IVR accepted it once. Do not switch every endpoint to in-band or SIP INFO to correct one untraced failure. Compare the same digit timing and method on one authorized control call, especially when a PBX or carrier bridges two legs with different DTMF representations.
Pilot update, network transitions and diagnostic-data handling
Run an authorized pilot through first sign-in, inbound and outbound calls, bidirectional audio, DTMF, hold, transfer, rejection, sleep and wake, audio-device changes, VPN and address changes, IPv4 and IPv6 where required, restart and rollback. MicroSIP troubleshooting suggests isolating interfaces, selecting local or public addresses and controlled STUN, ICE or source-port changes; change one variable at a time and preserve the prior value.
MicroSIP says automatic crash reports can include a crash dump, operating-system name and version, and the MicroSIP log when logging is enabled, while excluding passwords. Treat that as a documented content statement rather than proof that a log contains no identities, numbers, addresses or call metadata. Decide whether transmission is authorized, minimize logging, review retained files and protect support attachments. No package, installation, Windows host, file, credential, contact, SIP identity, PBX, certificate, network transition, DTMF event, transfer, diagnostic report, protected session or live call was tested for this guide.
Separate configured accounts, the active account and Local Account
MicroSIP can store several SIP accounts, but its help page says only one is active at a time. The active account supplies the current registration and ordinary call identity. Local Account is different: it enables direct IP or domain calls without registration. A successful Local Account call therefore does not prove registrar, proxy, authentication, inbound routing or the production account.
For each test, retain the selected account label, server and proxy chain, username, domain, authorization login, transport, registration result and dialed target. Protect passwords and tokens. When changing accounts, prove which identity sent the REGISTER and INVITE rather than reading a saved account list as live state.
Choose Single Call Mode or Call Manager deliberately
Single Call Mode is the documented default. Call Manager enables multiple calls, conferences and attended transfer. That is a client interaction model, not proof that the PBX or provider permits the resulting dialogs, transfer method or conference media. Closing a Call Manager call tab terminates that call, and closing Call Manager terminates its active calls, so include window and tab behavior in user acceptance.
Record the enabled mode, call count, dialog identifiers, hold state and transfer or conference result. Presence, BLF and pickup also depend on PBX support. Do not mark these ready from visible buttons alone.
Keep negotiated media, microphone state and Windows rendering separate
MicroSIP lets the user choose audio devices, codec priority, voice activity detection, echo cancellation and input level controls. These controls sit after account selection and alongside, not inside, SIP registration. Prove the SDP offer and answer, RTP packet direction and decoding before changing Windows input, output or driver state; prove local capture and playback before changing codecs or NAT.
The 3.22.19 notes include a microphone-muted fix and memory-corruption detection associated with problematic audio devices or drivers. Those notes do not prove that an uninspected driver is faulty or that an update repairs one workstation. Preserve the exact build, device, driver, MicroSIP input and output, Windows per-app route, mute state, level indication, application log and crash-report authorization before changing or replacing anything.
Keep negotiated media and Windows audio rendering separate
MicroSIP lets the user choose audio devices, codec priority, voice activity detection and echo cancellation. These controls sit after account selection and alongside, not inside, SIP registration. Prove the SDP offer and answer, RTP packet direction and decoding before changing Windows input, output or driver state; prove local capture and playback before changing codecs or NAT.
The 3.22.18 notes mention memory-corruption detection related to faulty audio devices or drivers. That is a diagnostic signal, not a declaration that a device is incompatible or that updating a driver will fix every silent call. Preserve the exact device, driver, selected MicroSIP input and output, Windows per-app route, application log and crash-report authorization.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- MicroSIP project and platform scope ↗
- MicroSIP stable downloads and changelog ↗
- MicroSIP current-version pointer ↗
- MicroSIP account, call and network settings ↗
- MicroSIP troubleshooting ↗
- MicroSIP frequently asked questions ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.