Skip to content

Add region-based PMA endpoints and call transfer functionality #200

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

Open
wants to merge 9 commits into
base: users/v-dharmarajv/CallAutomationTestApplication
Choose a base branch
from

Conversation

v-vkaluri
Copy link

@v-vkaluri v-vkaluri commented Apr 30, 2025

  • Add PMA endpoints for Arizona and Texas regions in app settings
  • Implement dynamic endpoint selection based on config boolean in app settings
  • Create setRegion endpoint to update PMA endpoint and reinitialize call automation client
  • Add call transfer capability for ACS participants

Purpose

  • This pull request adds multi-region support for PMA endpoints, specifically for Arizona and Texas regions. It implements dynamic endpoint selection based on configuration settings and adds the ability to transfer calls for ACS participants. These changes enhance the application's flexibility by allowing region-specific configurations and improving call handling capabilities.

Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code
1. Verify Arizona and Texas PMA endpoints are available in app settings
2. Test dynamic endpoint selection by toggling the config boolean
3. Test the setRegion endpoint functionality
4. Verify call transfer works correctly for ACS participants

What to Check

Verify that the following are valid

  • PMA endpoints for Arizona and Texas are correctly implemented and accessible
  • The application correctly switches between endpoints based on the configuration setting
  • The setRegion endpoint properly updates the PMA endpoint and reinitializes the call automation client
  • Call transfers work as expected for ACS participants

Other Information

…ality

- Add PMA endpoints for Arizona and Texas regions in app settings
- Implement dynamic endpoint selection based on config boolean in app settings
- Create setRegion endpoint to update PMA endpoint and reinitialize call automation client
- Add call transfer capability for ACS participants
@v-vkaluri
Copy link
Author

@microsoft-github-policy-service agree company="Microsoft"

@v-vkaluri v-vkaluri requested a review from v-dharmarajv April 30, 2025 23:55
@v-vkaluri v-vkaluri force-pushed the users/v-vkaluri/CallAutomationTestApplication branch from 526fd4b to 890d960 Compare May 1, 2025 05:56
v-vkaluri and others added 7 commits May 6, 2025 15:05
- Replaced ConfigurationRequest with a new CommunicationConfiguration model.
- Updated controllers to use CommunicationConfigurationService for configuration retrieval.
- Introduced SseController to handle server-sent events for incoming call notifications.
- Updated Program.cs to configure new services and remove obsolete configurations.
- Modified appsettings.json to reflect new configuration structure.
- Enhanced Swagger UI with new styles and functionality for configuring communication and incoming call parameters.
…ationTestApplication

Refactored configuration handling and enhanced swagger
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 this pull request may close these issues.

2 participants