ATA 188 rebooting every 8-hours

[andrew.butterworth]

I have a bit of a convoluted setup but the actual issue is fairly straight forward.

My 'lab' (i.e. home network...) is connected to the Internet via a consumer FTTP connection fronted by a Cisco C921-4P PPPoE router.  The service provider I was signed up with stopped proving broadband services last year and we were automatically moved to another service provider who operated on the same infrastructure. The cutover was a bit of a mess and I was offline for about a day.  Anyway once that was sorted I discovered that the new service provider didn't provide any voice services via the ONT, where the previous one did. When I checked, this was an optional extra at an extra cost.

I've had a free SIP account for years as part of the lab to do testing, so I thought I'd use this as its a local telephone number and allows free incoming calls, plus free emergency service outbound calls. I have an aging CUCM 7.1.5 VM in my lab when I was partially studying CUCM. This has a SIP trunk to another VM running FreePBX 17 (Asterisk) and the FreePBX has a SIP 'trunk' to the free SIP account. I've configured routes between the two systems for outbound and inbound call routing and it works reasonably well. Inbound calls hit FreePBX and it routes them via the trunk to the CUCM 7.1.5 system. Previously I had it ring a 7970 phone that's in the lab. As I now wanted this to ring the home phone (old analogue thing with three handsets), I blew the dust off an old ATA 188 I had in the garage and got this connected to the CUCM 7.1.5 system.  This took a bit of effort as it wasn't default and I had to go through the reset procedure with an attached analogue phone. Anyway its now reset, upgraded to the latest 3.02.04 SCCP image and both lines are registered to CUCM 7.1.5.  Everything works as expected.

However, every 8-hours the ATA 188 seems to reset or somehow disconnect from the Ethernet switch. I'm using IBNS 2.0 configurations on the switches and the ATA 188 is authenticated via MAB.  There are no session timers or restart timers pushed from RADIUS and only the 48-hour periodic accounting default is configured.  The DHCP lease is 3-days.  In the log on the switch I see this:

000698: Feb 24 07:09:11.759 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000699: Feb 24 07:09:13.765 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000702: Feb 24 07:09:42.124 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB0000009A2CBA28C1
000704: Feb 24 15:10:01.883 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000705: Feb 24 15:10:02.887 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
000707: Feb 24 15:10:05.005 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
000709: Feb 24 15:10:06.005 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000710: Feb 24 15:10:32.213 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB0000009B2E725AF1
000713: Feb 24 23:10:49.954 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000715: Feb 24 23:10:51.956 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000717: Feb 24 23:11:20.304 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB0000009C302A8553
000730: Feb 25 07:11:45.062 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000731: Feb 25 07:11:47.068 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000734: Feb 25 07:12:15.402 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000A431E2CB14
000736: Feb 25 15:12:33.143 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000738: Feb 25 15:12:35.145 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000740: Feb 25 15:13:03.493 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000A5339AF579
000752: Feb 25 23:13:28.216 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000754: Feb 25 23:13:30.223 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000756: Feb 25 23:13:58.581 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000A935533B21
000766: Feb 26 07:14:21.340 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000767: Feb 26 07:14:22.347 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
000770: Feb 26 07:14:24.465 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
000771: Feb 26 07:14:25.464 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000775: Feb 26 07:14:51.694 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000AF370B7933
000782: Feb 26 15:15:16.438 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000784: Feb 26 15:15:18.441 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000788: Feb 26 15:15:46.789 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000B138C3BEF1
000884: Feb 26 23:16:09.595 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000886: Feb 26 23:16:11.602 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000888: Feb 26 23:16:39.939 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000BB3A7BFD17
000893: Feb 27 07:17:04.669 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000895: Feb 27 07:17:06.679 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000897: Feb 27 07:17:35.054 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000C13C3442E6
000913: Feb 27 10:09:49.508 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000C43CD1F204
000916: Feb 27 15:17:59.739 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000918: Feb 27 15:18:01.742 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000920: Feb 27 15:18:30.111 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000C53DEC889A
000930: Feb 27 23:18:52.852 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
000931: Feb 27 23:18:53.855 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
000933: Feb 27 23:18:55.928 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
000935: Feb 27 23:18:56.931 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to up
000936: Feb 27 23:19:23.189 GMT: %DOT1X-5-FAIL: Authentication failed for client (0012.0196.5a5a) on Interface Gi0/3 AuditSessionID C0A8FFFB000000C83FA4C692

Additionally at the point of DHCP renewal (3-days) I also see a flurry of DHCP-SNOOPING_DENY logs which I assume is due to the redundant DHCP configuration there is (two IP Helpers on the SVI with split scopes on the two DHCP servers).  This doesn't seem to cause any issues, but seems to be an issue with the DHCP client in the ATA 188 as it shouldn't broadcast for renewal, but should just unicast to the DHCP server it has a lease with.

I have a couple of 7900 series IP phones as well as some Polycom VVX x50 series IP phones (registered to the FreePBX 17 system) and I don't see this behaviour with them.

A long shot, but any ideas or should I just throw this aging ATA 188 in the trash?