Quote by adwin:ftp://adwinp.org/psi.avi <--- This is a little clip I made to demonstrate that it was possible to use the chat functions.
I can't connect to this server... maybe you can upload it some where else /fix the problem?
Quote by adwin:ftp://adwinp.org/psi.avi <--- This is a little clip I made to demonstrate that it was possible to use the chat functions.
There is a login and password required, so we can't see it. :-(Quote by adwin on 03-16-2006, 01:57:ftp://adwinp.org/psi.avi <--- This is a little clip I made to demonstrate that it was possible to use the chat functions.
Quote by Kev:Jingle support is client-side, so the servers don't need to be modified.
Quote by Kev:Jingle support is client-side, so the servers don't need to be modified.
Quote by Kev:Jingle support is client-side, so the servers don't need to be modified.
I don't think Kev did a lot of Jingle work in Psi ;-)Quote by techieg:Thanx again on behalf of the community on your works
The client asks the other client whether it wants to do a voice chat, the other client replies, both clients negiotiate how they will contact each other and what codecs they will use, and when they agree, they start chatting. The client needs to implement everything (negotiation, audio coding/decoding, connecting to the other client, ...), the server nothing. The only thing a server could provide is something to make the connections non-direct (i.e. all traffic goes via the server), which could help when both clients are unable to connect to each other directly (e.g. via a firewall)Could you please brief me (or us) how Jingle process actually works, from call initiation to acceptance and real-time streaming two-way p2p audio, codecs, RTP,etc and what needs to go on the server and/or client?