The most recent content from our members.
How many times have you received a call from an unhappy user about poor call quality? If you’ve deployed any kind of VoIP system, then the answer is probably more than you want. Unfortunately, up until this point, there has not been a good way to troubleshoot poor VoIP performance without using invasive network probes or…
If you’ve deployed VoIP at any level then it is quite likely that you have received complaints about poor call quality. How exactly does one measure VoIP call quality and how does one go about troubleshooting the cause of the poor quality? VoIP Metrics Maintaining high quality VoIP calls can be difficult as VoIP is more…
Good morning everyone, I'm new to the VOIP piece of solarwinds, but I was wondering why I can see moss scores for handsets, however, I'm not able to see them for jabber users when making their calls. Also, I'm not sure if this can be down and if it can how to go about doing it. Thanks in advance!
Hi, Has anyone encountered an issue with specific network regions in Avaya realm not showing the call quality metrics in the VNQM. I can see the call origin, destination and duration of call but just n/a for MOS, jitter, packet loss and latency. Are there any pre-requisites for a network region to send this data? Or…
Pardon this idea if it already exists in SolarWinds, but I was not able to find anything in documentation, on Thwack, or just by browsing Orion that indicated I could measure R-Factor metrics. I understand that the MOS is derived from the R-Factor metrics, so if we know the MOS and have a chart telling us if MOS = x, then…
The report manager doesn't seem to have any options to create a report showing VNQM IPSLA data (MOS, Jitter). Can a report on these values only be created using SQL/SWQL queries?
Users describe call experience as ‘good’ ‘ok’ ‘poor’ ‘bad’ ‘terrible’. And call experience is defined by the elements of voice quality and the network factors that affect them. Elements of voice quality are loudness, distortion, noise, fading and cross talk whereas network factors that affect them are latency, jitter,…
Hello All, We are currently working on a Cisco environment and do not have encouraging MOS reporting as Cisco's K-Mos is not accurate and fails the IP SLA's. The highest value that can be provided by K-mos is 3.7 and we need a minimum of 3.7 to meet the SLA. With probes in parts of the network, we could provide accurate…
SolarWinds has just released our newest free tool, Call Detail Record Tracker, to make it easier for you to quickly view call detail records and see the relevant MOS score. With Call Detail Record Tracker you can: * Retrieve call detail records from Cisco CallManager 7.x and 8.x * Load up to 48 hours of CDR data * Search,…
Hi, on some of the IP SLA graphs we see spikes of zero latency, with corresponding dips in jitter and MOS. On looking at the data in Excel, these are caused by the minimum values being zero. What causes these data points and are they "valid"? Thanks.
It looks like you're new here. Sign in or register to get started.