History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCF-2671
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Scott Lawrence
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
sipXconfig

Click to dial should use the identity of the caller when authenticating REFER

Created: 2008-06-30 09:34   Updated: 2008-08-21 06:51
Component/s: sip stack
Affects Version/s: 3.11.4
Fix Version/s: 3.11.5

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File 0001-XCF-2671-pass-user-credentials-to-send-refer-method.patch (12 kb)
2. Text File 0003-XCF-2671.patch (9 kb)
3. XML File merged.xml (101 kb)
4. XML File merged.xml (79 kb)

Environment:
sipxconfig version 3.11.4-012989
Issue Links:
Duplicate
 
This issue also reported as:
XCF-2696 Caller without international dialing ... Major Closed
Related
This issue related to:
XCF-2670 call set up by sipXconfig does not ge... Critical Closed
 


 Description  « Hide
As shown in the attached merged.xml:

The click-to-dial function sets up a call to the calling phone successfully, and then sends a REFER to that phone to blind-transfer the call to the intended destination of the call.
This REFER is challenged by the sipXproxy for authentication.

In the current implementation, the click-to-dial function is authenticating as '~~id~config'; it should instead authenticate as the user actually executing the call, so that the resulting transfer leg will be authenticated as the real caller.


 All   Comments   Work Log   Change History      Sort Order:
M. Ranganathan - 2008-07-01 20:27
How do I access the credentials of the caller from sipxconfig? How will that result in the transfer leg being authenticated as the caller ( perhaps Scott can elaborate on this ).

Damian Krzeminski - 2008-07-03 10:40
We need to authenticate the REFER as user who initiated the call.
SipService.sendRefer now takes User parameter.
    
This patch does not actually use the credential informaton yet, it's just passing it to the SipService.

M. Ranganathan - 2008-07-03 20:58
Damian, please review attached patch and apply. You should apply patches for both 2670 AND 2671 and test both together. Thanks!

M. Ranganathan - 2008-07-03 20:59
Please review merged.xml for correct operation.

Damian Krzeminski - 2008-07-25 12:17
I have everything ready to be checked in but need to wait till new version of jain-sip (1.2.74) is ready to be installed on all build machines.

Damian Krzeminski - 2008-08-05 12:27
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=13216

XCF-2671 pass user credentials to send refer method

We need to authenticate the REFER as user who initiated the call.
SipService.sendRefer now takes User parameter.

This patch does not actually use the credential informaton yet, it's just passing it to the SipService.

------------------------------------------------------------------------
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=13217

XCF-2671 pass correct user credentials when authentication is required

New version of jain-sip (1.2.74) library has an updated AccountManager interface that passes
clientTransaction to AccountManager.getCredentials method. sipXconfig now stores credentials data
in TransactionApplicationData, which allows it to provide authentication info associated with the
user that initiated the transaction.

Chaitra Sharma - 2008-08-21 06:51
This issue is resolved. Verified using the following build :

sipxproxy 3.11.5-013228 2008-08-07T14:21:08 oem-centos5
sipxconfig 3.11.5-013228 2008-08-07T14:43:41 oem-centos5

In the current implementation, the click-to-dial function is authenticating as the user actually executing the call as seen below:
Proxy-Authorization: Digest response=\"5df015d790f815b514a225ab5bd8e0b6\",username=\"300\",nonce=\"11be5bef34ca6728da286fbd85
d05ae148ad4159\",realm=\"qantom.int\",uri=\"sip:300@xxx.xxx.x.xxx\"

Where username=300 instead of "~~id~config" which was used before.

Hence closing this issue.

Thanks,
Chaitra