<![CDATA[Buttons on action bar not in function]]>Hi!

Anyone else tried FOP2 on Trixbox 2.8.0?

I've installed it OK, and can track extension availibility and status ok. But from the buttons in action bar only a few of them are working (actually only Hangup I think?).

When I try to i.e. transfer a call, absolutely nothing happens. Any suggestions would be appreciated 🙂

Best regards
Stian

]]>http://localhost:4567/topic/45/buttons-on-action-bar-not-in-functionRSS for NodeTue, 27 Oct 2026 06:02:57 GMTTue, 21 Jul 2009 09:23:26 GMT60<![CDATA[Reply to Buttons on action bar not in function on Thu, 23 Jul 2009 23:47:30 GMT]]>Hi,

You need the "originate" permission for the manager user.. set that up in /etc/asterisk/manager.conf and you will be fine..

Best regards,

]]>http://localhost:4567/post/250http://localhost:4567/post/250Thu, 23 Jul 2009 23:47:30 GMT<![CDATA[Reply to Buttons on action bar not in function on Thu, 23 Jul 2009 07:49:27 GMT]]>Hi Nicolas!

I've tries the blind_transfer=1 option, and it works like hell 🙂

For "Dial", "Call pickup" and "Listen" fuctions it seems to be an issue about permissions.
Se debug below. Do you have any idea where these permission issues is?

1.1.101.5 <= <msg data="1|originate|3|1bc740888fe559742f81224f7a1463c8" />

127.0.0.1 -> Action: Originate
127.0.0.1 -> Channel: SIP/645
127.0.0.1 -> Exten: 647
127.0.0.1 -> Context: from-internal
127.0.0.1 -> Priority: 1
127.0.0.1 -> CallerID: <645>
127.0.0.1 -> Async: True

127.0.0.1 <- Response: Error
127.0.0.1 <- Message: Permission denied
127.0.0.1 <- Server: 0

Response: Error
Message: Permission denied
Server: 0

Best Regards
Stian

]]>http://localhost:4567/post/249http://localhost:4567/post/249Thu, 23 Jul 2009 07:49:27 GMT<![CDATA[Reply to Buttons on action bar not in function on Wed, 22 Jul 2009 13:51:27 GMT]]>Hi, I have an interim version where you can force regular redirects instead of atxfer. Atxfer is really nice because it performs an attendant transfer, it was availalbe in some 1.6 version, but it seems not in trixbox. I would have to track 1.6 development more closely.

The interim release you have to add in fop2.cfg:

blind_transfer=1

That will force the use of standard redirection (blind transfers) instead of attendant transfers.

That option is only available since july 20th, and it is not definitive.

That will take care of transfers on asterisk 1.6.

Best regards,

]]>http://localhost:4567/post/248http://localhost:4567/post/248Wed, 22 Jul 2009 13:51:27 GMT<![CDATA[Reply to Buttons on action bar not in function on Wed, 22 Jul 2009 10:53:58 GMT]]>From what I can see the atxfer AMI command is included by default on 1.6.1 and not 1.6.0 if this is right you would have to patch it in as I read that FOP2 will try do attended transfers on 1.6 versions. Maybe you could ask Andrew to add it into Trixbox 2.8.

]]>http://localhost:4567/post/247http://localhost:4567/post/247Wed, 22 Jul 2009 10:53:58 GMT<![CDATA[Reply to Buttons on action bar not in function on Wed, 22 Jul 2009 07:58:46 GMT]]>Hi Nicolas!

Thanks for your reply. I have tries a verbose debug from fop2, and below you'll find the debug output I think is relevant for a try on transfer. As you see, it looks like the Atxfer command is not supported?

1.1.101.5 <= <msg data="1|atxfer|3|5bc68f1ffd1a603cdc59ed440b684b12" />

127.0.0.1 -> Action: Atxfer
127.0.0.1 -> Channel: SIP/192.168.27.5-08debe20
127.0.0.1 -> Exten: 647
127.0.0.1 -> Context: from-internal
127.0.0.1 -> Priority: 1
127.0.0.1 -> Async: True

127.0.0.1 <- Response: Error
127.0.0.1 <- Message: Invalid/unknown command: Atxfer. Use Action: ListCommands to show available commands.
127.0.0.1 <- Server: 0

Response: Error

Message: Invalid/unknown command: Atxfer. Use Action: ListCommands to show available commands.

Server: 0

Please give me a word if you need more debug information. I'm running on a "out of the box" trixbox 2.8.0 with Asterisk 1.6.0.9-samy-r27.

Best regards
Stian

]]>http://localhost:4567/post/246http://localhost:4567/post/246Wed, 22 Jul 2009 07:58:46 GMT<![CDATA[Reply to Buttons on action bar not in function on Tue, 21 Jul 2009 14:13:07 GMT]]>Hi,

It is not easy to debug by forum! Try to catch me on the live help, it can be several things: misconfiguration, fop2 bug, or a user error. What to look for: debug output in the asterisk cli or full log (incrementing verbose and debug levels). Starting fop2_server in debug mode:

service fop2 stop
cd /usr/local/fop2
./fop2_server -X 15

And look for the output trying to spot errors or problems (it is very verbose, you might need to capture the output)

Best regards,

]]>http://localhost:4567/post/245http://localhost:4567/post/245Tue, 21 Jul 2009 14:13:07 GMT