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
  • #1259

Closed
Open
Created Apr 20, 2021 by Lukas Wallisch@LuWa

re-register to late

As the logs suggests the re-register timer is to long... as far as i know the reregister should come before the old register expires, not 10s after...

[1618330072.037|43625|sipaccount.cpp    :958  ] Start keep alive timer for account 7e9411aaf521bc4b
[1618330072.037|43625|sipaccount.cpp    :977  ] Registration Expire: 119
[1618330072.037|43625|sipvoiplink.cpp   :776  ] Register new keep alive timer 2099486383 with delay 129

OS : Ubuntu 20.04

Version: snap ( downloaded today)

jami -v gives:

Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...and using ALSA.
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]

i can only find the settings for the expire-timer, but the not the reregister-timer. am I missing something?

I'm using this client behind a Hardware-PBX, because of the late reregister my calls keep getting aborted

Assignee
Assign to
Time tracking