Plantronics + Polycom. Now together as Poly Logo

prov.usercontrol.enabled is not working as expected in 5.3.3

Member

prov.usercontrol.enabled is not working as expected in 5.3.3

Hi,

 

i have enable prov.polling and prov.usercontrol tags for polycom VVX 500 in 5.3.3 firmware. To update the phone to higher version, but i am not getting any option to postpone the update!

 

I have tried with polling mode relative and absolute but no luck still phone updating at the defined time without intimating. did I miss anything? please advice.... 

 

Here is the last log before phone restart

 

Spoiler
0728183600|copy |*|00|Server 'xxx.xxx.xxx.xxx' said 'CDK/test_kiran/0004f2804af6.cfg' is not present
0728183600|cfg |*|00|Prov|Starting to update 5.4.4revE/3111-44500-001.sip.ld
0728183601|cfg |*|00|Prov|Updating the Updater
0728183601|cfg |*|00|Prov|Image has been changed
0728183602|copy |*|00|Server 'xxx.xxx.xxx.xxx' said 'CDK/test_kiran/overrides/0004f2804af6-web.cfg' is not present
0728183603|copy |*|00|Server 'xxx.xxx.xxx.xxx' said 'CDK/test_kiran/0004f2804af6-license.cfg' is not present
0728183603|cfg |*|00|Prov|Provisioning needs to reboot to upgrade image(s)
0728183603|app1 |*|00|Event: Multiple Key Combo 1
0728183603|app1 |*|00|Manual Reboot
0728183603|cfg |*|00|Prov|Finished updating configuration
0728183603|ldap |4|00|ldapXfer::start:xferStart failed cState=-1
0728183603|app1 |*|00|AppC::appReboot cDynamicData shutdown complete
0728183603|cap |4|00|[SoVidVideoCaptureManagerC::captureFrameAndProcessLoop][ERROR] No active camera channel found! noActiveCameraChanCt=5
Message 1 of 7
6 REPLIES 6
Member

Re: prov.usercontrol.enabled is not working as expected in 5.3.3

Hello,

 

I am waiting for your word... is it possible for the user to control the firmware on VVX and sountpoint and soundstation?

 

Thanks in advance

Ansuman Manna

Message 2 of 7
Polycom Employee & Community Manager

Re: prov.usercontrol.enabled is not working as expected in 5.3.3

Hello Ansuman Manna,

welcome to the Polycom Community.

The community's is run by volunteers so you simply need to be patient and wait until someone replies.

 

If you are unable to wait and you need support you need to open a support ticket.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you. In case this is some sort of an Internet discounter please post your phone's MAC address so I can look up who would be able to support you.

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

Best Regards

Steffen Baier

Polycom Global Services




<======== 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 3 of 7

Re: prov.usercontrol.enabled is not working as expected in 5.3.3

Did you ever find a solution for this?

Im finding that prov.usercontrol.enabled="1" is also non-functional for us.

tried it on 5.4.4 and 5.4.5, but i get absolutely no control over delaying an update.

methodology here is:
Polling
new config file (which says which firmware to pull)
reboot
downloads new updater
reboots
downloads new firmware
but no prompt to stay on the same version or delay is shown on the VVX sets themselves.

Message 4 of 7
Polycom Employee & Community Manager

Re: prov.usercontrol.enabled is not working as expected in 5.3.3

Hello Stephen

I can only give you the same advise as the original poster

Replied via a mobile device



<======== 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 5 of 7
Highlighted
Polycom Employee & Community Manager

Re: prov.usercontrol.enabled is not working as expected in 5.3.3

Hello all,

 

not making any modifcations to the master configuration file aka <mac>.cfg and only having a limited configuration:

 

prov.polling.enabled="1"
		prov.polling.mode="rel"
		prov.polling.period="3610"
		prov.userControl.enabled="1"
		prov.userControl.postponeTime="00:15"
		reg.1.address="3050"
		reg.1.auth.userId="3050"
		reg.1.server.1.address="10.252.122.122"

My phone "pulls" after around 1h the new firmware that I placed into the directory after booting and then displays as follows:

 

VVX_SoftwareUpdate_01.PNG

 

Pressing Details will show:

 

VVX_SoftwareUpdate_02.PNG

 

There even appears a new SoftKey:

 

VVX_SoftwareUpdate_03.PNG

 

The logs show:

 

0104152835|cfg  |1|00|Prov|cfgProvLocalPollTimer: Next rel poll in 3610 seconds, next timer event 3610 seconds
0104152835|cfg  |*|00|Prov|Starting to provision
0104152836|cfg  |2|00|Prov|Starting to provision master configuration file
0104152836|cfg  |3|00|Prov|Starting to download file 0004f2ac89bb.cfg
0104152836|cfg  |3|00|Prov|File 0004f2ac89bb.cfg has not changed
0104152836|cfg  |3|00|Prov|Starting to download file 000000000000.cfg
0104152836|cfg  |3|00|Prov|Updated file 000000000000.cfg
0104152836|cfg  |*|00|Prov|Starting to update 3111-44600-001.sip.ld
0104152836|cfg  |3|00|Reading 3111-44600-001.sip.ld into RAM, this may take a while...
0104152836|cfg  |2|00|Buffered download init OK with URL 'ftp://551d:PlcmSpIp@10.252.149.100/3111-44600-001.sip.ld'
0104152836|cfg  |1|00|New id is d76baad8, old is b56ccddc
0104152836|cfg  |3|00|New load header information:
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|Magic Number:        0xFFFFFFFF
0104152836|cfg  |3|00|Code length:         0x02F27AD4
0104152836|cfg  |1|00|Offset:              0x0000013C
0104152836|cfg  |1|00|Destination Address: 0x00000000
0104152836|cfg  |1|00|Executable Address:  0x00000000
0104152836|cfg  |3|00|Header Checksum:     0x4126E5DF
0104152836|cfg  |3|00|Code Checksum:       0x3E3469CF
0104152836|cfg  |1|00|Next Header Offset:  0x00000000
0104152836|cfg  |3|00|Options:             0x00000080
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|Good header checksum
0104152836|cfg  |3|00|Application version of new load  on server = '5.5.0.20556'
0104152836|cfg  |1|00|hwBoardImageHdrCompare returned 0x0 0x0 from string Phy=16384;Lcd2=2;TargetFlash=64;Config=11;Dsp=1024;NandEcc=8;SigKey=1;Key=8388608;Lcd=2437939200;Region=14;Cpu=2048;Gpio=2147483648;AppType=1;Flash=524288;Iter=A;Gpio2=296;PhoneType2=5;Checksum=0x00004fdc;
0104152836|cfg  |1|00|imageCompatibility is 0x0 0x0
0104152836|cfg  |3|00|Recognized container image
0104152836|cfg  |1|00|Attempting to realloc from 0 to 128 bytes
0104152836|cfg  |1|00|Realloc OK of 128 bytes, address: 0x1c3ffc0
0104152836|cfg  |2|00|Container image 1 header 0x3b4 0x1cc 0x1cc 0x0
0104152836|cfg  |1|00|Attempting to realloc from 128 to 512 bytes
0104152836|cfg  |1|00|Realloc OK of 512 bytes, address: 0x1c32398
0104152836|cfg  |3|00|New load header information:
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|Magic Number:        0xFFFFFFFF
0104152836|cfg  |3|00|Code length:         0x0076F594
0104152836|cfg  |1|00|Offset:              0x000001CC
0104152836|cfg  |1|00|Destination Address: 0x00000000
0104152836|cfg  |1|00|Executable Address:  0x00000000
0104152836|cfg  |3|00|Header Checksum:     0x3DCDC125
0104152836|cfg  |3|00|Code Checksum:       0x3D56C9C5
0104152836|cfg  |1|00|Next Header Offset:  0x00000000
0104152836|cfg  |3|00|Options:             0x00000010
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|hwBoardImageHdrCompare returned 0x0 0x0 from string Iter=A;BuildID=18267;SigKey=1;Config=11;Cpu=2048;Dsp=1024;Flash=524288;Gpio2=296;Gpio=2147483648;Key=8388608;Lcd2=2;Lcd=2437939200;NandEcc=8;PhoneType2=5;Phy=16384;Region=14;TargetFlash=64;Checksum=0x00007494;SigMax=0;Sig_0=84fa927c4cd6fb7568e5099e64fb8501d0a870574ddd92ab852b3a026382778b07060f2b9f8113899cc0da62aaa53ef50d2c4b0cc61669fe49385e0d550d9a67;
0104152836|cfg  |1|00|Checking Updater sector 64 offset 0 for differences
0104152836|cfg  |3|00|Updater header is different
0104152836|cfg  |3|00|Updater in container image 1 is different
0104152836|cfg  |2|00|Container image 2 header 0x76fb14 0x1d0 0x0 0x0
0104152836|cfg  |3|00|New load header information:
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|Magic Number:        0xFFFFFFFF
0104152836|cfg  |3|00|Code length:         0x027B7DF0
0104152836|cfg  |1|00|Offset:              0x000001D0
0104152836|cfg  |1|00|Destination Address: 0x00000000
0104152836|cfg  |1|00|Executable Address:  0x00000000
0104152836|cfg  |3|00|Header Checksum:     0x027B7FC0
0104152836|cfg  |3|00|Code Checksum:       0x3E33E4ED
0104152836|cfg  |1|00|Next Header Offset:  0x00000000
0104152836|cfg  |3|00|Options:             0x00000002
0104152836|cfg  |1|00|-----------------------------------
0104152836|cfg  |1|00|hwBoardImageHdrCompare returned 0x0 0x0 from string Iter=A;BuildID=20556;AppType=1;Config=15;Cpu=2048;Dsp=1024;Flash=524288;Gpio2=296;Gpio=2147483648;Key=8388608;Lcd2=2;Lcd=2437939200;NandEcc=8;PhoneType2=5;Phy=16384;Region=14;TargetFlash=64;Checksum=0x000077c1;SigMax=0;Sig_0=3605c811aa7161effb9a1f40ca3358b80c9627293dcf0fc1338cfe0e03a3070e24e678742d0bcd32cf18610b24aa8004bfc1e049c7a5e2659b2bf1fc8ecbcc17;
0104152836|cfg  |3|00|Application header is different
0104152836|cfg  |3|00|Application in container image 2 is different
0104152836|cfg  |3|00|Using Updater

 if ((result == CfgUpdate_Okay) || (result == CfgUpdate_ImageIdChanged))  result:20104152836|cfg  |*|00|Prov|Updating the Updater
0104152836|cfg  |*|00|Prov|Image has been changed

and then

 

0104152836|app1 |2|00|AppHybridC::procLclMsg Software Update available
0104152836|app1 |2|00|WARNING popupWindow txt1: Information A Software Update Available. Press Update to start.

and then

 

0104152836|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [15/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104153336|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [10/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104153836|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [5/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104153936|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [4/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104154036|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [3/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104154136|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [2/00:15/0], to the file : [/ffs0/postponeTime.txt]
0104154236|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [1/00:15/0], to the file : [/ffs0/postponeTime.txt]

and finally:

 

0104154308|app1 |2|00|popupWindow txt1: Rebooting for software update in 30 secs. txt2:
0104154336|cfg  |2|00|DevUpdt|cfgProvUCWritePostponeTimeToFlash: Writing remaining reboot time : [0/00:15/0], to the file : [/ffs0/postponeTime.txt]

and display:

 

VVX_SoftwareUpdate_04.PNG

 

The above was tested UC Software 5.5.1 and I added the 5.5.0 file into the directory. I expect this to work with any other compatible version and if this fails you need to open a ticket.

 

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 6 of 7

Re: prov.usercontrol.enabled is not working as expected in 5.3.3


I found a solution for my version of this issue, if it helps you:

The issue on my side was ZTP.

From talking with our polycom sales engineer:

ZTP DOES NOT work with prov.userControl
-- this is stated in the admin guide

ZTP is enabled by Default on every VVX phone leaving the factory

-- this was news to me.

I was under the impression that since we had not explicitly enabled ZTP that it would be off

So we have gone to Home - Settings - Advanced - Network- Provisioning -- (last line) and turned off ZTP and BOOM! prov.usercontrol works as expected.

 

to do this via your config file, you would add:
 

    device.set="1"
    device.prov.ztpEnabled.set="1"
    device.prov.ztpEnabled="0"

as well as

 

    prov.userControl.enabled="1"
    prov.userControl.postponeTime="01:00"

 

we tested this by making a change to the firmware file, going to the phone and Home - Settings - Basic - Update Configuration, which gave us the prompt to delay the reboot.

 

Message 7 of 7