Mike - appreciate the pointer - seems very similar to Windows pathping.
It's also identical the methodology we leverage inside the DVQattest tool I
described earlier today - but instead we send RTP packets with decreasing
TTLs to effectively map out the exact path that the voice traffic took.
mtr
https://en.wikipedia.org/wiki/MTR_(software)
It isn't specific to VoIP. But it is still a very good first step in
troubleshooting which hop the packet loss begins at. Unlike the basic
traceroute tools that come with Linux or Windows, it can run
continuously for however long you need,
AppNeta by Broadcom is an awesome tool and includes this type of troubleshooting
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta/GA/analyze-results/investigating-violation-events.html#title-investigating-violation-events_voice-loss
Not too experienced, but my 2 cents
If it's based on a faulty router.
do a traceroute in the morning and in the afternoon a few days maybe you
will find a correlation to a specific route.
In morning hours try to ping every hop from the traceroute with BIG
packets so you could find how far you
Izzy – feel your pain – this is exactly why we built out our active testing
capabilities so we can point you exactly @ where this degradation is occurring.
SQmediator / DVQattest creates synthetic traffic that emulates voice as well as
video transactions and supports a wide range of
HI team
we recently noticed packet loss happening every morning from 6AM to 11AM,
our MOS drops during that time
our datacenter in garden City Long island (formerly Webair / now Opti9)
claims it is outside of their network and can't do anything - but they have
been unable to identify where the
