How much of an impact can/does local network traffic have on call quality? Would opening large files on local servers affect call quality? We are running QoS on the router but that will only prioritize traffic in/out of the network.
On Tue, 9 Aug 2005 12:07:07 -0400, Geoff Manning wrote:>How much of an impact can/does local network traffic have on call quality? >Would opening large files on local servers affect call quality? We are >running QoS on the router but that will only prioritize traffic in/out of >the network.Sure it can. If you have a network segment that's fully saturated and you're also pushing VOIP data over that segment you'll have problems. In practice most networks are not that busy, but it can happen. If your phones, switch and NICs are VLAN capable you can setup a dedicated VLAN for the voice traffic and ensure that it gets priority. Michael -- Michael Graves mgraves@pixelpower.com Sr. Product Specialist www.pixelpower.com Pixel Power Inc. mgraves@mstvp.com o713-861-4005 o800-905-6412 c713-201-1262 fwd 54245
Michael Graves wrote:> Sure it can. If you have a network segment that's fully saturated and > you're also pushing VOIP data over that segment you'll have problems. > In practice most networks are not that busy, but it can happen. If > your phones, switch and NICs are VLAN capable you can setup a > dedicated VLAN for the voice traffic and ensure that it gets priority. > > MichaelThanks for the info. We are experiencing issues with quality and I'm trying to smooth them out. Is there a way to determine the impact that is being caused by the local traffic? Monitoring tools that will show this in report form or realtime? Every day or so we get reports that there is a lot of problems for short bursts of time. I would like to be able to show that the local traffic is affecting this. Thanks, Geoff
Michael Graves wrote:> Oh, yes! That's a good possibility as well, expecially with some Cisco > gear. > > One problem that I had was related to saturating a segment during an > automated backup procedure. When a server in the UK started its backup > processes at an apparently idel time callers in the US had issues. > What's after hours there is middle of the day over here. > > MichaelThis is a dedicated Asterisk server fortunately! So I am not competeing with anything else for network resources on the same server. Thanks, Geoff
Eric Wieling aka ManxPower wrote:> Are your phones on shared links to the switch? > > i.e. > > PC -> Phone -> Switch?Actually it is a legacy PBX - Asterisk integration Legacy Handset --> Mitel SX 200 --> Asterisk --> Switch --> Router The calls come inbound over the internet as SIP to Asterisk and are routed into the Mitels ACD queue system where the user picks it up. Thanks, Geoff
Eric Wieling aka ManxPower wrote:> In my experience, for local LAN audio issues, duplex problems are the > problem, not LAN traffic. >Rock on! I am in half duplex mode: serv01:~# ethtool eth0 Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes This could help solve a lot of quality issues. Thanks!
Julio Arruda wrote:> Half duplex by itself doesn't hurt (depends in number of calls and etc > really, but anyway...) > What is a killer for VOIP is duplex mismatch. > If you have autonegotiation enabled, and your peer (the switch ?) has > autoneg off, and 100/Full-duplex hard coded, you WILL have a duplex > mismatch. > And this is as per the spec >We'll have only about 5 or 6 concurrent ulaw/alaw calls. And the server is on the LAN with all the other workstations. Here is my output of ifconfig where you can see alot of collisions. eth0 Link encap:Ethernet HWaddr 00:13:20:17:DA:84 inet addr:172.16.64.15 Bcast:172.16.255.255 Mask:255.255.240.0 inet6 addr: fe80::213:20ff:fe17:da84/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45521263 errors:0 dropped:0 overruns:0 frame:247 TX packets:46135708 errors:0 dropped:0 overruns:0 carrier:0 collisions:70538 txqueuelen:1000 RX bytes:1261961045 (1.1 GiB) TX bytes:1711703099 (1.5 GiB) Interrupt:177 Thanks, Geoff