15:05:38 <mentax> mc_: Is it confirmed that 5.1 will use Rocky linux? If so, will it be 8 or 9?
15:28:24 <mc_> mentax: we're wrapping up work on  8 and 9 (with 8 just being for the in-place upgrade from centos7)
15:28:39 <mc_> the discussion atm is how far back to go with rocky9 support 
15:29:22 <mc_> 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
15:30:03 <mentax> interesting
15:30:03 <mc_> 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
15:30:38 <mc_> we may manage an openssl compat lib for 1.1.1 and rocky9 too
15:30:42 <mc_> lots being discussed
15:31:08 <mentax> hopeffully it will not take another 10 years to test it :-D
15:33:34 <mentax> mc_: ETA for v5 still not in place?
15:35:46 <mc_> it continues to be a goal for kazoocon, so end of october
15:35:51 <mc_> i haven't heard differently
16:12:20 <pramsky> 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.
16:24:24 <mc_> i think just reset: https://docs.2600hz.com/dev/applications/crossbar/doc/presence/#reset-presence-state
16:24:37 <mc_> but maybe the POST with action=set would work for the extension?
16:39:52 <pramsky> 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)
16:41:47 <pramsky> 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}" 
16:41:59 <pramsky> am checking to see if the set is obeyed.
18:00:18 <pramsky> @mc_ That command just resets the BLF back to idle. 
18:01:43 <mc_> you do have the "manual_presence" callflow action but doesn't appear the API supports it for any presence_id
18:01:59 <mc_> could you create a "hidden" device with the presence_id you want to modify? :)
18:02:42 <pramsky> i'll give that a shot. But this would be a useful feature to add for crossbar :) 
18:02:51 <pramsky> since it would mirror the callflow object
18:03:13 <mc_> definitely
18:09:40 <pramsky> presence states for the device would be idle, busy and ringing right ?
18:10:30 <mc_> sounds right
18:11:46 <pramsky> I get a "Field must be set to a valid state" error response
18:12:24 <mc_> check the schema, probably an enum with valid states
18:12:43 <mc_>                 "early",
18:12:43 <mc_>                 "confirmed",
18:12:43 <mc_>                 "terminated"
18:15:25 <pramsky> 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 ?
18:20:19 <pramsky> It works if I use the user presence endpoint to update
18:22:16 <mc_> i don't think you need the device in the callflow, just presence_id = pivot callflow ext
18:49:16 <pramsky> that does not seem to work. it works with the user_id but not the presence_id
19:10:18 <pramsky> 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