Top 7 Tips for Getting the Most from MicroSIP Lite

Troubleshooting Common MicroSIP Lite Connection Issues

MicroSIP Lite is a compact SIP softphone but connection problems can come from account, network, NAT, codec, or audio-device issues. Follow this step‑by‑step guide to diagnose and fix the most frequent problems.

1) No registration / “Offline” or red status

1. Check credentials: verify domain, SIP server, username (auth ID), password and optional proxy exactly as your provider supplied.
2. SIP server vs domain: if you use a nonstandard port append :port to both Server and Domain fields (or append to Proxy when using a proxy).
3. Transport: try UDP, TCP, then TLS. Some providers require a specific transport.
4. Server-side limits / blocks: ask provider to confirm your IP isn’t blocked or that you haven’t hit concurrent-connection limits. Try a different network or VPN to rule out blocking.
5. User-Agent blocking: some providers block MicroSIP; you can change User-Agent in microsip.ini to a permitted client string.

2) “Forbidden”, “Incorrect password” or auth errors

• Re-enter credentials; check whether provider expects the username or full SIP URI (e.g., 100@domain).
• If your provider requires registration with a proxy or different auth name, fill those fields.
• Check time/date on PC (TLS/secure auth can fail with incorrect system clock).

3) Can call but no incoming calls / missed calls

• Registration is required to receive calls — confirm green “Online” icon.
• If behind NAT: enable STUN, test with/without ICE, and try disabling “Handle IP changes.”
• Leave only one active network adapter or manually select the correct local IP in account settings.
• Set source port to 5060 (local port) if advised by provider.
• Disable SIP ALG in router; ALG frequently breaks SIP signalling.

4) One‑way or no audio (RTP)

• Firewall/ports: ensure RTP ports (usually a high UDP range, e.g., 10000–20000) are open on router and host firewall.
• NAT / public IP: if MicroSIP sends private IP in SDP, enable STUN or set public IP / local_net (on PBX) so media addresses are correct.
• Transport mismatch: try changing transport (UDP/TCP). RTP is usually UDP.
• Codec mismatch: select common codecs (G.711 μ/ A-law or Opus if supported) on both ends. Force codec in MicroSIP to test.
• Direct media / PBX settings: disable direct media or allow IP rewrite per provider/PBX instructions.
• Test with another client or network to isolate whether problem is MicroSIP, your PC/network, or the PBX/provider.

5) Calls drop or disconnect unexpectedly

• Check codec negotiation (use G.711 for testing).
• Disable SIP session timers in PBX if disconnects happen at regular intervals.
• Try different transport and toggle STUN/ICE and “Allow IP rewrite.”
• Router NAT timeouts or SIP ALG can cause drops — disable ALG and increase UDP timeout where possible.

6) Audio device errors / “Unable to open sound device”

• Grant microphone access in Windows Settings → Privacy → Microphone.
• Ensure both output and input devices exist and are not used exclusively by another app.
• Update audio drivers; check antivirus or security software (e.g., Kaspersky) for blocked microphone access.
• For RDP/virtual sessions, ensure audio redirection is enabled.

7) TLS/secure connection or certificate failures

• Ensure system time is correct.
• Confirm provider supports TLS and provides the correct SIP TLS port.
• If certificate validation fails and provider uses self-signed certs, consult provider for a secure workaround (avoid disabling validation permanently).

8) Persistent or intermittent registration failures

• Try clean MicroSIP install (close app, delete config files / microsip.ini backup, then restart).
• Disable “Handle IP changes” to avoid frequent re-registration if your IP shifts.
• If provider uses IP whitelist, you may need their support to add your current IP or use VPN.

Diagnostic checklist (quick)

• Credentials correct? ✓
• Green “Online”? ✓
• Transport set properly? (UDP/TCP/TLS)
• STUN/ICE tried?
• SIP ALG disabled on router?
• RTP ports open?
• Common codec selected?
• Audio device permissions and drivers OK?
• Test on different network/client?

When to contact your provider or PBX admin

• Repeated “Forbidden” or “Incorrect password” after verifying credentials.
• Provider-side IP blocking, whitelist requirements, or server errors (Bad gateway, Service unavailable).
• PBX logs show media sent to wrong IP or codec incompatibility—provide SIP/SDP logs to admin.

Useful logs & info to collect before support

• SIP trace / INVITE and 200/401/403 responses (full SDP blocks).
• MicroSIP transport used and selected codec.
• Network environment (NAT type, router model, whether VPN used).
• Exact error messages and timestamps.

If you want, I can produce a short checklist you can copy into a support ticket, or walk through a specific error message you’re seeing.