Difference between revisions of "VoIP - Calling With a SIP URI"

Jump to navigation Jump to search
m
Get NetworkManager to takeover control of /etc/resolv.conf
(Hmm, refer to numbers and the first examples are names...)
m (Get NetworkManager to takeover control of /etc/resolv.conf)
 
(3 intermediate revisions by the same user not shown)
* 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 just works out of the box for calling SIP URIs (although an update in March 2019 has stopped this working)
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 just works out of the box for calling SIP URIs - provided they don't have numeric usernames: so you can call AAISP's office (althoughe.g. ansupport@aa.net.uk) updatebut inyou Marchcan't 2019call hassip:<number>@host (it'll call the stoppednumber thisdirect workinginstead).
 
==Known not-working==
379

edits

Navigation menu