New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 18, tbdialout, sip handler #12
Comments
Don't use userdefined URL in TBDialOut. That is intended for http. Just use sip: |
I followed your FAQ: |
So long since I wrote that part I'd forgetten about Ekiga and full sip URLs. It seems the way in which URL handlers are configured in Ubuntu has changed. I've just done this, and got somewhere… Create a file
I think this is needed because the default ekiga.desktop file does not have the -c %u part in the Exec statement. There may be a more elegant approach involving actions, but just creating a new sipurl.desktop seemed easier. Then run For me, that worked, in combination with the custom sip: URL |
Whow. That was great help. Thank you, that's the solution. |
Hi,
actually i am using tbdialout 1.8.0pre1 with Ubuntu 18, Thunderbird 68.7.0, with a snom phone. Works. Now i want to switch to a softphone. Ekiga is installed and works fine together with my sip provider, also by using command line with
ekiga -c sip:<number>@<provider>
in TBDialOut i did the setting to
"userdefinded URL"
and
sip:%NUM%@<sipprovder>
Trying to do a call, i get the message
sip is not a registered protocol or not allowed in this context
(not exactly, cause translated from german)
so i checked your wiki-page, found your advice about regisrtering sip and did this (with and without sudo):
gconftool-2 -s /desktop/gnome/url-handlers/sip/command '/usr/bin/ekiga -c %s' --type String
But the error message stays the same.
Checking the configuration with
gconftool-2 -t /desktop/gnome/url-handlers/sip/command
shows the correct entry.
Any suggestions would be great ...
The text was updated successfully, but these errors were encountered: