Hello,
Thanks for the feedback and the suggestion of the mod_audio_stream module. I'd like to share more details about the flow we're looking to implement to ensure we're on the same page.
I would like to share a diagram illustrating the desired flow of the system:
In this diagram, we can see the flow of the client's interaction with the IVR system, with a focus on the interaction with our Java service for processing. Let me explain each step:
Customer calls the number and interacts with the FreeSWITCH IVR:
The client initiates the connection and interaction with the FreeSWITCH IVR. In the IVR example above, it calls an endpoint for our internal control, then it will call the part of the ASR that is my Java project.
Audio Data Packet Sent to Java Service:
The FreeSWITCH IVR sends the audio data packet, containing the client's speech, to our Java service for processing. This step is crucial as our Java application is responsible for converting speech to text and performing further processing.
Processing in Java Service:
Our Java service receives the audio data packet and processes it as needed. This involves converting speech to text and analyzing the content to identify the problem reported by the customer.
Decision Making and Response:
Based on the analysis of the speech content, our Java service determines the action to be taken. This may involve selecting an option for further interaction or initiating a specific process to resolve the customer's issue.
Response sent to FreeSWITCH:
Once the decision is made, our Java service sends the response, placing the selected option or action, back to the FreeSWITCH IVR. This response guides the IVR on how to proceed with the customer interaction.
I hope this diagram helps clarify the role of our Java service in processing customer interactions and how it integrates with the FreeSWITCH IVR. Committed to ensuring smooth integration of our service with FreeSWITCH.
Please feel free to get in touch if you have any further questions or need further clarification.
Yours sincerely,
Daniel.