You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, esteemed Creator! Regarding the use of the 'janus.plugin.sip' plugin in janus.js, when the browser's memory allocation is insufficient or the browser is running in the background, the current page may freeze, causing the keepalive messages to gradually slow down and eventually stop sending. However, the SIP status remains registered.
I would like to ask if it is appropriate to use document.addEventListener('visibilitychange') to monitor visibility changes and proactively send a keepalive message, or if you have any better solutions.
The text was updated successfully, but these errors were encountered:
I found the issue: it's because I have two media servers. Media server A notifies me of an incoming call, but when I call "answer," the request is sent to media server B. I don't know why the receiving and sending media servers are different. I'm using WebSocket, and it should only connect to one media server, right? This is really troubling me. Could you please share any ideas or suggestions to help me with this?
Hello, esteemed Creator! Regarding the use of the 'janus.plugin.sip' plugin in janus.js, when the browser's memory allocation is insufficient or the browser is running in the background, the current page may freeze, causing the keepalive messages to gradually slow down and eventually stop sending. However, the SIP status remains registered.
I would like to ask if it is appropriate to use document.addEventListener('visibilitychange') to monitor visibility changes and proactively send a keepalive message, or if you have any better solutions.
The text was updated successfully, but these errors were encountered: