I agree, Nicolas. Thank you for pointing in the right direction :-)

Unfortunately that did not work. I checked the available states with the CLI command "devstate change", and I found the states:

*CLI> devstate change
Usage: devstate change <device> <state>
       Change a custom device to a new state.
       The possible values for the state are:
UNKNOWN | NOT_INUSE | INUSE | BUSY | INVALID | UNAVAILABLE | RINGING
RINGINUSE | ONHOLD

I tried setting both "UNAVAILABLE" and "INVALID" in the Perl script and restarted FOP2 each time, to no avail.
I did check that the devstate was set correctly with the CLI command "devstate list", and it was.

Do you have any other suggestions for this? How does Asterisk determine the device's state?

Thank you, that did the trick! :-)

Is it possible to change the custom devstate that is set when using different Presences?
It seems like no matter what is selected the devstate is "BUSY" (and by that the voicemail message say that the user is on the phone, "vm-isonphone"), but I would prefer to put the devstate in "NOT_AVAILABLE" mode (and getting the voicemail to respond with the "vm-isunavail" message.

Hi!

We are running the following setup:
Asterisk 1.6.1.19
Fop2 v2.29.01
FreePBX 2.9.0.15

We recently upgraded FOP2 from v2.11 to v2.29 (as you might recall from our chat earlier).

For some reason, the Asterisk system has stopped reacting to Agents Presence status in FOP2. Earlier when a Presence was set an incoming call would be redirected to the users VM, and the caller would get a message about it.
The Asterisk CLI command "database show fop2state" shows that the users presence is set.

*CLI> database show fop2state
/fop2state/USER/652                               : Do not Disturb           
1 results found.

I can also see using fop2_server in debug mode that events are created:

x.x.x.x:65255  <= <msg data="5|setastdb|fop2state~652~RG8gbm90IERpc3R1cmI=|e5fee7f31b09970432e88bad2913663d" ></msg>

127.0.0.1            <- Response: Follows
127.0.0.1            <- Privilege: Command
127.0.0.1            <- Updated database successfully
--END COMMAND--

127.0.0.1            <- Response: Success
127.0.0.1            <- Message: Event Sent

127.0.0.1            <- Event: UserEvent
127.0.0.1            <- Privilege: user,all
127.0.0.1            <- UserEvent: FOP2ASTDB
127.0.0.1            <- Action: UserEvent
127.0.0.1            <- Family: fop2state
127.0.0.1            <- Key: USER/652
127.0.0.1            <- Channel: USER/652
127.0.0.1            <- Value: Do not Disturb

This leads to my questions:

1. What could cause this to not work anymore (it did work after the upgrade, but has stopped working for some reason)?
2. How does Asterisk know if the user is available or not?
3. Is it possible to change where the call is directed based on what Presence is used (ie. if a user is "On Vacation" could FOP2 redirect the call to the switchboard, instead of the VM)?

Best Regards,