Summary:	ASTERISK-20955: Create default endpoint identification services for the new SIP channel driver
Reporter:	Matt Jordan (mjordan)	Labels:	Asterisk12 NewSIP
Date Opened:	2013-01-18 09:44:15.000-0600	Date Closed:	2013-02-13 14:49:50.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_pjsip
Versions:		Frequency of Occurrence
Related Issues:	must be completed before resolving ASTERISK-20953 Create default authentication provider for chan_gulp
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 endpoint identification. There is a {{res_sip_endpoint_identifier_constant}}, but it does basically what the name implies - it returns the same endpoint for all requests. So, we need an endpoint identifier. This resource module should implement the function callbacks for endpoint identification 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 identifying! What does identification mean? # You must be able to query the data access layer for endpoints and return the correct endpoint. # The data access layer needs to be robust enough to provide endpoints from (at a minimum) a static configuration file. # The endpoint identification should have well defined business logic that determines how it identifies an endpoint from a SIP request. This MUST be documented on the wiki.
Comments: