A softphone is just your extension running as an app instead of a desk handset — same number, same voicemail, but on your laptop or phone. This guide gets you registered and making calls in about five minutes. TEST
You'll need the SIP credentials from your welcome email: a username (your extension), a password, and a server address (something like sip.londonict.com). If you can't find them, ask us to resend — never share them in chat or email threads.
Before you start
- A reliable internet connection — wired or strong Wi-Fi. Softphones are sensitive to packet loss, not just speed.
- A headset. Laptop mics echo; a £20 USB headset transforms call quality.
- Five minutes of quiet to test a call.
Install the app
dfdfdf
dfdfdfdf
dfdfdfdf
dfdfdfdf
dfdfdfdf
dfdfdf
We support the same SIP app across platforms, so the steps barely differ:
| Platform | App | Where to get it |
|---|---|---|
| macOS | Groundwire / Zoiper | Mac App Store |
| Windows | MicroSIP / Zoiper | Vendor download |
| iPhone / iPad | Groundwire | App Store |
| Android | Zoiper | Play Store |
Software phones can't reliably reach 999 / 112 emergency services and won't share your location. Keep a mobile to hand for emergencies.
Add your account
Open the app and add a new SIP account. You only ever need four fields:
; The four values from your welcome email
username = 2041 ; your extension
domain = sip.londonict.com
password = •••••••• ; paste, don't retype
transport = TLS ; encrypted; falls back to UDP if blocked
Most apps auto-detect the rest. If yours asks for a port, use 5061 for TLS or 5060 for UDP.
On desktop you can jump straight to the dial pad with the keyboard shortcut ⌘ K — handy when a call comes in while you're heads-down in something else.
Check it registered
A registered account shows a green dot. If it's red, test that the SIP port is reachable from your network:
# TLS first, then plain UDP as a fallback check
nc -vz sip.londonict.com 5061
nc -vzu sip.londonict.com 5060
If those time out, a firewall is blocking SIP — see troubleshooting below.
On mobile
Mobile is the same four fields, with one extra consideration:
Leave push notifications enabled. Without push, the OS suspends the app to save battery and you'll miss calls. With push on, the app wakes only when a call actually arrives — so battery impact is negligible.
Troubleshooting
- One-way audio — almost always NAT/firewall. Make sure UDP 10000–20000 (RTP) is open outbound, and prefer TLS+SRTP.
- Choppy or robotic calls — packet loss. Switch off Wi-Fi power-saving, or go wired. Run a line test before blaming the line.
- Registers, then drops every few minutes — the firewall is timing out the SIP session. Lower the registration interval to 60 seconds, or ask us to enable keep-alives.
- No incoming calls on mobile — push is off, or the app was force-quit. Reopen it and re-enable notifications.
Still stuck after that? Open a ticket with the app name, platform and whether the dot is red or green, and we'll have you sorted quickly.