"Failed to create looper" during call

[GoogleCodeExporter]

"Failed to create looper" during call

[GoogleCodeExporter]

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 [email protected] on 4 Nov 2012 at 7:56

[GoogleCodeExporter]

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 [email protected] on 7 Nov 2012 at 11:28

[GoogleCodeExporter]

You should attach full js log

Original comment by [email protected] on 7 Nov 2012 at 7:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Please see attached

Original comment by [email protected] on 7 Nov 2012 at 9:17

Attachments:

• log.txt

[GoogleCodeExporter]

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 [email protected] on 7 Nov 2012 at 9:19

[GoogleCodeExporter]

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 [email protected] on 7 Nov 2012 at 9:25

• Changed state: Accepted

[GoogleCodeExporter]

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

Original comment by [email protected] on 7 Nov 2012 at 9:40

[GoogleCodeExporter]

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 [email protected] on 7 Nov 2012 at 9:42

[GoogleCodeExporter]

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 [email protected] on 8 Nov 2012 at 8:55

[GoogleCodeExporter]

Fixed by Doubango SVN 755 and will be part of the next release (installer).

Original comment by [email protected] on 12 Nov 2012 at 8:15

[GoogleCodeExporter]

Closed by "webrtc4all_windows_1_12_756"

Original comment by [email protected] on 12 Nov 2012 at 12:04

• Changed state: Fixed