So do you mean: add code so that if someone calls your jabber client
using jingle, you can hand off that call to a sip phone somewhere
else?
It sounds like this should be implemented as a non-interactive client
that only supports the jingle-to-sip translation.
On 6/26/07, Jacek Konieczny <[EMAIL PROTECTED]> wrote:
On Tue, Jun 26, 2007 at 02:07:45PM +0200, Norman Rasmussen wrote:
> I'm not sure exactly what you want to do, but adding sip support to a jabber
> client doesn't sound like a good idea. (It would change it into a
> multi-protocol client)
It is not a full SIP client implementation. It's like creating AJAX
Jabber client -- HTML is implemented (as the interface between Jabber
and the web browser), but that doesn't make it a web browser or a
fully-featured web server.
I was thinking about that as a way to include voice messaging to my
console client -- I don't want to add codecs and voice-related
functionality to it -- it is already well done in sip clients, like
Ekiga -- I would just route the voice media to Ekiga... or a hardware IP
phone -- can you imagine a better user interface to voice messaging than
a physical telephone handset? Such hardware is available and 'talks'
SIP, why shouldn't we use that?
Greets,
Jacek
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
