Hello all,
The Coturn server we have deployed in not responding for STUN Requests origination from a certain Browser Client (Binding requests).
We have deployed a
Coturn Server (coturn/stable,now 4.5.2-3 amd64 [installed]) in
Debian 11 AWS EC2 instance (Linux ip-10-10-6-88 5.10.0-20-cloud-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux).
As browser Client we are using
JsSIP v3.9.0 for both, a slightly modified version of tryit-jssip to test (where it is working successfully) in once case and our enterprise production application in another case (where it fails). There are no major differences in terms of implementation of JsSIP.
Have attached the relevant Documents with Coturn logs in Both cases (Verbose flag set), Relevant SIP Message exchange in both cases and WebRTC Internals.
Not sharing the entire PCAP file at the moment for both cases but have attached some screenshots showing the difference in both cases, with binding responses from Coturn when we user JsSIP standalone as expected but not otherwise. I could not see any reasonable difference in the individual packets in the two scenarios.
Any help is appreciated. (Also in case there is anything I have overlooked anything or any relevant detail is missing, please let me know).
More information about the Logs:
- Coturn Verbose Logs - Starting with coturn_Verbose.
- The arrows for SIP Traces are similar to what we see on browser Network Tab (WS), indicating whether messages are incoming (⬇️) or outgoing (⬆️).
- The WebRTC Internals Dump with the WebRTC connection failure. (webrtc_internals_dump.txt)
- PCAP screenshot for Successful JsSIP Test (pcap_jssip-test_success.png)
- PCAP screenshot for Failed Enterprise JsSIP Test (pcap_enterprise-ui_fail.png)
Thanks.