[standards-jig] VoIP Standard for Jabber
vapor at 66oc.org
Thu Jan 16 13:05:41 UTC 2003
I think I may have failed to make my point clearly. At first I was
thinking it would be nice to adopt a non standard protocol. But as time
progress It became clearly not what jabber was about. So what I am
proposing is that jabber find one of the standards based protocols,
whether it be SIP or h.248 and adopt it as the defacto standard for voice
with jabber. Then if any others come along that we want to connect to,
transports can be written to communicate with the other standards. But
if we dont have one that is officially the Standard for jabber clients to
support, I dont think the jabber clients will adopt any voice very
So what I think is needed is a standard adopted, and then working toward
a proof of concept impementation of that standard for both client and
I dont want to see the voice protocol relying or requiring peer2peer
communication. That typically becomes and administrative hell for
I also envision voice conference server components written for jabber
too. But that would probably be a ways down the road.
On a side note, one of the problems I have seen discussed with VoIP is
that there are too many standards available. Because of that, I think We
need to adopt the one with the most potential and te one that would "fit"
with jabber the best.
From: "Richard Dobson" <richard at dobson-i.net>
To: <standards-jig at jabber.org>
Date: Thu, 16 Jan 2003 11:18:16 -0000
Subject: Re: [standards-jig] VoIP Standard for Jabber
> > I spent a while yesterday on jdev pounding the pulpit about jabber
> > VoIP. At first I was pushing to try to work with the TeamSpeak
> > (www.teamspeak.org) to figure out a way of integrating Teamspeak into
> > jabber. But as the discussion progressed it became apparent that as
> > it would be, it would not be a suitable solution for voice support in
> > Jabber.
> Im not sure if VoIP should really be specifically built in to the
> protocol, this is a client issue.
> > So what jabber really needs is a VoIP Standard to adopt and stick
> > any other VoIP technologies want to be adopted after that, transports
> > written to merge the two. Or at least that is my personal opinion.
> This is IMO not a protocol issue so creating transports is irrelivant,
> if we were altering the VoIP protocol into some jabber protocol then we
> not embrasing standard protocol (since we are altering it), I dont see
> point in branching out into this when solutions already exist, SIP is
> for things such as this and if we go creating our own standards for
> everything then it is doomed to failure, since IMO it will make people
> even less of Jabber and even less likely to adopt, all is really
> is some kind of initiation protocol.
> > Personal experience has shown me that Jabber not having Voice support
> > into it has kept quite a few away from adopting it.
> But it doesnt need it built into the Jabber protocol itself, again its
> client side issue, the protocol being used is irrelivant, be it Jabber
> SIP or something else, the user doesnt want to know those details as
> long as
> it is there and works. Why not just work with others who have already
> significant work into this instead of doing a lets invent our own
> > And finally, this could prove to be an area that Jabber blows the
> rest of
> > the industry away. **In Comming Pipe Dream** Jabber enables users
> > anywhere to use the net for presence, messaging, voice and video
> > communications with anybody anywhere... **End Pipe Dream**
> But it already does to a degree using callto: urls in jabber:iq:oob,
> this is
> used by some clients to initiate the computers built in voice and video
> conferencing software, e.g. netmeeting in Rival. When using jabber like
> for initiation and handing off to another application the protocol
> largely irrelivant, again all is needed is an initiation protocol.
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards