SPA 303 constantly upgrading firmware

Dataspeed — Mon, 05 Jul 2021 14:45:19 GMT

See the picture below. Once and hour, all 20 of my phones will do this. It lasts about 10 seconds. From time to time it will also say initializing network. Please help!

Re: SPA 303 constantly upgrading firmware

Flavio Miranda — Fri, 20 Oct 2017 00:14:19 GMT

Hi @Dataspeed

The pic is not available. Can you share it again?

-If I helped you somehow, please, rate it as useful.-

Re: SPA 303 constantly upgrading firmware

Dataspeed — Fri, 20 Oct 2017 14:29:19 GMT

The picture is a message that all phones display. It states: Upgrading Firmware Please do not unplug power Phone will reboot automatically.

All phones do this once every half hour

Re: SPA 303 constantly upgrading firmware

Flavio Miranda — Fri, 20 Oct 2017 15:01:55 GMT

Alright.

Where are you managing this IP phones ? Is it a Cisco solution or Third part solution?

Are you using PoE or DC plug?

Re: SPA 303 constantly upgrading firmware

Dataspeed — Fri, 20 Oct 2017 15:07:11 GMT

They are managed from a onsite freepbx server

DC plug

Re: SPA 303 constantly upgrading firmware

Flavio Miranda — Fri, 20 Oct 2017 15:15:42 GMT

Alright.

The first thing I´d try is validate the network. Starting from basic step, start a ping from a laptop to the freepbx with -t option and let this run for a while. When the Phone get the problem, make sure that you are not facing packet loss. This could justify your problem.

This is pretty basic but it is important. If you already did this, just ignore.

On the Freepbx, log in using SSH and enter with the command "asterisk -rvvvvv"

Keep the eye on the SSH output. When the phone drop out you must see some logs on it. Share this information here and I can try to help you.

-If I helped you somehow, please, rate it as useful.-

Re: SPA 303 constantly upgrading firmware

Dataspeed — Fri, 20 Oct 2017 16:30:58 GMT

This is all that showed up

Connected to Asterisk 13.7.1 currently running on dataspeedpbx (pid = 1838)
[2017-10-20 11:52:54] NOTICE[1910]: chan_sip.c:29381 sip_poke_noanswer: Peer '4104' is now UNREACHABLE! Last qualify: 10
-- Registered SIP '4104' at 10.20.1.103:5061
[2017-10-20 11:53:02] NOTICE[1910]: chan_sip.c:23945 handle_response_peerpoke: Peer '4104' is now Reachable. (5ms / 2000ms)
dataspeedpbx*CLI>

Re: SPA 303 constantly upgrading firmware

Flavio Miranda — Mon, 23 Oct 2017 12:19:14 GMT

Hi @Dataspeed

Although the logs is very short, it shows a Lag of 2000ms which is pretty high and we can see also the unreachable message.

Have you try to ping from server to IP phone? You may facing some network issue.

-If I helped you somehow, please, rate it as useful.-

Re: SPA 303 constantly upgrading firmware

Dataspeed — Wed, 01 Nov 2017 13:43:55 GMT

Please see below. Doesn't seem to be any issues

PING 10.20.1.115 (10.20.1.115) 56(84) bytes of data.
64 bytes from 10.20.1.115: icmp_seq=1 ttl=64 time=0.663 ms
64 bytes from 10.20.1.115: icmp_seq=2 ttl=64 time=0.598 ms
64 bytes from 10.20.1.115: icmp_seq=3 ttl=64 time=0.638 ms
64 bytes from 10.20.1.115: icmp_seq=4 ttl=64 time=0.596 ms
64 bytes from 10.20.1.115: icmp_seq=5 ttl=64 time=0.544 ms
64 bytes from 10.20.1.115: icmp_seq=6 ttl=64 time=0.602 ms
64 bytes from 10.20.1.115: icmp_seq=7 ttl=64 time=0.598 ms
64 bytes from 10.20.1.115: icmp_seq=8 ttl=64 time=0.598 ms
64 bytes from 10.20.1.115: icmp_seq=9 ttl=64 time=0.597 ms
64 bytes from 10.20.1.115: icmp_seq=10 ttl=64 time=0.590 ms
64 bytes from 10.20.1.115: icmp_seq=11 ttl=64 time=0.599 ms
64 bytes from 10.20.1.115: icmp_seq=12 ttl=64 time=0.598 ms
64 bytes from 10.20.1.115: icmp_seq=13 ttl=64 time=0.598 ms
64 bytes from 10.20.1.115: icmp_seq=14 ttl=64 time=0.599 ms
64 bytes from 10.20.1.115: icmp_seq=15 ttl=64 time=0.562 ms
64 bytes from 10.20.1.115: icmp_seq=16 ttl=64 time=0.602 ms
64 bytes from 10.20.1.115: icmp_seq=17 ttl=64 time=0.601 ms
64 bytes from 10.20.1.115: icmp_seq=18 ttl=64 time=0.600 ms
64 bytes from 10.20.1.115: icmp_seq=19 ttl=64 time=0.604 ms
64 bytes from 10.20.1.115: icmp_seq=20 ttl=64 time=0.536 ms
64 bytes from 10.20.1.115: icmp_seq=21 ttl=64 time=0.601 ms
64 bytes from 10.20.1.115: icmp_seq=22 ttl=64 time=0.601 ms
64 bytes from 10.20.1.115: icmp_seq=23 ttl=64 time=0.629 ms
64 bytes from 10.20.1.115: icmp_seq=24 ttl=64 time=0.601 ms
64 bytes from 10.20.1.115: icmp_seq=25 ttl=64 time=0.534 ms
64 bytes from 10.20.1.115: icmp_seq=26 ttl=64 time=0.606 ms
64 bytes from 10.20.1.115: icmp_seq=27 ttl=64 time=0.605 ms
64 bytes from 10.20.1.115: icmp_seq=28 ttl=64 time=0.603 ms
64 bytes from 10.20.1.115: icmp_seq=29 ttl=64 time=0.608 ms
64 bytes from 10.20.1.115: icmp_seq=30 ttl=64 time=0.534 ms
64 bytes from 10.20.1.115: icmp_seq=31 ttl=64 time=0.636 ms
64 bytes from 10.20.1.115: icmp_seq=32 ttl=64 time=0.604 ms
64 bytes from 10.20.1.115: icmp_seq=33 ttl=64 time=0.633 ms
64 bytes from 10.20.1.115: icmp_seq=34 ttl=64 time=0.603 ms
64 bytes from 10.20.1.115: icmp_seq=35 ttl=64 time=0.552 ms
64 bytes from 10.20.1.115: icmp_seq=36 ttl=64 time=0.606 ms
64 bytes from 10.20.1.115: icmp_seq=37 ttl=64 time=0.638 ms
64 bytes from 10.20.1.115: icmp_seq=38 ttl=64 time=0.605 ms
64 bytes from 10.20.1.115: icmp_seq=39 ttl=64 time=0.636 ms
64 bytes from 10.20.1.115: icmp_seq=40 ttl=64 time=0.536 ms
64 bytes from 10.20.1.115: icmp_seq=41 ttl=64 time=0.629 ms
64 bytes from 10.20.1.115: icmp_seq=42 ttl=64 time=0.608 ms
64 bytes from 10.20.1.115: icmp_seq=43 ttl=64 time=0.640 ms
64 bytes from 10.20.1.115: icmp_seq=44 ttl=64 time=0.605 ms
64 bytes from 10.20.1.115: icmp_seq=45 ttl=64 time=0.558 ms
64 bytes from 10.20.1.115: icmp_seq=46 ttl=64 time=0.604 ms
64 bytes from 10.20.1.115: icmp_seq=47 ttl=64 time=0.638 ms
64 bytes from 10.20.1.115: icmp_seq=48 ttl=64 time=0.609 ms
64 bytes from 10.20.1.115: icmp_seq=49 ttl=64 time=0.639 ms
64 bytes from 10.20.1.115: icmp_seq=50 ttl=64 time=0.620 ms
64 bytes from 10.20.1.115: icmp_seq=51 ttl=64 time=0.631 ms
64 bytes from 10.20.1.115: icmp_seq=52 ttl=64 time=0.632 ms
64 bytes from 10.20.1.115: icmp_seq=53 ttl=64 time=0.607 ms
64 bytes from 10.20.1.115: icmp_seq=54 ttl=64 time=0.640 ms
64 bytes from 10.20.1.115: icmp_seq=55 ttl=64 time=0.579 ms
64 bytes from 10.20.1.115: icmp_seq=56 ttl=64 time=0.636 ms
64 bytes from 10.20.1.115: icmp_seq=57 ttl=64 time=0.631 ms
64 bytes from 10.20.1.115: icmp_seq=58 ttl=64 time=0.636 ms
64 bytes from 10.20.1.115: icmp_seq=59 ttl=64 time=0.627 ms
64 bytes from 10.20.1.115: icmp_seq=60 ttl=64 time=0.574 ms
64 bytes from 10.20.1.115: icmp_seq=61 ttl=64 time=0.639 ms
64 bytes from 10.20.1.115: icmp_seq=62 ttl=64 time=0.615 ms
64 bytes from 10.20.1.115: icmp_seq=63 ttl=64 time=0.645 ms
64 bytes from 10.20.1.115: icmp_seq=64 ttl=64 time=0.615 ms
64 bytes from 10.20.1.115: icmp_seq=65 ttl=64 time=0.635 ms
64 bytes from 10.20.1.115: icmp_seq=66 ttl=64 time=0.614 ms
64 bytes from 10.20.1.115: icmp_seq=67 ttl=64 time=0.639 ms
64 bytes from 10.20.1.115: icmp_seq=68 ttl=64 time=0.616 ms
64 bytes from 10.20.1.115: icmp_seq=69 ttl=64 time=0.647 ms
64 bytes from 10.20.1.115: icmp_seq=70 ttl=64 time=0.608 ms
64 bytes from 10.20.1.115: icmp_seq=71 ttl=64 time=0.655 ms
64 bytes from 10.20.1.115: icmp_seq=72 ttl=64 time=0.617 ms
64 bytes from 10.20.1.115: icmp_seq=73 ttl=64 time=0.642 ms
64 bytes from 10.20.1.115: icmp_seq=74 ttl=64 time=0.617 ms
64 bytes from 10.20.1.115: icmp_seq=75 ttl=64 time=0.639 ms
64 bytes from 10.20.1.115: icmp_seq=76 ttl=64 time=0.621 ms
64 bytes from 10.20.1.115: icmp_seq=77 ttl=64 time=0.642 ms
64 bytes from 10.20.1.115: icmp_seq=78 ttl=64 time=0.621 ms
64 bytes from 10.20.1.115: icmp_seq=79 ttl=64 time=0.642 ms
64 bytes from 10.20.1.115: icmp_seq=80 ttl=64 time=0.534 ms
64 bytes from 10.20.1.115: icmp_seq=81 ttl=64 time=0.635 ms
64 bytes from 10.20.1.115: icmp_seq=82 ttl=64 time=0.618 ms
64 bytes from 10.20.1.115: icmp_seq=83 ttl=64 time=0.644 ms
64 bytes from 10.20.1.115: icmp_seq=84 ttl=64 time=0.615 ms
64 bytes from 10.20.1.115: icmp_seq=85 ttl=64 time=0.638 ms
64 bytes from 10.20.1.115: icmp_seq=86 ttl=64 time=0.649 ms
64 bytes from 10.20.1.115: icmp_seq=87 ttl=64 time=0.639 ms
64 bytes from 10.20.1.115: icmp_seq=88 ttl=64 time=0.621 ms
64 bytes from 10.20.1.115: icmp_seq=89 ttl=64 time=0.649 ms
64 bytes from 10.20.1.115: icmp_seq=90 ttl=64 time=0.556 ms
64 bytes from 10.20.1.115: icmp_seq=91 ttl=64 time=0.643 ms
64 bytes from 10.20.1.115: icmp_seq=92 ttl=64 time=0.649 ms
64 bytes from 10.20.1.115: icmp_seq=93 ttl=64 time=0.645 ms
64 bytes from 10.20.1.115: icmp_seq=94 ttl=64 time=0.644 ms
64 bytes from 10.20.1.115: icmp_seq=95 ttl=64 time=0.637 ms
64 bytes from 10.20.1.115: icmp_seq=96 ttl=64 time=0.625 ms
64 bytes from 10.20.1.115: icmp_seq=97 ttl=64 time=0.648 ms
64 bytes from 10.20.1.115: icmp_seq=98 ttl=64 time=0.649 ms
64 bytes from 10.20.1.115: icmp_seq=99 ttl=64 time=0.645 ms
64 bytes from 10.20.1.115: icmp_seq=100 ttl=64 time=0.556 ms
64 bytes from 10.20.1.115: icmp_seq=101 ttl=64 time=0.662 ms
^C
--- 10.20.1.115 ping statistics ---
101 packets transmitted, 101 received, 0% packet loss, time 100197ms
rtt min/avg/max/mdev = 0.534/0.613/0.663/0.045 ms
[root@dataspeedpbx ~]#

topic Re: SPA 303 constantly upgrading firmware in Wireless

SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware

Re: SPA 303 constantly upgrading firmware