Toggle sidebar Toggle sidebar
  • We do not provide troubleshooting help for unsupported phones. Please try with a supported phone.
  • V20 Update 10 Alpha 2 Learn more

Grandstream GDS37 Series | Configuration Guide

Status
Not open for further replies.
KaterinaK_3CX

KaterinaK_3CX

Joined
Feb 24, 2016
Messages
246
Reaction score
36
Supported models:
  • Grandstream GDS3705 - available in V16 Update 6 or above
  • Grandstream GDS3710 - available in V16 Update 6 or above
Read the guide.
 
Provisioning is function, but reprovisioning delete important value: "Number Called When Door Bell Pressed" ! I have to provisioning off, than OK. Tested today.
 
JanBa said:
Provisioning is function, but reprovisioning delete important value: "Number Called When Door Bell Pressed" ! I have to provisioning off, than OK. Tested today.
Click to expand...
Hi!

We mention this in Step 3.5:
Go to the “BLF” tab and assign a Speed Dial to the first entry. This will be the number that is automatically dialed when the Doorbell button is pressed on the device.
 
  • Like
Reactions: JanBa
Ok, thanks.
 
Hi,

We have 3CX v18 operational running in house, Linux vm.

We have one GDS3705. The Grandstream team have asked me to update the firmware from 1.0.1.6 to 1.0.3.10 to overcome some problems with settings retention. The device is randomly losing settings currently and I would like to solve that problem.

The 3CX documentation refers to version 1.0.1.6 as the supported firmware version.

I'm not sure what is the best approach here. Take the advice from Grandstream or 3CX?

Your advice is appreciated.

Regards.
 
StuNor said:
The 3CX documentation refers to version 1.0.1.6 as the supported firmware version.

I'm not sure what is the best approach here. Take the advice from Grandstream or 3CX?
Click to expand...
The newer versions have not yet been released to 3CX - as soon as Grandstream provides them we will publish them for your 3CX system.
 
Hi John,

I understand your point.

I can update the firmware manually though, even if it is not published by 3CX. Do you think that would create an incompatible combination between the new Grandstream firmware and 3CX?

I don't want to break the operation by introducing firmware unvetted by 3CX. Is this a concern? Does the 3CX team closely vet new device firmware before it is published to confirm its compatibility with 3CX?

Thanks for your advice.
 
The firmware is tested by the manufacturer on a 3CX system before it is released to us, and we also perform some tests to confirm basic functionality is solid.

While rare, bugs do sometimes crop up so I cannot say for sure that the latest version is fully compatible. Regardless, we have informed Grandstream and they will try to test the firmware soon so we can also release it here.
 
Thank you John.

I appreciate your help and advice and I'll watch for the release of that version.
 
  • Like
Reactions: JohnS_3CX
StuNor said:
Thank you John.

I appreciate your help and advice and I'll watch for the release of that version.
Click to expand...
Did you ever get this device to work? I had a 3710 on Ring Central and it worked flawlessly for 3 years and died. So I replaced with with the 3705 and cannot get it to work. I am wondering if it is a model issue or RC issue.

I was going to try to test it on our 3cx, then I found this, which is disheartening. I too have the latest firmware. But it seems like I have no recourse to get this to work at this point unless you got it to work.
 
Hi kynetguy,

My problem is that it doesn't keep some settings changes permanently. It only keeps an admin password change for one login and then defaults back to a system generated one. Thankfully it's a strong one, but I have to retrieve it using the 'Forgot Password' link.

It also periodically loses the 'Number Called When Door Bell Pressed' setting and it reverts to the extension number I used for testing before I installed it. I know when that happens because that test number was my extension and I get the call.

Apart from that it is working fine with firmware v10.0.1.6. Although Grandstream have asked me to update the firmware to v10.0.3.10 I haven't done that yet. I'm waiting for the normal approval process to occur between Grandstream and 3CX that John described. I don't have the nerve to upgrade it before that happens. Perhaps that is silly but I'll wait a little longer as it is working ok as I mentioned.
 
Hi kynetguy,

Your question prompted me to review the setup guide and this discussion and I had forgotten that I had setup a number in the BLF field for the device in the 3CX console, guide step 3.5. That was still set to my test extension so that must be why the device is being set with that number. I've corrected that now and I'll see what happens.
 
  • Like
Reactions: kynetguy
StuNor said:
Hi kynetguy,

My problem is that it doesn't keep some settings changes permanently. It only keeps an admin password change for one login and then defaults back to a system generated one. Thankfully it's a strong one, but I have to retrieve it using the 'Forgot Password' link.

It also periodically loses the 'Number Called When Door Bell Pressed' setting and it reverts to the extension number I used for testing before I installed it. I know when that happens because that test number was my extension and I get the call.

Apart from that it is working fine with firmware v10.0.1.6. Although Grandstream have asked me to update the firmware to v10.0.3.10 I haven't done that yet. I'm waiting for the normal approval process to occur between Grandstream and 3CX that John described. I don't have the nerve to upgrade it before that happens. Perhaps that is silly but I'll wait a little longer as it is working ok as I mentioned.
Click to expand...

The one I am dealing with is connected to Ring Central and not working at all the way I need. I need it to call two numbers in serial. It will only call the first one. Which is why I am planning on testing this on 3cx to see what happens. I will likely just try it with the current firmware and set it to not upgrade and see what happens before downgrading it.

Both numbers would be external to the 3cx system. I guess I could always setup extensions that forward out to an external number when set Away and leave them that away.

You mentioned the BLF. So that is not a necessary setting? The way things were reading, it seemed to be needed to get it to dial out.
 
I agree that it is specified to be set as a BLF in the 3CX guide. Therefore I believe it to be necessary. I have not tested to prove it.

The mistake I made was setting a value on the device and not letting 3CX perform its job. The setting that I made on the device was in conflict with the BLF value. They were different extensions. The BLF value was being pushed to the device and I had forgotten I had set it. This led to my confusion about the device losing the setting.

I also have the call going to a group in 3CX. If you had a group consisting of both your numbers you could achieve the same result. In 3CX I have set the BLF to a Custom Speed Dial and set the group number. I've attached a screenshot for you.

Now that I have corrected the extension number in the BLF setting it is being sent to the device and is stable. It continues to operate well.
 

Attachments

  • DoorPhoneBLF.PNG
    DoorPhoneBLF.PNG
    7.6 KB · Views: 30
Nope, only the ones mentioned above
 
  • Like
Reactions: MorlingCollege and dgeene
  • Like
Reactions: MorlingCollege and rbalderaz80
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,147
Messages
590,961
Members
165,167
Latest member
Finatra.us
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom