Ecessa Firmware Release Notes
Release Date: 2017.05.19
Revision 1.0: 2017.05.19
1. The SIP Proxy needs the ability to send to the original destination of the SIP packet that is received on the LAN side of the proxy instead of determining the SIP destination based on the RFC 3261 specification.
2. The SIP proxy needs an option to source NAT inbound SIP requests.
3. An SRV record which is entered with an underscore in the protocol or service will cause duplicate underscores in the zone file.
1. If the option 'Enable accessing Idle Service via Active Device (WAN Only)' is enabled for the Hardware Failover feature then traffic destined to the LAN which uses the same ports as management services for the Ecessa device will be rejected.
2. Adding a site to the Ecessa Insight may report as successful while the site will show DOWN in the dashboard even though the live site is UP.
3. When multiple IPSec IKEv1 VPNs are enabled with a remote identifier configured, The VPNs may not connect.
4. SIP phone Busy Lamp Field soft keys may not display properly when UDP SIP messages are processed by the Ecessa SIP Proxy.
5. When loading a configuration, Uplink and Downlink speeds for a WAN Virtualization site may not load properly.
6. The Ecessa SIP proxy can become unresponsive when a call that is establishing contains multiple SDP media sections in the SIP signaling.
7. Session statistics for UDP sessions can show much higher usage than expected.
8. The Ecessa SIP proxy does not display statistics correctly for faxes that are proxied.
9. SIP proxy handling of SIP Cancel requests may fail.
10. Phones that modify our SIP VIA headers can cause SIP response packets to be dropped.
11. A configured PPPoE server may provide addresses outside the associated LAN subnet.
12. A configured PPPoE server uses an MTU of 1500 even if it is configured for a different value.
13. A VPN IPSec VTI security association can get into a state where it reports as UP traffic will not pass.
14. When remote connection from an IPsec VPN is closed, the VPN will not reinitiate the connection.
15. WAN Virtualization configurations where tunnels have high packet loss and the tunnel testing parameters are set high can cause the tunnel to bounce more often then the testing parameters.
16. Web Diagnostics ping timeout not working as expected.
17. SIP proxy configurations which use domain authentication can cause the system to crash when a call needs to fail over more than once.
18. SIP Proxy does not start properly after multiple Hardware Failovers.
19. Changing SIP Proxy port range can result in old rules being left in place.
20. Ecessa SNMP MIB file may not be accepted by SNMP monitoring programs due to syntax errors.
21. The Ecessa SIP proxy can become unresponsive when a high RTP port is used to establish a call.
22. Old DHCP addresses may silently remain on the device after a new one is received.
23. Using CLI to modify DNS records does not update zones properly.
24. Email alerts are not sent for expiring Self CA certificates after a certificate is renewed.
25. Diagnostics speed-test upload can fail if an aspx server is chosen.
26. Activating the WAN Virtualization advanced site Web UI page can display the wrong tunnel encryption selections.
27. SIP Proxy process can unexpectedly restart during initialization.
28. Within DNS domain configuration, Simple Host Records and Load Balanced Host Records mail entry should not be a dropdown menu.
29. Site-to-site VPN may attempt to use a WAN that is down.
30. Usage of PPPoE WANs can cause the system to restart.
31. A VTI VPN on an Ecessa device which is behind NAT will not be able to connect.
32. SRV record hostname error message is unclear.
33. WAN graphs will report double the expected throughput for encrypted WAN Virtualization receive traffic.
1. Virtual Product may boot slowly.
2. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
3. The DHCP service can stop unexpectedly.
4. The LCD display can become stuck and not display new information when keys are pressed.
5. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN security association entry which has no name.
6. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
7. 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.
8. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
9. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
10. DNS Reverse Zone may not work correctly for load-balanced hosts.
11. 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.
12. WAN Virtualization hub location cannot have a site number that is greater than 127.
13. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected.
14. IPSec VPN Failback option does not work as expected.
15. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
See Ecessa's full line of products and solutions
Ecessa Firmware Release Notes