eeremin

Probably related to https://bugs.chromium.org/p/webrtc/issues/detail?id=15764 Try to reproduce it in Chrome Canary and see if issue is still there

Tested with patch below (set `response` to `null`, added `cause`) and it seems to work - no session termination after timeout, didn't notice other issues. ```diff diff --git a/lib/RTCSession/Info.js b/lib/RTCSession/Info.js...

I noticed that it will be not possible to handle this timeout on the consumer side. Maybe its worth to add some `onTimeout` to the `options` parameter of `RTCSession::sendInfo` method

> Can you please be specific here? When i, as a user of the jssip library, will use `session.sendInfo` method then it will be not possible for me to know...