Implement DTMF recognition functionality for enhanced call interaction #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR implements comprehensive DTMF (Dual-Tone Multi-Frequency) recognition functionality to enable interactive voice response (IVR) capabilities in the ACSforMCS telephony system. The implementation follows the existing architectural patterns and provides seamless integration with the current caller identification and bot conversation infrastructure.
Key Features
Enhanced CallContext
DtmfSequenceproperty to store recognized DTMF tones (0-9, *, #)HasDtmfInputboolean flag to track DTMF availabilityAddDtmfTone()method for real-time sequence buildingGetDataQuality()method to consider DTMF input in data completeness assessmentNew DtmfExtractor Service
Created a comprehensive DTMF processing service following the same pattern as
CallerInfoExtractor:RecognizeCompletedeventsEvent Processing Integration
RecognizeCompletedevent handler in the webhook endpointUsage Example
When a caller presses phone keys during a call, the system now:
DTMF_INPUT=5|DTMF_SEQUENCE=12345Benefits
Backward Compatibility
Testing
/test/dtmf) for functionality verificationThis enhancement significantly expands the system's telephony capabilities while maintaining the existing architecture and ensuring reliable operation in production environments.
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.