Topic: Asterisk Flash Operator Panel

[Teviot]

Hi

I am very new to Asterisk but have used SME for many years.  The documentation for the SAIL addon to SME is difficult for me to navigate.

I'm wondering is there someone who can point me in the direction on how to change and I guess first of all what is the password for the Asterisk Flash Operator Panel?

Also, is there a plan to create a downloadable manual?

Regards
Teviot

[SARK devs]

FOP password is to be found in globals panel (password for FOP ops), default is 1234

admin and user guides are downloadable here

http://sarkpbx.com/sail/pdfs/

Kind Regards

S

[Teviot]

Thank you selintra

That helps a lot. While at the time of writing this responce I haven't read them. Thank you for your quick responce

Teviot

[Teviot]

Tried the password suggested and think I found where to change the password.  Unfortunately have been unsuccessful in loging into the Asterisk Flash Operator Panel

Teviot

[SARK devs]

are you logging in from a different sub net to the sark box?

exactly how are you trying to log in to FOP?

[Teviot]

selintra

I'm using a server-gateway setup

external ip is 192.168.0.x/255.255.255.0
internal ip is 192.168.76.x/255.255.255.0

I am entering FOP from the server-manager page (https://192.168.76.3/extfop/) and it won't login even with the default password

Teviot

[Teviot]

Hi S and All

Still have been unable to access FOP.

Regards
Teviot

[SARK devs]

Hello Teviot,

I'm sorry, but "can't log in" is too big a problem space for us.  First of all, there is no requirement to log-in to FOP, you just click the button and the FOP screen appears. There is no challenge response unless you attempt to have FOP make a call for you.    So... "can't log in" is, itself, a puzzling statement on the face of it.  However, you need to give us some more clues...  What state is the screen in after the attempt?  What does the SME server message log have to say on the subject (if anything). 

These things we need to know to help you. FOP has been present almost from the first in SAIL and we've never had anyone report a "log-in" type fault with it before.


Best


S 

[Teviot]

Ok ... What I mean is that it won't accept a password to log in

Teviot

[SARK devs]

I am at a loss with this.  I want to help you but you just aren't giving me enough information. As I explained in my last post, there is no requirement to log in to FOP.  It doesn't ask for a password.  I don't know how to make this any plainer.   So therefore what you are seeing is NOT what everyone else sees when they fire up FOP.  Now, I need you to explain to me what you are doing and seeing in order to help you.  If you simply keep repeating that it won't accept a password then I really can't help you much because I don't understand what you are telling me.  I need narrative and context so that I can visualize what is wrong.

S



 

[Teviot]

I hear what you are saying.  Maybe it's the way I explained myself.

When I click on the link that looks for

Code: [Select]

https://192.168.76.3/extfop/
I get the the screen that show extentions & trunks & parking and conferences etc. I then click on the opened lock which brings up a window asking for a password.  I enter the password and click the OK button and the lock remains in the same state as it did before.  I have used the same panel with trixbox but I didn't configure that.

Hope I have explained better this time.

Teviot

[SARK devs]

OK....

I had no idea that you could click on the lock.  In the past, I've simply grabbed a phone icon and dragged it to a conference room or whatever and then FOP asks for the password.  Once entered you can drag and drop with gay abandon.  The lock thing does seem to display odd behaviour; whether it is open or closed seems to bear little relationship to whether FOP will let you drag and drop.  If I were you I would try dragging stuff around and see what happens. 

We have no control over FOP behaviour whatsoever.  We simply guest it under the SARK umbrella.  In other words, it is what it is.  All we ensure is that whenever the FOP guy brings out a new release, we update SARK to use it.  SARK uses SME templates to generate the FOP layout file (which controls the number, labeling and size of the end-point widgets), but that's it.

Most of our customers switch it off in practice because it is a serious resource hog.  Still others run their own versions on a separate machine to keep load off the PBX.  In such cases, they handcraft the layout screen to suit their individual installations.


Kind Regards

S

[soprom]

Did you check Global Settings:
- 4-digit Password for FOP Ops
- Run FOP Daemon? Yes

[Teviot]

Did you check Global Settings:
- 4-digit Password for FOP Ops
- Run FOP Daemon? Yes

4 digit password in place

I don't have an option for the FOP Daemon in global settings

Is there a CMD line command I can issue to check and or start the FOP Daemon?

Teviot

[SARK devs]

Is there a CMD line command I can issue to check and or start the FOP Daemon?

Code: [Select]

/etc/init.d/fop {start|stop|status}

[Teviot]

Hi S

I'm having another look at this.  What I meant in earlier post was all I get is the red flashing dots.  The system doesn't appear to accept any passwords at all

Code: [Select]

[root@sail ~]# /etc/init.d/fop status
op_server.pl (pid 9414) is running...
[root@sail ~]#
I think with this one for me particularly we should take this one step at a time which unfortunately could be very time consuming given the time between posts.

[pfloor]

What I meant in earlier post was all I get is the red flashing dots. 

If all you see is flashing dots, this means that the FOP isn't working correctly and the most common cause I have seen is that tcp port 4445 is closed.

[Teviot]

Ok ... to fix my problem with the FOP, what steps do I need to take?

[pfloor]

I'm not sure as I don't run sail.  I'll just take a guess here, let's start with the output of:

Code: [Select]

config show asterisk
config show sark
config show sail

[SARK devs]

OK....  FOP.

check that you have permissions set correctly in the manager interface...

Code: [Select]

[general]
enabled=yes
port=5038
;bindaddr=127.0.0.1
displayconnects=yes
[fop]
secret=xxxxxxxx
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
;Authorization
read=system,call,log,verbose,command,agent,user
write=system,call,log,verbose,command,agent,user

The system default for the manager interface is to only allow comms from the localhost (bindaddr).  However, in the above example we widen this to allow coms from the local sub-net.  You might need to widen this still further if you are attempting to communicate from a different subnet or external IP. 

   

[Teviot]

Hi Guys

done all the above with the following result.

Code: [Select]

[root@sail ~]# config show asterisk
asterisk=service
    UDPPorts=4569,5060,10000:20000
    status=disabled
[root@sail ~]# config show sark
sark=service
    UDPPorts=4569,5060,10000:20000
    status=enabled
[root@sail ~]# config show sail
[root@sail ~]# /etc/init.d/fop status               
op_server.pl (pid 12725) is running...
[root@sail ~]# /etc/init.d/fop stop 
Shutting down Flash Operator Panel:                        [  OK  ]
[root@sail ~]# /etc/init.d/fop start
Starting Flash Operator Panel:                             [  OK  ]
[root@sail ~]#
and my manager.conf is as follows

Code: [Select]

[general]
enabled=yes
port=5038
bindaddr=127.0.0.1
displayconnects=yes
[fop]
secret=XXXXXXXX
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
permit=192.168.76.1/255.255.255.0;
;
;writetimeout=100
;
;Authorization
read=system,call,log,verbose,command,agent,user
write=system,call,log,verbose,command,agent,user
Still have the falsing red dots and the system doesn't appear to accept any password including those in the global setting tab.


Where or what should I be looking for now?

[SARK devs]

you should comment out the bindaddr in manager.conf.  Place a semicolon at the beginning of the line.

 

[Teviot]

S

Done that with no change fo FOP

[SARK devs]

I'm assumimg you restarted asterisk and fop after the change


which release of sail do you have?

[Teviot]

S

Yeap ... with no change. I was fortunate to have a power blackout around the same time I as I was working on this problem and I also rebooted the machine

[SARK devs]

and the release?

[Teviot]

S this may be a silly question ... how do I find that?

I did install from an iso burnt to a cd of 7.3

[SARK devs]

SAIL release is printed at top of globals panel

[David Harper]

Or from the command line:

Code: [Select]

rpm -q sail

From my (updated) test VM:

Code: [Select]

[root@herodotus ~]# rpm -q sail
sail-2.2.1-684
[root@herodotus ~]#


[Teviot]

The version I am using is:- Version: sail-2.2.1-617

[SARK devs]

Try -688 - we fixed a couple of bugs last night.



Best

S

[Teviot]

S

Sorry to be a pain, but how do I go about updating ?

[David Harper]

This should do the trick:

Code: [Select]

wget http://www.sarkpbx.com/sail/sail-2.2.1/sail-2.2.1-688.noarch.rpm
yum -y localupdate sail-2.2.1-688.noarch.rpm
signal-event post-upgrade ; signal-event reboot


[Teviot]

Upgrade went ok.  Did get the following errors

Code: [Select]

SELMERGE - doing MTIME Conversion
WARNING in /etc/e-smith/db/selintra/migrate//20-selmerge: Use of uninitialized value in string eq at /etc/e-smith/db/selintra/migrate//20-selmerge line 148.
SELMERGE - Enabling MTIME
SELMERGE - Merge Ends... Tuples Deleted 1, Tuples Added 26, Messages 141
WARNING: Template processing succeeded for /: 1 fragment generated warnings
 at /usr/lib/perl5/site_perl/esmith/DB.pm line 459
smeserver trap post-install: perl-Date-Calc
smeserver trap post-install: perl-Bit-Vector
smeserver trap post-install: sail

Dependency Installed: perl-Bit-Vector.i386 0:6.3-3 perl-Date-Calc.i386 0:5.3-9
Updated: sail.noarch 0:2.2.1-688
Complete!

[SARK devs]

its fine.

there was a change to the timing mechanism in 684 which causes the warning.  You can ignore it.

Best

S

[Teviot]

S

the FOP works now.  Must have been something to do with the older version.

Thanks for your help