| Summary: | ASTERISK-25670: Add regcontext to PJSIP | ||
| Reporter: | Daniel Journo (journo) | Labels: | |
| Date Opened: | 2016-01-08 03:49:22.000-0600 | Date Closed: | 2016-01-14 06:49:42.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_pjsip |
| Versions: | 13.6.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | chan_sip has an option called regcontext which functions like this:
If regcontext is specified, Asterisk will dynamically create and destroy a NoOp priority 1 extension for a given peer who registers or unregisters with us. The actual extension is the 'regexten' parameter of the registering peer or its name if 'regexten' is not provided. More than one regexten may be supplied if they are separated by '&'. Patterns may be used in regexten. In order for me to switch to PJSIP, I need to have regcontext added to chan_pjsip in order to use DUNDI. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-01-08 03:49:23.928-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2016-01-08 08:07:16.539-0600 [~journo] You are working on implementing this, correct? If so I shall leave it open for your submission. | ||