FOP2 debug help. Can't connect to server

  1. 12 years ago

    I have a FreePBX 2.9 system and installed FOP2. When I try to log in I get the message connecting to server. After many attempts I get a message that the server is not available.

    I have disables iptables and still the same problem.

    Here are some debug logs.

    ** DIGEST_EVENT: start

    • * PROCESA_BLOQUE 0
    • * PROCESA_BLOQUE MESSAGEWAITING 0

    It's blessed into class Extension

    DIGEST canal SIP/501, comando voicemail, datos 0, slot

    DIGEST canal SIP/501, comando voicemailcount, datos &vmail_count!0!0, slot

    • * MAIN New client connection 192.168.250.77
    • * MAIN New client connection 192.168.250.77

    ** MAIN AMI event received...

    HTML5 Web Socket Connection

    websocket handshake version hiby v8

    HTTP/1.1 101 Switching Protocols
    Upgrade: WebSocket
    Connection: Upgrade
    Sec-WebSocket-Accept: UJ3Mzq/G3BJMXwV1dugyNWyLsyQ=

    192.168.250.77 => HTTP/1.1 101 Switching Protocols
    Upgrade: WebSocket
    Connection: Upgrade
    Sec-WebSocket-Accept: UJ3Mzq/G3BJMXwV1dugyNWyLsyQ=

    • * MAIN AMI event received...
    • * MAIN Processing command received from flash clients...

    192.168.250.77 <= <msg data="GENERAL|contexto|1|" />

    -- PROCESS_FLASH_COMMAND origen GENERAL accion contexto destino 1 password

    192.168.250.77 => { "btn": "0", "cmd": "key", "data": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "slot": "" }

    192.168.250.77 => { "btn": "0@GENERAL", "cmd": "version", "data": "2.26!XXXXXXXXXXXXXXXXXXl, IL!1", "slot": "" }

    ** MAIN New client connection 127.0.0.1

    • * MAIN AMI event received...
    • * MAIN Processing command received from flash clients...

    127.0.0.1 <= <msg data="GENERAL|contexto|1" />

    -- PROCESS_FLASH_COMMAND origen GENERAL accion contexto destino 1 password

    127.0.0.1 => { "btn": "0", "cmd": "key", "data": "XXXXXXXXXXXXXXXXXXXXh", "slot": "" }

    127.0.0.1 => { "btn": "0@GENERAL", "cmd": "version", "data": "2.26!XXXXXXXXXXXXXXXXXXXXXXXXL!1", "slot": "" }

    • * MAIN AMI event received...
    • * MAIN Processing command received from flash clients...

    127.0.0.1 <= <msg data="GENERAL|checkauth|301|3cd6b224aae4a683d2ced1942e813762" />

    -- PROCESS_FLASH_COMMAND origen GENERAL accion checkauth destino 301 password 3cd6b224aae4a683d2ced1942e813762

    • * CLEAN SOCKET connection lost removing socket IO::Socket::INET=GLOB(0x111d5c54)
    • * CLEAN SOCKET flash client connection lost

    Flash clients connected: 2
    ---------------------------------------------------
    192.168.250.77:62837 IO::Socket::INET=GLOB(0x1114ec18), none
    192.168.250.77:62838 IO::Socket::INET=GLOB(0xeaccd80), none
    ---------------------------------------------------

    ** MAIN closing 192.168.250.77

    • * CLEAN SOCKET connection lost removing socket IO::Socket::INET=GLOB(0x1114ec18)
    • * CLEAN SOCKET flash client connection lost

    Flash clients connected: 1
    ---------------------------------------------------
    192.168.250.77:62838 IO::Socket::INET=GLOB(0xeaccd80), none
    ---------------------------------------------------

    ** MAIN End of block from localhost

    127.0.0.1 <- Event: PeerStatus
    127.0.0.1 <- Privilege: system,all
    127.0.0.1 <- ChannelType: SIP
    127.0.0.1 <- Peer: SIP/800
    127.0.0.1 <- PeerStatus: Registered
    127.0.0.1 <- Address: 10.253.181.59:5060
    127.0.0.1 <- Server: 0

    • * MAIN AMI event received...
    • * MAIN There's an 'Event' in the event block
    • * MAIN Event detected block_count = 1 (Event: PeerStatus)
    • * MAIN There are 1 blocks for processing
    • * MAIN Answer block cleared

    ** DIGEST_EVENT: start

    • * PROCESA_BLOQUE 0
    • * PROCESA_BLOQUE PEERSTATUS 0

    SET QUALIFY para SIP/800 lo dejo como estaba ok

    ** MAIN End of block from localhost

    127.0.0.1 <- Event: PeerStatus
    127.0.0.1 <- Privilege: system,all
    127.0.0.1 <- ChannelType: SIP
    127.0.0.1 <- Peer: SIP/8009
    127.0.0.1 <- PeerStatus: Registered
    127.0.0.1 <- Address: 10.253.181.59:5060
    127.0.0.1 <- Server: 0

    • * MAIN AMI event received...
    • * MAIN There's an 'Event' in the event block
    • * MAIN Event detected block_count = 1 (Event: PeerStatus)
    • * MAIN There are 1 blocks for processing
    • * MAIN Answer block cleared

    ** DIGEST_EVENT: start

    • * PROCESA_BLOQUE 0
    • * PROCESA_BLOQUE PEERSTATUS 0

    SET QUALIFY para SIP/8009 lo dejo como estaba ok

    Exiting...

  2. admin

    7 Sep 2012 Administrator

    Hi,

    The registration name has an invalid character, please run:

    /usr/local/fop2/fop2_server --reactivate

    Then restart fop2

    service fop2 restart

    And try again..

    Best regards,

  3. That worked. Thank you.

or Sign Up to reply!