Bug 37080 - Can't hear anything with voxalot account
Summary: Can't hear anything with voxalot account
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: rakia (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Mikhail Zabaluev
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-10 11:19 UTC by Xavier Claessens
Modified: 2019-12-03 19:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Empathy log (11.58 KB, text/plain)
2011-05-10 11:21 UTC, Xavier Claessens
Details
Sofiasip (9.26 KB, text/plain)
2011-05-10 11:21 UTC, Xavier Claessens
Details
more verbose sofiasip logs (48.22 KB, text/plain)
2011-05-10 11:49 UTC, Xavier Claessens
Details
more verbose sofiasip logs (48.22 KB, text/plain)
2011-05-10 11:53 UTC, Xavier Claessens
Details
Log with stun turned off (46.56 KB, text/plain)
2011-05-13 12:38 UTC, Xavier Claessens
Details
Logs for case 3 (25.66 KB, text/plain)
2011-05-13 14:43 UTC, Xavier Claessens
Details

Description Xavier Claessens 2011-05-10 11:19:29 UTC
I have 2 voxalot SIP accounts, one connected on my Siemens C470IP sipphone, and one connected in Empathy or N900. When I call from the sipphone to empathy, it rings, I can answer the call and the empathy's call window appear but it says "connecting" forever (on my sipphone it says the call is running). When calling to N900, I can also answer the call and N900 starts counting the call time, but no sound can be heard on any side.
Comment 1 Xavier Claessens 2011-05-10 11:21:04 UTC
Created attachment 46560 [details]
Empathy log
Comment 2 Xavier Claessens 2011-05-10 11:21:36 UTC
Created attachment 46561 [details]
Sofiasip
Comment 3 Xavier Claessens 2011-05-10 11:49:18 UTC
Created attachment 46562 [details]
more verbose sofiasip logs
Comment 4 Xavier Claessens 2011-05-10 11:53:27 UTC
Created attachment 46563 [details]
more verbose sofiasip logs
Comment 5 Mikhail Zabaluev 2011-05-11 05:48:13 UTC
telepathy-sofiasip resolves the STUN server from the SRV domain record, and this breaks media connectivity for your case, where apparently both endpoints are on the same private network. Try setting the parameter 'discover-stun' to false.

Usage of ICE could resolve this problem automagically, if the other endpoint supports ICE as well.
Comment 6 Xavier Claessens 2011-05-13 12:38:53 UTC
Created attachment 46690 [details]
Log with stun turned off

Still same issue. I also had that issue when the call comes from outside my network, I don't have logs for that though, would that help you providing them?
Comment 7 Xavier Claessens 2011-05-13 12:39:16 UTC
Reopening
Comment 8 Xavier Claessens 2011-05-13 14:42:01 UTC
Some more observations:

1) TURN was disabled on sipphone side, if I enable it both in empathy and sipphone then it works fine.

2) If TURN is disabled both sides it didn't work because I have a VM configured and it used that interface... if I do "ifconfig virbr0 down" then it works.

3) If a friend call from outside to empathy, it doesn't work (see next log attached).

4) If a friend call from outside to sipphone, it works.


I've talked with Youness and Olivier, it seems 2 is not fixable. What about 3?
Comment 9 Xavier Claessens 2011-05-13 14:43:04 UTC
Created attachment 46694 [details]
Logs for case 3
Comment 10 Xavier Claessens 2011-05-13 14:46:51 UTC
Actually in case 3, my friend did hear me but no the other way. I've checked with wireshark and indeed I'm sending PCMA packets to voxalot's IP but I get nothing back.
Comment 11 GitLab Migration User 2019-12-03 19:37:34 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-rakia/issues/20.


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.