sundance-communications.com/forum Forums TDM Business Telephone Systems NEC Telephones & Systems netlink on the sv8100

I have a 3 Nec Sv8100's running over the network on netlink. The IT department installed 3 new sonicwalls and gave me new ip adresses for each system. They all communicate but one of my secondary systems keeps rebooting around every 2 hours. Any suggestions.

check the internet connection for that location. i would start by setting up a laptop to continuously ping google or yahoo out of the router, from the location having the issue.

go to RUN, type in CMD & click enter
type in ping yahoo.com -t

to stop the continuous ping press ctrl c

The version on the system is 2.0 would that have cause any probtlems with the nodes rebooting?

I think I would upgrade to the latest version of software on all sites and then go from there. We found that some sites running R2.0X were not the most reliable on NetLink but were better with say R4.0X..

Are the Sonicwalls doing VPN's to the Netlink sites? If they are make sure you have the keep alive on for the VPN connection.

Yes the sonic walls are doing vpns for the netlink sites. What do you recomend the keep alive setting be.

Upgrade all sites to 5.1

D

See bellow cut and paste from NEC T.S. Document. I would definnetly upgrade, 5.01 is the most current software version. I would also verify the throughput with the IT vendor. I have a netlink site running accross a wireless bridge and when the throughput dropped low the site will reset, even though the bandwith states 50+ Mbs.

The remote Netlink site will reset, by design, whenever messaging to the main site is not replied to within certain timing parameters. By default, the remote site will send a message to the main and wait up to 250ms for the acknowledgment or reply to the message. Many Netlink installations are installed on Networks (Internet) that will periodically experience latency that can cause this timer to be exceeded thus invoking the reset in the remote site to allow Primary (survival) mode to initiate.
To allow for loss in these unqualified networks, change CM 99-03-23 to a "2". This will increase the wait for reply time to 500ms. This change is only available on software version 3.13A or higher and must be assigned via telephone
programming in both the main and remote sites. To make this change in the remote site, the system must be in Primary (survival) mode. A Central Processing Unit (CPU) reset is required after making this change.

To upgrade this site and get NTAC support, you will also, need to be the registered technician or company associated with the hardware key for the switch.

I have 2 sites "netlinked" together, both are running v5.01, and both have command 99-03-02 set to a 2 "500ms" sites are VPN'ed together using Sonicwall routers, and I still have secondary site resetting every couple of hours. I am at a loss of what to do IT guy thinks he might have to upgrade Sonicwall units but he is unsure. I also experience echo but only on the TDM terminal side, we are upgrading to a PRI so that should solve that issue according to the NTAC forum.