Plantronics + Polycom. Now together as Poly Logo

[Bug] Polycom 410 Version 4.1.x - Does not handle presence versioning properly

Highlighted
Occasional Contributor

[Bug] Polycom 410 Version 4.1.x - Does not handle presence versioning properly

Hello!

 

Just dropping in to report an intermittent but persistent bug that has been plaguing our university for over a year now.  According to our support vendor, there are cases where the polycom can have two subscriptions (one current and one not yet expired) to our VOIP PBX running kamailio (but the phone ends up thinking it has one) and from there presence will attempt to update the subscription for that monitered number by sending a notify.  The phone rejects the notify with a 481 (possibly other error messages as well), but does record the presence version number from that dialog event.  When the phone receives a new notify based upon an active subscription kamilio will start the version number at 1, which is lower than what the phone has recorded from the non-active subscription.

 

To clarify the problem state:

Server has one current subscription for the phone (good) AND the server has a subscription for the phone that the phone doesn't recognize or have stored (power cycle or other event).  When the server updates based upon the second subscription that phone  the phone didn't know it had it gets put into a bad state.

 

While we are working on a work-around so the server is more careful what it sends to the phones, the phones could also be more resilient with regards to presence so I'm passing along this bug.

 

 

 

Message 1 of 2
1 REPLY 1
Highlighted
Polycom Employee & Community Manager

Re: [Bug] Polycom 410 Version 4.1.x - Does not handle presence versioning properly

Hello Robert,

welcome back to the Polycom Community.

 

Did you ever find a solution to your issue => here <=

 

I would have suggested a DNS entry and a short failBack time.


For your new issue 4.1.x is not really for end users as we only maintain this for our service providers.

 

A current software would 5.6.0 or prior to this 5.5.2

 

As you class this as a bug I suggest you get this tested against a currently supported software and if you can still reproduce this raise this so our support team can look at this.

 

Simply posting here with no logs or even wireshark will not get this 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 usually unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter please post either your phone's MAC address or your Polycom devices serial so I can look up who would be able to support you. This may not be who you purchased the Polycom device from.

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

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. My official "day" Job is 3rd Level support at Poly but I am unable to provide official support via the community.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 2