[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Linphone Android issue - Far too many SIP regi

From: Sylvain Berfini
Subject: Re: [Linphone-developers] Linphone Android issue - Far too many SIP register attempts
Date: Fri, 23 Oct 2020 15:35:14 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0


If it is getting worse after each restart, it means you are probably creating new proxy config objects in addition to existing ones.

Check your config file on your device using 'adb shell run-as <package name> cat files/.linphonerc'. You can also use mCore.getProxyConfigList() and check it's size.

Once created, a proxy config is stored, so you don't have to create it again at the next start.


Sylvain Berfini Software Engineer @ Belledonne Communications
Le 23/10/2020 à 15:12, Janek Haus a écrit :

we are using the Open Source Library on Android and are experiencing problems caused by SIP-Register calls.
As far as I can tell the normal rate for SIP-Register attempts is 4 seconds, however over time, presumably caused by application restarts, it increases extraordinarily up to several tenthousand attempts per minute.
This leads to crashes of the Server and other involved parties. The registers seem to increase linearily with application restarts.
We are using Linphone 4.4+ and follow the example from, which does not show this behaviour.
Obviously we adjusted the LinphoneService to our needs by removing the call handling logic from the service.
We made sure that only one instance of the Service holding the LinphoneCore is active at a time and that both service and core are terminated properly (following the sample app),
double checking by using ADB:

Here is the LinphonService onDestroy() call:
override fun onDestroy() {
  mCore = null
  instance = null
We also remove all other listeners and the Service is terminated correctly.
Also the registers stop once the application is terminated (but further increase on the next start).

If someone has experienced something similar or can help solving this issue we would be very thankful.
Of course we will provide further information needed to solve this problem.

Kind regards

Janek Haus
casenio AG

Linphone-developers mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]