| Summary: | ASTERISK-21081: New SIP Channel Driver - Registrar - Part One | ||||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 | ||
| Date Opened: | 2013-02-13 16:40:33.000-0600 | Date Closed: | 2013-03-04 11:18:35.000-0600 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Channels/chan_pjsip | ||
| Versions: | Frequency of Occurrence | ||||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | Now that we have endpoint identification and authentication, we can get down with Registration.
This task is to scope out and implement the data objects and basic services for a registrar. We should go ahead and - if it's feasible - separate endpoint and location correctly (which Joshua is probably already working out) such that multiple User Agents can register to a location, as well as having multiple locations be assigned to a single endpoint. This may also mean tweaking our domain support. This task should also entail persisting the registrations in sorcery, such that they survive reload operations, shutdowns, etc. The actual act of handling REGISTER requests/responses and registering ourselves can be done in Part 2, although basic handling of REGISTER requests/responses would be needed to test out the data access layer work. | ||||
| Comments: | |||||