No, I'm not ignorant of how this works. You'll notice I put it
appears bad when I posted my results. Yes, it's not a perfect way to
show problems -- but taken with a grain of salt it's not half bad.
Especially when sampled over a longer period of time, and if the
original poster can correlate
On Friday 01 April 2005 04:28, Joseph Gutowski wrote:
Ok, since I guess no one else wanted to bite -- I will.
I installed PingPlotter, switched to UDP just to be the same as you,
and ran it against sip.broadvoice.com. Absolutley no problems, no
packet loss at all.
Ran it with all of the
Bob Goddard wrote:
The apparent packet loss you are seeing may be just fine tuning
of the routers in question.
This is the conclusion I came to as well; however, with the way
PingPlotter works the router is not sending ICMP unreachables but rather
ICMP TTL expired responses. In any case, the
The apparent packet loss you are seeing may be just fine tuning
of the routers in question.
This is the conclusion I came to as well; however, with the way
PingPlotter works the router is not sending ICMP unreachables but rather
ICMP TTL expired responses. In any case, the routers in
Rich Adamson wrote:
In other words, as the ttl value is increased and additional icmps
are sent, you might see what you believe is congestion, but you still
don't have any clue as to whether hop #2, #5, or #10 actually was
involved with that congestion.
Sure. But there is a way around this.
The
No, I'm not ignorant of how this works. You'll notice I put it
appears bad when I posted my results. Yes, it's not a perfect way to
show problems -- but taken with a grain of salt it's not half bad.
Especially when sampled over a longer period of time, and if the
original poster can correlate the
Johnathan Corgan wrote:
First off, I have Sprint Broadband Direct internet service, a fixed
wireless setup with a 2-5 Mbps downlink and a terrible 128 kbps uplink.
So I know I'm in for trouble anyway.
The broadvoice edge router (63.251.209.126, their lax site) is another
11 hops away. One hop
Discussion
Subject: Re: [Asterisk-Users] VoIP Provider problems
Johnathan Corgan wrote:
First off, I have Sprint Broadband Direct internet service, a fixed
wireless setup with a 2-5 Mbps downlink and a terrible 128 kbps
uplink.
So I know I'm in for trouble anyway.
The broadvoice edge router
On Thursday 31 March 2005 15:59, Kellner, Peter wrote:
Ping runs as a low priority service so it is not realistic to measure
response time using ping.
Try tracepath. It's not using port 7 and can be used by normal users.
--
Steve Szmidt
They that would give up essential liberty for
Ok, since I guess no one else wanted to bite -- I will.
I installed PingPlotter, switched to UDP just to be the same as you,
and ran it against sip.broadvoice.com. Absolutley no problems, no
packet loss at all.
Ran it with all of the published proxy addresses, again no problems.
I then used the
Joseph Gutowski wrote:
I installed PingPlotter, switched to UDP just to be the same as you,
and ran it against sip.broadvoice.com. Absolutley no problems, no
packet loss at all.
Well, that's good to hear.
I then used the 63.251.209.126 that you posted, and it was awful (at
least it appears awful).
We recently configure an asterisk server to use with an VoIP provider
to make calls to a PSTN. We use (voipjet, nufone, diamond)
We feel that we haven't got the quality that we hope. Sometimes our
calls gets mute, or we feel communication cuts on our phone calls.
We have got an QOS
It is not that simple. But you can begin by doing a traceroute to the
many providers at different times of the day. This will see the route
changes and time delays between hops to get to VoIP Providers gateways.
The best tool I've found for monitoring connections, routes, congestion,
is called
Give me a try! www.shelltel.com And don't use G711 for your calls.
invest in the G729 codec. you'll find your calls will start working
better. I'm a G729 shop.
Thanks
Michael D. Schelin
626-814-2454
Max W Blackmer Jr wrote:
We recently configure an asterisk server to use with an VoIP
Robert Terzi wrote:
The best tool I've found for monitoring connections, routes, congestion,
is called PingPlotter. http://pingplotter.com/ It's a shareware
visual traceroute. It continually graphs the traceroute style
responses. There is a scrollable timeline to view how things change.
You
On Tue, 2005-03-29 at 12:36 +0200, Ismael Gil wrote:
Hello all,
We recently configure an asterisk server to use with an VoIP provider
to make calls to a PSTN. We use (voipjet, nufone, diamond)
If you find the same problem with multiple ITSP's, then it may not be
them that is at fault.
16 matches
Mail list logo
