Gatling 2.3 websocket reconnect

We re getting status code 1013 from the websocket server which means-

/// Indicates that the service is experiencing overload. A client should
/// only connect to a different IP (when there are multiple for the target)
/// or reconnect to the same IP upon user action.
static value const try_again_later = 1013;

This status code,it seems,though not sure,was added later in the RFC.
So our websocket is closing with invalid Status code 1013

io.netty.handler.codec.CorruptedFrameException: Invalid close frame getStatus code: 1013
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.protocolViolation(
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.checkCloseFrameBody(
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.decode(
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(

Is there a way we can modify the framework to accept this as accepted status code?

Please note that we are using gatling 2.3.1…
We didn’t move to gatling 3.0.0 because ping/pong was not happening.

Thanks in advance.