Patches item #1669448, was opened at 2007-02-26 20:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=637566&aid=1669448&group_id=104305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: sipp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: monica (monica_sarbu)
Assigned to: Nobody/Anonymous (nobody)
Summary: uri parameter in [authentication]

Initial Comment:
Hi,

I would like to propose this small patch that allows defining custom 
authentication URI as a parameter per message. Something like:

[authentication [EMAIL PROTECTED] password=pass uri=sip:[EMAIL PROTECTED]

This is useful when there are both REGISTER and INVITE in the same scenario and 
both must be authenticated. -auth_uri command line option is not enough in this 
case. In my patch, the -auth_uri has higher priority than the uri defined in 
the [authentication]. That's only for keeping the changes to minimum.

I've noticed that this was requested before on the emailing list.

Also, the 'sip:' scheme should not be hardcoded if the authentication URI is 
provided by user.

Monica Sarbu


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=637566&aid=1669448&group_id=104305

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to