Unable to register to IPv6 server
See original GitHub issueUsing version 11.2.0 from F-Droid on Android version 5.1
Steps to reproduce:
- Create new account: user@pbx.home.nivex.net
- Set Authentication password
- Check the “Register” box
- Tap confirm (checkmark in upper right)
Expected result:
- Registration to server
Actual result:
- Error message displayed:
Registering of
sip:user@pbx.home.nivex.net
failed.: Protocol not supported
Issue Analytics
- State:
- Created 4 years ago
- Comments:58 (30 by maintainers)
Top Results From Across the Web
Configure IPv6 for advanced users - Windows Server
Provides step-by-step guidance for how to use the Windows registry to disable IPv6 or certain IPv6 components in Windows.
Read more >Unable to register endpoints with Session Manager over IPv6
Use CLI command ifconfig eth1 to check if the ASSET component has configured the Session Manager's IPv6 address. · Check if Session Manager...
Read more >Direct Access clients will not Register their IPv6 Record in DNS
Solution: Ok, was finally able to resolve this with Microsoft help. The issue was not that the clients were not registering in DNS....
Read more >Registration to SCC does not work from a pure IPv6 Network
Environment. SUSE Linux Enterprise Server 15 · Situation. The System needs to be registered to SUSE Customer Center (SCC) from a pure IPv6...
Read more >Some systems not attempting to register IPv6 reverse
You've manually configured an IPv6 address on this server. Do the ones that work also have manually configured IPv6 addresses? – Michael Hampton....
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 FreeTop 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
Top GitHub Comments
I can see that this is the intent, but I don’t see why this is necessary or beneficial. If baresip needs to choose a source address, it should be obtained by asking the routing table what source address would be used for a particular destination. And if it doesn’t need to specifically choose, it shouldn’t, so that the normal routing process works.
Started a new job this week so I only just now had a chance to test the latest package out. It appears to be working correctly. Thank you!