fix(calling): removed-events-dependency-on-call-buttons

[Shreyas281299]

COMPLETES

This pull request addresses

In the calling samples page, if we don't receive the CALL_ESTABLISHED event the samples page gets stuck. The 'end-call' button remains disabled.

by making the following changes

We have removed the dependency of any event on the button state. As soon as we make the call 'end-call' button is enabled and we can cut the call.
Also
The advanced settings or region and country take effect when the calling.init() button is pressed. But the button is located above the Advanced section. So a user will miss the chance to change the settings before initializing calling. So moved the 'Initialize Calling' button bellow Advanced settings

Changed UI in credentials section

Dialing a number that is not part of the org

Screen.Recording.2023-10-13.at.2.27.31.PM.mov

Dialing a number that is part of the org

Screen.Recording.2023-10-13.at.2.33.59.PM.mov

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios where tested

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

I certified that

• I have read and followed contributing guidelines

• I discussed changes with code owners prior to submitting this pull request

• I have not skipped any automated checks

• All existing and new tests passed

• I have updated the documentation accordingly

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-3147.d3m3l2kee0btzx.amplifyapp.com

[sreenara]

Changes look fine. Thanks.
There was another issue I noticed in the samples page.

In the above image, the workflow can be mis-understood by a user. The advanced settings or region and country take effect when the calling.init() button is pressed. But the button is located above the Advanced section. So a user will miss the chance to change the settings before initializing calling.
The expectation is to move the calling.init() button below the Advanced settings so it's clear that initialization will take them into account too.

Also, can we reword calling.init() to 'Initialize Calling'?

[Shreyas281299]

Changes look fine. Thanks. There was another issue I noticed in the samples page.

In the above image, the workflow can be mis-understood by a user. The advanced settings or region and country take effect when the calling.init() button is pressed. But the button is located above the Advanced section. So a user will miss the chance to change the settings before initializing calling. The expectation is to move the calling.init() button below the Advanced settings so it's clear that initialization will take them into account too.

Also, can we reword calling.init() to 'Initialize Calling'?

Made the changes.