Action Bar Buttons do not work

[pwd]

I am trying to do a call pickup.
we are running Version 2.24 on a Trixbox server with the configuration tools.

I have set myself to "all" Permissions.

When I select a extension (not my own) the border turns blue (not red as the manual says it should)
when that extension is ringing (can see on the FOP2) and I try to click the pickup (or any
other button) nothing happens, the call just goes to voice mail (I picked someone who is not in the office at this time)

I can't see any action that FOP2 is taking in the CLI of Asterisk (which is version 1.6.0.26-FONCORE-r78 )

How do I start troubleshooting this problem.

[nicolas]

Be sure you add "all" permissions in /etc/asterisk/manager.conf file , both in read/write lines.

[DVillavisanis]

None of the buttons work . I select an active extension then I hit the listen button. My extension does not ring.

From My phone I can activate the channel spy, so I know that asterisk is working.

using asterisk version 1.60.26 and FOP2 version 2.23
trixbox ce

---

buttons.cfg

---

[SIP/200]
type=extension
extension=200
label=Receptionist
mailbox=200@default
context=from-internal
queuecontext=from-internal
extenvoicemail=*200@default
privacy=none
queuechannel=Local/200@from-internal/n|Penalty=0|MemberName=Receptionist|StateInterface=SIP/200|Queue=6001
originatechannel=Local/200@from-internal
customastdb=CF/200

[SIP/201]
type=extension
extension=201
label=Irving Figueroa-ABC
mailbox=201@default
context=from-internal
queuecontext=from-internal
extenvoicemail=*201@default
privacy=none
group=Shipping
queuechannel=Local/201@from-internal/n|Penalty=0|MemberName=Irving Figueroa-ABC|StateInterface=SIP/201
customastdb=CF/201

---

manager.conf

---

[admin]
secret = *************
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read =all,system,call,log,verbose,command,agent,user
write =all,system,call,log,verbose,command,agent,user

---

fop2.cfg

---

[general]
; AMI definitions
manager_host=localhost
manager_port=5038
manager_user=fop2
manager_secret=************
;event_mask=agent,call,command,system,user,dialplan

; Daemon definitios
listen_port = 4445
;restrict_host = www.asternic.org
;web_dir = /var/www/html/operator/fop2

; Global Config
poll_interval = 86400
poll_voicemail = 1
monitor_ipaddress = 0

; Force blind transfer on asterisk 1.6
blind_transfer = 1

; Force supervised transfer on asterisk 1.4
; requires the atxfer manager backport patch
; supervised_transfer = 1

; Force delimiter for asterisk applications
force_parameter_delimiter = ","

; When adding or removing members to a queue, fop2 will default to
; AddQueueMember/RemoveQueueMember commands. If you set use_agentlogin
; to 1, together with the QueueChannel in a button definition set to
; an Agent number it will use AgentCallbackLogin and Agentlogoff instead.
;
; use_agentlogin = 0

; Master Password that overrides any individual one
master_key = 7270

; Options to send to chan_spy when doing a Listen action
; This global setting is overriden by the individual button
; spyoptions directive if set (in the button config).
; Asterisk 1.6.1 or higher has the option "d" that lets you
; switch spying modes using the keypad:
4 = spy mode
5 = whisper mode
;6 = barge mode
;spy_options="q"
spy_options="bq"

; Options to send to chan_spy when doing a Whisper action
; In Asterisk 1.6.1 or higher you can use B to enable barge (speak
; to both channels on a call).
whisper_options = "w"

; When you spy to an ongoing call, your spy session will end as
; soon as the conversation you are listening to finishes. If you
; rather keep the chan spy session open after the call end, uncomment
; the following line.
;persistent_spy=1

[nicolas]

From manager.conf you posted your admin user, but you connect in fop2.cfg with the "fop2" user. My guess is that you do not have the correct manager permissions. You would clearly see that when starting fop2 in debug mode:

service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 511
(do your tests)
ctrl-C
exit

You can then analyze the capture.log file. Anyways, most probably your fop2 user in manager.conf does not have enough permissions to originate calls.

Best regards,