Writing here for future users running into issues, here is a correct button configuration for Yeastar S Series, that you must add in buttons_custom.cfg
[PJSIP/10001]
type=extension
extension=10001
context=DLPN_DialPlan10001
label=RECEPTIONIST 1
mailbox=10001@default
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
[PJSIP/10002]
type=extension
extension=10002
context=DLPN_DialPlan10002
label=John Doe
mailbox=10002@default
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
Also a reminder on FOP2 usage: to perform actions, you must log with a user (defined in the users section in the FOP2 Manager) that has a button visible with the same extension=x header in its config. Taking the above example, you can create users 10001 and 10002 and log as any of them. Then you will be able to perform actions from their respective device.
In this case, button config was incorrect, user attempted to log with user "100" and there was no device with such extensions, but it did have a queue configured with extension=100.. So action buttons appearead, but actions did not work, as it was not logged as a valid user.
In the next release I will add a script that will be available for now in the config_generatos directory that will connect to the yeastar box and generate the proper buttons_custom.cfg file in one swoop.
Best regards,
