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 89
    • Issues 89
    • 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
  • #411

Closed
Open
Created Feb 07, 2016 by RingBot@RingBotOwner

Unable to setup call

Issue generated from Tuleap's migration script. Originally submitted by: JB (bluetac)

I have the ring client installed on Xubuntu 14.04 and on my Nexus phone (Android 6.0 "Marshmallow") with the ring beta client installed and I'm unable to get a call setup between the two.

Messaging seems to be okay, so I assume there is no problem with the RingID's.

When calling from PC to Mobile - The call sometimes doesn't make it to the mobile, but when it does it takes a long time to initiate ringing (however the messages appear almost instantly). Once ringing you can answer the call but you get no audio and the PC continues to think the call is still setting up. The mobile client eventually gives up and closes the call, then after a few more seconds the PC recieves the OK and thinks the call has begun. The PC then shortly gets the disconnect or the BYE and then hangs up.

I have a network capture of the issue described, please let me know if you would like a copy. I am unaware of how to decrypt TLS messages so I can view to original SIP but I assume this is being caused by a timeout period being reached on either of the clients.

Assignee
Assign to
Time tracking