Fanvil credentials doesn't match after reboot

[ChrisNL]

We have a local 3cx on Debian with 300+ Fanvils.
After a power problem we are having problems with authentication of the phones. All are powered by PoE, so we restarted the switches for a reboot en renew the registration.
30% are connected, but the rest has an authenciation problem:
Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

BUT when I restart a phone by hand it connects with the 3CX

How is this possible?

I don't want to restart 150 phones by hand, does anybody have a solution?

Thanks in advance, Chris

 

[cobaltit]

You mean, like get Yealink phones?

Stock templates? 3CX approved firmware? Network whitelisted? Do they eventually register? Definitely seems odd.

 

[ChrisNL]

Agree , but its a hotel, so I got the Fanvil H phones.
They were all registered through provisioning without a problem, before the power outage. Range is whitelisted.
They register only when I reboot them one by one...

 

[cobaltit]

Ahh ok. I have played with those phones. My gut says to look at the switch in case it's reacting to the rush of traffic from 150 phones rebooting at once but I would expect that to block traffic entirely, not give that error message in 3CX. You have a wireshark of the failed registrations in bulk vs the individual by any chance?

 

[seegreen]

It would be interesting to restart them in batches to try and determine how many can be rebooted at the same time before the 'Credentials don't match' error occurs. Presume you have these devices spread over a number of PoE switches so just try restarting 1 or 2 of them at same time.

Dave.

 

[ChrisNL]

Hi Dave,

this already happens with a reboot of 1 switch with 22 phones. See the activity log for more details.
I have to look up the wireshark @cobaltit

 

[JohnS_3CX]

Hi

Your PBX should be able to handle 22 devices coming up at the same time.

I would be more concerned with the provided response not matching. I think you should run a capture on the PBX, see what happens with the authentication