Open zyddnys opened 1 year ago
Hi The reason should be more likely into the logs
linphone.log
here is the log file, I ran using ./OUTPUT/bin/linphone -V
I encountered a similar issue "Failed to register". In my case, a typo in a field.
I had to turn on logging under advanced, find the log, see the error, fix it, then go back to turn off logging and clear the logs.
That wasn't too bad for me (an engineer), but it isn't very user-friendly. Good error messages tell you what's wrong. (Excellent ones tell you how to fix it!)
It would be helpful if "Failed to register" included the error message, a window or easy way to see what would be logged. Saving the log messages for register in memory shouldn't be costly. Perhaps limit to something reasonable, like the last 25 or 50 lines...
Context
I use linphone compiled from source code downloaded from this repository, I want to connect a Ubuntu laptop to two Android phones. For SIP server I am using kamailio.
General information
Expected behaviour
I wanted to do a simple call with the Linux client calling the Android phone. However, after setting my account using account assistant I was unable to register to the SIP server. So I went to use the Android app from Google Play, it worked and I can make calls between two Android phones. So I captured packets from both registration procedure of both Android and Desktop version, I found that the Desktop version didn't send Authorization header in its second message to the SIP server. I have attached both pacp dumps.
To Reproduce
Use "ACCOUNT ASSISTANT" feature in the Desktop app. I followed its instructions, entered my username, password and SIP domain. I choose UDP for protocol. I didn't have DNS setup so all addresses are in plain IP.
Additional context
pcaps.zip
SDK logs URL
No response