ed_fr Posted October 19, 2022 Report Share Posted October 19, 2022 Hello, Following the activation of the OPUS codec on some extensions, these can no longer use the DTMF of the SVI... bug present on VODIA v68.0.22 & v68.0.24 Quote Link to comment Share on other sites More sharing options...
Vodia Support EU Posted October 19, 2022 Report Share Posted October 19, 2022 Hello ed_fr, Can you please send us a ticket and record a pcap of such an event and send it as an attachment? vodia@zammad.com Thank you very much Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 19, 2022 Report Share Posted October 19, 2022 It is probably because the client thinks that the 48 kHz of OPUS does not match the 8 kHz of the telephone-event. What device are you using? Quote Link to comment Share on other sites More sharing options...
LECSJH Posted October 20, 2022 Report Share Posted October 20, 2022 (edited) We are seeing it inside our Vodia web client. Here is a capture using G.711U (IPs anonymized)https://vm.lecsvoip.com/cdr.php?cdrId=5369381&anonIps=1&hash=c4117d7c26025aedb291edf108285f95ce3dd9716503348d0839f57184b97276 Here is a our capture using OPUS (IPs anonymized)(IPs anonymized) https://vm.lecsvoip.com/cdr.php?cdrId=5369419&anonIps=1&hash=d4ba553883edfc35afe6c866267ac0f29ad5372b2cf32a14422567c315b8cbd7 Edited October 20, 2022 by LECSJH Posted same link twice Quote Link to comment Share on other sites More sharing options...
LECSJH Posted October 20, 2022 Report Share Posted October 20, 2022 (edited) A log level 9 with only Media events of during the call with a DTMF 2 being pressed. [4] 22:44:20.230 Last message repeated 4 timesⓘ [6] 22:44:20.230 Port 271: Allocating port for SIP Call-ID e4624c61@pbxⓘ [7] 22:44:20.230 Port 271: SRTP tx keys: pTMcOzZqTnGl4CARsWO8sHfxjWOfwiOYhqypZjvP AA02E18Eⓘ [7] 22:44:20.231 Port 271: Allocated ports 59466 and 59467ⓘ [8] 22:44:20.231 Port 271: Added predefined codec 6 (mapped to 9)ⓘ [8] 22:44:20.231 Port 271: Added predefined codec 2 (mapped to 0)ⓘ [8] 22:44:20.231 Port 271: Added predefined codec 3 (mapped to 8)ⓘ [8] 22:44:20.231 Port 271: Added predefined codec 9 (mapped to 13)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 8 (mapped to 111)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 15 (mapped to 103)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 16 (mapped to 104)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 17 (mapped to 106)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 18 (mapped to 105)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 19 (mapped to 110)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 20 (mapped to 112)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 21 (mapped to 113)ⓘ [8] 22:44:20.231 Port 271: Added rtpmap codec 1 (mapped to 126)ⓘ [7] 22:44:20.234 Port 271: Set codec preference count 5ⓘ [6] 22:44:20.234 Port 272: Allocating port for SIP Call-ID 9abc7c31@pbxⓘ [7] 22:44:20.234 Port 272: SRTP tx keys: 1lnoEih28yogD2I1eQzuxNW5vwJAa6W4pazQodaA 0BD9AC23ⓘ [7] 22:44:20.234 Port 272: Set codec preference count 5ⓘ [8] 22:44:20.234 Port 272: state code from 0 to 100ⓘ [9] 22:44:20.234 Port 272: Adding codec opus/48000 to available listⓘ [9] 22:44:20.234 Port 272: Adding codec PCMU/8000 to available listⓘ [9] 22:44:20.234 Port 272: Adding codec G722/8000 to available listⓘ [9] 22:44:20.234 Port 272: Adding codec G729/8000 to available listⓘ [9] 22:44:20.234 Port 272: Update codecs preference size 5, available codecs size 5ⓘ [7] 22:44:20.235 Port 272: Allocated ports 57278 and 57279ⓘ [8] 22:44:20.236 Port 271: state code from 0 to 183ⓘ [8] 22:44:20.236 Port 271: Ignore double SDPⓘ [9] 22:44:20.237 Port 271: Adding codec opus/48000 to available listⓘ [9] 22:44:20.237 Port 271: Adding codec PCMU/8000 to available listⓘ [9] 22:44:20.237 Port 271: Adding codec G722/8000 to available listⓘ [9] 22:44:20.237 Port 271: Connected device does not support codec G729/8000ⓘ [9] 22:44:20.237 Port 271: Update codecs preference size 5, available codecs size 4ⓘ [6] 22:44:20.237 Port 271: Choose codec opus/48000ⓘ [6] 22:44:20.395 Port 271: Sending RTP to 312.321.321.321:24798, codec opus/48000ⓘ [7] 22:44:20.572 Port 271: Set DTLS SRTP key for clientⓘ [7] 22:44:20.573 Port 271: SRTP tx keys: onsAyI4tkuBFvR1I1K+a4EP2gP3CmKr2LTyQe4BS 1C38146Aⓘ [7] 22:44:20.573 Port 271: SRTP rx keys: Fr7d0ZAt2l5RZLozRGA9FTlKon6iJgnbLtjunBG0 00000000ⓘ [9] 22:44:20.594 Port 271: Received first RTP packetⓘ [8] 22:44:21.545 Port 272: Added predefined codec 2 (mapped to 0)ⓘ [8] 22:44:21.545 Port 272: Added rtpmap codec 1 (mapped to 101)ⓘ [7] 22:44:21.545 Port 272: Set packet length to 20ⓘ [6] 22:44:21.546 Port 272: Choose codec PCMU/8000 in answerⓘ [6] 22:44:21.546 Port 272: Sending RTP to 10.0.1.167:21834, codec PCMU/8000ⓘ [7] 22:44:21.546 Port 272: Determine pass-through mode after receiving responseⓘ [8] 22:44:21.547 Port 272: state code from 100 to 200ⓘ [8] 22:44:21.547 Port 271: state code from 183 to 200ⓘ [7] 22:44:21.548 Port 271: RTP pass-through modeⓘ [7] 22:44:21.548 Port 272: RTP pass-through modeⓘ [7] 22:44:21.548 Port 272: Media-aware pass-through modeⓘ [8] 22:44:21.554 Media: Dropping audio_uk/mb_no_name_ask1.wav from cacheⓘ [6] 22:44:21.584 Port 272: Sending RTP to 123.123.123.123:21834, codec PCMU/8000ⓘ [9] 22:44:21.584 Port 272: Received first RTP packetⓘ [6] 22:44:21.584 Port 271: Different Codecs (local PCMU/8000, remote opus/48000), falling back to transcodingⓘ [9] 22:44:22.732 Port 271: RTCP SR time=3875222662:3819711984 timestamp=2850696874 packets=107 octets=16820ⓘ [9] 22:44:25.562 Port 272: RTCP SR time=3875222665:2390673286 timestamp=32800 packets=199 octets=31840ⓘ [9] 22:44:27.297 Port 271: RTCP SR time=3875222667:1958822914 timestamp=2850916090 packets=336 octets=51162ⓘ [9] 22:44:29.582 Port 272: RTCP SR time=3875222669:2476478142 timestamp=64960 packets=400 octets=64000ⓘ [9] 22:44:33.602 Port 272: RTCP SR time=3875222673:2562343129 timestamp=97120 packets=601 octets=96160ⓘ [9] 22:44:33.873 Port 271: RTCP SR time=3875222674:133234180 timestamp=2851231690 packets=664 octets=103760ⓘ [9] 22:44:37.393 Port 271: RTCP SR time=3875222677:2371818379 timestamp=2851400698 packets=840 octets=132096ⓘ [9] 22:44:37.622 Port 272: RTCP SR time=3875222677:2648233885 timestamp=129280 packets=802 octets=128320ⓘ [9] 22:44:41.551 Port 271: RTCP SR time=3875222681:3053700272 timestamp=2851600378 packets=1048 octets=165584ⓘ [7] 22:44:42.392 Port 271: Received RFC4733 DTMF on codec 126ⓘ [9] 22:44:42.642 Port 272: RTCP SR time=3875222682:2734163295 timestamp=169440 packets=1053 octets=168480ⓘ [9] 22:44:47.051 Port 271: RTCP SR time=3875222687:906332588 timestamp=2851864330 packets=1324 octets=209545ⓘ [9] 22:44:47.662 Port 272: RTCP SR time=3875222687:2820028281 timestamp=209600 packets=1304 octets=208640ⓘ [8] 22:44:50.812 Port 272: Clearing port with SIP Call-ID 9abc7c31@pbxⓘ [8] 22:44:50.833 Media: File recordings/xxxxxxxxxxx/102/20221019-224421-o-102.wav has been writtenⓘ [8] 22:44:50.902 Port 271: state code from 200 to 486ⓘ [8] 22:44:50.902 Port 271: Send hangup with reason byeⓘ [8] 22:44:50.971 Port 271: Clearing port with SIP Call-ID e4624c61@pbxⓘ Edited October 20, 2022 by LECSJH more log goodness Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 20, 2022 Report Share Posted October 20, 2022 Looks like we need to add telephone-event/48000 to the list of supported codecs... We'll do that in the next build. Quote Link to comment Share on other sites More sharing options...
LECSJH Posted October 20, 2022 Report Share Posted October 20, 2022 ETA of release? The use of OPUS would be fantastic, especially for mobile app users. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 20, 2022 Report Share Posted October 20, 2022 We'll make a 68.0.25.beta at the end of the week if you want to try that one out. Quote Link to comment Share on other sites More sharing options...
LECSJH Posted October 20, 2022 Report Share Posted October 20, 2022 Oh neat! I'll keep an eye out for it. Quote Link to comment Share on other sites More sharing options...
LECSJH Posted October 21, 2022 Report Share Posted October 21, 2022 If I wanted to download the beta version, how would I go about doing that? Quote Link to comment Share on other sites More sharing options...
Vodia Support EU Posted October 21, 2022 Report Share Posted October 21, 2022 Hello LECS.JH Navigate to Admin/Maintenance/Software Update, select the last version 6.80 (the button on the right). Then you only have to manually change ....22 to 23.beta.xml and execute it with "Save". Quote Link to comment Share on other sites More sharing options...
ed_fr Posted November 22, 2022 Author Report Share Posted November 22, 2022 On 10/19/2022 at 11:55 AM, Vodia PBX said: It is probably because the client thinks that the 48 kHz of OPUS does not match the 8 kHz of the telephone-event. What device are you using? I use Vodia phone on Windows. But in Vodia v68.0.25.beta it's works. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 22, 2022 Report Share Posted November 22, 2022 Yes, we'll hopefully release 68.0.26 in the next few days. Quote Link to comment Share on other sites More sharing options...
ed_fr Posted November 24, 2022 Author Report Share Posted November 24, 2022 Great! On the other hand, the sound quality when the OPUS codec is used is poor from the iOS app. (background noise & metallic voice) Quote Link to comment Share on other sites More sharing options...
mskenderian Posted November 24, 2022 Report Share Posted November 24, 2022 @ed_frwhich ios version are you using? this might of already been fixed. Quote Link to comment Share on other sites More sharing options...
ed_fr Posted December 2, 2022 Author Report Share Posted December 2, 2022 On 11/22/2022 at 1:38 PM, Vodia PBX said: Yes, we'll hopefully release 68.0.26 in the next few days. Hello, I installed v68.0.26 yesterday instead of V68.0.25.beta. Since then, the DTMF no longer works with the OPUS codec from the Windows application. But it works from the iOS app... Quote Link to comment Share on other sites More sharing options...
Frederic Pi Posted December 2, 2022 Report Share Posted December 2, 2022 68.0.26 works well but there is still a metallic voice with android and iOS softphones Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 3, 2022 Report Share Posted December 3, 2022 Its complicated... For a call between two extensions that both support OPUS, it should sound awesome. Calls to the PSTN are a different story, because every transcode operation reduces the call quality, even if a great codec is in use. This might cause a small metallic sound, but it should not be dramatic. If the mobile phone has a great connectivity, it is better to use G711. If the mobile phone has less-than-perfect network connectivity, it makes sense to give OPUS a try. It can handle packet loss much better then G.711. Quote Link to comment Share on other sites More sharing options...
Frederic Pi Posted December 4, 2022 Report Share Posted December 4, 2022 Hello, I agree with your analysis but the problem is that this is an internal call between an Android application and an iOS application and/or the other way round so we are in the vodia environment and not outside, so OPUS should not create a metallic voice... Quote Link to comment Share on other sites More sharing options...
mskenderian Posted December 5, 2022 Report Share Posted December 5, 2022 I believe that metallic sound was fixed. I had the same issue. Christian fixed it end of September. Quote Link to comment Share on other sites More sharing options...
Frederic Pi Posted December 5, 2022 Report Share Posted December 5, 2022 Yes but this is a new problem related to opus on 68.0.26 during a call between the iOS vodia app (updated) and the android vodia app (updated). Quote Link to comment Share on other sites More sharing options...
ed_fr Posted December 15, 2022 Author Report Share Posted December 15, 2022 Hello, I am having metallic voice issues again from the iphones. And the DTMF does not work with OPUS on the Windows app. I am on version 68.0.26 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 25, 2022 Report Share Posted December 25, 2022 We tried to reproduce this problem, but had no problems. What codec are you using? And what iPhone model? Quote Link to comment Share on other sites More sharing options...
Frederic Pi Posted December 29, 2022 Report Share Posted December 29, 2022 Codec Opus : on android 12 Samsung s22 and iPhone 13pro iOS 16 Quote Link to comment Share on other sites More sharing options...
ed_fr Posted December 29, 2022 Author Report Share Posted December 29, 2022 Iphone SE 2020 iOS 16.0.3 & OPUS codec. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.