You can save yourself a lot of troubleshooting time by starting out measuring 'issues other than bandwidth' like Latency, Efficiency, Jitter, RTT consistency, etc. The final answer for us was to set QoS reservations to enough bandwidth for all our phones to make a call simultaneously & let the PCs argue over the remainder. Study the term "BufferBloat" carefully & be sure the vendors of the routers & switches you buy have at least considered that in their code (else don't give them your money). If you can't provide a totally separate physical layer for your phones, you're going to have to rely on "tricks". ![]() You won't need fancy switches & buffer tricks if there's no contention for the phones' collision domain. (BTW, even if you do use PSTN "analog trunks", you're still going to be using SIP & RTP up to your PBX) I think it would be cheaper, quicker-to-deploy, and a lot less headache for you to just pull new network drops for all the phones (or rearrange your cable plant if new pulls aren't feasible) & 'Keep 'em Separated' all the way to the wall. ![]() Sometimes in the RTP phase, sometimes during SIP. ![]() ![]() In a much smaller network than yours, I have seen Windows Updates & driver downloads (PC repair shop, 1 office-staff member, 2 phones, 4PCs + bench work) kill VoIP phone calls & vice-versa.
0 Comments
Leave a Reply. |