On Dec 6 2006, 1:27 pm, "Andri" <[EMAIL PROTECTED]> wrote:
> Not conflicting. Major advantages would be to integrate Jabber to
> company's PBXs running SIP.
> Imaging not being at the office but on a hotel in London logged on to
> Google Talk. Then you get a call through work and you just take it on
> your computer for free instead of routing it through your cellphone.
> And besides, Google have already announced planning SIP support.
> -http://code.google.com/apis/talk/open_communications.html
> SIP, like XMMP is an open standard widely implemented in alot of VOIP
> hardware including PBX, phones and softphones.
> I have a SIP phone on my desk and an Icelandic phone number although I
> currently live in Denmark. Google Talk integration would enable "you"
> to call me by clicking on your computer for free.
And all of the exact same scenarios could be achieved by using
XMPP/Jingle/Jingle Audio if the PBX supports XMPP/Jingle/Jingle Audio.
And the implementation ends up being *much* cleaner than trying to
support multiple protocols in the client. If its a halfway decent VoIP
capable PBX, its already doing SIP, H.323, MGCP, maybe even SCCP, so
its already dealing with multiple access protocols, and is designed to
deal with that sort of thing anyway. XMPP/Jingle/Jingle Audio would
just be one more and should be more easily implemented there than
trying to juggle multiple protocols in the client.
I agree with Paul...skip SIP in the client, let the PBX talk
XMPP/Jingle/Jingle Audio and there are much larger benefits that accrue
across the community, not just in the one client software
implementation.
Jeff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-talk-open" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-talk-open?hl=en
-~----------~----~----~----~------~----~------~--~---
