<![CDATA[No actions toolbar]]>We are currently in the proces of setting up or Asterisk server. I defined a few SIP phone devices and extensions, and I wanted to take a look at FOP2. We use the MAC adres to define the name of the device, or a string in case of a softphone.

I thought I'd take a look with a small config.. I only defined one extension, and my two trunks.. I don't have voicemails or queues setup yet, so I thought I'd comment that out.

[SIP/spRoland]
type=extension
extension=337
context=stumpel-zwaag
label=Roland
;mailbox=620@default
;extenvoicemail=*620@from-internal
;external=5551234@from-internal
;privacy=clid
;queuechannel=Local/620@from-queue/n|Penalty=1|MemberName=Nicolas|StateInterface=SIP/620

Now when I go to the webclient of FOP, I do see the button for extension 337, but I don't see the action buttons in the toolbar. I cannot dial, or do anything else.

I was also wondering: do these extensions in sop2.cfg (user=622:1234 for example) need to match the sip.conf in asterisk?

Am I missing something in my Asterisk config files?

]]>http://localhost:4567/topic/990/no-actions-toolbarRSS for NodeTue, 27 Oct 2026 14:25:47 GMTThu, 29 Dec 2011 21:03:49 GMT60<![CDATA[Reply to No actions toolbar on Thu, 01 Mar 2012 17:10:24 GMT]]>wow, that is super strange!

fop2 is mostly a javascript application, so it could work cached, but perhaps not fully. Not sure how that would impact the toolbar as there is no php involved, but most probably the cached client you had was from a previous version than the running fop2 server, and that will cause all sorts of strange issues (using old client on new server or viceversa).

Best regards,

]]>http://localhost:4567/post/4367http://localhost:4567/post/4367Thu, 01 Mar 2012 17:10:24 GMT<![CDATA[Reply to No actions toolbar on Thu, 01 Mar 2012 16:33:58 GMT]]>Both the fop2.cfg and buttons.cfg were configured correctly. After confirming the configuration, I started looking at other issues. I was using Firefox to test; however when I would try either IE or Chrome, I couldn't even get to the website at all. I finially figured out that the Apache service wasn't running. Once I started it, everything is working great. Strange that Firefox would have cached the ability to get to some services and work somewhat. It actually show status of my calls, I just couldn't control them without the action menu.

thanks

]]>http://localhost:4567/post/4366http://localhost:4567/post/4366Thu, 01 Mar 2012 16:33:58 GMT<![CDATA[Reply to No actions toolbar on Thu, 01 Mar 2012 16:33:55 GMT]]>Both the fop2.cfg and buttons.cfg were configured correctly. After confirming the configuration, I started looking at other issues. I was using Firefox to test; however when I would try either IE or Chrome, I couldn't even get to the website at all. I finially figured out that the Apache service wasn't running. Once I started it, everything is working great. Strange that Firefox would have cached the ability to get to some services and work somewhat. It actually show status of my calls, I just couldn't control them without the action menu.

thanks

]]>http://localhost:4567/post/4365http://localhost:4567/post/4365Thu, 01 Mar 2012 16:33:55 GMT<![CDATA[Reply to No actions toolbar on Thu, 01 Mar 2012 02:42:59 GMT]]>Does your button for 103 has the line "extension=103" in it? If so, and you do not see action buttons, it is because your user line in fop2.cfg does not have any permissions set. Basically, having

user=103:mypassword:all

and in the buttons.cfg file

[SIP/whatever]
type=extension
extension=103
label=whatever
context=from-internal

That will work, for sure, no questions, no other posibilites or outcomes. However, if you have this

user=103:mypassword:all

and in buttons.cfg

[SIP/103]
type=extension
label=whatever
extension=9999
context=idonotknowwhattowritehere

Then it will fail, as there is no match between the user number and the extension=xxx in your buttons.cfg file

Best regards,

]]>http://localhost:4567/post/4364http://localhost:4567/post/4364Thu, 01 Mar 2012 02:42:59 GMT<![CDATA[Reply to No actions toolbar on Wed, 29 Feb 2012 23:11:21 GMT]]>I have read the FAQ several times now. I have configured a SIP phone with extension 103. I have created a user in fop2.cfg of 103 with the sip secret from the user in Sip.conf. I have a button for 103 created in buttons.cfg. I log into fop2 and it doesn't show the main action menu. It does have my button for 103 as well as several others. Any ideas?

]]>http://localhost:4567/post/4363http://localhost:4567/post/4363Wed, 29 Feb 2012 23:11:21 GMT<![CDATA[Reply to No actions toolbar on Fri, 30 Dec 2011 18:08:10 GMT]]>Not sure what you mean.. but in fop2 you can monitor multiple devices in just one button using the channel field, for example:

[SIP/100]
type=extension
extension=100
context=from-internal
channel=IAX2/100
channel=SIP/200
channel=DAHDI/1

however, actions that involves origination, will use only the default device, or the originatechannel that you also might configure on the button config:

[SIP/100]
type=extension
extension=100
context=from-internal
channel=IAX2/100
channel=SIP/200
channel=DAHDI/1
originatechannel=Local/100@from-internal

Using Local channels will go to your dialplan and reach whatever device is 'attached' to that extension.

Best regards,

]]>http://localhost:4567/post/4362http://localhost:4567/post/4362Fri, 30 Dec 2011 18:08:10 GMT<![CDATA[Reply to No actions toolbar on Fri, 30 Dec 2011 10:05:49 GMT]]>Ok, I feel pretty stupid now, especially because I browsed through that FAQ page. Thank you for your quick reply and patience with people like me 🙂

So it seems to me that FOP assumes that an extension is always connected to one device, am I right?

But I could connect several devices to one extension. How does FOP handle this? (I browsed the FAQ again before asking this question).

]]>http://localhost:4567/post/4361http://localhost:4567/post/4361Fri, 30 Dec 2011 10:05:49 GMT<![CDATA[Reply to No actions toolbar on Fri, 30 Dec 2011 05:01:57 GMT]]>Hi,

You missed the 3rd question in the FAQ:

http://www.fop2.com/documentation-faq.php

In order for the action toolbar to appear, you MUST login with an extension that is also listed in the extensions list. If there is no matching button for the extension your are loggin as, the toolbar will not be displayed, as FOP2 will not be able to figure out the device to use for performing the actions. If you are using the free version, you must have to login with an extension that is part of the first 15 buttons displayed.

So, if you have a button with extension 337, you must login with the 337 user.

]]>http://localhost:4567/post/4360http://localhost:4567/post/4360Fri, 30 Dec 2011 05:01:57 GMT