- Joined
- Jul 22, 2019
- Messages
- 4
- Reaction score
- 0
Good afternoon,
We've noticed an issue with the Grandstream GPX2130 & 40 devices were phones get assigned a 0.0.0.0 IP address in the 3CX console and become unusable. These phones need to be manually rebooted either physically or by the console. These are not accessible via the 3CX console and can only be viewed.
When the phone is then rebooted the phones are assigned an IP via DHCP from the 3CX server on a VOIP VLAN. The IP is picked up, but the subnet is blank and will eventually drop out again. But the phone is usable whilst it is active and connection to the 3CX console is established again.
When the phone is factory reset, in between the phone rebooting to apply firmware and cfg, the network status shows all the correct information within the network status page. Once it reboots they are all then lost again and then the waiting game again begins for when the phone may drop out again.
This issue does not occur on the Yealink devices we have and all network settings show.
For testing we raised another DHCP server with a different subnet range and brought up a Grandstream within this scope but the issue persisted through.
Cheers,
Rob.
We've noticed an issue with the Grandstream GPX2130 & 40 devices were phones get assigned a 0.0.0.0 IP address in the 3CX console and become unusable. These phones need to be manually rebooted either physically or by the console. These are not accessible via the 3CX console and can only be viewed.
When the phone is then rebooted the phones are assigned an IP via DHCP from the 3CX server on a VOIP VLAN. The IP is picked up, but the subnet is blank and will eventually drop out again. But the phone is usable whilst it is active and connection to the 3CX console is established again.
When the phone is factory reset, in between the phone rebooting to apply firmware and cfg, the network status shows all the correct information within the network status page. Once it reboots they are all then lost again and then the waiting game again begins for when the phone may drop out again.
This issue does not occur on the Yealink devices we have and all network settings show.
For testing we raised another DHCP server with a different subnet range and brought up a Grandstream within this scope but the issue persisted through.
Cheers,
Rob.
Last edited: