The configuration was already as you indicated:
There was a manager user specifically for FOP2 with following configuration:
[fop2]
secret = **********
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = all
write = all
writetimeout = 1000
eventfilter=!Event: RTCPSent
eventfilter=!Event: RTCPReceived
eventfilter=!Event: VarSet
eventfilter=!Event: Cdr
eventfilter=!Event: ExtensionStatus
eventfilter=!Event: ChannelUpdate
All SIP peers have qualify=yes defined.
We are in production and it worked alright until installing newer Asterisk version. I don't espect to get the solution to the problem here. However, I woul like to know which can be the causes of having all extension buttons showing as available at start. Is there more than one option? Is my reason logic ok? (At FOP2 start, fop2 manager user "asks" for peers' status and it shows them as it gets it. I think Asterisk might be sending that they are available, although it's strange. Where does Asterisk get this information from?..astdb?
Regards,
Borja