Another login problem

palacista · July 2009

I have read all other login problem threads and checked my configs but I still can't login.
I doubt that the passwords are incorrect because I can see no port 5038 traffic between fop2 and asterisk.

I had manually installed fop2 to work with an asterisk 1.6.1.1 on a Centos 5.0 box. Asterisk is working well.

1. fop2_server --test works i.e:

[asterisk@phone1 fop2]$ ./fop2_server --test
Flash Operator Panel 2 - No valid license found. Demo Mode
Connection to manager OK!

and is reported on the asterisk console:

phone1*CLI>
== Manager 'flash' logged on from 127.0.0.1
== Manager 'flash' logged off from 127.0.0.1
phone1*CLI>

2. A manual login also works i.e:

[asterisk@phone1 ~]$ telnet localhost 5038
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
Asterisk Call Manager/1.1

3. When I start fop2 as a service I see no traffic on port 5038.

4. I can connect to the the web pages from a client and enter the extension a password.

fop2.cfg

[general]
; AMI definitions
manager_host=localhost
manager_port=5038
manager_user=flash
manager_secret=pl41nt3xt
;event_mask=call,agent

; Daemon definitions
listen_port = 4445 Display IP Address as tooltips for SIP peers
monitor_ipaddress = 0
web_dir = /var/www/http/fop2
; Force blind transfer on asterisk 1.6
blind_transfer = 0

;master_key = 5678

; USER LIST
user=2691:2692:all
user=2692:2692:all
;user=622:1234:all
;user=623:1234:all
;buttonfile=buttons.cfg

;#exec autoconfig-users-freepbx.sh

The user password match the voicemail password

etc/asterisk/manage.conf

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

bindaddr = 0.0.0.0

debug = on ; enable some debugging info in AMI messages (default off).
; Also accessible through the "manager debug" CLI command.

[flash]
secret = pl41nt3xt
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,agent,user,config,dtmf,reporting,cdr,dialplan
write = system,call,agent,user,config,command,reporting,originate
displayconnects = yes ; Display on CLI user login/logoff

buttons.cfg

[SIP/2691]
type=extension
extension=2691
context=willow
label=2691
mailbox=2691@default
extenvoicemail=*620@from-internal

[SIP/2692]
type=extension
extension=2692
context=willow
label=2692
mailbox=2692@default
extenvoicemail=*621@from-internal

nicolas · July 2009

Hi,

fop2.cfg

[general]
; AMI definitions
manager_host=localhost
manager_port=5038
manager_user=flash
manager_secret=pl41nt3xt
;event_mask=call,agent

; Daemon definitions
listen_port = 4445 Display IP Address as tooltips for SIP peers

Is the last line textual from your fop2.cfg file? That will mess the listen port as it should only say 4445 and not "4445 Display ...."

Anyways, your mail was super detailed, but I do not know what your exact problem is? You cannot login... are you prompted for the extension and password and then it ask for the password again, or it tries to connect to the server forever?

palacista · July 2009

Thanks for the reply , I have fixed the line in fop2.cfg but it has made no difference.

The error is that, when I enter the number/password the web page just reshows the entered number & (blocked out) password.
There is no port 5038 traffic from fop2 to asterisk and no sign on the asterisk console of a login for the user "flash" except for the command fop2_server --test.

Is there a restriction on unix permissions/users that own the fop2 installation?

nicolas · July 2009

Hello,

FOP2 client login and communication does not use port 5038 but port 4445 by default. Port 5038 is used for fop2_server to AMI connection, so you have to see traffic when you start fop2_server, not when you try to login with your browser.

The best way to see activity is to launch fop2_server in debugging mode, if you started it from init scripts, stop it and start it from the command line:

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

You will see fop2_server trying to connect to AMI, you will see errors if the login is not successfull, or just plain errors if there is something wrong in other parts.

Then try to connect with your browser, and if you want to capture traffic, do so by listening on port 4445. That might be one problem.. fop1 also uses port 4445 by default. You cannot run both daemons on the same port, the recommendation as stated in the FAQ is to run fop1 on port 4444, or just disable fop1.

In fop2_server output you can see login attempts from clients and responses from the server too.

If you still have issues, try to catch me online on the live help so we can work this out.

Best regards,

palacista · July 2009

My problem was with the button.cfg file. :oops: All working now thanks.

Another login problem

Comments