Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • jami-project jami-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 156
    • Issues 156
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #170

Closed
Open
Created Aug 10, 2016 by RingBot@RingBotOwner

daemon: crash when receiving a call

Issue generated from Tuleap's migration script. Originally submitted by: Alexandre Lision (alision)

I got a crash du to this commit 1e249e4fe

Crash happends in setSecure method in sipcall.cpp:

void
SIPCall::setSecure(bool sec)
{
    if (srtpEnabled\_)
        return;
    if (sec && getConnectionState() != ConnectionState::DISCONNECTED) {
        throw std::runtime\_error("Can't enable security since call is already connected");
    }
    srtpEnabled\_ = sec;
}

The two conditions for the Runtime Exception are met every time:

- sec > 0

- state is CONNECTING, I can see the last state change event is:

libdring: call.cpp:163 | [call:6414282570080789912] emit client call state change CONNECTING, code 0

Assignee
Assign to
Time tracking