SIP Trunk password cannot contain spaces

[recond]

Trying to configure a Bandwidth SIP trunk with a provider that uses Bandwidths API but not with Bandwidth directly. Their system configures passwords that contain spaces and I have no way to change that detail on their end.

First up, why would 3CX care that the password contains spaces? It's always a bummer when websites or services don't see that as a standard special character, it makes using passphrases difficult!

Has anyone encountered this issue, is there a workaround? It doesn't seem to be related to URL encoding or at least substituting '%20' yields no solution.

I'm new to 3CX, are they responsive to feature requests and if so, what might be the best avenue to suggest changes?

 

[YiannisH_3CX]

Hi @recond and welcome to the community.

You could actually use spaces in the password field in the past but we removed it and added a check because many users that copied their passwords over also copied a space which caused registrations to fail. Since we made the change we had a lot less complains. I would recommend contacting your provider and ask them to change your password. You also could have a partner request this for you in the ideas section of the forum but since this was changed recently I would not expect much.