[Home]

Summary:ASTERISK-17694: Originate via AMI does not work.
Reporter:Michael Munger (drdamnit)Labels:
Date Opened:2011-04-14 15:32:35Date Closed:2011-06-07 14:00:52
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/General
Versions:1.8.3 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:SVN: None. 1.8.3.2 STABLE from asterisk.org.

Platform:
Distributor ID: Ubuntu
Description:    Ubuntu 9.10
Release:        9.10
Codename:       karmic

Issue and reproduction steps:
1. Originate from the CLI works.

2. "manager show commands" in the CLI lists Originate as an available command via the CLI.

3. ListCommands when logged into AMI does not list Originate.

4. Originate via AMI fails with the response:

Action: Originate
Channel: SIP/4101
Application: MeetMe
Data: 1234

Response: Error
Message: Permission denied

Response: Error
Message: Invalid/unknown command: Originate. Use Action: ListCommands to show available commands.

It also fails if I try: Channel Originate:

Action: Channel Originate
Channel: SIP/4101
Application: MeetMe
Data: 1234

Response: Error
Message: Permission denied

Response: Error
Message: Invalid/unknown command: Channel Originate. Use Action: ListCommands to show available commands.



****** ADDITIONAL INFORMATION ******

Core show version:
Asterisk 1.8.3.2 built by root @ voip on a i686 running Linux on 2011-03-29 21:01:32 UTC
Comments:By: Richard Mudgett (rmudgett) 2011-04-14 16:41:08

You have not enabled the "originate" write permission in manager.conf.

Although, I don't think it should be sending the invalid command response after sending the permission denied response.

By: Michael Munger (drdamnit) 2011-04-14 16:49:47

I thought of that. I checked to make sure before I submitted the bug request. It was enabled. Here's manager.conf with the password changed to protect the innocent.

[general]
displaysystemname = yes
enabled = yes
;webenabled = yes
port = 5038

;httptimeout = 60
; a) httptimeout sets the Max-Age of the http cookie
; b) httptimeout is the amount of time the webserver waits
;    on a action=waitevent request (actually its httptimeout-10)
; c) httptimeout is also the amount of time the webserver keeps
;    a http session alive after completing a successful action

bindaddr = 0.0.0.0
;displayconnects = yes
;
; Add a Unix epoch timestamp to events (not action responses)
;
;timestampevents = yes

;[mark]
;secret = mysecret
;deny=0.0.0.0/0.0.0.0
;permit=209.16.236.73/255.255.255.0
[agi]
secret=hidden
;deny=0.0.0.0/0.0.0.0
;permit=173.165.161.160/255.255.255.240

;
; If the device connected via this user accepts input slowly,
; the timeout for writes to it can be increased to keep it
; from being disconnected (value is in milliseconds)
;
; writetimeout = 100
;
; Authorization for various classes
;read = system,call,log,verbose,command,agent,user,config
write = system,call,log,verbose,command,agent,user,config

By: Richard Mudgett (rmudgett) 2011-04-14 17:17:15

The last line in the file does not give permission to originate new calls.  You need to add originate to the list.  See the manager.conf.sample file for documentation.