User can logout of the embeddable while on a call ... it gets strange

Steps to reproduce:

• start a call via the embeddable
• logout of the embeddable
• you're still on the call, you can still hear the people on the other end, the embedable shows you're on a current call but the API can't interact with it (e.g. our own 'hangup button' can't work without a session etc).

What is the expected behaviour if you logout in the middle of a call? Should it drop the call, but the call on hold, or just keep

Embeddable throws errors like

logger.ts:11 [ERROR] WEBPHONE Fail to disconnect call session msyns709aharcpo

[RingCentral] Cannot perform action: User is not logged into RingCentral

If the other end does disconnect, when you next logback in you're "stuck" and in the console we see

[DialerUI] make call error Error: rc-widget-webphone-channel-v2-timeout
at MultipleTabsTransport.js:95:44

with zero information in the dialer itself. It shows no indication that the call is not proceeding or not working it just appears not to work at all which might be a separate issues to have that error show up in the UI

Also: Version 3.0.0-beta

Reproduce the logout-during-call flow in the embeddable, then inspect logger.ts, MultipleTabsTransport.js, and the DialerUI call path mentioned in the report. The expected logout behavior still needs a decision; done should include consistent call/session handling and a visible indication when a subsequent call fails.