Not log in on centos5

rickygmrickygm
in Support
Hi forum, I installs the version demo of the fop2 in centos 5, configure following the manual of the web and all ok until here, but when I log in with one of the extensions configured inside the fop2.cfg shows me this message :

he attempts it 10 times and later it leaves the message:

Could not connect to server

fop2.cfg

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

; Daemon definitios
;listen_port = 4447
;restrict_host = http://www.asternic.org
#web_dir = /var/www/html/operator/fop2
#web_dir = /var/www/html/fop2

; Global Config
language = en
poll_interval = 86400
poll_voicemail = 1
monitor_ipaddress = 0

;master_key = 5678


; USER LIST
user=101:liwewwsq:all
user=102:21qalux:all
user=103:linsddsdaxcx:all
;user=623:1234all
buttonfile=buttons.cfg

I have something bad inside the configuration ?

regardss

Comments

  • nicolasnicolas
    Things to check:

    1) flash player installed and working
    2) fop2_server running and listening on port 4445
    3) port 4445 not filtered or forwarded if needed

    Not that important but check anyways:

    4) does buttons.cfg exists? What's inside?

    Best regards,
  • rickygmrickygm
    Things to check:

    1) flash player installed and working

    yes , all is ok

    2) fop2_server running and listening on port 4445

    # netstat -an | grep 4445
    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN

    3) port 4445 not filtered or forwarded if needed

    I don't have any firewall at the moment

    Not that important but check anyways:

    4) does buttons.cfg exists? What's inside?

    buttons.cfg

    [SIP/101]
    type=extension
    extension=101
    context=netport
    label=Ventas
    mailbox=101@default
    extenvoicemail=101@default

    [SIP/102]
    type=extension
    extension=102
    context=netport
    label=Consultoria
    mailbox=102@default
    extenvoicemail=102@basicos

    [SIP/103]
    type=extension
    extension=103
    context=netport
    label=Soporte
    mailbox=103@default
    extenvoicemail=103@basicos

    [CONFERENCE/9000]
    type=conference
    label=Sala de Conferencia
    server=1
    extension=9000
    context=basicos



    Best regards,

    regardss
  • diatonicdiatonic
    Might want to make sure that the original fop isn't running on TCP 4445. Stop the fop2 service and recheck your netstat. If you want to run both fop and fop2 change op_server.pl for fop to run on 4444 (See the FAQ).

    .:diatonic:.
  • nicolasnicolas

    2) fop2_server running and listening on port 4445

    # netstat -an | grep 4445
    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN


    regardss

    Try with:
    netstat -lnp

    To verify that fop2 is the one listening on port 4445 (and not fop1)

    Best regards,
  • rickygmrickygm
    Hi, I stop the fop2 the port 4445 this closed , I forget to comment that I use pure asterisk, I don't use any asterisk gui o other version de fop

    only fop2

    some idea where the error can be?, I install the fop2 from the gz

    service fop2 stop
    Shutting dows Flash Operator Panel 2: [ OK ]

    netstat -an | grep 4445
  • nicolasnicolas
    Start fop2_server from the command line:
    cd /usr/local/fop2
./fop2_server -X 15

    Leave it running there, look for potential errors or something...

    From the browser machine, telnet to port 4445 at the fop2 server...
    telnet xxx.xxx.xxx.xx 4445

    Does it connect? If not, check your firewall. If it connects ok, open the browser and navigate to the fop2 page.

    Be ABSOLUTELY sure you have the flash player installed and working on that browser. If everything else fails, try with another browser, firefox, chrome, IE, safari, etc..
  • rickygmrickygm
    ok look

    ./fop2_server -X 15
    Flash Operator Panel 2 - No valid license found. Demo Mode

    Can't listen to port 4445

    telnet 192.168.10.3 4445
    Trying 192.168.10.3...
    Connected to vxserver (192.168.10.3).
    Escape character is '^]'.

    its ok connection

    the screen of the fop2 load well, the problem is that when I put the extension to log in he never enters
  • nicolasnicolas
    Ok.. wait a minute
    Can't listen to port 4445

    That's not good... after that fop2_server will exit. Not sure what you did to get this, but it means you have another process binding to port 4445.

    Did you try the netstat -lnp ??

    Are you sure you are not running another instance or software binding to port 4445? After starting fop2_server with -X 15 you should see lots of events from AMI and from your flash clients.
  • rickygmrickygm
    when I run the command netstat -lnp and I stop the fop2, I don't see the port in listens for another program

    tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 2640/hpiod
    tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 2813/dovecot
    tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 2813/dovecot
    tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 2570/slapd
    tcp 0 0 0.0.0.0:646 0.0.0.0:* LISTEN 2160/rpc.statd
    tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2784/mysqld
    tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 2972/asterisk
    tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 2813/dovecot
    tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 2813/dovecot
    tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2120/portmap
    tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 2972/asterisk
    tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2677/cupsd
    tcp 0 0 0.0.0.0:1720 0.0.0.0:* LISTEN 2972/asterisk
    tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2879/master
    tcp 0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 2645/python
    tcp 0 0 :::7777 :::* LISTEN 3301/java
    tcp 0 0 :::993 :::* LISTEN 2813/dovecot
    tcp 0 0 :::9090 :::* LISTEN 3301/java
    tcp 0 0 :::9091 :::* LISTEN 3301/java
    tcp 0 0 :::995 :::* LISTEN 2813/dovecot
    tcp 0 0 :::389 :::* LISTEN 2570/slapd
    tcp 0 0 :::5222 :::* LISTEN 3301/java
    tcp 0 0 :::5223 :::* LISTEN 3301/java
    tcp 0 0 :::5229 :::* LISTEN 3301/java
    tcp 0 0 :::110 :::* LISTEN 2813/dovecot
    tcp 0 0 :::1935 :::* LISTEN 2928/java
    tcp 0 0 :::9999 :::* LISTEN 2928/java
    tcp 0 0 :::4559 :::* LISTEN 3166/hfaxd
    tcp 0 0 :::143 :::* LISTEN 2813/dovecot
    tcp 0 0 :::80 :::* LISTEN 2916/httpd
    tcp 0 0 :::50865 :::* LISTEN 2928/java
    tcp 0 0 :::7443 :::* LISTEN 3301/java
    tcp 0 0 :::5269 :::* LISTEN 3301/java
    tcp 0 0 :::22 :::* LISTEN 2663/sshd
    tcp 0 0 :::5080 :::* LISTEN 2928/java
    tcp 0 0 :::443 :::* LISTEN 2916/httpd
    tcp 0 0 :::7070 :::* LISTEN 3301/java
    udp 0 0 0.0.0.0:640 0.0.0.0:* 2160/rpc.statd
    udp 0 0 0.0.0.0:45699 0.0.0.0:* 3366/iaxmodem
    udp 0 0 0.0.0.0:643 0.0.0.0:* 2160/rpc.statd
    udp 0 0 0.0.0.0:49951 0.0.0.0:* 3229/avahi-daemon:
    udp 0 0 0.0.0.0:2727 0.0.0.0:* 2972/asterisk
    udp 0 0 0.0.0.0:4520 0.0.0.0:* 2972/asterisk
    udp 0 0 0.0.0.0:5060 0.0.0.0:* 2972/asterisk
    udp 0 0 0.0.0.0:4569 0.0.0.0:* 2972/asterisk
    udp 0 0 0.0.0.0:5353 0.0.0.0:* 3229/avahi-daemon:
    udp 0 0 0.0.0.0:111 0.0.0.0:* 2120/portmap
    udp 0 0 0.0.0.0:631 0.0.0.0:* 2677/cupsd

    I stop the and I run the fop2 with the command. /fop2_server -X 15

    127.0.0.1 <- NewMessages: 1
    127.0.0.1 <- OldMessages: 0
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: MailboxStatus
    127.0.0.1 -> Mailbox: 102@default

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Mailbox Status
    127.0.0.1 <- Mailbox: 102@default
    127.0.0.1 <- Waiting: 0
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: MailboxCount
    127.0.0.1 -> Mailbox: 102@default

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Mailbox Message Count
    127.0.0.1 <- Mailbox: 102@default
    127.0.0.1 <- NewMessages: 0
    127.0.0.1 <- OldMessages: 0
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: MailboxStatus
    127.0.0.1 -> Mailbox: 101@default

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Mailbox Status
    127.0.0.1 <- Mailbox: 101@default
    127.0.0.1 <- Waiting: 0
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: MailboxCount
    127.0.0.1 -> Mailbox: 101@default

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Mailbox Message Count
    127.0.0.1 <- Mailbox: 101@default
    127.0.0.1 <- NewMessages: 0
    127.0.0.1 <- OldMessages: 0
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: Status

    127.0.0.1 -> Action: QueueStatus

    127.0.0.1 -> Action: SipPeers

    127.0.0.1 -> Action: Agents

    127.0.0.1 -> Action: Command
    127.0.0.1 -> Command: meetme list 9000 concise
    127.0.0.1 -> ActionID: meetme_9000

    127.0.0.1 -> Action: Command
    127.0.0.1 -> Command: database show fop2state
    127.0.0.1 -> ActionID: fop2state

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Channel status will follow
    127.0.0.1 <- Server: 0

    Response: Success
    Message: Channel status will follow
    Server: 0

    127.0.0.1 <- Event: StatusComplete
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Queue status will follow
    127.0.0.1 <- Server: 0

    Response: Success
    Message: Queue status will follow
    Server: 0

    127.0.0.1 <- Event: QueueStatusComplete
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Peer status list will follow
    127.0.0.1 <- Server: 0

    Response: Success
    Message: Peer status list will follow
    Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 108
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: -none-
    127.0.0.1 <- IPport: 0
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: UNKNOWN
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 106
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: -none-
    127.0.0.1 <- IPport: 0
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: UNKNOWN
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 105
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: 192.168.10.15
    127.0.0.1 <- IPport: 5060
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: OK (14 ms)
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 104
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: -none-
    127.0.0.1 <- IPport: 0
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: UNKNOWN
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 103
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: 192.168.10.30
    127.0.0.1 <- IPport: 5061
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: OK (7 ms)
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 102
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: 192.168.10.10
    127.0.0.1 <- IPport: 5062
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: OK (30 ms)
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerEntry
    127.0.0.1 <- Channeltype: SIP
    127.0.0.1 <- ObjectName: 101
    127.0.0.1 <- ChanObjectType: peer
    127.0.0.1 <- IPaddress: 192.168.10.10
    127.0.0.1 <- IPport: 5060
    127.0.0.1 <- Dynamic: yes
    127.0.0.1 <- Natsupport: no
    127.0.0.1 <- VideoSupport: yes
    127.0.0.1 <- ACL: no
    127.0.0.1 <- Status: OK (29 ms)
    127.0.0.1 <- RealtimeDevice: no
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Event: PeerlistComplete
    127.0.0.1 <- ListItems: 7
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Agents will follow
    127.0.0.1 <- Server: 0

    Response: Success
    Message: Agents will follow
    Server: 0

    127.0.0.1 <- Event: AgentsComplete
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Response: Follows
    127.0.0.1 <- Privilege: Command
    127.0.0.1 <- ActionID: meetme_9000
    127.0.0.1 <- --END COMMAND--
    127.0.0.1 <- Server: 0

    127.0.0.1 <- Response: Follows
    127.0.0.1 <- Privilege: Command
    127.0.0.1 <- ActionID: fop2state
    127.0.0.1 <- --END COMMAND--
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: MEETME-REFRESH
    127.0.0.1 -> Meetme:

    127.0.0.1 <- Event: UserEvent
    127.0.0.1 <- Privilege: user,all
    127.0.0.1 <- UserEvent: MEETME-REFRESH
    127.0.0.1 <- Action: UserEvent
    127.0.0.1 <- Meetme:
    127.0.0.1 <- Server: 0

    asterisk cli

    manager show connected
    Username IP Address
    ragm 127.0.0.1
    ragm 127.0.0.1
  • nicolasnicolas
    You do not need to verify that you have the manager user connected, because you have problems with your client connections: Those will show as events in the output from fop2_server -X 15 with "=>" and "<=". So, try to telnet FROM your browser machine to the fop2 server and see if you spot the connection. Then try the same with your browser. And be sure you have a proper user defined in fop2.cfg and a proper buttonfile too.

    Best regards,
  • tommy_fctommy_fc
    I am having the exact same issue, except on Ubuntu 8.04

    It works in our testing environment, but not in production. There are two main differences: The test environment runs a free version while the prod is registered. The production environment is also fire-walled.

    Do I understand you correctly when you say that the browser has to have access to the fop2 service itself. That the event traffic does not go through apache?
  • nicolasnicolas
    Yes, you understood correctly. FOP and FOP2 use a flash feature called xmlsockets: it uses a direct connection between the browser (the flash plugin) and the server (fop daemon). It uses port tcp 4445 by default. If your production machine is firewalled, you will need to redirect that port, or connect via VPN.

    HTML5 specification includes that feature too. So I asume in the future flash won't be needed anymore, but a direct connection to a special purpose server will still be required.

    Best regards,
  • tommy_fctommy_fc
    Interesting reading. Thank you very much for the quick, precise and informative post.
Sign In or Register to comment.

© Asternic Corp 2024