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
SDK Version
Which version of the SDK have you added from pub.dev? Feel free to add the whole dependency implementation:
eg. telnyx_webrtc: ^0.0.16
Describe the bug
Our Flutter application, which uses the Telnyx WebRTC SDK, encounters an issue where the app retries making a call multiple times when the receiving user cuts the call without picking it up. This behavior is unintended and seems to occur because the app does not correctly handle the call state when the call is rejected or canceled by the receiver.
Expected behaviour
The app should recognize that the call was canceled or rejected by the receiving user and should not retry the call.
Potential Cause:
This might be due to incorrect handling of the call state (e.g., interpreting a rejected or canceled state as an opportunity to retry the call).
Suggestions:
Ensure that the app correctly handles all call states (e.g., ringing, busy, canceled, rejected).
Implement state management logic to prevent the app from retrying a call if it was intentionally cut by the receiver.
Logs
Logs show normal call initiation, but no logging occurs when the retry logic is triggered.
The text was updated successfully, but these errors were encountered:
TestDevloper1
changed the title
[Bug] Short Bug Description
Call Retries Multiple Times After Receiver Cuts Call Without Answering
Aug 13, 2024
TestDevloper1
changed the title
Call Retries Multiple Times After Receiver Cuts Call Without Answering
Call retries multiple times after receiver cuts call without answering
Aug 13, 2024
Bug Category
SDK Version
Which version of the SDK have you added from pub.dev? Feel free to add the whole dependency implementation:
eg. telnyx_webrtc: ^0.0.16
Describe the bug
Our Flutter application, which uses the Telnyx WebRTC SDK, encounters an issue where the app retries making a call multiple times when the receiving user cuts the call without picking it up. This behavior is unintended and seems to occur because the app does not correctly handle the call state when the call is rejected or canceled by the receiver.
Expected behaviour
The app should recognize that the call was canceled or rejected by the receiving user and should not retry the call.
Potential Cause:
This might be due to incorrect handling of the call state (e.g., interpreting a rejected or canceled state as an opportunity to retry the call).
Suggestions:
Logs
Logs show normal call initiation, but no logging occurs when the retry logic is triggered.
The text was updated successfully, but these errors were encountered: