search

madboy06 / webrtc4all

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

"Failed to create looper" during call #1

Closed GoogleCodeExporter closed 8 years ago

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

1. Install latest stable Firefox (16.x)
2. Install latest webrtc4all (1.11.745)
3. Checkout latest sipml5 (r121)
3. Start browser, configure credentials
4. Register
5. Try call some number

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

Expected successful call. Instead the sipml5 hangs in "Call in progress" state 
with error message "Failed to create looper" in JS console

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

Firefox 16.0.1
webrtc4all 1.11.745
sipml5 r121
Windows 7 (64-bit)

Can provide any additional information upon request.

Original issue reported on code.google.com by sfinx.so...@gmail.com on 4 Nov 2012 at 6:58

GoogleCodeExporter commented 8 years ago 
Add:

Latest stable (22.x) Chrome, Safari and IE9 hangs in call in the same way, 
though IE do not shows error message in JS console. Opera do not work at all 
with w4a as seems like w4a mode is not detected by sipml5 code, so it shows 
alert asking for download w4a again.

Original comment by sfinx.so...@gmail.com on 4 Nov 2012 at 7:56

GoogleCodeExporter commented 8 years ago 
Update: the "failed to create looper" message is not related to hang in call. 
Enabling debug show errors in w4a :

......
WARNING: no real random source present!
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: bind have failed.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: (SYSTEM)NETWORK ERROR ==>The requested address is not valid in its context.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: Invalid socket.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: (SYSTEM)NETWORK ERROR ==>The operation completed successfully.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: bind have failed.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: (SYSTEM)NETWORK ERROR ==>The requested address is not valid in its context.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: Invalid socket.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: (SYSTEM)NETWORK ERROR ==>The operation completed successfully.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: bind have failed.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: (SYSTEM)NETWORK ERROR ==>The requested address is not valid in its context.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: Invalid socket.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: (SYSTEM)NETWORK ERROR ==>The operation completed successfully.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: bind have failed.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "227"
MSG: (SYSTEM)NETWORK ERROR ==>The requested address is not valid in its context.

***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: Invalid socket.
***ERROR: function: "tnet_socket_ctor()"
file: ".\src\tnet_socket.c"
line: "262"
MSG: (SYSTEM)NETWORK ERROR ==>The operation completed successfully.

***ERROR: function: "tnet_ice_utils_create_sockets()"
file: ".\src\ice\tnet_ice_utils.c"
line: "109"
MSG: Failed to bind sockets
......

Original comment by sfinx.so...@gmail.com on 7 Nov 2012 at 11:28

GoogleCodeExporter commented 8 years ago 
You should attach full js log

Original comment by boss...@yahoo.fr on 7 Nov 2012 at 7:55

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Please see attached

Original comment by sfinx.so...@gmail.com on 7 Nov 2012 at 9:17

Attachments:

GoogleCodeExporter commented 8 years ago 
I've managed to compile w4a with visual studio 10 (spent an hour porting the 
project though), so can try some debug patches for tinyNET.dll. By the way: 
does some trace flag for function calls exists in w4a ?

Original comment by sfinx.so...@gmail.com on 7 Nov 2012 at 9:19

GoogleCodeExporter commented 8 years ago 
Why are you setting ws server (ws://10.1.1.100:6060)? -> not needed as you 
already have an udp outbound proxy
debug: 
http://code.google.com/p/sipml5/source/browse/trunk/src/tinySIP/src/transports/t
sip_transport.js#474

Original comment by boss...@yahoo.fr on 7 Nov 2012 at 9:25

GoogleCodeExporter commented 8 years ago 
ws setting remained from previous native WebRTC test - as it is unused in w4a 
mode anyway so you can ignore it.

Original comment by sfinx.so...@gmail.com on 7 Nov 2012 at 9:40

GoogleCodeExporter commented 8 years ago 
debug != trace. Exact the first log in this issue is recorded by debug, but 
with trace it will be possible to know from what places the tnet_socket_ctor() 
have been called and in what order.

Original comment by sfinx.so...@gmail.com on 7 Nov 2012 at 9:42

GoogleCodeExporter commented 8 years ago 
Seems I've found the way to reproduce the problem. The w4a stops working when 
laptop is configured over wifi. If the laptop is configured over LAN (or 
desktop is used) no problem is observed in sending call INVITE from w4a. There 
are exists other problems with w4a (extra UDP traffic and no sound), but this 
will be another issues

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

GoogleCodeExporter commented 8 years ago 
Fixed by Doubango SVN 755 and will be part of the next release (installer).

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

GoogleCodeExporter commented 8 years ago 
Closed by "webrtc4all_windows_1_12_756"

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