Open ai6yr opened 6 years ago
@kk6fut, It sounds very strange that the @ sign is the culprit. I'd rather suspect the usage of lower case letters. I think the Echolink passwords are always upper case. A difference I can see is that Qtel always upper case the passwords but SvxLink Server does not.
It's been awhile since I filed this, but the password (without the @ symbol) was working. But, I have not verified it since.
Ok, that's strange indeed. Maybe it would have worked if written as @TEST12345 since SvxLink Server is missing the upper case. I cannot see any other difference between Qtel and SvxLink Server. They use the same code to communicate to the Echolink server but the way to read configuration differs.
If you have an EchoLink password with the "@" character encoded, even if valid (working in EchoLink Windows and qtel), svxlink will always return "invalid PASSWORD". How to replicate: change your password to "@test12345" or similar and attempt to load svxlink.