mc_: Is it confirmed that 5.1 will use Rocky linux? If so, will it be 8 or 9?

mentax: we're wrapping up work on 8 and 9 (with 8 just being for the in-place upgrade from centos7)

the discussion atm is how far back to go with rocky9 support

there are lots of changes (esp openssl v3) that aren't compatible with erlang 23, and upgrading to 24+ means some of our dep libraries would need updating to be compilable

interesting

so at the moment, 5.3+ will expect to run rocky9, previous versions will likely run rocky8 but we'll see what the powers that be decide

we may manage an openssl compat lib for 1.1.1 and rocky9 too

lots being discussed

hopeffully it will not take another 10 years to test it :-D

mc_: ETA for v5 still not in place?

it continues to be a goal for kazoocon, so end of october

i haven't heard differently

Is there a way to manually set the presence for an extension via crossbar API ? This extension is just in a callflow and not assigned to any user. It is set to run a pivot flow which sets the manual presence correctly there. I would like to see if this can be done via a crossbar api post.

i think just reset: docs.2600hz.com/dev/applications/cr…/doc/presence/#reset-presence-state

but maybe the POST with action=set would work for the extension?

Since the presence_id is not assigned to a device (it is a pivot that updates time conditions and turns on the light when night mode is on)

I tried doing a post to /v2/accounts/{ACCOUNT_ID}/presence/{EXTENSION} and in the data body I put {"data":{"action":"set","state": "busy"}} . I get a 200/OK regardless of what I put as the state. And I get "data": "reset command sent for extension ${PRESENCE_ID}"

am checking to see if the set is obeyed.

@mc_ That command just resets the BLF back to idle.

you do have the "manual_presence" callflow action but doesn't appear the API supports it for any presence_id

could you create a "hidden" device with the presence_id you want to modify? :)

i'll give that a shot. But this would be a useful feature to add for crossbar :)

since it would mirror the callflow object

definitely

presence states for the device would be idle, busy and ringing right ?

sounds right

I get a "Field must be set to a valid state" error response

check the schema, probably an enum with valid states

"early",

"confirmed",

"terminated"

they don't seem to change the blf, just to confirm, if I am setting up a device without a user and set the callflow as first to device, then to pivot or first to pivot then to device ?

It works if I use the user presence endpoint to update

i don't think you need the device in the callflow, just presence_id = pivot callflow ext

that does not seem to work. it works with the user_id but not the presence_id

so to fix, i am going to pull the user with the presence id and then issue the presence update to the user presence endpoint. Which should fix my immediate issue. I'll see if I can add the set feature for the presence_id endpoint to update the blf