-
Notifications
You must be signed in to change notification settings - Fork 671
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
To configure DTMF RTP events duration and volume. (AUD-5521) #1227
Comments
I think may be |
Hello @TempoTian, Indeed the first prototype API would satisfy us, thanks!! We don't need (at present) to control the rtp packets individually. As you said, |
I have implement the new API, you can use library to verify it also. |
Hi @TempoTian, Thanks a lot for this api! |
Describe the situation
I use the esp_rtc_send_dtmf to send dtmf events out-of-band as part of the VOIP (rtp/sip) stream. In order for the receiving device to understand them certain durations and volume are required. This arrises even more when the out-of-band dtmf packet reaches a gateway device that converts it in analogue, in band, for a PSTN (non-packetted) telephone network.
The current values I see are :
Describe the solution you'd like
Additional context
![Screenshot 2024-07-09 at 11 22 10](https://private-user-images.githubusercontent.com/16382858/346900525-c5722438-3d5e-4f60-ab49-888c104465c7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU3ODA1MzgsIm5iZiI6MTcyNTc4MDIzOCwicGF0aCI6Ii8xNjM4Mjg1OC8zNDY5MDA1MjUtYzU3MjI0MzgtM2Q1ZS00ZjYwLWFiNDktODg4YzEwNDQ2NWM3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA4VDA3MjM1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU5ODM0NDBlMmVjMDcxYTllYTI5YzRjMzQyMmJlZDMxMzlmNzI3MjU5NTBhOGVjMThmYWIxYzI5NDdjMTc5MzQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.gBODi8EmMVtW7xH-9RbyHSvnv4mF71fJQgAByBwhxYo)
To dive deeper in the protocol, here is what I see, none of that is concretely problematic. In the above sniffed packets, the Dtmf event starts on packet N°2468 and ends after 3 end-event packets on N°2881. According to the RFC, the event duration should increase with each non-end-event rtp packet. We sniffed these 9 non-end-event packets a bunch of milliseconds apart (2-5ms) corresponding to increases of roughly about 40units, instead, I see the duration stay fixed. This can be especially practical for a gateway converting an analogue dtmf, in-band, to a digital RTP/SIP, out-of-band, dtmf. It allows for minimal latency and full information. Again, no issue here, the behaviour as is is satisfactory for my current needs.
OS darwin arm64 23.5.0
Visual Studio Code version 1.90.2
Visual Studio Code language en
Visual Studio Code shell /bin/zsh
ESP-IDF Extension version 1.8.0
Git version 2.45.0
ESP-IDF version v4.4.5
ADF version v2.6-122-g28736657
Python version 3.12.4
Python's pip version 24.0
Chip used: ESP32-S3 custom board
Build system: idf.py
The text was updated successfully, but these errors were encountered: