-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update incomingCall.ts #186
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Stir shaken fix
Cdsk 1163 jwt token integration
prevent incoming and outgoing call if permission not granted
- Enhanced Heartbeat timer for improved network monitoring. - The reason for disconnection/connection is published with the onConnectionChange event. - Streamlined the gathering of local media stream during the ringing state for incoming calls. - Introduced helper methods (isRegistered, isConnecting, and isConnected) for checking the client connection status. - Implemented automatic restart of heartbeat service when the browser fails to reconnect the socket.
- Enhanced CallInfo Object by removing remoteCancelReasonand introducing granular attributes: Reason, Protocol, ErrorCode, and Originator. - Removed Google STUN and implemented Plivo STUN Servers to improve reliability. This change is now configurable via the 'usePlivoStunServer' flag. - Resolved type error issue causing "getHeader is not a function". - Improved call management: Calls will now disconnect automatically in the event of a network switch while in the Ringing state.
* Implemented new local hangup reasons to provide additional insights into the cause of call hangups. * Graceful disconnection of the websocket before emitting `onLoginFailed`. * Resolved a type error issue resulting in: "Cannot assign to read-only property 'uri' of object". * Preventing the establishment of a new websocket connection if there is an ongoing connection.
Resolved a issue where the `onLoginFailed` event was not emitted when encountering registration failure.
…results when emitting the 'onLoginFailed' event
- Resolved an issue where noise reduction failed to initiate as anticipated due to necessitating a user gesture. - A new event named `onNoiseReductionReady` has been introduced, which is triggered when the noise reduction is prepared to commence.
- Implemented webRTC logging service for monitoring calls.
1. Enhanced WebSocket connection optimization and refined fallback mechanisms to minimize delays in establishing a connection. 2. Streamlined the process for reconnecting active calls during network changes for improved stability and reliability.
* Improved error handling by emitting "LoginFailed" event upon unsuccessful creation of User Agent (UA). * Implemented a check to prevent sending DTMF signals when there is no internet connection.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.