The resulting output:
root@asterisk1:~# wget http://download3.fop2.com/fop2-2.27-debian-x86_64.tgz
--2014-01-30 13:14:00-- http://download3.fop2.com/fop2-2.27-debian-x86_64.tgz
Resolving download3.fop2.com (download3.fop2.com)... 69.85.88.167
Connecting to download3.fop2.com (download3.fop2.com)|69.85.88.167|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8566172 (8.2M) [application/octet-stream]
Saving to: `fop2-2.27-debian-x86_64.tgz'
100%[===================================================================>] 8,566,172 1.92M/s in 5.1s
2014-01-30 13:14:05 (1.61 MB/s) - `fop2-2.27-debian-x86_64.tgz' saved [8566172/8566172]
root@asterisk1:~# tar -xvzf fop2-2.27-debian-x86_64.tgz
[..]
fop2/server/fop2_server
root@asterisk1:~# cp fop2/server/fop2_server /usr/local/fop2/fop2_server
root@asterisk1:~# /usr/local/fop2/fop2_server -X 3
Flash Operator Panel 2 - License file fop2.lic not found.
** SSL Certificate File cannot be read (/etc/pki/tls/certs/localhost.crt). Disabling TLS.
** SSL Certificate Private Key File cannot be read (/etc/pki/tls/private/localhost.key). Disabling TLS.
127.0.0.1 -> AuthType: md5
127.0.0.1 -> Action: Challenge
127.0.0.1 -> ActionID: 1
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 1
127.0.0.1 <- Challenge: 518046693
127.0.0.1 -> AuthType: md5
127.0.0.1 -> Events: on
127.0.0.1 -> Username: admin
127.0.0.1 -> Action: login
127.0.0.1 -> Key: [*Redacted*]
127.0.0.1 -> ActionID: 2
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 2
127.0.0.1 <- Message: Authentication accepted
127.0.0.1 -> Action: Status
127.0.0.1 -> Action: QueueStatus
127.0.0.1 -> Action: Agents
127.0.0.1 -> Action: SipPeers
127.0.0.1 -> Action: IaxPeers
127.0.0.1 -> Action: ParkedCalls
127.0.0.1 -> Command: database show fop2notes
127.0.0.1 -> Action: Command
127.0.0.1 -> ActionID: 3
127.0.0.1 -> Command: database show fop2state
127.0.0.1 -> Action: Command
127.0.0.1 -> ActionID: 4
127.0.0.1 -> Action: CoreSettings
127.0.0.1 -> ActionID: 5
127.0.0.1 <- Event: FullyBooted
127.0.0.1 <- Privilege: system,all
127.0.0.1 <- Status: Fully Booted
127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Channel status will follow
127.0.0.1 <- Event: StatusComplete
127.0.0.1 <- Items: 0
127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Queue status will follow
127.0.0.1 <- Event: QueueStatusComplete
127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Agents will follow
127.0.0.1 <- Event: AgentsComplete
127.0.0.1 <- Response: Success
127.0.0.1 <- EventList: start
127.0.0.1 <- Message: Peer status list will follow
127.0.0.1 <- Event: PeerlistComplete
127.0.0.1 <- EventList: Complete
127.0.0.1 <- ListItems: 0
127.0.0.1 <- Response: Success
127.0.0.1 <- EventList: start
127.0.0.1 <- Message: Peer status list will follow
127.0.0.1 <- Event: PeerEntry
127.0.0.1 <- Channeltype: IAX2
127.0.0.1 <- ObjectName: demo/asterisk
127.0.0.1 <- ChanObjectType: peer
127.0.0.1 <- IPaddress: [*Redacted*]
127.0.0.1 <- IPport: [*Redacted*]
127.0.0.1 <- Dynamic: no
127.0.0.1 <- Trunk: no
127.0.0.1 <- Encryption: no
127.0.0.1 <- Status: Unmonitored
127.0.0.1 <- Description: Demo System At Digium
127.0.0.1 <- Event: PeerlistComplete
127.0.0.1 <- EventList: Complete
127.0.0.1 <- ListItems: 1
127.0.0.1 <- Response: Success
127.0.0.1 <- Message: Parked calls will follow
127.0.0.1 <- Event: ParkedCallsComplete
127.0.0.1 <- Total: 0
127.0.0.1 <- Response: Follows
127.0.0.1 <- Privilege: Command
127.0.0.1 <- ActionID: 3
127.0.0.1 <- 0 results found.
--END COMMAND--
127.0.0.1 <- Response: Follows
127.0.0.1 <- Privilege: Command
127.0.0.1 <- ActionID: 4
127.0.0.1 <- 0 results found.
--END COMMAND--
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 5
127.0.0.1 <- AMIversion: 2.0.0
127.0.0.1 <- AsteriskVersion: 12.0.0
127.0.0.1 <- SystemName:
127.0.0.1 <- CoreMaxCalls: 0
127.0.0.1 <- CoreMaxLoadAvg: 0.000000
127.0.0.1 <- CoreRunUser:
127.0.0.1 <- CoreRunGroup:
127.0.0.1 <- CoreMaxFilehandles: 0
127.0.0.1 <- CoreRealTimeEnabled: No
127.0.0.1 <- CoreCDRenabled: Yes
127.0.0.1 <- CoreHTTPenabled: No
This seems to be succesful.
When running as server daemon I get prompted the Login details now. It seems that the problem is solved!
Just out of curiousity, was the problem the response header?
Thank you for this, we can now proceed with implementation tests 