Hi
Has anyone used this switch to connect only voip phones in a voip system?
The problem I am dealing with here is that in all phones, I have complaints from my colleagues that during the call the voice is constantly interrupting which makes the call intolerable.
All the ip phones are the same model and support protocol 802.3.at Also support the af older protocol.
From the 24 ports using 23 at the moment .
From the total 195W of the switch, the power consumption is currently 32 Watts
Poe status at the Power Over Ethernet page is in Delivering ,. Should it be otherwise??
Already checked:
-cabling
-Yealink s20 voip system which has no problem.
-Talked several times to my ip provider giving him the number and the time when the problem occurs (They came up with nothing)
What I am monitoring right now
Instant on switch 24 poe ports. Management is local by the way.
Upon refreshing I noticed 2-3 times gave me at Poe Status the Fault which didnt stay this way for long time. After some refreshes went away. the problem with the sound is constant of course.
Now I tried to power some of the phones with their own power adapter still this doesnt solve the issue.
Do the ports need any special configuration other than the default one?
Priority->Low
High Power Mode -> off
Power Detect Type->802.3.af/at
Power Management Mode->Usage.
PS How to disable a port from distributing power (not disable it at all) since the specific ports have upon them devices (phones) which are powered from power adapters?
New Edit 1 Just did it again
Can you see the faulty state at the status and the port 15 as well. It gives it only there (now and then) and 24.
Also going inside 15 port
New Edit 2
Just noticed that the ports 15 and 24 are the only ones that are connected to 15=mini pc (in order to remote to it and check switches / APs / Router of the voip line (I have separated voip and data with different routers and different switches)) and 24=router, are the ones that alarms the fault. Changed the port from 15 to 16 and now the fault is occasionally on port 16. So the fault follows the device and not the port itself.
------------------------------
Jim tsoutsouras
------------------------------