Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webrtc2sip crashing randomly in SIPML5 scenario #185

Open
GoogleCodeExporter opened this issue Aug 20, 2015 · 1 comment
Open

Webrtc2sip crashing randomly in SIPML5 scenario #185

GoogleCodeExporter opened this issue Aug 20, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

Hi Masters,

We are having random crashes of webrtc2sip on CentOS6.
I cannot reproduce since it is generated randomly when we are in concurent 
calls.

Scenario: call(sip) with softphones -> Asterisk -> webrtc2sip -> sipML5

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

VERSION: 2.7.0
CentOS 6.6
Linux localhost.localdomain 2.6.32-504.30.3.el6.i686 #1 SMP Wed Jul 15 10:55:56 
UTC 2015 i686 i686 i386 GNU/Linux

I attach the bt full logs, sorry if I missed somehting.
In the coredump directory I can find this relevant output:

Process /usr/local/sbin/webrtc2sip was killed by signal 6 (SIGABRT)

Aug 11 09:13:07 localhost abrt[2942]: Saved core dump of pid 1944 
(/usr/local/sbin/webrtc2sip) to /var/spool/abrt/ccpp-2015-08-11-09:13:06-1944 
(566190080 bytes)

Others:

I could see in the bt full log the mention of libtinySACK and libtinyNET 
objects, and found this issue already fixed: 
https://code.google.com/p/webrtc2sip/issues/detail?id=122

The thing is that under my doubango/tinySACK/src/ I was not able to find the 
fixed lines suggested per patch (issue122) in tsk_object.c. Same in 
tinyNET/src/tnet_transport.c. 

Can this be the problem? Or maybe Im missing information.

Thanks for your great work!

Original issue reported on code.google.com by rodmont...@gmail.com on 11 Aug 2015 at 9:03

Attachments:

@vinodpandey23
Copy link

I am also having same problem when using webrtc2sip with more than 8-10 calls simultaneously. Behavior is not always reproducible but it occurs abruptly.

Have you made changes and tried. Please confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants