[Standards-JIG] VoIP Jabber

[Heiner Wolf]

Hi,

>> Yes, Jabber creates open standards for IM. VoIP is also
communication,
>> but it is a different field. Apart from such wording theory, it seems
>> that nobody in the Jabber comunity had the time to create an
>> interoperable, open, firewall traversing, efficient VoIP system. The
>> conclusion is, that we don't make it, we use one or more. 
>
>Is the real problem, that no one has time for implementing and setting
a
>standard for VoIP or is it general policy that Jabber is IM and IM
only?

Apparently no one had the time for implementation. Although I assume
there are Jabber clients with VoIP, like Apple's. So the general
statement is not correct. Only, there is no open source, well known,
widely used Jabber/VoIP client. 

"The mission of the Jabber Software Foundation (JSF) is to create the
world's best protocols for instant messaging, presence, and other forms
of near-real-time communication based on XML."

I don't know if "near-real-time" includes VoIP. Maybe VoIP is too
real-time :-) A common thinking is that at least signaling for VoIP is
covered. 

_happy coding_
hw
--
Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
http://www.bluehands.de/people/hw
+49 (0721) 16108 75
--
Jabber enabled Virtual Presence on the Web: http://www.lluna.de/
Open Source Future History: http://www.galactic-developments.com/






>-----Original Message-----
>From: standards-jig-bounces at jabber.org
>[mailto:standards-jig-bounces at jabber.org]On Behalf Of Jens Mikkelsen
>Sent: Wednesday, February 09, 2005 4:40 PM
>To: Jabber protocol discussion list
>Subject: RE: [Standards-JIG] VoIP Jabber
>
>
>On Wed, 2005-02-09 at 15:33, Heiner Wolf wrote:
>> Hi,
>> 
>> >I dont know about SIP but Skype isn't an open standard. Isn't the
>> Jabber
>> >project all about creating open standards for IM. As IM is 
>going to be
>> >extended to include VoIP, there should be a serious open 
>standard for
>> >this. If this doesn't exist, Jabber could be first.
>> 
>> Yes, Jabber creates open standards for IM. VoIP is also 
>communication,
>> but it is a different field. Apart from such wording theory, it seems
>> that nobody in the Jabber comunity had the time to create an
>> interoperable, open, firewall traversing, efficient VoIP system. The
>> conclusion is, that we don't make it, we use one or more. 
>
>Is the real problem, that no one has time for implementing and 
>setting a
>standard for VoIP or is it general policy that Jabber is IM 
>and IM only?
>
>> 
>> Yes, Skype isn't an open standard. The point is not about 
>choosing Skype
>> as preferred VoIP for Jabber. Skype is just one example. We want to
>> exchange addresses to launch VoIP tools. The address is 
>probably just a
>> character string with a type. Simply speaking: client requests the
>> address, gets address and type, then launches the VoIP tool with the
>> address as parameter. Does not care what the tool does with 
>the string.
>> No mention of Skype. 
>
>I see. This is fine, but I must admit, that from a users point, I would
>much rather have one program/client taking care of everything, than
>having a client launching another client/tool.
>
>[...]
>> Yes, it hopefully is. The goal is to get the VoIP addresses across
>> gateways. So that a Jabber user can talk to an ICQ user. My simple
>> picture: Jabber client requests VoIP address from an ICQ 
>user. Gateway
>> somehow gets the ICQ VoIP address from ICQ-Central. Jabber client
>> receives the address and start the appropriate tool. The appropriate
>> tool to communicate with an ICQ user is probably an ICQ-VoIP 
>client. Bad
>> luck, but if the ICQ user has only ICQ-VoIP running then you 
>got to use
>> ICQ-VoIP. It would be cool to use your favourite open source 
>VOip tool
>> to talk to ICQ-VoIP, but that's real work, which nobody has 
>done yet. 
>
>Then it is nescesarry to have multible clients speaking different
>protocols or one client speaking multible protocols instead of having a
>single client speaking a single protocol, which is then translated in a
>gateway. 
>This is my opinion, but if JSF and the community don't think that VoIP
>is a part of IM, I understand.
>
>> 
>> What the Jabber community can do is to gateway IM/P messages. We will
>> not gateway VoIP traffic.
>> 
>
>OK
>
>[...]
>> hw
>> --
>> Dr. Klaus H. Wolf
>> bluehands GmbH & Co.mmunication KG
>> http://www.bluehands.de/people/hw
>> +49 (0721) 16108 75
>> --
>> Jabber enabled Virtual Presence on the Web: http://www.lluna.de/
>> Open Source Future History: http://www.galactic-developments.com/
>> 
>> _______________________________________________
>> Standards-JIG mailing list
>> Standards-JIG at jabber.org
>> http://mail.jabber.org/mailman/listinfo/standards-jig
>