Connect disconnect and too time out ping time in WP810

#1

We have 50 WP810 devices and we have been using them for 6 months
Our wireless is UNIFI AC Pro, of which there are 20 in the collection
We have a problem with WP810 devices that are constantly disconnected and reconnected
Ping time has a lot of fluctuation .that are in the same access point of other devices (such as laptops or systems) with a ping time of less than 1 are working without interruption and …
The device firmware is also the latest official version, please help

i’m test
Enable OPTIONS Keep Alive
OPTIONS Keep Alive Interval

i’m test in beta Firmware
WP810 1.0.11.2

i’m test stable Firamware
WP810 1.0.9.23

but not OK this Problem
I’m Use KERIO OPERATOR SIP Server

[01/May/2022 07:30:34] Extension “213” is not registered (offline).
[01/May/2022 07:30:55] Extension “213” is registered (online) at IP using Grandstream WP810 1.0.11.2.
[01/May/2022 07:31:25] Extension “275” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:33:29] Extension “204” is not registered (offline).
[01/May/2022 07:33:55] Extension “204” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:36:30] Extension “271” is not registered (offline).
[01/May/2022 07:36:55] Extension “271” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:41:06] Extension “254” is not registered (offline).
[01/May/2022 07:41:25] Extension “254” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:41:36] Extension “275” is not registered (offline).
[01/May/2022 07:41:56] Extension “275” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:42:28] Extension “203” is not registered (offline).
[01/May/2022 07:42:28] Extension “245” is not registered (offline).
[01/May/2022 07:43:17] Extension “203” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:43:25] Extension “245” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:44:35] Extension “220” is not registered (offline).
[01/May/2022 07:45:18] Extension “220” is registered (online) at IP using Grandstream WP810 1.0.9.23.
[01/May/2022 07:47:05] Extension “213” is not registered (offline).
[01/May/2022 07:47:26] Extension “213” is registered (online) at IP using Grandstream WP810 1.0.11.2.

#2

Hi guys,

I’m experiencing the same issue. I’m using the phone with an TP-Link Omada WIFI infrastructure and FreePBX/Asterisk PBX.

  == Endpoint xx is now Reachable
    -- Contact xx/sip:xx@192.168.x.x:27748 is now Reachable.  RTT: 125.387 msec
  == Endpoint xx is now Unreachable
    -- Contact xx/sip:xx@192.168.x.x:27748 is now Unreachable.  RTT: 0.000 msec
  == Endpoint xx is now Reachable
    -- Contact xx/sip:xx@192.168.x.x:27748 is now Reachable.  RTT: 5.173 msec
  == Endpoint xx is now Unreachable
    -- Contact xx/sip:xx@192.168.x.x:27748 is now Unreachable.  RTT: 0.000 msec
  == Endpoint xx is now Reachable
    -- Contact xx/sip:xx@192.168.x.x:27748 is now Reachable.  RTT: 9.586 msec

Also the ping, block wise, is very high:

64 bytes from <fqdn> (192.168.x.x): icmp_seq=883 ttl=64 time=32.3 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=884 ttl=64 time=420 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=885 ttl=64 time=647 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=886 ttl=64 time=110 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=887 ttl=64 time=487 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=888 ttl=64 time=409 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=889 ttl=64 time=637 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=890 ttl=64 time=96.4 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=891 ttl=64 time=8563 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=892 ttl=64 time=7550 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=893 ttl=64 time=6527 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=894 ttl=64 time=5503 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=895 ttl=64 time=4479 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=896 ttl=64 time=3455 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=897 ttl=64 time=2431 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=898 ttl=64 time=1407 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=899 ttl=64 time=383 ms
64 bytes from <fqdn> (192.168.x.x): icmp_seq=900 ttl=64 time=203 ms

For a notebook standing next to the device the ping is constantly fine. I’ve no WIFI problems with any other devices in the network.

Looking at the package traces I made on the WP810 and the PBX it looks like the following:

On the PBX: Request SIP Options to WP810? -> wait ~ 500-1000ms -> Request SIP Options to WP810? -> wait ~ 500-1000ms -> Request SIP Options to WP810? -> delay up to seconds -> Response Status 200 OK -> Response Status 200 OK -> Response Status 200 OK

On the WP810: Request SIP Options to WP810? -> Request SIP Options to WP810? -> Request SIP Options to WP810? -> 1-2ms -> Response Status 200 OK -> Response Status 200 OK -> Response Status 200 OK

Sometimes I can see some of these events for the pone in the Omada Controler logs:

[Failed]<WP810> failed to connected to AP <name> with SSID "<SSID>" on channel 13 because WPA Authentication times out/failed.(3 times in a minute)

On different AP’s and on different channels.

So on the PBX it looks like the initial SIP Options request is resend after 500-1000ms after getting no response from the WP810. On the WP810 it looks like the PBX is sending the request 3 times one after another and it respondes 3 times.

I’m struggling now for month with call terminations and unavailability on the WP810 always using the latest available firmware (including beta). Currently I’m using v1.0.11.22.

#3

Hi! Did You solve this problem?

I have more than 20 WP810, WP822 in different network environments and the problem is exactly as you described. Firmware up to date.I stopped offering grandtream to my clients because I have to replace all the phones and they are not cheap :frowning:
Grandstream washes hands of this.