U
Unregistered
Guest
I thought I would post a minor correction to your otherwise excellent review of these 2 phones.
It is with regards to the power consumption of the phones. You state in your review
"While I was not able to measure the power drawn from each phone, a search online revealed that both phones draw just 6 W. The IP650 draws 12 W with three optional sidecar modules attached. Both draws are within the 802.3af spec of 14.5 W maximum per device, so standard PoE-equipped switches will handle them just fine."
I recently raised a case with Polycom regarding this very issue, and received the following response (after 6 months).
"Polycom phones do support PoE rating according to the 802.3af standard. This requires that the phones supply an electronic signature according to their peak power draw. We are investigating whether per phone model we have sufficient confidence that the peak power draw will not exceed the 6.5W maximum for a Class 2 device such that we could modify the power signature."
and was pointed to the following technical note
http://knowledgebase.polycom.com/kb...dfPage_1&dialogID=4544171&stateId=1 0 4542134
The issue I experienced was due to the devices not identifying themselves as Class 2 devices ,which caused a problem with the POE switch I was using in an implementation (Zyxel ES-2024PWR).
The issue was that the switch was capable of supporting 24 Class 2 devices (24 x 6.5W =156W) but as the devices did not present themselves as only requiring 6.5W, the switch defaulted to allowing them the maximum available wattage per port (14.5W). As the switch firmware would not re distribute power that wasnt used to other ports this meant that the 24 port POE switch was then only capable of powering 10 phones. We eventually managed to get a unsupported firmware which distributed only power that was required to each port, but this was a lot of hassle.
It could be argued that the switch was at fault but, had the Polycom phones been class 2 compliant this issue would not have occured.
Just thought I would mention this as it may inconvenience others, as it did me.
It is with regards to the power consumption of the phones. You state in your review
"While I was not able to measure the power drawn from each phone, a search online revealed that both phones draw just 6 W. The IP650 draws 12 W with three optional sidecar modules attached. Both draws are within the 802.3af spec of 14.5 W maximum per device, so standard PoE-equipped switches will handle them just fine."
I recently raised a case with Polycom regarding this very issue, and received the following response (after 6 months).
"Polycom phones do support PoE rating according to the 802.3af standard. This requires that the phones supply an electronic signature according to their peak power draw. We are investigating whether per phone model we have sufficient confidence that the peak power draw will not exceed the 6.5W maximum for a Class 2 device such that we could modify the power signature."
and was pointed to the following technical note
http://knowledgebase.polycom.com/kb...dfPage_1&dialogID=4544171&stateId=1 0 4542134
The issue I experienced was due to the devices not identifying themselves as Class 2 devices ,which caused a problem with the POE switch I was using in an implementation (Zyxel ES-2024PWR).
The issue was that the switch was capable of supporting 24 Class 2 devices (24 x 6.5W =156W) but as the devices did not present themselves as only requiring 6.5W, the switch defaulted to allowing them the maximum available wattage per port (14.5W). As the switch firmware would not re distribute power that wasnt used to other ports this meant that the 24 port POE switch was then only capable of powering 10 phones. We eventually managed to get a unsupported firmware which distributed only power that was required to each port, but this was a lot of hassle.
It could be argued that the switch was at fault but, had the Polycom phones been class 2 compliant this issue would not have occured.
Just thought I would mention this as it may inconvenience others, as it did me.