-
Notifications
You must be signed in to change notification settings - Fork 372
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
Crash in 7.5.2.2 #903
Comments
Hm, failed assertion, but the line number doesn't seem to match the code... Anyway, can you open the dump in gdb, execute and post the output of:
|
Sure.
|
Another machine, same version, another crash:
And frame 4:
|
Can you tell if these are happening during a re-invite? |
The commit above (64e56d7) should fix this |
The only call-ID I could find was in frame number 7. And, oh wow, does this look weird. First, these are the logs for this Call-ID:
I looked into the call flow for this call. This was an incoming call, going to one of our customers. There were two devices online, so the call was forked inside Kamailio and sent out to both devices. Now the "fun" part begins. 14:44:39 - INVITE sent out to both devices. Device 1 starts ringing, Device 2 doesn't react. Mind. Blown. I can totally understand if this is something you never thought of. But can you still do something about the crash? |
Wow, that was quick. So yes, it was a codec change, because it was a "device change". Can you already tell, what package in your repository will contain that fix? We stopped building our own packages a while ago because our packages became unstable and the ones built by you didn't. Thanks a lot. |
This will be in the -daemon package. Do you want to test this patch separately first? |
Actually I don't really know how to test it separately, since we use your packages and the error occurs so sporadically. But maybe I can build a sipp scenario for that. My question actually should have been: What version of your packages will contain the fix? |
Ok I'll push the patch out then. For the 7.5.2 branch, it will be 7.5.2.3. |
A client can potentially change the codec used for a RTP payload type number, so we must confirm that an existing handler matches the codec from the SDP. fixes #903 Change-Id: Id9ae379425359f776883d6ace7fdb44ad651b37e
Hi,
we updated our rtpengines to 7.5.2.2 on Debian Buster last month, today one of the instances crashed.
Version:
Coredump Output:
Can you see a cause for this crash?
The text was updated successfully, but these errors were encountered: