It seems like with each call, new audioContext instance is created, and since every single one of them is active, red tab indicator never disappears even when you hand up the call. Also seems like with each call even more memore has been used. I guess need to rethink how to use one instance and handle hand-up when yo have more than one active call, also on some other events such as: ended, failed.
It's recommended to create one AudioContext and reuse it instead of initializing a new one each time,
and it's OK to use a single AudioContext for several different audio sources and pipeline concurrently.
Also there is small mistake in the readme file:
Should be getSipOptions
Hello there,
It seems like with each call, new audioContext instance is created, and since every single one of them is active, red tab indicator never disappears even when you hand up the call. Also seems like with each call even more memore has been used. I guess need to rethink how to use one instance and handle hand-up when yo have more than one active call, also on some other events such as: ended, failed.
You can take a look at DevTools WebAudio:
Any improvements and optimizations on that? :)
https://developer.mozilla.org/en-US/docs/Web/API/AudioContext
Also there is small mistake in the readme file: Should be getSipOptions
By the way, thanks for this wrapper! :)