It is possible that SPA922 is using other option than SPA303. So at the first, you must found what option is triggering
src/dict_tftp.c: dictParseServerScp: 1501 script too short
error. Use option 150 but not option 66 and vice versa. It should reveal what option will cause the error.
Also, you should catch the DHCP server's response packet. It's nice to know Cisco 881's configuration, but the bug may be in Cisco 881 itself. If it's response is malformed (in option used by SPA922 but ignored by SPA303, or SPA303 may be more resistent to bug than SPA922) then it's waste of time to play with SPA922's configuration.
Welcome back for issue number 2 of the small business support community newsletter. Over the coming months we're going to share exciting news on the hardware and support community side. For now, we'll highlight our new favorite docs, pertinent...
Change in ASD Automatic Software Download Feature
Dec 13th, 2019
Cisco RV160, 260, 340, and 345 Series Routers
Due to an API change in Cisco’s software download platform the Automatic Download Feature (ASD) on RV series routers will be temporarily ...
SFP Module Support List for RV160x and RV260x Devices
Small form-factor pluggable (SFP) ports are included on the RV160 and 260 routers to allow the use of optical SFP transceiver modules. SFP’s convert the optical signals to electrical signals. SFP’s al...
Cisco is excited to offer its San Jose customers a unique opportunity to join us at Cisco headquarters for a design thinking workshop. This exclusive gathering, of no more than 20 people, is designed for an immersive interactive one-day session bet...