Firmware 1.0.7.5 for DP750/DP720/DP760 officially released

firmware-release

#1

Dear Grandstream Customers,

Firmware 1.0.7.5 for DP750/DP720/DP760 is now released as official. Here is the link to the release notes:
http://firmware.grandstream.com/Release_Note_DP7xx_1.0.7.5.pdf

The firmware and release notes can be downloaded from: http://www.grandstream.com/support/firmware

Please contact us should you have any issues. Thank you for your support for Grandstream products.

Technical Support
Grandstream Networks, Inc.


#2

#3

BUG.

35%20PM


#4

Refresh browser (CTRL +F5). It is typical bug if you have old cache.


#5

I have just upgraded to 1.0.7.5 on my DP750/720’s and tried to migrate my config to the latest config-template however most of the configuration will not import

The information provided says the phones should still function using either the P Codes or the new format for example “Pnetwork.type” however this doesn’t appear to be the case.

When exporting the blank config for the phone it mainly appears in the new format.

Is there a new config template using the new coding solution?


#6

The P-codes used in DP750 will work. It’s the same firmware. The new config format is coming soon but I know they are working on implementing it on every phone. This is gonna help a lot of people with provisioning!

You just need to add the few ones that are specific to DP752/722/730 like PTT.


#7

With the DP750 my original config works perfectly fine under 1.0.4.10. When the base upgraded to 1.0.7.5 it lost half the configuration.

Every time I try to import the configuration including copying my settings to the new template file the same settings are missing every time for example. If I use P6713 the config remains blank. If I use Pphonebook.global.xml.auto.username

It appears correctly.


#8

Sounds like their aliases are not working correctly.

Get a syslog of when you upload the config file so they can check where it’s happening.


#9

I do any setting of the phones entirely from scratch configuring with my own “P” and I never have problems.


#10

Just looking in a bit more depth. Appears the Admin Code: P27008 is not saving via GUI and is not in the config when exported. Cant find anything regarding it being removed.

DP750 > Dect > General Settings.


#11

You mean the Admin PIN?

Have you tried using the latest beta? See if the result is different, they might have fixed a few things.


#12

BUG

The Admin Code: P27008 is not saving via GUI and is not in the config when exported. Cant find anything regarding it being removed.

DP750 > Dect > General Settings.

Same in the Beta Version 1.0.9.1


#13

on zero config there is the right place to insert the admin pswd to send to the terminals, what’s the point of creating a “P”?


#14

If you are referring to the zero config template files or auto provisioning, that is exactly what I am doing.

However the template file contains all of the following however the phone will not save or export config files containing the following?

Maybe its something I’m missing

#Admin PIN Code. Sets the admin PIN code for authentication, default is 0000.
#Number: 4 digit number
#Mandatory
P27008=0000

Same issue with

P4120 to P4129 which is the sip account passwords
P196 User Password
P2 Admin Password

its pointless it being there as the firmware does not even know what to do with it. Web GUI does not save it, and exporting in txt or xml does not contain the setting at all


#15

The PIN code and all the password will not be included in the downloaded XML file for security concerns, we are working on a feature request that to include these password fields, but in encrypted format.

As for now, you will need manually add the P values: Pxxxx=xxxx into the txt file, save it, and use it to import to back up. Be safe.

Edit: if it’s XML file, use <Pxxx>xxx</Pxxx>


#16

Thank you for the clarification Shawn.

I genuinely did not see anything regarding this in the revision notes.


#17

#18

Having similar problems … Upgraded to 1.0.9.1 and nothing worked like when we were on 1.0.4.10

I downgraded to 1.0.7.5 and still have the same problem. The DP750 downloads the cfg.xml from the webserver, but NONE of it applies to the device.

I enabled syslogging to our server and I see a problem there when I manually upload XML file that we KNEW worked on 1.0.4.10, but now does not work on 1.0.7.5:

2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume kernel_image on dev mtd16 with mtd partition /dev/mtd6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume root_squash on dev mtd10 with mtd partition /dev/mtd7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume app_squash on dev mtd11 with mtd partition /dev/mtd8
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume lcl_squash on dev mtd13 with mtd partition /dev/mtd8
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume oem_squash on dev mtd12 with mtd partition /dev/mtd8
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume hs_squash on dev mtd14 with mtd partition /dev/mtd8
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Found a UBI volume recovery_image on dev mtd17 with mtd partition /dev/mtd4
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for uboota is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for ubootb is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for core is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for base is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for prog is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for prog is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for prog is = 0
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for prog is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Current partition upgrade counter for recovery is = 6
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Selecting BACKUP boot for upgrading.(M:6 / B:6)
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for uboota will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for ubootb will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for core will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for base will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for prog will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for prog will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for prog will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for prog will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: New partition upgrade counter for recovery will be = 7
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: provision is running online
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: opened file:///tmp/local_cfg_file ( len 476459 )
2019 Apr 10 21:19:02  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: setup image source type file
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP7500 0  PROVISION: md5sum: dd58208bdcc3265769dc7d93c463e46b
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP7500 0  PROVISION: ERROR 246
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Parsing XML configuration failed
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: config update not completed
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: opened file:///tmp/local_cfg_file ( len 476459 )
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: setup image source type file
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: config file decryption error
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: unable to qualify config data
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: config update not completed
2019 Apr 10 21:19:03  172.27.122.135     user.notice    DP750 [00:0B:82:GH:IJ:KL] [1.0.7.5]PROVISION: Config upload failed

The key parts probably being:
2019 Apr 10 21:19:03 172.27.122.135 user.notice DP7500 0 PROVISION: md5sum: dd58208bdcc3265769dc7d93c463e46b
2019 Apr 10 21:19:03 172.27.122.135 user.notice DP7500 0 PROVISION: ERROR 246


#19

I also find it curious why the DP750 added “Use Random SIP Port” P-Values that are not the same P-Values as all the other devices that already support this?

They decided to use P20501-P20504 for this, when P78, P778, P578, and P4792 were already defined.


#20

could you please send us the cfg.xml file? it’s the file’s md5sum error, not the one that some p values not take effect after provisioning, the later one we already fixed in 1.0.9.6 (Beta release at the moment)