sundance-communications.com/forum Forums TDM Business Telephone Systems NEC Telephones & Systems NEC SV8100 Network busy error

We use a phone system where 5 people work from home and the 5 employees see the following message:
Network Busy (restart)

This happens to all remote phones at the same time.

Any ideas?

Below is a direct article about this from NEC. I hope it helps. I also suggest that your SV8100 be at the most current software level which is version 8 and your IP phones be at the most current firmware version 5.0.4.0. I am not sure if you are the installer, if not you will need to have a certified installer come out to load this software. You will also need to be familiar with Wireshark to perform the following:

Remote NEC SIP MLTs Reset Periodically
ID# 6175 | Published 05/05/2011 04:31 PM | Updated 10/28/2012 09:58 AM
Products: SV8100, UX5000 Categories: Documentation, Engineering, KB Article, Terminals/End Points, IP Terminal/Adapter

Why do NEC SIP MLTs reset from time to time? The display says "Network Busy" and then the terminal reboots.

The only way to determine the cause is to use Wire Shark to obtain a packet capture at Site A and Site B at the same time of the event. Once captured, open Wire Shark. Then in the "Filter Bar" type SIP and then apply. This will then show just SIP packets.

Browse down through the SIP packets and look for "Notify" or "Register" packets that are not acknowledged by the other side. Usually you will find many packets in a row that go unanswered. This is typically where the problem starts. Now you need to look at both captures to see if the "Register" or "Notify" packet made it to the other site.

If you can see packets being transmitted from site A, but never arriving at site B, then the most likely cause is a firewall at either site A or B.

I had this issue for a few weeks on a site it was driving me MAD .. NEC Japan suggested
84-23-02 to be set to 180 ( set to 3600 by default in Au. systems ). Problems went away!!!!
I also had another problem that was SW related before this on the same site, the NIC was shutting down 3 times a minute, I would ping the system & it was ok, but took for ever to web browse to it ... I then decided to do a ping count of 100 .. that's when I noticed the 10% packet loss !!!!!! ( a default count of 4 was not picking the issue up .. put Australian V6 on the CPU & problem went away .. ( thought that would shorely fix the "RESTART issue" but I still had issues , that's when the 84-23-02 fixed that one ! I love those "Double faults ! " )