RejectCall action btnValue alternates between true/false

[deklandialpad]

Noticed that the RejectCall btnValue that's triggered from the headset seems to alternate between true/false? Does the device need to be set to a specific state to get it to consistently return RejectCall with btnValue true? Or does the btnValue for this action not matter?

In the flow diagram for rejecting calls, I also noticed that 'RejectCall' enumType isn't being used, so wondering if this is not the recommended way to reject a call?

Use case/steps to reproduce:
Headset Jabra Engage 50

Incoming call -> set device to ringing -> device rejects call, sends RejectCall with btnValue=True to app -> app ends call -> device stops ringing

Second incoming call -> set device to ringing -> device rejects call, this time sends with RejectCall btnValue = False

[jabra-slawaetz]

Thanks for pointing this out.
We have created corresping ticket on the Developer Zone to manage the case.
But we can already now say that you are right, the diagram is wrong, pressing the Reject Call button on the headset does not fire an offhook event, but rather a RejectCall event.