Bug 29649

Summary:	Empathy can not establish audio call to asterisk using XMPP:Jingle
Product:	Telepathy	Reporter:	Arie Skliarouk <skliarie>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	devurandom
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Arie Skliarouk 2010-08-18 08:46:13 UTC

asterisk 1:1.6.2.7-1 registers under skliarouk@gmail.com using GTalk.

I am able to establish voice calls to the asterisk using GTalk windows client.

When I try to do the same from empathy 2.30.2-0ubuntu1 (Ubuntu Lucid) I get following error on the asterisk side:

JABBER: asterisk INCOMING: <iq type="set" to="skliarouk@gmail.com/asterisk78B417C5" id="98726360956" from="skliarie@gmail.com/2b999d02"> <session type="candidates" id="1150454130" initiator="skliarie@gmail.com/2b999d02" xmlns="http://www.google.com/session"> <candidate name="rtp" generation="0" network="0" component="1" type="relay" protocol="udp" preference="0.007629" password="" username="fh6E9eY027CoqXVC" port="19295" address="209.85.229.126"/>
</session>
</iq>

JABBER: asterisk OUTGOING: <iq type='result' from='skliarouk@gmail.com/asterisk78B417C5' to='skliarie@gmail.com/2b999d02' id='98726360956'/>

JABBER: asterisk INCOMING: <iq type="error" to="skliarouk@gmail.com/asterisk78B417C5" id="aaaaj" from="skliarie@gmail.com/2b999d02"> <session initiator="skliarie@gmail.com/2b999d02" id="1150454130" type="transport-accept" xmlns="http://www.google.com/session"> <transport xmlns="http://www.google.com/transport/p2p"/>
</session>
 <error type="modify" code="400"> <bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
 <text>action 'transport-accept' unknown (using dialect 1)</text>
</error>
</iq>
[Aug 18 18:38:12] NOTICE[12434]: chan_gtalk.c:1769 gtalk_parser: Remote peer reported an error, trying to establish the call anyway

The empathy shows "Connecting..." till the call is terminated by asterisk.

Comment 1 Simon McVittie 2012-03-01 07:41:10 UTC

What version of telepathy-gabble was this?

Do you still see this bug with current versions of Gabble and Asterisk?

(In reply to comment #0)
> JABBER: asterisk INCOMING: <iq type="error"
> to="skliarouk@gmail.com/asterisk78B417C5" id="aaaaj"
> from="skliarie@gmail.com/2b999d02"> <session
> initiator="skliarie@gmail.com/2b999d02" id="1150454130" type="transport-accept"
> xmlns="http://www.google.com/session"> <transport
> xmlns="http://www.google.com/transport/p2p"/>
> </session>
>  <error type="modify" code="400"> <bad-request
> xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
>  <text>action 'transport-accept' unknown (using dialect 1)</text>
> </error>

This is telepathy-gabble (as used by Empathy) reporting that it couldn't understand a message sent earlier by Asterisk.

"Dialect 1" is the proto-Jingle protocol used by libjingle3, before it became an XMPP standard as XEP-0166 (which would be called dialect 3 or 4 in Gabble). So Gabble is basically saying "given that you're speaking the libjingle3 dialect, I didn't expect you to send transport-accept". transport-accept didn't exist in that old version of Jingle - it's a new addition in the different dialect used by libjingle4, and in the XEP-0166 standard.

If this error message is what was causing the call to fail, then either Asterisk should stop sending transport-accept in a Jingle dialect that didn't support it, or Asterisk should implement a newer dialect of Jingle (like the standard version, XEP-0166 version 0.32 or later), or Gabble should accept transport-accept in this older dialect like it does in newer dialects.

Comment 2 Simon McVittie 2012-03-01 07:45:53 UTC

(In reply to comment #1)
> So Gabble is basically saying "given that you're speaking the libjingle3
> dialect, I didn't expect you to send transport-accept".

This could be caused by Bug #25426, actually.

Comment 3 GitLab Migration User 2019-12-03 19:48:37 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/94.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.