Cannot Login: Elastix 64 bit

[rscl]

Hello,

CentOS 5 64 bit Host with latest VirtualBox and Elastix 64 bit Guest.
Installed the appropriate latest tarball of FOP2
Installation went well and I service fop2 start does not throw any errors.

When I try to login, it just won't work.
After entering username/password and press enter, the form again sliding down.
How to debug ?

Are there any known issues with 64 bit Elastix + FOP2 ?

The license key is bound to the production server and this is a new test server hence, for now, I am working with the free version.

Best regards,
Sans

[nicolas]

If you are prompted again for the password, then you are entering incorrect credentials (bad extension or password). Run /usr/local/fop2/autoconfig-users-freepbx.sh and look at the output, it will give you a hint on what is going on, for example, it could be that you have and old fop2admin on a newer fop2 server version.

Best regards,

[rscl]

Hi,

[root@e1 ~]# /usr/local/fop2/autoconfig-users-freepbx.sh
user=1003:1003:all
user=1001:1001:all
user=1002:1002:all
buttonfile=autobuttons.cfg
[root@e1 ~]#

Everything looks good above.

But restarting amportal gave some unexpected results:

[root@e1 ~]# amportal restart



STOPPING ASTERISK
Asterisk ended with exit status 0
Asterisk shutdown normally.

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

Asterisk Stopped

STOPPING FOP SERVER
SETTING FILE PERMISSIONS
Permissions OK

STARTING ASTERISK
Asterisk Started

STARTING FOP SERVER

-----------------------------------------------------
The FOP's server (op_server.pl) could not start!
Please correct this problem
-----------------------------------------------------
[root@e1 ~]#

Looks like FOP2 is not starting.

What do you suggest ?

Thank you for your time.

Best regards,
Sans

[nicolas]

Hi,

FOP2 is not started from amportal. FOP(1) is. You might want to disable fop1 altogether by setting

FOPRUN=false

in /etc/amportal.conf

best regards,

[rscl]

FOPRUN is already set to false

Asterisk is running:

[root@e1 ~]# asterisk -rvvvvvv
Asterisk 1.6.2.13, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
  == Parsing '/etc/asterisk/asterisk.conf':   == Found
  == Parsing '/etc/asterisk/extconfig.conf':   == Found
Connected to Asterisk 1.6.2.13 currently running on e1 (pid = 7095)
Verbosity was 3 and is now 6
    -- Registered SIP '1001' at 192.168.1.41 port 16800
       > Saved useragent "eyeBeam release 1013t stamp 43070" for peer 1001
e1*CLI>

Still the same issue... FOP2 login screen does not accept credentials.

Pls help.

Thx & Rgds,
Sans

[nicolas]

Not sure what your problem is... I asked you to run /usr/local/fop2/autoconfig-users-freepbx.sh so you can see the list of valid users and password to login to fop2, but you did not do it and email some other captures that are not related at all with fop2.

If you are prompted for extension and password one time, you enter something, and you are asked again, then you are using WRONG credentials.

If you are prompted only ONE time, and then it attempts to connect and fail (attempt 1,2,3,4....), then fop2 server is not running, or port 4445 is blocked.

Best regards,

[rscl]

Not sure what your problem is... I asked you to run /usr/local/fop2/autoconfig-users-freepbx.sh so you can see the list of valid users and password to login to fop2, but you did not do it and email some other captures that are not related at all with fop2.

Look at the 3rd post in this thread.
What am I missing ?

[nicolas]

You do not say if you are prompted once or several times (read 2nd post). If you are prompted several times, then you are entering incorrect credentials. Perhaps you modify fop2.cfg beyond the defaults and broke the config in itself.. I cannot know myself. What extension and password are you entering?

In the other hand, if your are prompted once to login and then attempts to connect and retries until timeout, then you have to check if fop2 server is running, if port 4445 is being taken by fop2 server (and not fop1), that you do not have personal firewalls or flash blockers, etc. Problemas and solutions are listed in the FAQ and in around 20% of the posts in this forum.

[mac86]

In the other hand, if your are prompted once to login and then attempts to connect and retries until timeout, then you have to check if fop2 server is running, if port 4445 is being taken by fop2 server (and not fop1), that you do not have personal firewalls or flash blockers, etc. Problemas and solutions are listed in the FAQ and in around 20% of the posts in this forum.

Yo tengo exactamente ese problema....

tengo fop2 corriendo, el puerto 4445 abierto (fop1 desactivado) , y el navegador queda
mostrando "Connecting to server, attempt number : 1" durante algunos minutos, y
al cabo de un tiempo con el mensaje "Could not connect to server"

problema de usuario y contraseña no tengo, ya que lo he corroborado con

[root@jorju src]# /usr/local/fop2/autoconfig-users-freepbx.sh

group=All Buttons:SIP/113,SIP/123,ZAP/7,SIP/SIM1,SIP/125,SIP/103,SIP/126,SIP/127,SIP/128,SIP/102,SIP/129,PARK/default,SIP/130,ZAP/1,SIP/131,ZAP/5,SIP/132,ZAP/4,SIP/4987713,SIP/124,SIP/122,SIP/114,SIP/111,SIP/115,SIP/116,ZAP/6,SIP/112,SIP/110,SIP/118,SIP/117,SIP/108,ZAP/11,ZAP/8,SIP/119,SIP/105,SIP/120,SIP/104,SIP/121,SIP/134,SIP/4987718,SIP/232,SIP/302,SIP/226,QUEUE/999,SIP/224,ZAP/12,SIP/223,SIP/109,ZAP/3,SIP/234,SIP/SIM2,SIP/4987717,SIP/301,SIP/4987716,SIP/237,SIP/4987715,SIP/236,SIP/4987714,SIP/211,SIP/156,SIP/137,SIP/152,SIP/138,SIP/100,SIP/151,SIP/Secretaria Gerencia,SIP/136,SIP/4987711,SIP/154,SIP/101,SIP/155,SIP/135,ZAP/2,SIP/4987712
group=All Extensions:SIP/109,SIP/118,SIP/111,SIP/302,SIP/100,SIP/108,SIP/102,SIP/101,SIP/103,SIP/104,SIP/105,SIP/Secretaria Gerencia,SIP/110,SIP/135,SIP/151,SIP/138,SIP/137,SIP/136,SIP/152,SIP/134,SIP/132,SIP/131,SIP/130,SIP/154,SIP/155,SIP/301,SIP/237,SIP/236,SIP/234,SIP/232,SIP/226,SIP/224,SIP/223,SIP/156,SIP/129,SIP/128,SIP/127,SIP/119,SIP/117,SIP/116,SIP/115,SIP/121,SIP/114,SIP/120,SIP/122,SIP/124,SIP/211,SIP/123,SIP/113,SIP/126,SIP/112,SIP/125
group=All Queues:QUEUE/999
group=All Trunks:ZAP/12,SIP/4987714,SIP/4987715,SIP/4987716,SIP/4987718,SIP/4987717,ZAP/8,ZAP/5,SIP/4987713,ZAP/7,ZAP/4,SIP/4987712,SIP/SIM2,ZAP/11,ZAP/6,SIP/4987711,ZAP/2,SIP/SIM1,ZAP/3,ZAP/1
user=302:302:all:All Trunks,All Conferences,All Extensions,All Buttons
buttonfile=autobuttons.cfg

para ello he utilizado el user y pass 302 / 302
si pongo un pass incorrecto me da la pantalla de error

pero si pongo user y pass correcto, sucede lo que indique....

version 2.22 para 64 bits bajo centox (elastix 2.0.3)

ahora tambien me dejo de funcionar la licencia (sera por tantas
pruebas de instalacion y desinstalacion que hice de fop2?)

ayuda, por favor.!

gracias!

[nicolas]

Si pones usuario y clave incorrectos y te vuelve a preguntar, entonces la conexion al puerto 4445 esta ok, ahora, si pones usuario y clave correctos y se queda pensando, entonces el cliente javascript esta roto. Quizas tengas en cache la version vieja corriendo con un servidor nuevo. Un cliente version 2.20 puede tener problemas conectando con el servidor 2.22.

En cualquier caso, prueba siempre con un navegador diferente, eso te permitira tambien ir descartando posibilidades. Y si la aplicacion javascript esta rota por algun motivo, ese motivo lo veras casi con seguridad abriendo la consola javascript de safari/chrome, o bien instalando firebug para firefox y mirando alli. Incluso la consola javascript de IE9 funciona bien.

[mac86]

Si pones usuario y clave incorrectos y te vuelve a preguntar, entonces la conexion al puerto 4445 esta ok, ahora, si pones usuario y clave correctos y se queda pensando, entonces el cliente javascript esta roto. Quizas tengas en cache la version vieja corriendo con un servidor nuevo. Un cliente version 2.20 puede tener problemas conectando con el servidor 2.22.

En cualquier caso, prueba siempre con un navegador diferente, eso te permitira tambien ir descartando posibilidades. Y si la aplicacion javascript esta rota por algun motivo, ese motivo lo veras casi con seguridad abriendo la consola javascript de safari/chrome, o bien instalando firebug para firefox y mirando alli. Incluso la consola javascript de IE9 funciona bien.

Gracias por contestar Nicolas.

en realidad, ya probe con Iexplore, chrome y firefox.

Tengo otro servidor mas viejo con fop2.11 (64bits) y funciona perfecto.
Sin embargo con este mas nuevo tengo dicho inconveniente.

No te entiendo a que te referis con

Un cliente version 2.20 puede tener problemas conectando con el servidor 2.22.

es decir, si instalo fop2.22 , entiendo que se instala el servidor 2.22 y el cliente 2.22
en /usr/local/fop/ y en /var/www/html/fop2 respectivamente.

digo bien?

porque asi es como lo tengo instalado