Hi there,

I'm not sure whether this will be helpful or not, but Google provides
some info about the XMMP architecture here:
http://code.google.com/apis/talk/jep_extensions/extensions.html

As far as I know, Libjingle is the only way that voice calls can be
made with Google Talk at the moment, although they are apparently
working on a SIP implementation. Everything about Google Talk's
development is taking so ridiculously long though - the ideas the team
have are fantastic, but I wish Google would put more of its resources
into it. There's lots of information about Libjingle here, along with
diagrams and explanations: 
http://code.google.com/apis/talk/libjingle/libjingle_applications.html

Good luck!

Ian

On Feb 26, 11:23 pm, "anish" <[EMAIL PROTECTED]> wrote:
> hello,
>
> I have multiple questions regarding how to talk to googletalk using
> custom application.
>
> 1) due to the nature of my application, I would not like to use
> libjingle. so wanted to find out if there is a document that describes
> the overall architecture and messages used for different actions
> ( like, login, voice call, IM etc) for googletalk. I have noticed that
> formats for these messages is different then the ones in the proposed
> xmpp standards.( this is also mentioned on the libjingle web pages.)
>
> 2) is it possible to connect to googltalk client for voice call in
> federation mode? if so, how do one do that? similar to above, I am
> looking for detailed messages that are required?
>
> 3) I have noticed that libjingle 0.4.0 now supports video calls, so
> answeres to above two questions also needed for video calls.
>
> Thanks
> -anish


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to