[asterisk-bugs] [Asterisk 0018932]: [patch] Wrong uri in the authentication header
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Mar 6 13:27:03 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18932
======================================================================
Reported By: viraptor
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18932
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.8.3
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-06 12:51 CST
Last Modified: 2011-03-06 13:27 CST
======================================================================
Summary: [patch] Wrong uri in the authentication header
Description:
I just tried to send a call via callcentric.com from asterisk 1.8.3 box.
During the password check is seems to send a wrong URI - skipping the user
part. For example, the packet sent out was:
-----
INVITE sip:17771234567 at callcentric.com SIP/2.0.
...
Proxy-Authorization: Digest username="17772777xxx",
realm="callcentric.com", algorithm=MD5, uri="sip:callcentric.com",
nonce="xxxxxxxxxxxxxxxxxxxxxxxxxx", response="xxxxxxxxxxxxxxxxxxxxxxxxxx".
-----
While according to the RFC3261 (22.4 step 3), it should be the request
uri, so "sip:17771234567 at callcentric.com".
======================================================================
----------------------------------------------------------------------
(0132670) viraptor (reporter) - 2011-03-06 13:27
https://issues.asterisk.org/view.php?id=18932#c132670
----------------------------------------------------------------------
Attached patch fixes the issue for invites... I'm not sure what else could
be affected here. I switched the cases around to prefer uri over domain,
but I'm not even sure why a situation without uri would ever occur.
If it does, this might cause some other issues.
Issue History
Date Modified Username Field Change
======================================================================
2011-03-06 13:27 viraptor Note Added: 0132670
======================================================================
More information about the asterisk-bugs
mailing list