fix(samples): avoid init failure for tokens without additional features

[sreenara]

COMPLETES # NA

This pull request addresses

The issue of initialization failure while using WxCC access tokens. These tokens do not have additional features enabled such as voicemail. Moreover, XSI API requests such as Call Settings (Forwarding, DND, Call Waiting) will also fail.

by making the following changes

1. Move initialization of all additional features under a new function
2. Provide a new button for fetching all settings so we don't do this automatically
3. Voicemail.init() is now triggered when clicking the Voicemail button and not automatically during initialization

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

With regular Webex suite access token:

1. Register with Webex Calling
2. Place call and check for media
3. Check voicemail
4. Check settings and test whether DND setting works

With WxCC token:

1. Register with Webex Calling
2. Ensure calls work.
3. Ensure no errors encountered during initialization so we can do tests as needed

Console logs:
cc-token-fix-console.log
Network logs:
cc-token-fix-network.har.txt

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-3257.d3m3l2kee0btzx.amplifyapp.com

[mkesavan13]

Looks good to me

[Shreyas281299]

Changes look good