Hello,
I am giving every open source voip sip client a shot.
jami seems interesting so I installed it.
Unfortunately, I entered my SIP login password and server and I did see the main screen, then it crashed to desktop.
Now when i start, it will also immediately crash to desktop.
I deleted
%USERPROFILE%\AppData\Local\Jami
Now I could start Jami again.
So starting it, it is like the first time setup again
I click advanced features
image of Advanced button
Then I click
And I enter my SIP information
Then I see the main page for a few seconds
And then it crashes to desktop when I try to restart, it crashes again. I can see the window rectangle appear, empty, and then it disappears.
Hello @shodanx Welcome to Jami community. Which version of Jami is affected by that challenge?
If you’re not familiar with finding the version. At the bottom centre of almost all pages, click on About Jami button. A window will open. The version number is under Euclid. On the right side of that Euclid, there is a useful copy button. For example:
Build ID:
Version: 0e6be21b.8b453e5
This message is a note to myself. This challenge might be related to this ticket https://git.jami.net/savoirfairelinux/jami-client-qt/-/work_items/2142#note_57641
@shodanx We were facing a similar challenge here. For you consideration, when configuring Jami SIP, I suggest double-checking that you use only valid characters. I mean valid from the point of view of Jami SIP. Any invalid character(s) risk to result in Jami crashing and exiting. This temporary resolution worked for us.
For example, but not limited to, if you use the SIP fields TURN address or STUN address or all other configuration text fields in all Jami configuration pages.
Below is an example for one SIP field titled TURN address.
VALID characters for TURN address field:
INVALID characters for TURN address field:
_ underscores?:/ Empty space
That above resolution is the same for all other Jami text fields. The type of characters accepted by Jami may vary per text field.
Same answer but with details if you are interested in those at https://git.jami.net/savoirfairelinux/jami-client-qt/-/work_items/2142#note_57641
Hello,
Here is my version information
Build ID: 202605251205
Version: 304f0d38.d0498a23c
So it seems the problem I have is that my SIP DID provider, which is voip.ms, only allows subaccounts that are the account number followed by underscore followed by a unique identifier.
I created a video from fresh setting wipe to crash
This forum does not accept .mp4 files, so I have posted it on youtube.
After that , launching Jami crashed immediately
youtube watch?v=nj9OcH7Sl2g
I’m having issues completing this message
If I enter a bad password but leave everything else as is, it also crashes.
If I enter a non-existing server, it does not crash
If I enter a non existing server where the username does contain an underscore, it does not crash.
Lastly, I try the “main account” which does not contain an underscore.
And that DOES still crash, so it appears the underscore isn’t the only problem here.
Note, the password does contain a hyphen (but no underscore) in the very last case, all other cases the password were only alphanumerical.
