Registration VS IP Based - Asterisk and VOIP-ms

[Wolf1098]

I have noticed inconsistencies, it be nice to get a registration based option for asterisk
as well as IP-based for voip-ms

Usecase:
I have a hamsoverip and they run asterisk with registration; presumably as they support hotdesking. very little control without filing a ticket for that to be changed.

I also use VOIP-ms for my personal and company lines; which I have more control over, and they do support using IP based auth (not just whitelisting)... toggling it on the voip-ms webpanel does break 3cx I found out, as they the template used for voip-ms trunks EXPECTS a registration to be sent/received.

 

[Wolf1098]

it would be nice to get rid of the warning, so I can check the dashboard and see the trunks are all healthy, which seems to be supported on the asterisk profile, but it doesn't support sending registration...

 

[NikolasA_3CX]

Hi @Wolf1098

The warning appears when an untested provider is used, indicating that 3CX cannot guarantee the stability of that provider.