Certificate Warning on Phones of several clients 3

[jayjr1105]

I know Manager has been barking about an expiring certificate for a while now. What does this one mean?

 

[budbyrd]

Same thing. You need to up date your security certificate.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[IPGuru]

I know Manager has been barking about an expiring certificate for a while now. What does this one mean?

Exactly the same!

go into security settings & regenerate your security certificate


Do things on the cheap & it will cost you dear

 

[qtelcom]

It means the same thing. You must be using a secure ip phone deployment, my guess is you'll need to update the certificate on the IPO that phone is registered to before it expires.

 

[jayjr1105]

Thanks all, Never realized there was a self signed cert to renew. Thanks!

 

[derfloh]

Look here:

https://blog.fwilke.com/ip-office-expiring-certificates/

 

[snowman50]

I have just got the same issue appearing on a single IP phone..

If the certificate is regenerated do all the IP phones have to be rebooted
Or will just the regeneration of the certificate do without a reboot.

I have 200 IP phones spread over 3 buildings.
I want to avoid a reboot if I can in case it takes a while for the phones to come back up.

 

[derfloh]

I guess you have to reboot them because they have to learn the new certificate as trusted. That info is part of 46xxsettings.txt that is read during a phone reboot.

Better is to generate a license from a CA (AppServer perhaps) and establish the CA as trusted. Look for the “Securing IP Office” guide.

 

[budbyrd]

Been doing a little research and can't seem to get a clear answer. Fixing the issue with the certificate is a simple task with just a few systems. We have a few thousand customers across the country and getting them all updated in the next 60 days might be a challenge. Is there any real service affecting problems we should be prioritizing? Like One-x, One-x mobile, communicator etc?

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[holdmusic34]

The PSN related to the IP500V2 certificate expiry has been updated, it has additional information which includes seeing the alarm on the handset.

The PSN is available at the original location of:

https://downloads.avaya.com/css/P8/documents/101042398

daddy? are you doing blah blah blah things again?

 

[jayjr1105]

So Manager no longer barks about the cert but phones are still popping up cert warning. I assume a reboot of the PBX and POE switch will clear this up?

 

[budbyrd]

If your system is new enough you can go it to web manager to verify it is updated. And yes, as derfloh stated you need to reboot the phones. The PBX should already be okay.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[Scotty_IT]

Hi All,

So I'm having the same issue, I've regenerated the certificate and rebooted phones, but the warning continues to pop up on the phones. IPO version 10.4 with Avaya 9608 phones.

 

[jayjr1105]

Either you didn't renew the cert properly or you don't have DHCP options setup (or working) to grab the new settings file.

 

[Scotty_IT]

it isn't hard to click "renew", but our DHCP is setup from our DC's with correct options. This only started happening when we upgraded to the latest version 10.4 build 5. The cert in the security settings has an expire date of 2020.
I'm going to try a complete reboot of the phone system this weekend to see if that changes anything.

 

[edlee321]

Only one of my phones came with this certificate warning, and shows issuer as "SLA Monitor Server"
But all my other phones use issuer as "ipoffic-00e007090e95.avaya.com"

How do i change the issuer on the phone thats reporting the expiring certificate

 

[edlee321]

Forget it, i just restarted the phone, #craft, and cleared settings, and now its okay

 

[tlpeter]

If you have read the PSN then you could have adjusted the 46xxsettings.txt and rebooted the phones. It will then not read the certificate. Removing that one line again and another reboot of the phones would have solved the problem. Now you had to do stuff on each phone while rebooting can be done remotely.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Scotty_IT]

The solution I had to preform was to clear the phone. I had looked at the 46XX file but didn't help. Likely I only had about 20 phones to do this too.