Plantronics + Polycom. Now together as Poly Logo

VVX 601 reboot loop when up.analogHeadsetOption is set to non zero

Occasional Advisor

VVX 601 reboot loop when up.analogHeadsetOption is set to non zero

Hi,

 

I am currently evaluating VVX601 and Plantronics CS540 setup.

Both are connected with Plantronics APP-51 EHS Adapter.

 

During the test, CS540 was constantly cuts off the audio, (VVX601 side headset button LED is on, but CS540 side switch off after 30 to 60 seconds.  It is not terminating the call, audio link between VVX601 and CS540 headsets cuts off)

 

When I contacted Plantronics support, I was told to enable "Headset Memory" and "Hookswitch Mode" to be set properly.


https://blog.merrittcomm.com/2017/08/16/8-steps-to-enable-electronic-hook-switch-control-with-polyco...

 

When I set them by following above info, VVX601 was forced reboot then after that VVX601 went into endless reboot loop.

 

With try and error, I noticed the phone enters in reboot loop when up.analogHeadsetOption was set to "2", if it is set to default value of "0", VVX601 will not fall into reboot loop.  (But CS540 will keep losing audio link, it is pretty much useless.)

 

 

I am curious to know how to stop reboot loop and how to configure CS540 to be usable with VVX601.

Any comment / feedback is highly appreciated.

 

Environment:
Phone

Model VVX 601
Part Number 3111-48600-001 Rev:A
IP Mode IPv4
UC Software Version 5.8.1.7278
Updater Version 5.9.6.8818

Headset

Plantronics CS540 connected with Plantronics APP-51 EHS Adapter

 

 

 

 

 

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

Re: VVX 601 reboot loop when up.analogHeadsetOption is set to non zero

Hello @domosute,

 

welcome back to the Polycom Community.

 

I am not aware of similar reports to this would need to come into support.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

End Customers are unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter providing your MAC address or your Polycom devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Polycom device from.

If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

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 2 of 4
Occasional Advisor

Re: VVX 601 reboot loop when up.analogHeadsetOption is set to non zero

Hi Steffen,

 

Thanks for the advise.  I contacted resaller, waiting for tech suppor response.

FYI, below is the dump from the phone, are you familiar with "error number = 92", the phone rebooted shortly after those error messages.

 

1031180539|so   |4|00|[MsgSoTR069Init] Start
1031180539|dectU|*|00|Initial log entry. Current logging level 4
1031180539|dectU|4|00|DECT_UPDATER SDectUpdaterS0: BaseEventInit: Wait, NotPaired
1031180539|log  |4|00|UtilLogServerC::uploadFifoLog: upload error. protocol 0 result = 13
1031180539|log  |4|00|UtilLogServerC::uploadFifoLog: upload error. protocol 0 result = -1
1031180539|log  |4|00|Failed to upload boot log on start up.
1031180539|log  |4|00|UtilLogServerC::uploadFifoLog: upload error. protocol 0 result = 13
1031180539|copy |*|00|Server 'pbx' said 'xxxxxxxxxxxx-app.log' is not present
1031180539|copy |4|00|Could not set the custom header Content-Range for HTTP/s request. Head request failed to get content-length of server file.
1031180539|log  |4|00|UtilLogServerC::uploadFifoLog: upload error. protocol 0 result = -1
1031180541|dectU|4|00|DECT_UPDATER size of (updateStatusDetails) 384
1031180541|dectU|4|00|DECT_UPDATER Read Could not open file
1031180541|dect |4|00|Dect Base macId from config:. Len:0
1031180541|so   |4|00|[soMainWriteBootProvProxies] Provisioning proxy resolve state '0'
1031180542|app1 |4|00|AppC::appReboot stopping UI applications.
1031180542|dbs  |5|00|CDbsLayoutMgr::Quit() - Enter
1031180542|acom |4|00|App "dbs" has failed to read a message, error number = 92
1031180542|acom |5|00|AppComServer encountered a connection error.
1031180542|acom |4|00|Application dbs from 127.0.0.1 [6313] has been disconnected.
1031180542|dbs  |5|00|CDbsLayoutMgr::Quit() - Exit
1031180542|em   |5|00|EMLayoutMgr::Quit() - Entry
1031180542|em   |5|00|EMLayoutMgr::Quit() Disconnected event loop.
1031180542|acom |4|00|App "em" has failed to read a message, error number = 92
1031180542|acom |5|00|AppComServer encountered a connection error.
1031180542|acom |4|00|Application em from 127.0.0.1 [6057] has been disconnected.
1031180544|em   |5|00|EMLayoutMgr::Quit() - Exit
1031180544|osd  |5|00|COsdLayoutMgr::Quit - Entry
1031180544|osd  |5|00|COsdLayoutMgr::Quit - Exit
1031180544|acom |4|00|App "osd" has failed to read a message, error number = 92
1031180544|acom |5|00|AppComServer encountered a connection error.
1031180544|acom |4|00|Application osd from 127.0.0.1 [6569] has been disconnected.
1031180544|brow |5|00|CWebLayoutMgr::Quit - Entry
1031180544|brow |5|00|CWebLayoutMgr::stopTimersAndSignals()- Enter
1031180544|brow |5|00|CWebLayoutMgr::stopTimersAndSignals()- Exit
1031180546|brow |5|00|CWebLayoutMgr::Quit - Exit
1031180546|acom |4|00|App "browser" has failed to read a message, error number = 92
1031180546|acom |5|00|AppComServer encountered a connection error.
1031180546|acom |4|00|Application browser from 127.0.0.1 [6825] has been disconnected.
1031180546|ec   |5|00|CEcLayoutMgr::Quit() - Entry
1031180546|ec   |5|00|QCoreApplication::exit() - Exit
1031180546|acom |4|00|App "ec" has failed to read a message, error number = 92
1031180546|acom |5|00|AppComServer encountered a connection error.
1031180546|acom |4|00|Application ec from 127.0.0.1 [7081] has been disconnected.
1031180548|ec   |5|00|CEcLayoutMgr::Quit() - Exit
1031180552|acom |4|00|Application spipgui from 127.0.0.1 [5801] has been disconnected.
1031180552|ldap |4|00|ldapXfer::start:xferStart failed cState=-1
1031180552|app1 |*|00|AppC::appReboot cDynamicData shutdown complete
1031180552|so   |4|00|SoNcasC::procMsg: Test Automation is not blocking processing (count 0)
1031180552|app1 |4|00|AppC::appReboot waiting on watchdog timer expiry for reboot.
1031180552|nisvc|2|00|Request(-1)nisvc,(4)ServiceSetMsgKey,(-1),(-1),(Expiry,TransactionId,Time,Type):(-1,-1,1541027152,0)IndicationLevel:(200)
1031180552|auth |2|00|Request(-1)auth,(4)ServiceSetMsgKey,(-1),(-1),(Expiry,TransactionId,Time,Type):(-1,-1,1541027152,0)IndicationLevel:(200)
1031180552|clist|4|00|dbJson::requestSubmit:<DESTROY> - failed
1031180552|nisvc|2|00|NI Module received ServiceSetMsgShutdown
1031180552|auth |2|00|ShutDown event is received, Running SMs(0)
1031180552|acom |5|00|AppComServer is exiting, cleaning up all connections.
1031180553|so   |*|00|SoNcasC::procMsg: Client service shutdown complete
1031180614|wdog |*|00|Watchdog Expired: tSupObjs, 8
1031180614|log  |*|00|---------- Final log entry ----------
000007.408|wdog |*|00|Initial log entry. Current logging level 4
000010.262|rdisk|*|00|Initial log entry. Current logging level 4
000010.621|pgui |*|00|Initial log entry. Current logging level 4
000010.263|rdisk|*|00|RAM disk created and mounted at "/rfs0"
000010.264|rdisk|*|00|RAM disk created, size: 16,777,216 bytes
000010.276|so   |*|00|Platform: Model=VVX 601, Assembly=3111-48600-001 Rev=A Region=0
000010.277|so   |*|00|Platform: Interface    eth0 MAC=xxxxxxxxxxxx
000010.278|so   |*|00|Platform: BootBlock=3.0.5.0130 (48600-001) 16-Oct-15 16:43
000010.281|so   |*|00|Platform: BootL1=1.0.0.0011 (48600-001) 16-Oct-15 16:15
000010.283|so   |*|00|Platform: Updater=5.9.6.8818 15-Oct-18 05:35
000010.283|so   |*|00|Application, main: Label=SIP, Version=Grande1 5.8.1.7278 15-Oct-18 05:25
000010.283|so   |*|00|Application, main: P/N=3150-11530-581
000010.284|pec  |*|00|Initial log entry. Current logging level 4
000010.286|rdisk|*|00|RAM disk created, size: 16,777,216 bytes
000010.287|ocsp |*|00|O.C.S.P. Enabled = 0
000010.287|log  |*|00|---------- Initial log entry ----------
Message 3 of 4
Occasional Advisor

Re: VVX 601 reboot loop when up.analogHeadsetOption is set to non zero

I think I found the cause, this is a conflict between acoustic fence feature and EHS handset feature.

I was configuring acoustic fence feature before and when I remove from the configuration, the phone stop rebooting and CS540 headset start working flawlessly.

 

  <!-- <acoustic_fence -->
  <!--    feature.acousticFenceUI.enabled="1" -->
  <!--     voice.aec.hd.enable="1" -->
  <!--     voice.aes.hd.enable="1" -->
  <!--     voice.ns.hs.enable="1" -->
  <!--     voice.ns.hs.enhanced="1" -->
  <!--     voice.ns.hd.enable="1" -->
  <!--     voice.ns.hd.enhanced="1" -->
  <!--     voice.ns.hs.nonStationaryThresh="8" -->
  <!--     voice.ns.hd.nonStationaryThresh="8"> -->
  <!-- </acoustic_fence> -->
  <headset
      up.headsetMode="1"
      up.analogHeadsetOption="2">
  </headset> 

 

Message 4 of 4