Plantronics + Polycom. Now together as Poly Logo

VVX 300 Fails on last 512 Bytes of Provisioning

SOLVED
Occasional Visitor

VVX 300 Fails on last 512 Bytes of Provisioning

Hello,

 

I've got a VVX 300, MAC: 64167F98A946 that we've formatted the file system on. It's currently at version 5.9.7. We use Polycom phones with Jive.

 

The phone doesn't boot, providing 'Application not Found'. I've turned my laptop into a TFTP server that the phone can connect to and download its goodies from, but while it downloads 3111-46161-001.sip.ld, it fails on the last 512 bytes.

Here's the bootlogs:

1011144559|cfg  |*|00|Prov|Starting to provision
1011144559|cfg  |3|00|Prov|Starting to download file 64167f98a946.cfg
1011144559|copy |3|00|[performRedundant] proxy mode '7'
1011144559|sec  |4|00|utilCryptoLightBufferDecrypt: Bad parameters
1011144559|copy |3|00|[connectToProxy] Proxy not supported for mode '7'
1011144559|copy |3|00|'tftp://10.20.64.85/64167f98a946.cfg' from '10.20.64.85'
1011144559|copy |3|00|cfgProvSrvTypeGet()[0]
1011144559|copy |3|00|UtilCopyC::performCurl status data is:avgUploadSpeed(0.000000), uploadSize(0.000000), connTime(0.000000), totalTime(0.026223), ftpEntryPath(NULL)
1011144559|copy |3|00|Download of '64167f98a946.cfg' succeeded on attempt 1 (addr 1 of 1)
1011144559|cfg  |3|00|Prov|Updated file 64167f98a946.cfg
1011144559|cfg  |*|00|Prov|Starting to update 3111-46161-001.sip.ld
1011144559|copy |3|00|[performRedundant] proxy mode '7'
1011144559|sec  |4|00|utilCryptoLightBufferDecrypt: Bad parameters
1011144559|copy |3|00|[connectToProxy] Proxy not supported for mode '7'
1011144559|copy |3|00|'tftp://10.20.64.85/3111-46161-001.sip.ld' from '10.20.64.85'
1011144559|copy |3|00|cfgProvSrvTypeGet()[0]
1011144559|cfg  |3|00|New load header information:
1011144559|cfg  |3|00|Code length:         0x02C5E778
1011144559|cfg  |3|00|Code Checksum:       0x2855D4B9
1011144559|cfg  |3|00|Options:             0x00000080
1011144559|cfg  |3|00|Recognized container image
1011144559|cfg  |3|00|New load header information:
1011144559|cfg  |3|00|Code length:         0x0072FA40
1011144559|cfg  |3|00|Code Checksum:       0x3B34CCB9
1011144559|cfg  |3|00|Options:             0x00000010
1011144559|cfg  |3|00|Updater is already present
1011144559|cfg  |3|00|Updater in container image 1 is not different
1011144559|cfg  |3|00|New load header information:
1011144559|cfg  |3|00|Code length:         0x0252DFB0
1011144559|cfg  |3|00|Code Checksum:       0x2854E58B
1011144559|cfg  |3|00|Options:             0x00000002
1011144559|cfg  |3|00|Could not open application file for checking
1011144559|cfg  |3|00|Application in container image 2 is different
1011144559|cfg  |3|00|Using application
1011144617|cfg  |*|00|Prov|Updating the Application
1011144617|cfg  |3|00|Using compatible image 0
1011144754|copy |3|00|UtilCopyC::performCurl status data is:avgUploadSpeed(0.000000), uploadSize(0.000000), connTime(0.000000), totalTime(115.103397), ftpEntryPath(NULL)
1011144754|copy |3|00|Download of '3111-46161-001.sip.ld' succeeded on attempt 1 (addr 1 of 1)
1011144754|cfg  |4|00|Could not get all 38986508 bytes of the file (got 38985996 bytes)
1011144755|cfg  |4|00|Prov|File 3111-46161-001.sip.ld failed to download
1011144755|app1 |4|00|Error downloading 3111-46161-001.sip.ld
1011144755|cfg  |3|00|Prov|Image has not changed
1011144755|cfg  |4|00|Prov|Provisioning failed
1011144755|app1 |6|00|Error application is not present.
1011144755|app1 |6|00|Uploading boot log, time is Fri Oct 11 14:47:55 2019

1011144755|cfg  |*|00|Prov|Finished updating configuration
1011144755|copy |3|00|[performRedundant] proxy mode '7'
1011144755|sec  |4|00|utilCryptoLightBufferDecrypt: Bad parameters
1011144755|copy |3|00|[connectToProxy] Proxy not supported for mode '7'
1011144755|copy |3|00|'tftp://10.20.64.85/64167f98a946-boot.log' to '10.20.64.85'
1011144755|copy |3|00|cfgProvSrvTypeGet()[0]
1011144755|copy |3|00|UtilCopyC::performCurl status data is:avgUploadSpeed(331903.000000), uploadSize(92871.000000), connTime(0.000000), totalTime(0.279813), ftpEntryPath(NULL)
1011144755|copy |3|00|Upload of '64167f98a946-boot.log' succeeded on attempt 1 (addr 1 of 1)
1011144800|app1 |5|00|Unknown provisioning state 45.
1011144800|app1 |3|00|Event: Multiple Key Combo 1
1011144800|app1 |6|00|Manual Reboot
1011144808|wdog |*|00|Watchdog Expired: tApp1, 3084

While the phone downloads the sip.ld. file the phone's display transitions from 'Updating ... sip.ld. Please Wait..' to 'Downloading new application', and the bar visually appears to fill completely, but when it reaches the end the phone immdiately displays the 'Application not found' error and restarts.

 

Thank you for your time,

 

Message 1 of 3
2 REPLIES 2
Polycom Employee & Community Manager

Re: VVX 300 Fails on last 512 Bytes of Provisioning

Hello @BrianV ,

 

Welcome to the Poly Community.

 

Please do not use a TFTP server. Use FTP instead.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier




<======== Signature / Disclaimer ========>
Please be aware:For questions about the type of support to expect please check here

Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

The title Polycom Employee & Community Manager is an automatic setting within the community and any forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Poly employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and maybe answered on weekends, bank holidays or personal holidays.
Message 2 of 3
Highlighted
Occasional Visitor

Re: VVX 300 Fails on last 512 Bytes of Provisioning

Hi @SteffenBaierUK,

 

Thank you for your reply. That did the trick! 

 

I did encounter a reboot loop on the same VVX 310 while I was trying to install 5.9.4 onto it. It would launch the application successfully once and then any reboot requests would cause it to be caught in a reboot loop.

This was resolved by pointing the FTP server to 5.5.4 combined. After that, the phone successfully downloaded and installed the application and behaved normally.

 

Again, thanks for the help.

 

Message 3 of 3