Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-lrc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-lrc
  • Issues
  • #427

Closed
Open
Opened Apr 03, 2020 by Sébastien Blin@sblinOwner

Wrong call status (hold/setCurrentCall)

There is two issues:

Incorrect hold for incoming calls (libwrap)

  • When in call with someone, receive some incoming call
  • Do not answer to that incoming call
  • The first call is in hold even if not answered. This should not be the case.

Incorrect hold for outgoing calls

  • If SIP is cached, when in call with someone else, try another outgoing call.
  • When the peer will ring (calling status), the first call will be "In hold". It should be the case only if the other answers.
Edited Apr 06, 2020 by Ming Rui Zhang
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-lrc#427