• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

We have a centrally provisioned polycom soundpoint IP 560 running 3.3.1F-split code, it has a single registration with the linekeys=4 and callsperlinekey=1 paramaters set.

 

Every ~2-3 weeks or so the phone will stop accepting additional calls.  The first call will come in, and the rest will reject.  The indicator on the phones dispaly indicates that all lines are still there and registered.

 

Any help with this would be appreciated.

2 REPLIES 2
HP Recommended

So.. it just did it again.  Is there anything that would be helpful to post to track this down?

 

No changes happened on the server (an asterisk box), phone when from 3.2.mumble to 3.3.1.  When it happens no matter what first line gets a call and then all of the others are rejected, reboot of the phone, with no change on the server fixes it. 

 

No reported problems on the dozens of IP331s which are all configed the same way (well, with linkeys=2 instead).

HP Recommended

Hi DavidCross,

We don't have any currently known issues like what you're experiencing. It's hard to say why the issue is occuring without seeing the actual SIP traffic occuring between the phone and PBX. I'd recommend taking a packet capture as the failure occurs. This will show exactly what is happening, and you can troubleshoot from there depending on the results of the failure.

 

Additionally, I also recommend taking a comparison capture at one of the "linekeys=2" phones and use it as a base line of comparision to the failed trace, since you mentioned those phones have not experienced the problem.

 

Also, you mentioned you had upgraded from 3.2.x to the UC3.3.1f. When you did this, did you migrate your files to the newer UC code per TB60519 (http://bit.ly/plcmtb)?

 

Regards,

James

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.