Hello. Please note that we have several Grandstream WP820 in the office with Anveo. They all broke after this update. Outgoing calls drop after 20 seconds. No problem with incoming calls. All phones started to present that problem as soon as they go updated (sadly, I had auto-update set up in all phones, lesson learned).
We are reverting back to Firmware 184.108.40.206 to correct the issue. Could you please look into it?
Note: We have those phones used as remote extensions at multiple locations (different networks) and they all are presenting the same problem after the update. They all were working well before 3 days ago.
Please know that back in 2016 this already happened to one of your firmware:
Could you please take a debugging capture of an outgoing call on the WP820 on 220.127.116.11 and send it to us for analysis? On the WP820 web UI, go to Maintenance->System Diagnosis->Debug. Press “start” then perform the call until the issue is reproduced. Stop the capture and press “List” and download the package. Please also provide the device configuration. You can download the device configuration under Maintanence->Upgrade->Config file.
After upgrading a 18.104.22.168 device to 22.214.171.124 the primary SIP account lost registration. I have tried everything I can think of including a factory reset and total reconfiguration, but I can’t get the device to register with my FreePBX server. Any advice other than downgrade to the last firmware?
I cranked up the debugging on asterisk and I don’t see any requests coming in from the device. I can see REGISTER requests for other devices, but I’m getting nothing from the 126.96.36.199 hitting the log file at all.
Could you please download your device configuration (Maintanence->Upgrade->Config file) and attach it here for us to review? Is your FreePBX server located in your local network or on external network? Any special configurations?
Thanks for your help. Yes, the FreePBX server is on the same local network as the phone. There’s nothing special about the setup, just a basic PJSIP extension which the device registers to. I’m attaching the requested config file (had to ZIP it to allow upload).
I noticed in your config file you are using TLS for registration. That is a tricky one to troubleshoot. Here are some settings I suggest you try System Settings->Security Settings->TLS->Minimum TLS version set to “1.0.” If there’s any sort of certificate your using you may want to try re-uploading and reboot the device. Also under Account1->Advanced Settings->Only Accept SIP Requests from Known Servers, uncheck this feature for now. Try to see if these settings help. If the request isn’t going through likely the TLS handshaking is failing. If the settings don’t help, you would need to enabled debug syslog, then do the one click debugging to capture the logs for us.
No problem. I was looking through the release at the changes that may impact TLS. That seems the most likely culprit setting but yeah you should try to use systems that have TLS 1.1 as minimum (1.2 preferred) for better security.
127.0.0.8 is a loopback address (internal address) and is likely the culprit of why your WP820 isn’t able to route the ACK back to the server. I’m surprised if 188.8.131.52 can work fine in this scenario. Could you please check with your SIP provider on the contact URI?
After dialing a number, then pressing “Call”, a popup with two options “Audio call” and “Video call” appears. I have Enable Video Call uncheck in settings. I do not want people to see this “Video” option, just dial the number.
Hi, it seems we cannot save the configuration of Automatic Upgrade section. We tried to set Automatic Upgrade on, randomized on Sunday 0-23, then saved. Returning back on that page later, it had turned back as before with Automatic Upgrade set to off.
Hello. The very useful feature is permit scheduling reboot still unavailable. Some errors cannot be repaired until WP820 is restarted. Please add this feature as soon as possible. We are grateful for your assistance.