Opened 9 years ago

Last modified 8 years ago

#12099 new plugin request

jingle in pidgin

Reported by: Hsilgos Owned by: deryni
Milestone: Component: XMPP
Version: 2.7.1 Keywords: jingle other client
Cc:

Description

Hi. I develop client for jabber. Now i'm adding support for jingle. When i call to pidgin, session starts and we hear each other. When i call from pidgin to my client, session starts, pidgin hears my client, but my client can't hear pidgin. I observed traffic in "Wireshark" and saw, that no any packet received from pidgin in this case. I don't understand, which difference between this situations. Somebody can help me? I can provide all xmpp-traffic when i try start session.

Change History (5)

comment:1 follow-up: Changed 9 years ago by malu

Do you set the ICE controlling role correctly? There used to be a bug in Pidgin, where receiving calls from Psi failed, due to Pidgin not setting the controlling role correctly. Do you use some existing library to implement ICE? You can look at ticket #11276 for reference.

comment:2 in reply to: ↑ 1 Changed 9 years ago by Hsilgos

Replying to malu:

Do you set the ICE controlling role correctly? There used to be a bug in Pidgin, where receiving calls from Psi failed, due to Pidgin not setting the controlling role correctly. Do you use some existing library to implement ICE? You can look at ticket #11276 for reference.

Xm... I use psi's ICE implementation (last version), may be it's why i get this error. I want to read more about this mistake, but it's seems that you incorrectly pointed out number of ticket. 11276 is about tray icon.

comment:3 follow-up: Changed 9 years ago by malu

Oh, sorry, it was #11267 And you use a current version of Pidgin?

comment:4 in reply to: ↑ 3 Changed 9 years ago by Hsilgos

Replying to malu:

Oh, sorry, it was #11267 And you use a current version of Pidgin?

I use 2.7.0 Is it sense to use 2.7.1 ?

comment:5 Changed 8 years ago by Robby

  • Component changed from unclassified to XMPP
  • Owner changed from rekkanoryo to deryni
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!