[asterisk-bugs] [JIRA] (ASTERISK-28092) res_pjsip. AMI event Registry. Field Cause is empty
Dmitriy Serov (JIRA)
noreply at issues.asterisk.org
Fri Oct 5 15:44:54 CDT 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-28092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Serov updated ASTERISK-28092:
-------------------------------------
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
was:
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
> 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
> Assignee: Dmitriy Serov
> Severity: Minor
> Labels: patch, pjsip
> Attachments: res_pjsip_outbound_registration.c.diff
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list