Changes

Jump to: navigation, search

VoIP - Calling With a SIP URI

259 bytes added, 15:25, 23 July 2019
m
Get NetworkManager to takeover control of /etc/resolv.conf
* Ekiga (Linux)
* Linphone 4.0.1 (Android)
* Twinkle (Linux) - although currently (Dec 2018) there's a problem with SRV records when using systemd-resolved (on Ubuntu and Debian at least). Need to do
systemctl stop systemd-resolved
* Voipfone Softphone (Android) deserves a mention. It needs an account with voipfone.co.uk, but you can signup and try for free. Their softphone app works out of the box for calling SIP URIs - provided they don't have purely numeric usernames: so you can call an AAISP VoIP number (+44....) or AAISP's office (e.g. support@aa.net.uk) but you can't call sip:<number>@host (it'll call the number direct instead).
systemctl disable systemd-resolved
systemctl mask systemd-resolved
add the line
dns=default
to the ''main'' section of ''/etc/NetworkManager/NetworkManager.conf''
and then
rm /etc/resolv.conf
to get NetworkManager to take over control of resolving.
 
* Voipfone Softphone (Android) deserves a mention. It needs an account with voipfone.co.uk, but you can signup and try for free. Their softphone app works out of the box for calling SIP URIs - provided they don't have purely numeric usernames: so you can call an AAISP VoIP number (+44....) or AAISP's office (e.g. support@aa.net.uk) but you can't call sip:<number>@host (it'll call the number direct instead).
 
==Known not-working==
378
edits

Navigation menu