[Top][All Lists]

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

[Linphone-developers] STUN per-setting on Android is buggy

From: German Cancio
Subject: [Linphone-developers] STUN per-setting on Android is buggy
Date: Tue, 21 Jan 2020 14:25:45 +0100

Dear Developers,

On Android, some parameters, including STUN/TURN and ICE, can be set in two places - in the general network configuration but also for each SIP account. Setting STUN at the account level does NOT work, even if I put it afterwards in the general network setting. What works well is setting these in the general network config and leaving the per-account settings untouched. (I had to delete my account on the phone and recreate it.) 

When setting a (correct) STUN value in the account settings, I see the following in the Android logs:

2020-01-21 14:19:45:474 [liblinphone] MESSAGE Created new ICE check list for stream [0]
2020-01-21 14:19:45:474 [mediastreamer] MESSAGE ms_filter_link: MSRtpRecv:0x6f2cbcf180,0-->MSVoidSink:0x6f2bf8cb00,0
2020-01-21 14:19:45:474 [liblinphone] WARNING ICE is used without STUN server
2020-01-21 14:19:45:475 [liblinphone] MESSAGE ICE: bypass candidates gathering
2020-01-21 14:19:45:475 [mediastreamer] MESSAGE ms_filter_unlink: MSRtpRecv:0x6f2cbcf180,0-->MSVoidSink:0x6f2bf8cb00,0

Which of course, is incorrect as I have configured a (correct) STUN server.

I can confirm this problem is still present in the current Google Play beta version. 

Any hints? Should I report this as a bug to gitlab?

Many thanks and best regards,


reply via email to

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