Firmware para SPA 400 1.0.0.c
Corrige un bug importante que fue reportado por Rosa de Avanzada7 y yo hice v铆nculo a Linksys.
Con cuatro llamadas simult谩neas por PSTN se quedaba colgado el SPA400.
-- since 1.0.0.11 --
. System reboot when a SIP CANCEL method is received from
SPA9000 after receiving SIP INVITE and before responding
to it with 200 OK response
-- since 1.0.0.9 --
. System crash under intensive incoming call storm from
FXO ports.
. Application code unload/reload does not completely
recover system back to stable running condition.
Problem results in system in a deal lock condition
failing to to respond to ICMP ping request, web
browser access request, and call request from FXO ports
and network. Problem fixed by replacing application
code unload/reload with system restart.
. Fail to respond to call request from FXO ports and network
when certain non-alphanumeric characters (including &, $,
#, (, ), [, ], {, }, |, and ',' (comma)) are included
in the display name of the From header or caller ID name.
Lo pod茅is descargar de la p谩gina de Linksys.
Con cuatro llamadas simult谩neas por PSTN se quedaba colgado el SPA400.
-- since 1.0.0.11 --
. System reboot when a SIP CANCEL method is received from
SPA9000 after receiving SIP INVITE and before responding
to it with 200 OK response
-- since 1.0.0.9 --
. System crash under intensive incoming call storm from
FXO ports.
. Application code unload/reload does not completely
recover system back to stable running condition.
Problem results in system in a deal lock condition
failing to to respond to ICMP ping request, web
browser access request, and call request from FXO ports
and network. Problem fixed by replacing application
code unload/reload with system restart.
. Fail to respond to call request from FXO ports and network
when certain non-alphanumeric characters (including &, $,
#, (, ), [, ], {, }, |, and ',' (comma)) are included
in the display name of the From header or caller ID name.
Lo pod茅is descargar de la p谩gina de Linksys.
