Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • 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-client-gnome
  • Issues
  • #516
Closed
Open
Created Oct 11, 2016 by RingBot@RingBotOwner

GNOME: calls which fail immediately are not shown

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

When making a call, if it fails immediately (eg: no compatible account available), then in the conversations list view it is marked as "failed"; however the current call view is not shown so that the user can easily see that it failed and aknowledge this by hanging up the failed call. Instead, the user has to first select another item and then again select the Person/CM which has the failed call.

This is because the CallModel emmits callAdded for these calls, however, the addCall() method is never called on the CM for calls which fail immediately.

Assignee
Assign to
Time tracking