I cannot get Jingle to work at all. I’‘ve read docs, I’‘ve tried fresh installs. Still cannot get it to work. I’‘ve tried on Vista and 2003 server. Hasn’'t worked on either yet.
This is all local. The server has the windows client installed and we can text chat on it just fine but every time we try to use Jingle to make a computer to computer call, there is about a 10 second delay and then the following error pops up on the person’'s window that tried to initiate the call:
Session closed due to unable to negotiate session. This may be caused by firewall configuration problems.
My issue here is that since we’‘re all on the same network, there should be no firewall configuration issues as we’‘re all behind the firewall. However, I’'m willing to open some ports for this to work, however I do not see any listing of ports that the Jingle addon uses.
Does anyone have a list of the ports its trying to use or another solution otherwise?
The difference between IM messages and Jingle is that Jingle is a client -> client protocol. The server just sets up the call.
Therefore, if the clients themselves have firewalls, they will not necessarly be able to talk to each other. One solution to this is to use a Media Gateway on the Openfire Server.
From here I’'d suggest you:
Look at the traffic sent from the client using Spark. It should show what ports the client suggest you use.
Turn off the local firewalls in order to ensure they are the issue.
Have you find a soultion to this problem? If yes, then can you share it with me. Also, how has been your expernce so far with Jingle’s voice session setup? I am working on a project in which I am required to support PC-to-PC voice calls.