Bugfix - SIP authentication username option missing in desktop clients

assigned to @mzhang

@mzhang is on it, but currently in holiday.

If you want, you can modify ~/.config/jami/dring.yml you have your SIP account infos under credentials. so you can enter the auth username.

However, I don't think it's a common used feature (I don't think we have a SIP account with this kind of config to test), so if you can share details about the provider or test it.

Also, it's already available on the Android client in the account's settings

added SIP label

@sblin @mzhang I want to use Jami with my work SIP account (Cisco Unified Callmanager).

I've tried to modify the file, but it got overwritten with the previous data from the client UI at startup...

If you could provide a version with the option available, I can test it.

Hi Robin,

Just let me make sure something first,

You were having this problem on the creation of SIP account right?

Can you put authentication username in the username option? (igonre username)

Try to see if it can connect to the server.

Hi Ming,

unfortunately no, this doesn't work. Also with other SIP clients like Jitsi, it is necessary to provide both - a valid username and the matching authentication username.

Hi @robimac04 ,

If possible, could you use your account to provide an example SIP package grabbed by wireshark or something else.

I think there is a mismatch of information between what we write to the SIP header than yours.

In the meantime, I will take a look at Jitsi.

Because the sip service provider that we use does not really differentiate authentication username and username, so it is better for us to see the difference.

Best, Ming

@mzhang is on it, but still in holiday. We will ping you as soon as the option is available

@mzhang we agree that this option is available nnow?

not really, but it should,

added it to the list

I have problems with jami too because of that missing option. My sip provider uses authentication username and username, and both are differents, without that there is no registration...

see that application @robimac04 https://github.com/LubosD/twinkle/ It's what Im using right now and have this option. The bad side is that is much older and without pulseaudio and G722 between others. @mzhang Is it known something about the fix to that problem?

@sblin is it known something about this? I am well with twinkle option but I think that this bug should be fixed for someone other. And I think that this issue is being not noticed by anybody !

Hi @userofryzen,

Sorry, this issue was forgotten as there are other priorities,

but it will be fixed soon, possibly next release.

Additionally, can you provide us SIP package grabbed by Wireshark when you register?

You send it by text and hide the sensitive info, we just need to see the header.

But it is optional

Thanks, Ming

I can't right now sorry. Do you need it yet?. I ll try to do this the next time Im in the pc. But I don't promise anything since I have not used never wireshark. If you provide some guide it would be useful.

Not need to be sorry man. I am not paying for anything. Thanks to all of you for all.

I think it is better to have it.

Cause, currently, we do not know any sip provider that requires an authentication username.

Although I have the patch implemented, I cannot be sure about whether it will work or not.

So, we are currently trying to find some sip providers that do require it and a sip package set would be good to analyze as well.

For Wireshark on Linux, you can just install it and on the main page, there will be Capture option and you can just select any.

In Apply a display filter section, just type sip for the filter is enough.

You can make some calls or just do registrations. And there should be packages shown on Wireshark.

@mzhang REGISTER sip:ims.xxx.com SIP/2.0 Via: SIP/2.0/TCP 192.168.1.6;rport;branch=XXXXXXXXXXXXXXXXXXXXX Max-Forwards: 70 To: "Alberto" sip:*USERNAME*@ims.xxx.com From: "Alberto" sip:*USERNAME*@ims.xxx.com;tag=lykjy Call-ID: XXXXXXXXXXXXXXXXXXXXX@albertosobremesa CSeq: 76 REGISTER Contact: sip:*USERNAME*@192.168.1.6;transport=tcp;expires=600 Authorization: Digest username="AUTHENTICATE USERNAME@ims.xxx.com",realm="ims.xxxx.yyy.3gppnetwork.org",nonce="XXXXXXXXXXXXXXXXXXXXX",uri="sip:ims.xxx.com",response="XXXXXXXXXXXXXXXXXXXXX",algorithm=MD5,cnonce="XXXXXXXXXXXXXXXXXXXXX",qop=auth,nc=XXXXXXXXXXXXXXXXXXXXX Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE User-Agent: Twinkle/1.10.2 Content-Length: 0

I hope it is the correct header you are looking for.

Thank you, I will take a look at it

if you need something, be fast to ask because I'm pending now but after I have to do things and I 'm not sure if I will be able to.

It serves to you? how is going the patches?

https://review.jami.net/q/topic:%22sip+authentication+username%22+(status:open%20OR%20status:merged)

Is it a patch that make the user authentication usable on Jami? Or am I wrong.

What a fast patch ._. not?

By the way. If I use the https://aur.archlinux.org/packages/jami-client-qt-git/ package can I use your patch or have I got to do something more?

I am not sure about this https://aur.archlinux.org/packages/jami-client-qt-git/

But you can build Jami yourself by using this https://git.jami.net/savoirfairelinux/ring-project/-/wikis/technical/Build-instructions.

For the patches, currently, they are not ready yet, but you can try it out if you want.

Any news?

@mzhang @sblin news?:(

Hi @userofryzen

Sorry for the late reply,

Other changes were prioritized, and this one was left out.

But I will rebase and test the patches that I did and I will generate a test installer for you.

It should not take too long,

Thank you for reminding us!

okey @mzhang I use manjaro, you can if you want make an aur package if you know how to do it or maybe I can use the aur jami-git package or something. To be hones I only know the 1,2,3 of compilation and patch and let's say with error and retry jajaj.

Thanks for your work and your welcome -

Oh, sorry, I thought you were using Windows.

Then I have to contact my colleague who does the Linux package to see what we can do.

Thanks for letting me know.

we don't provide support for Manjaro nor build aur packages. So once the patch is done, and realeased via dl.jami.net, for the .aur it will need to wait for someone to package it.

okey sebastien, advise me so I can " ask" in aur website

any new? @sblin @mzhang

Not really, the team is really reduced and Ming was on another project and will leave the team for new adventures.

The patches are there, so in fact anybody can test it. I don't have any account with this needs so I can't test the patches.

I can test if you make me some aur package for me. Do you know how to do It? or may be i can ask the aur mantainer to do a package separated for me and i can test it,

https://aur.archlinux.org/packages/jami-client-qt-git/ @sblin may be i can request the mantainer of this package to make another one equal to the other but with the paths here: https://review.jami.net/q/topic:%22sip+authentication+username%22+(status:open%20OR%20status:merged)

all the patchs or it has to be done from part to part? explain all and Ill contact with the mantainer!

For arch the easiest is to build from sources, I do it only on my pinephone

@sblin how can I test one time compilled? putting some string into a config file or I have only to guide me by GUI tool?

if you have the qt client and the 3 patches, Just fill "Authentication Username (Optional)"

if you only have the daemon, in the dring.yml, there should be "Account.authenticationUsername"

@sblin I have a friend that took a luck into this and I received this responded from him. Take a look to see if you can say something and thanks in advance

Alberto,

The patches described in https://review.jami.net/c/jami-daemon/+/17660 dont match any files I can find in their git.

If you would ask me personally, their git is nothing short of a "clusterfcuk". It doesn't seem to me they had linux in mind for this project. I think i'm always navigating through their windows projects but I am not sure.

After some digging, I am guessing the linux source is located at https://git.jami.net/savoirfairelinux/jami-client-qt, but those don't contain the files the patches specified.

Can you give me the true linux source that is compatible with said patches? Personally I am lost in their git and explanations and cannot continue :(

If I had to guess, they just referred you to the windows patches. But I can't be sure at all. I am just so confused.

jami-daemon matches on jami-daemon (https://review.jami.net/admin/repos/jami-daemon or mirrored in https://git.jami.net/savoirfairelinux/jami-daemon/), jami-libclient on jami-libclient (https://review.jami.net/admin/repos/jami-daemon or mirrored https://git.jami.net/savoirfairelinux/jami-libclient), jami-client-qt on jami-client-qt (https://review.jami.net/admin/repos/jami-client-qt or mirrored https://git.jami.net/savoirfairelinux/jami-client-qt).

On the page you linked: https://review.jami.net/c/jami-daemon/+/17660 applies to jami-daemon and in download there is the command to apply by cherrypick, checkout, do a branch or pull or even download the diff.

Every projects got a README with instructions of how to build (in daemon "How to compile on Linux" https://git.jami.net/savoirfairelinux/jami-daemon/-/blob/master/README), or there is a "build.py" script used to build all the project at once:

https://git.jami.net/savoirfairelinux/jami-project/ and following the README

./build.py --init

./build.py --dependecies

./build.py --install --qt

@sblin I'll try to make someone do it because I have not sufficient time to check how to do it but I can test it so I'll try. I'll let you know what happens! Let's see if there is username in jami to make it works with yoigo ISP SIP

Bugfix - SIP authentication username option missing in desktop clients

Designs

Child items ...

Activity