Recent content by in2digital

We use it in this way too. The only values set in our GDMS device parameters are Fusionpbx config file URL, user and pass. However, we wanted to use GDMS platform device diagnostics for checking devices on sites where we don't have remote/VPN capabilities. Changing these TR-069 values in our...

Nope, it's TR-069 connection request username (should be device MAC without :- in uppercase). From GDMS support:

FusionPBX config. We use FusionPBX for provisioning, and GDMS platform for their device diagnostic tools which would all timeout prior to me changing the FusionPBX xml config.

I've had a chat with Grandstream GDMS support. They found an authorisation error from the device packet/syslog capture. To resolve this they mentioned that P4512 (TR-069 Connection Request Password) should be supplied and be the device MAC, so I added to the config template...

I've had this working for about 12 months but all my devices across multiple sites aren't able to be controlled by GDMS actions e.g. phone rebooting, factory defaulting, diagnostic tests. All the tasks just timeout. If the WAN drops at said sites I do get account unregistered/register/reboot...

This works - thanks. However if I try toggling using the BLF key it tries dialing flow+*30 which fails - do you know how I can add that to the phone dial plan?

Did you ever receive anything back?

Hi, I have an issue where after 30 seconds our BLF for Call Flows goes to green status, then to a red status and after another 30 seconds, then back to a green and so on... Call Flow extension is *30 In /etc/freeswitch/autoload_configs/lua.conf.xml I have "call_flow_monitor.lua" activated for...

Fixed by adding the below to the mac xml template.

Hi, In v4.5.22 it looks like the Grandstream GXV3275 .mac xml file for provisioning does not have the dynamic syntax to display defined FusionPBX > Devices > Keys. If I add any keys in FusionPBX > Devices it doesn't appear in the provisioning xml file, and I cannot see any syntax in the xml...