MicroSIP is a small, open-source Windows softphone that does one thing well and stays out of the way. It is a common choice for call centres because it is portable, uses almost no memory, and can be pre-configured and copied to every agent machine as a single folder. This guide covers a working configuration and the details that matter when you deploy it to more than one person.
Portable or installed
MicroSIP ships in two forms and the choice matters more than it looks.
The installer puts settings in the user profile, which is fine for one machine. The portable ZIP keeps microsip.ini next to the executable, which means you can configure one machine, copy the folder to every other agent, and have identical settings everywhere without touching each one. For any deployment past about three seats, take the portable build.
Download from the official site. The name is common enough that search results include repackaged builds carrying extras you do not want.
Adding the account
Open Menu → Add Account and fill in the fields that matter:
| Field | What goes in it |
|---|---|
| Account name | Any label you like — it only shows in the UI |
| SIP server | The hostname or IP your provider gave you |
| SIP proxy | Leave blank unless you were given an outbound proxy |
| Username | Your authentication user or account ID |
| Domain | Usually the same as the SIP server |
| Login | Normally identical to Username |
| Password | As supplied |
| Display name | What you want shown internally |
Leave Register ticked. Set Transport to UDP unless your provider specified TCP or TLS.
If you were given an IP-authenticated trunk rather than a username and password, MicroSIP on a workstation is the wrong place for it — IP authentication needs a stable public address, which a laptop on a dynamic connection does not have.
Pin the codec
In the account dialog, open the codec list and disable everything except what your route actually uses. For most international termination that is G.711 u-law (North America) or G.711 a-law (most of the rest of the world).
Leaving the full list enabled invites transcoding somewhere along the path, which adds delay and degrades audio on every call. Pinning also turns a silent quality problem into an honest, immediate failure — much easier to diagnose.
Audio devices, before anyone complains
MicroSIP defaults to the Windows default device, which changes the moment somebody plugs in a monitor with speakers. Under Settings → Audio, set the input, output and ringing devices explicitly to the headset.
Set ringing device to the machine's speakers rather than the headset if agents do not wear headsets constantly — a ring nobody hears is indistinguishable from a call that never arrived.
Turn off any Windows "audio enhancements" on the headset in Sound Control Panel. They are tuned for music and do unhelpful things to speech.
Dial plan rules save a lot of retyping
MicroSIP can rewrite numbers before dialling, which removes an entire category of agent error. Under Settings → Dialplan, add rules so agents can paste numbers in whatever format the CRM holds and still dial correctly.
A common pair of rules:
# strip a leading 00 international prefix
^00(\d+)$ -> \1
# strip a leading + so the trunk receives digits only
^\+(\d+)$ -> \1Confirm with your provider whether the trunk wants a leading + or digits only, then normalise everything to that. Numbers should reach the trunk in E.164 form: country code, then national number, no trunk prefix.
Deploying to a team
Configure one machine completely, then open microsip.ini in the portable folder. It contains the account block, codec selection, audio devices and dial plan in plain text.
Copy that folder to each agent machine and change only the account credentials. Give every agent their own SIP account rather than sharing one — shared credentials cause registration conflicts where whichever endpoint registered last receives the calls, and they make call records useless for attributing anything to anyone.
Audio device names differ between machines, so expect to set those per machine even when everything else is copied.
Common problems
Registered but no inbound calls. The router is closing the UDP mapping before the registration refreshes. Shorten the registration expiry or enable keep-alives.
One-way audio. SIP signalling is working while RTP media is not — usually NAT, a firewall blocking the media port range, or SIP ALG on the router rewriting headers incorrectly. Work through it in the order set out in the one-way audio guide rather than changing several things at once.
IVR menus do not respond to keypresses. DTMF method mismatch. MicroSIP defaults to RFC 2833, which is what most providers expect; if the far end wants SIP INFO, change it in the account's advanced settings.
Audio breaks up under load. Check whether the machine is genuinely short of CPU or the connection is short of upload capacity. Voice needs consistency more than speed — see SIP, RTP, codecs and bandwidth for how to size it.