VoIP.ms no longer reports connection as secure.
See original GitHub issuePreviously we worked out configuration settings on an earlier version of baresip that resulted in VoIP.ms reporting a secure connection to their service.
This how I have configured baresip for supporting their service:
Media Encryption: SRTP-MAND
DTMF Mode: In-band RTP Events
Telephony provider: citylocation.voip.ms:5061;transport=tls
Similar equivalent settings on other apps, including Jami on Android and desktop applications such as MIcroSIP, VoIP.ms reports as being connected securely. (Note that Jami has an outstanding and unrelated to this issue of their app not receiving TLS connected calls.)
This is using 47.2.0. in LineagOS 18.1 / Android 11.
Issue Analytics
- State:
- Created a year ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
How to Diagnose the Most Common VoIP Connectivity ...
Check if there are intermediary devices like a switch or internet outlet on the wall and try overpassing them by connecting the SIP/IAX...
Read more >Getting Started - VoIP.ms Wiki
You can create an account for free by clicking Here. You will access the sign-up page, please enter the information required and click...
Read more >General Security - VoIP.ms Wiki
Your calls and the login process for VoIP.ms are very secure from our network. To login to your account you will need to...
Read more >Features - VoIP.ms Wiki
From VoIP.ms Wiki ; This feature will allow you to prevent any foreign country IP from accessing your Customer Portal. You can receive...
Read more >DID Troubleshooting - VoIP.ms Wiki
If you are using the main account, go to Main menu >> Account Settings >> Inbound Settings, confirm the device type and protocol...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This problem was resolved by setting the following in the account Outbound Proxies:
Paul writes:
See https://github.com/juha-h/baresip-studio/wiki/Debugging.