SIP phone dropping connection on network

So This just started happening.

I have a single extension that is dropping connection to the PBX. The Phone is on the same switch as three other phones and they dont appear to be dropping connection.

-- Registered SIP '101' at 192.168.0.96:5060

[2016-02-03 12:52:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 12:57:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:02:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:07:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (15ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:12:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:17:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:22:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:27:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:32:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:37:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:42:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:47:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:52:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 13:57:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 14:02:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 14:07:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
LCPAPBXCLI>
LCPAPBX
CLI>
LCPAPBXCLI>
– Registered SIP ‘101’ at 192.168.0.96:5060
[2016-02-03 14:12:03] NOTICE[18831]: chan_sip.c:23739 handle_response_peerpoke: Peer ‘101’ is now Reachable. (4ms / 2000ms)
LCPAPBX
CLI>

are these yealink phones?

All phones are Digium D70’s