Welcome to Ecessa Support, we have a variety of technical information and tools for a variety of solutions. If you aren't finding a solution, or would like to talk to a technical support team member, please call 800-669-6242.

See Ecessa's full line of products and solutions
Ecessa Firmware Release Notes
Version: 10.7.4
Release Date: 2018.04.30
Revision 1.0: 2018.04.30

New Features
1. Ability to set network interface receive and transmit ring buffers.

1. The self certificate authority can be configured to use sha1 message digest in addition to md5.

1. Performing CLI certificate actions can cause the SSL security associations to get removed from the configuration.
2. IPSec VPN connections with active testing appear to be up when all remote endpoints are down.
3. IPSec VPN connections do not get re-started after WAN changes are made, or after a WAN gets a new IP address.
4. IPSec VPN monitoring can stop after WAN changes are made, or after a WAN gets a new IP address.
5. Email reports from the live device have links which do not work.
6. Adding multiple self CA certificates in the command line interfaces will cause the certificates to show up with blank information.
7. Adding a self CA certificate with the option to add the certificate to the main list, via the command line interface, will cause the certificate in the main list to not be present.
8. WAN Virtualization traffic can cause the device to lock up and reboot.
9. Creating self CA certificates via the command line interface causes the certificates not to be created correctly.

Known Issues
1. Creating a WAN using the CLI, with an alias of 24 characters, causes a software restart.
2. Creating a WAN Virtualization site with a name longer than 22 characters causes a software restart.
3. When a device is running a configuration which has WAN Virtualization sites and loads a configuration which does not have WAN Virtualization sites configured the device software may restart.
4. Virtual Product may boot slowly.
5. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
6. The DHCP service can stop unexpectedly.
7. The LCD display can become stuck and not display new information when keys are pressed.
8. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN entry with no name.
9. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
10. Using the CLI to create an alias with multiple addresses will reorder the addresses and remove duplicates, making the alias unusable for firewall forwarding rules.
11. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
12. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
13. DNS Reverse Zone may not work correctly for load-balanced hosts.
14. WAN Virtualization which is using non base IP addresses can not route as expected when a static route is in place which applies to all traffic.
15. WAN Virtualization hub location cannot have a site number that is greater than 127.
16. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
17. Failback static route over WAN Virtualization doesn't fail back after failing over to a WAN.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.