Skip to content
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

"Direction" Property is missing for calls in the "new" and "ringing" Call State #316

Open
tedg opened this issue Jun 21, 2023 · 0 comments

Comments

@tedg
Copy link

tedg commented Jun 21, 2023

Hello, when I receive inbound calls and want to check the direction, the property is totally absent. It does appear for outbound calls.

EDIT: After testing a bit more, direction does show up for inbound calls but only after the new and ringing call events have passed, and the call state has transitioned to active. This is a bit inconsistent and it would be good to always have direction present. There is nothing about this quirk in the documentation.

For outbound calls, direction is also absent for calls in the new state.

The issue with this is it hurts our ability to lower render latency in our app by updating our UI instantly upon creation of a new call. Instead we must wait until the call is out of the new state.

@tedg tedg changed the title "Direction" Property is missing for Inbound Calls "Direction" Property is missing for Inbound Calls in the "new" Call State Jun 22, 2023
@tedg tedg changed the title "Direction" Property is missing for Inbound Calls in the "new" Call State "Direction" Property is missing for calls in the "new" and "ringing" Call State Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant