Call sample app: vcall doesn't work to Xoom tablet

[GoogleCodeExporter]

What steps will reproduce the problem?
I built the 'call' sample app and am able to use vcall to place video calls to 
myself in Gmail.  I see the lava lamps when I send the sample video RTP data.

But when I call myself on my Xoom tablet, the vcall fails.  The incoming call 
does appear on the Xoom, but the 'call' app displays "call destroyed" before I 
even press Accept or Decline on the Xoom,

I see the following logs:

(call) Created channel
Created channel
Setting local voice description
Setting local video description

calling...
(mself.com@gmail.com/android587bb1992ab3) Channel enabled
Changing voice state, recv=1 send=0
Channel enabled
Changing video state, recv=1 send=0
Jingle:Net[en1:192.168.15.126]: Allocation Phase=Udp (Step=0)
Jingle:Port[:local:Net[en1:192.168.15.126]]: Port created
Jingle:Port[rtcp:local:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Port[:stun:Net[en1:192.168.15.126]]: Port created
Jingle:Port[rtcp:stun:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Net[en1:192.168.15.126]: Allocation Phase=Udp (Step=0)
Jingle:Port[:local:Net[en1:192.168.15.126]]: Port created
Jingle:Port[rtp:local:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Port[:stun:Net[en1:192.168.15.126]]: Port created
Jingle:Port[rtp:stun:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Net[en1:192.168.15.126]: Allocation Phase=Udp (Step=0)
Jingle:Port[:local:Net[en1:192.168.15.126]]: Port created
Jingle:Port[video_rtcp:local:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Port[:stun:Net[en1:192.168.15.126]]: Port created
Jingle:Port[video_rtcp:stun:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Net[en1:192.168.15.126]: Allocation Phase=Udp (Step=0)
Jingle:Port[:local:Net[en1:192.168.15.126]]: Port created
Jingle:Port[video_rtp:local:Net[en1:192.168.15.126]]: Added port to allocator
Jingle:Port[:stun:Net[en1:192.168.15.126]]: Port created
Jingle:Port[video_rtp:stun:Net[en1:192.168.15.126]]: Added port to allocator

call not answered
(mself.com@gmail.com/android587bb1992ab3) Error(session.cc:705): Session error:
<cli:error code="0" type="modify" xmlns:cli="jabber:client"/>
in response to:
<cli:iq to="mself.com@gmail.com/android587bb1992ab3" type="set" id="9" 
xmlns:cli="jabber:client"><jingle xmlns="urn:xmpp:jingle:1" 
action="transport-info" id="3855018740" 
initiator="2.mself.com@gmail.com/call23EEAAA5"><content name="audio" 
creator="initiator"><transport 
xmlns="http://www.google.com/transport/p2p"><candidate name="rtcp" 
address="192.168.15.126" port="59785" preference="1" 
username="XQp9UEFAEMrYiBfH" protocol="udp" generation="0" 
password="4XTEwiehmZprBbsS" type="local" network="en1"/><candidate name="rtp" 
address="192.168.15.126" port="51391" preference="1" 
username="uZpzVfd+8SS5CeQY" protocol="udp" generation="0" 
password="WMOJEDlPOOFs/fnF" type="local" 
network="en1"/></transport></content></jingle><session 
xmlns="http://www.google.com/session" type="candidates" id="3855018740" 
initiator="2.mself.com@gmail.com/call23EEAAA5"><candidate name="rtcp" 
address="192.168.15.126" port="59785" preference="1" 
username="XQp9UEFAEMrYiBfH" protocol="udp" generation="0" 
password="4XTEwiehmZprBbsS" type="local" network="en1"/><candidate name="rtp" 
address="192.168.15.126" port="51391" preference="1" 
username="uZpzVfd+8SS5CeQY" protocol="udp" generation="0" 
password="WMOJEDlPOOFs/fnF" type="local" network="en1"/></session></cli:iq>
Channel disabled
Changing video state, recv=0 send=0
Destroyed channel
Channel disabled
Changing voice state, recv=0 send=0
Destroyed channel

call destroyed

Original issue reported on code.google.com by mself....@gmail.com on 22 Apr 2011 at 2:25

[GoogleCodeExporter]

Could you please attach the full xmpp stanza (including the initiate message). 
It's hard to tell whether the "call not answered" was an user error or 
something wrong previously.

Original comment by jun...@google.com on 14 Jun 2011 at 8:33

• Changed state: Accepted

[GoogleCodeExporter]

No response. Set low priority.

Original comment by jun...@google.com on 17 Nov 2011 at 12:32

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by juberti@google.com on 31 May 2013 at 8:32

• Changed state: WontFix