| Summary: | ASTERISK-28092: res_pjsip. AMI event Registry. Field Cause is empty | ||
| Reporter: | Dmitriy Serov (Demon) | Labels: | patch pjsip |
| Date Opened: | 2018-10-04 18:07:52 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | In Progress/In Progress | Components: | Resources/res_pjsip_outbound_registration |
| Versions: | 15.5.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) res_pjsip_outbound_registration.c.diff | |
| Description: | I use pjsip. Often there are problems with outbound registration.
By tracking the AMI Registryevent, you want to know the textual cause of registration problems that the server often reports. Cause field of AMI event is the most appropriate way to get this information. https://wiki.asterisk.org/wiki/display/AST/Asterisk+15+ManagerEvent_Registry | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-10-04 18:07:53.868-0500 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: Dmitriy Serov (Demon) 2018-10-04 18:09:21.194-0500 Patch is attached By: Joshua C. Colp (jcolp) 2018-10-05 12:36:15.610-0500 Do you plan on putting this up for code review per the initial automatic comment? By: Dmitriy Serov (Demon) 2018-10-05 16:05:14.592-0500 Done | ||