Poniżej podsumowująca odpowiedź Acrobits:
First, I understand this can be a frustrating process sometimes.
But our apps are used with hundreds if not thousands of different SIP servers/providers. For most of them, just username, password and domain are enough. But if they aren't and we aren't getting feedback from the provider, just the user (you in this case), it can be time consuming to troubleshoot the exact problem. Here, I understand the change didn't help, but the new logs are as much about confirming the setting is working as expected and if the exact problem has changed or now.
That said, I can now see more than before. It looks like the SIP provider is actually returning an error.
SIP/2.0 403 Forbidden - 6034
I think what is happening is they return the error at first, but after a few failed attempts they block you temporarily, which explains what I saw in previous logs (no response at all). Making the change I suggested would make no difference if they are actually blocking you.
For now, I think the best thing is to just delete the account completely, then exit the app for a while (maybe an hour or so to be sure they stop blocking you), then open the app and try to add the account again, being as careful as possible entering the password (We don't put password in logs for obvious reasons, but I can see username and domain appear to be correct).
If it still doesn't work, you can send the log again right after (before they start actively blocking you again) and we can take a look.
But if it's still the same, we may need feedback on why they are returning this error to know if it can be resolved from our side.
Again, I understand this can be frustrating, tedious process. Unfortunately, not every issue has an obvious fix in SIP.
Logi po ostatniej, również nieskutecznej próbie wysłałem i póki co to tyle.
