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

customParams field in Active Call is null on Answer event. #232

Open
agent515 opened this issue May 8, 2024 · 0 comments · May be fixed by #233
Open

customParams field in Active Call is null on Answer event. #232

agent515 opened this issue May 8, 2024 · 0 comments · May be fixed by #233

Comments

@agent515
Copy link
Contributor

agent515 commented May 8, 2024

Issue Summary

Active Call has a field customParams which contains extraOptions passed during a Twilio Call. If it's passed, customParams has a non-null value on Ringing event which is correct. But it is null on Answer event.

Steps to Reproduce

  1. Receive a Twilio Call with non-null customParams
  2. Answer the call
  3. Get Active Call by calling TwilioVoice.instance.call.activeCall and check customParams value.

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

I expect to get a similar customParams value of Active on both Ringing and Answer events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant