search

zhqiyi / webrtc4all

Automatically exported from code.google.com/p/webrtc4all
GNU General Public License v2.0
0 stars 0 forks source link

No sound in w4a when client is behind the NAT #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1.Connect with NAT'ed Boghe (RTCWeb profile) to SIP server and observe the 
clear sound in both ways

2.From the same box connect with w4a and browser - no sound in both ways

What is the expected output? What do you see instead?

Expected is the same behaviour of the Doubango engine (as in Boghe as in w4a), 
instead it differs.

What version of the product are you using? On what operating system?

The latest svn at the time of writing, os is win7 64-bit

Can provide any additional information including credentials to test server for 
reproducing the bug.

Original issue reported on code.google.com by sfinx.so...@gmail.com on 8 Nov 2012 at 10:33

Attachments:

GoogleCodeExporter commented 9 years ago 
Can provide the Boghe log too if somebody tell me how to get it

Original comment by sfinx.so...@gmail.com on 8 Nov 2012 at 10:33

GoogleCodeExporter commented 9 years ago 
Your logs shows that ICE is not enabled on Asterisk (SIP 200 OK)

Original comment by boss...@yahoo.fr on 12 Nov 2012 at 8:08

GoogleCodeExporter commented 9 years ago 
Enabling the ICE have no sound too, moreover in 376131 asterisk the ICE is 
enabled by default - so this is not the issue about.

But there is some good news: the 756 version with 376131 asterisk patch _and_ 
_enabled_ google STUN server in rtp.conf gives the sound ! So the issue still 
remains without using the STUN server. The logs are attached for the same call :

- bad.txt: is the w4all call without sound (STUN in rtp.conf disabled)
- good.txt: is the w4all call with sound (STUN in rtp.conf enabled)

The sound in good case is normal (two-way).

P.S. The simpl5 with latest stable (23.x) chrome gives no sound in any STUN 
case with the same server config. The log attached if interested, but this is 
not the w4a issue.

Original comment by sfinx.so...@gmail.com on 12 Nov 2012 at 9:57

Attachments: