Support for free(dom) VoIP clients
Bug #1182580 reported by
GenghisKhan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Audio Recorder |
New
|
Wishlist
|
Unassigned | ||
twinkle (Debian) |
New
|
Unknown
|
Bug Description
Please add support for the followings: ANT, Coccinella, Ekiga, Gajim, GPhone, IHU, Jitsi, Linphone, Mumble, Pidgin, Psi & Psi+, QuteCom, SFLphone, Twinkle.
http://
http://
http://
https:/
https:/
http://
https:/
https:/
http://
http://
http://
http://
http://
http://
http://
no longer affects: | twinkle (Ubuntu) |
Changed in twinkle (Debian): | |
status: | Unknown → New |
To post a comment you must log in.
Hello, spesification. This is how the media players interact the the Audio-Recorder program. Please see http:// specifications. freedesktop. org/mpris- spec/latest/
Those VOIP-clients should support the MPRIS2-
See the mpris2_ detect_ players( ) function in src/dbus-mpris2.c, it detects all players (and maybe voip-clients?) that broadcast themselves as org.mpris. MediaPlayer2. xxxx on the DBus. Replace xxxx with a name of your void-client.
Voip-clients should reply to these DBus (MPRIS2) requests:
"Identity" : They should return its name + version, like "Ekiga 2.3".
"DesktopEntry" : They should return the base_name of its desktop file.
If your desktop file is "xxxx.desktop" then return "xxxx". Drop the .desktop part.
Audio- recorder will read the program's executable name from "xxxx" + ".desktop" file.
The voip-clients should return data to the "Metdata" request and some kind of start/stop/paused signals.
The Pithos media player provides a good sample of simple MPRIS2-interface. kevinmehall. net/p/pithos/
http://
Please see: bazaar. launchpad. net/~osmoma/ audio-recorder/ trunk/view/ head:/src/ dbus-mpris2. c
http://
The Skype-module is espescialmente hardcoded for the audio-recorder. Please see the bazaar. launchpad. net/~osmoma/ audio-recorder/ trunk/view/ head:/src/ dbus-skype. c module.
http://
The other VOIP-clients should implement the MPRIS2 or equivalent standard. It may not be easy hardcode or maintain spesific modules for all of'em.
It is possible that the sound-menu also reads and responds to MPRIS2-messages (from the DBus) and displays correct play-information and status in the menu.