Failed ws DCP

[ManhPham18]

I am using setDisconnectCancelAllWindowV2, but the documentation states:
"Your private websocket connection must subscribe to the 'dcp' topic in order to trigger DCP successfully."
However, when I subscribe using:
wsOrder.subscribeV5("dcp.future",'linear')
wsOrder.subscribeV5("dcp.spot",'spot')
or
wsOrder.subscribeV5(["dcp.future","dcp.spot"])
it fails every time, returning errors such as:
success: false,
ret_msg: 'error:handler not found,topic:dcp.future',
conn_id: 'd9jhogatbetvf6evjmc0-8eoj',
req_id: 'dcp.future',
op: 'subscribe',
wsKey: 'v5LinearPublic',
isWSAPIResponse: false or Error: Category cannot be undefined.
Could you please explain this and review the library?

[tiagosiebler]

Has your client manager enabled the DCP feature on your account? This feature is reserved for institutional clients and has to be enabled by your client manager on Bybit's side.

[tiagosiebler]

That being said it also doesn't look correct to send the DCP subscribe to the public web socket connection. Let me double check that...

[tiagosiebler]

Pushed a fix that will release shortly with v4.7.2, so that DCP topics are correctly routed to the private/authenticated WebSocket connection. Via #562

[tiagosiebler]

Released, the WS topic should correctly route to the private websocket now.