[asterisk-bugs] [JIRA] (ASTERISK-28092) res_pjsip. AMI event Registry. Field Cause is empty

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245074#comment-245074 ] 

Asterisk Team commented on ASTERISK-28092:
------------------------------------------

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].

> res_pjsip. AMI event Registry. Field Cause is empty
> ---------------------------------------------------
>
>                 Key: ASTERISK-28092
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28092
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_pjsip_outbound_registration
>    Affects Versions: 15.5.0
>            Reporter: Dmitriy Serov
>            Severity: Minor
>              Labels: pjsip
>
> I use pjsip. Often there are problems with outbound registration.
> By tracking the AMI Register event, 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



--
This message was sent by Atlassian JIRA
(v6.2#6252)