[asterisk-bugs] [JIRA] (ASTERISK-29271) How to fetch existing peers/extensions from Asterisk DB by enabling Asterisk Manager Interface ?

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29271:
------------------------------------------

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> How to fetch existing peers/extensions from Asterisk DB by enabling Asterisk Manager Interface ? 
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29271
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29271
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: Addons/General
>    Affects Versions: 11.25.3
>            Reporter: Haseeb Raza
>            Severity: Major
>
> We have asterisk 11.25.3 in production and I have enabled AMI using following guide:
> https://medium.com/@pascomnet/asterisk-tutorial-56-asterisk-ami-configuration-758e0976e601
> Its up and working but it is not showing existing peers or any extensions.
> On web its showing empty everything means no extension no trunk.
> So I want to know how we can access all the things from our database to GUI of AMI ??
> kindly share any guide 



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