Fails to register to more than one account from the same provider

Bug #313753 reported by Kjell Braden
4
Affects Status Importance Assigned to Milestone
Ekiga
Fix Released
Medium
ekiga (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: ekiga

I have multiple accounts at my SIP-provider freenet.de, and I can register only one of them at the same time. I fired up my network sniffer and watched the login-process, and noticed that ekiga seems to mix up with the "username" part of the digest authentication.

Say, I have account <email address hidden>, <email address hidden> and <email address hidden>, and I register a, it works. When I now register b and c they both still use "a" in the username field of their digest authentication.

I first noticed this with ekiga 3, and it worked without issues in ekiga 2.

Using 3.0.1-1ubuntu1.

Kjell Braden (afflux)
Changed in ekiga:
importance: Undecided → Low
Changed in ekiga:
status: New → Triaged
Changed in ekiga:
status: Unknown → New
Changed in ekiga:
status: New → Fix Released
Andreas Moog (ampelbein)
Changed in ekiga (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Dmitriy Geels (dmig) wrote :

The problem is in authorization info, ekiga uses. It takes auth info of first registered account (see Authorization header).

This short log of ekiga talking to asterisk shows what causes this problem:
<--- SIP read from 87.249.10.61:52335 --->
REGISTER sip:ssof01 SIP/2.0
Route: <sip:ssof01:5060;lr>
CSeq: 15 REGISTER
Via: SIP/2.0/UDP 10.1.1.168:5060;branch=z9hG4bK2663d012-8f6f-de11-8d5b-001bfcafddc3;rport
User-Agent: Ekiga/3.2.0
Authorization: Digest username="1x123", realm="asterisk", nonce="0e437ac4", uri="sip:ssof01", algorithm=MD5, response="6fbc872af5a973cb4bcee731f1a62804"
From: <sip:1x100@ssof01>;tag=aceecd12-8f6f-de11-8d5b-001bfcafddc3
Call-ID: 76d9cd12-8f6f-de11-8d5b-001bfcafddc3@dmig-desktop
To: <sip:1x100@ssof01>
Contact: <sip:1x100@10.1.1.168>;q=1
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
Expires: 3600
Content-Length: 0
Max-Forwards: 70

<------------->
--- (14 headers 0 lines) ---
Using latest REGISTER request as basis request
Sending to 87.249.10.61 : 52335 (NAT)
ssof01*CLI>
<--- Transmitting (NAT) to 87.249.10.61:52335 --->
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.1.1.168:5060;branch=z9hG4bK2663d012-8f6f-de11-8d5b-001bfcafddc3;received=87.249.10.61;rport=52335
From: <sip:1x100@ssof01>;tag=aceecd12-8f6f-de11-8d5b-001bfcafddc3
To: <sip:1x100@ssof01>
Call-ID: 76d9cd12-8f6f-de11-8d5b-001bfcafddc3@dmig-desktop
CSeq: 15 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: <sip:1x100@87.249.26.213>
Content-Length: 0

<------------>
ssof01*CLI>
<--- Transmitting (NAT) to 87.249.10.61:52335 --->
SIP/2.0 403 Authentication user name does not match account name
Via: SIP/2.0/UDP 10.1.1.168:5060;branch=z9hG4bK2663d012-8f6f-de11-8d5b-001bfcafddc3;received=87.249.10.61;rport=52335
From: <sip:1x100@ssof01>;tag=aceecd12-8f6f-de11-8d5b-001bfcafddc3
To: <sip:1x100@ssof01>;tag=as0afda709
Call-ID: 76d9cd12-8f6f-de11-8d5b-001bfcafddc3@dmig-desktop
CSeq: 15 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0

<------------>

Revision history for this message
gsdasdfgsf (ae21c01c0bdb8) wrote :

does anybody have a solution ?

Changed in ekiga:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.