NO JOY All Extensions Lagging

[FitnessPlus]

I've exhausted all I can think of on this one and I need help.
All of my regular extensions (Aastra 575Xi phones) will lose contact with the server (display "No Service" on the phones) randomly about 10-15 times a day for about 60-120 seconds and then reconnect to the server. I have 3 ATAs on the network for less used extensions that do not exhibit this behavior. Near as I can tell the problem started when I ran a "yum update" to plug the nasty little bash bug from last month. In retrospect perhaps I should have only updated bash, and not everything else, as I typically try to avoid "yum update" unless there is a serious security flaw. Here is what I have done to this point:

• Eliminated the entire network as an issue (moving to a backup router and disconnecting every other network device but the pbx and the phones)
• Eliminated the phones as an issue by disconnecting half the phones, observing the behavior, then connecting only the other half and still observing the behavior.
• Eliminated the firewall as an issue by allowing any traffic on any port from 192.168.9.0/24 in iptables.
• updated firmware on aastra phones, problem persists

Here is a copy from asterisk -r with verbosity set at 1.

[2014-10-28 19:55:00] NOTICE[9653]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 19:55:47] NOTICE[9717]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 19:56:03] NOTICE[9723]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 19:57:05] NOTICE[9742]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '114' is now Reachable. (93ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '126' is now Reachable. (95ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '125' is now Reachable. (95ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '120' is now Reachable. (97ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '116' is now Reachable. (94ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '130' is now Reachable. (94ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '122' is now Reachable. (96ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '121' is now Reachable. (96ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '112' is now Reachable. (98ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '115' is now Reachable. (97ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '113' is now Reachable. (96ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '119' is now Reachable. (96ms / 2000ms)
[2014-10-28 19:57:36] NOTICE[4266]: chan_sip.c:23554 handle_response_peerpoke: Peer '117' is now Reachable. (97ms / 2000ms)
[2014-10-28 19:58:01] NOTICE[10000]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 19:59:00] NOTICE[10007]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint
[2014-10-28 20:00:00] NOTICE[10014]: pbx_spool.c:402 attempt_thread: Call completed to Local/s@tc-maint

Please HELP! My office has been working (while muttering under their breath) though phones disconnect for a few weeks now and I NEED to get this corrected. One thing we have noticed is that if you are on an active phone call, that extension will not drop, so customers are not getting cut off.

 

[briankelly63]

Other than internet or hardware problems this might be of help

http://www.888voip.com/forum/aastra/381-aastra-phones-going-to-no-service.html

 

[FitnessPlus]

Other than internet or hardware problems this might be of help

http://www.888voip.com/forum/aastra/381-aastra-phones-going-to-no-service.html

As much as I wanted this to work, alas it did not. These are phones on a LAN, so NAT *shouldn't* be an issue I'm dealing with here.

 

[briankelly63]

I had heard there might be a phone firmware issue that contributed to the "no service" issue but generally the "no service" indicator comes up when the box loses the internet or DNS.