KubuntuVOIPSOlution
|
Size: 2962
Comment: openwengo 2.1 SIP account support platforms other than the Wengo platform
|
← Revision 15 as of 2013-04-07 12:57:05 ⇥
Size: 3753
Comment: obsolete page
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from KubuntuVOIPSOlution | |
| Line 4: | Line 5: |
| * '''Created''': [[Date(2006-10-17T22:45:26Z)]] by AnthonyMercatante * '''Contributors''': AnthonyMercatante |
* '''Created''': <<Date(2006-10-17T22:45:26Z)>> by AnthonyMercatante * '''Contributors''': AnthonyMercatante , JavierJardon |
| Line 11: | Line 12: |
| Several QT/KDE solution exist, but none of them is currently included in Kubuntu. Ubuntu as Ekiga and we need to ship the best equivalent. | Several QT/KDE solution exist, but some of them is currently included in Kubuntu. Ubuntu as Ekiga and we need to ship the best equivalent. |
| Line 13: | Line 14: |
| * Wengophone: SIP solution using a closed network, that should be opened soon. * Jabbin: libjabbin based jabber client, supposed to support video with v3. |
* Wengophone: SIP solution using a closed network, that should be opened soon. -> no longer active * Jabbin: libjabbin based jabber client, supposed to support video with v3. -> no longer active |
| Line 18: | Line 19: |
| * KPhone: SIP solution for Linux. (note - using it for UDS MTV at this time - no problems) -- nixternal [[DateTime(2006-11-05T19:45:06Z)]] | * KPhone: SIP solution for Linux. (note - using it for UDS MTV at this time - no problems) -- nixternal <<DateTime(2006-11-05T19:45:06Z)>> * QuteCom: VoIP/IM solution (SIP, xmpp, msn, yahoo, aim...) with support for audio and video (on SIP conections). QuteCom is the new name for WengoPhone |
| Line 30: | Line 32: |
| * QuteCom: the most complete. | |
| Line 33: | Line 36: |
| The most complete solution was openwengo but the difficulties to work with upstream make it hardly choosable as the default provided solution. The future will probably be with kopete whom is targeted to act as a telepathy frontend. |
The most complete solution was QuteCom but the difficulties to work with upstream make it hardly choosable as the default provided solution. |
| Line 36: | Line 38: |
| Kcall is interesting and based on Decibel/Tapioca which is still a bit young to be implemented as the default VOIP solution (same issue than with telepathy). Kiax client is nice but using a completely different backend too (based on Asterisk) and creates the same issue than the previous described products. | Kcall is interesting and based on Decibel/Tapioca which is still a bit young to be implemented as the default VOIP solution (same issue than with telepathy). |
| Line 38: | Line 40: |
| We need to find a solution in the meantime waiting for telepathy to become a mature product (ubuntu targets this) and the best is probably to concentrate on a pure SIP client, which is a real standard widely used. We'll have to test all QT/Kde SIP clients (twinkle, kphone...) during the feisty dev cycle, and then choose the appropriate one, depending on the SIP implementation quality and good usability. |
Kiax client is nice but using a completely different backend too (based on Asterisk) and creates the same issue than the previous described products. We need to find a solution in the meantime waiting for telepathy to become a mature product (ubuntu targets this) and the best is probably to concentrate on a pure SIP client, which is a real standard widely used. -> Now telepathy is a mature product (we can do audio calls with empathy!!, a gnome/telepathy client). The future will probably be with kopete whom is targeted to act as a telepathy frontend -> Other solution was improving KCall who uses decibel/telepathy for not reinvent the wheel We'll have to test all QT/Kde SIP clients (twinkle, kphone...) during the jaunty dev cycle, and then choose the appropriate one, depending on the SIP implementation quality and good usability. |
| Line 42: | Line 49: |
Package KCall. Maybe is the best solution: it integrates well with KDE desktop and is based in decibel/telepathy. https://bugs.launchpad.net/ubuntu/+bug/252913 Package QuteCom: https://bugs.launchpad.net/ubuntu/+bug/241630 .PPA is avaliable here: https://edge.launchpad.net/~cavedon/+archive |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/kubuntu-voip-solution
Created: 2006-10-17 by AnthonyMercatante
Contributors: AnthonyMercatante , JavierJardon
Packages affected:
Summary
Kubuntu should integrate a VOIP solution out of the box, possibly providing video support, with interoperability with Windows/OSX.
Rationale
Several QT/KDE solution exist, but some of them is currently included in Kubuntu. Ubuntu as Ekiga and we need to ship the best equivalent. Softwares existing:
Wengophone: SIP solution using a closed network, that should be opened soon. -> no longer active
Jabbin: libjabbin based jabber client, supposed to support video with v3. -> no longer active
- Twinkle: SIP based solution, no video support is planed in the future.
- Kopete: Suposed to be libjabbin compatible, but doesn't work with latest libjabbin version.
- KCall: Telephony application of Kontact and based on Decibel framework. Once Decibel is functional, KCall will use the same.
KPhone: SIP solution for Linux. (note - using it for UDS MTV at this time - no problems) -- nixternal 2006-11-05 19:45:06
QuteCom: VoIP/IM solution (SIP, xmpp, msn, yahoo, aim...) with support for audio and video (on SIP conections). QuteCom is the new name for WengoPhone
Use Case
- Paul's ISP offers an SIP service, and he wants to use it with Kubuntu.
- Kate has contacts using windows or OSX, and wants to audio/video chat with them.
Scope
Kubuntu should focus on using the best software, with the best kde integration, and interoperable features.
Wengophone looks like the most complete software, but its network isn't currently opened to other SIP services. -> No more since version 2.1
- Jabbin doesn't support video at the moment.
- Twinkle is a superb SIP client, but is limited to audio.
- KCall: With Decibel it will be possible to use any telephony backend a plugin exists for. Kontact integration too.
QuteCom: the most complete.
There is no perfect solution at time.
The most complete solution was QuteCom but the difficulties to work with upstream make it hardly choosable as the default provided solution.
Kcall is interesting and based on Decibel/Tapioca which is still a bit young to be implemented as the default VOIP solution (same issue than with telepathy).
Kiax client is nice but using a completely different backend too (based on Asterisk) and creates the same issue than the previous described products.
We need to find a solution in the meantime waiting for telepathy to become a mature product (ubuntu targets this) and the best is probably to concentrate on a pure SIP client, which is a real standard widely used. -> Now telepathy is a mature product (we can do audio calls with empathy!!, a gnome/telepathy client).
The future will probably be with kopete whom is targeted to act as a telepathy frontend -> Other solution was improving KCall who uses decibel/telepathy for not reinvent the wheel
We'll have to test all QT/Kde SIP clients (twinkle, kphone...) during the jaunty dev cycle, and then choose the appropriate one, depending on the SIP implementation quality and good usability.
Implementation
Package KCall. Maybe is the best solution: it integrates well with KDE desktop and is based in decibel/telepathy. https://bugs.launchpad.net/ubuntu/+bug/252913
Package QuteCom: https://bugs.launchpad.net/ubuntu/+bug/241630 .PPA is avaliable here: https://edge.launchpad.net/~cavedon/+archive
BoF agenda and discussion
Kubuntu/Archives/KubuntuVOIPSOlution (last edited 2013-04-07 12:57:05 by HSI-KBW-078-043-071-031)