FOP2 Community Forum

AMI events for SIp peer status do not include the useragent. Without that is not possible to add the feature. 127.0.0.1 <- Event: PeerEntry 127.0.0.1 <- Channeltype: SIP 127.0.0.1 <- ObjectName: 333 127.0.0.1 <- ChanObjectType: peer 127.0.0.1 <- IPaddress: 192.168.1.6 127.0.0.1 <- IPport: 51733 127.0.0.1 <- Dynamic: yes 127.0.0.1 <- AutoForcerport: no 127.0.0.1 <- Forcerport: yes 127.0.0.1 <- AutoComedia: no 127.0.0.1 <- Comedia: yes 127.0.0.1 <- VideoSupport: yes 127.0.0.1 <- TextSupport: no 127.0.0.1 <- ACL: yes 127.0.0.1 <- Status: OK (207 ms) 127.0.0.1 <- RealtimeDevice: no 127.0.0.1 <- Description:

Start fop2_server in debug mode and look at the actual connection between the fop2 server and all of your manager_hosts: service fop2 stop cd /usr/local/fop2 script capture.log ./fop2_server -X 3 After things settle down, stop capturing: ctrl-C exit service fop2 start You will have a capture.log file to review, with the actual connection and authorization attempts and their replies.