Summary:	ASTERISK-20953: Create default authentication provider for chan_gulp
Reporter:	Matt Jordan (mjordan)	Labels:	Asterisk12 NewSIP
Date Opened:	2013-01-18 09:41:35.000-0600	Date Closed:	2013-02-14 19:00:58.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_pjsip
Versions:		Frequency of Occurrence
Related Issues:	cannot be resolved before completion of ASTERISK-20955 Create default endpoint identification services for the new SIP channel driver
Environment:		Attachments:
Description:	For reference, please see the following wiki pages: * [New SIP Channel Driver Architecture|https://wiki.asterisk.org/wiki/display/AST/New+SIP+Channel+Driver+Architecture] * [res_sip Design|https://wiki.asterisk.org/wiki/display/AST/res_sip+design] In the current incarnation of  {{res_sip}} and {{chan_gulp}}, there is no authentication. (Heck, there isn't even configuration yet!) There are, however, the beginnings of hooks for authentication. Authentication is not provided by these modules - by default, there is no authentication! Instead, {{res_sip}} looks for an authentication provider, and, if it finds one, asks the provider to authenticate the request. So, we need a default authentication provider (say, {{res_sip_authentication}}?). Said authentication provider should implement the function callbacks as documented on the [res_sip Design|https://wiki.asterisk.org/wiki/display/AST/res_sip+design] page, register itself with {{res_sip}} (making sure, of course, that it's loaded after res_sip), and start authenticating! What does authentication mean? # Use the resource module that provides endpoint identity - see []. # We need a resource module that provides the meat of the authentication. This means returning ast_sip_digest_challenge_data when something needs a challenge, but could also mean 'accept all endpoints' if configured to do so (scary!), as well as ACL support, etc.
Comments: