Yeah, I figured it'd be pretty pointless from the point I lose control to my ISP, but I figured I'd give 'er a shot anyhow.

It really is perplexing me why the inbound calls would be only asymmetrically horrible.

/rg

On Feb 1, 2005, at 5:04 PM, Gene Willingham wrote:


Unfortunately no matter how much Qos tagging you do it will not help the
inbound side of your call. Qos is a two way street. Everyone in the path
has to support it. If even one router in the path does not support it you
can get very poor results.


Wouldn't it be funny if Voicepulse was not doing Qos tagging with QOs on
their routers? The drops in the incoming calls could be they are not
prioritizing voice traffic. The outbound leg is fine because you are.


Also, as mentioned before, the quality issues I am experiencing only occur
on some DIDs. Specifically 703 numbers are the worst. Last week during the
4 hour outage, 703 (reston Virginia) numbers would not work but 240
(Bethesda Md, across the river) did. Go figure.


Try www.txlink.net. They may have a DID in your area. They have a fairly
large calling area. They have a different pricing model then Voicepulse,
but that may work in your favor.


Gene


Original Message: -------------------------------

Yeah, I've been beating my head against the wall thinking it was
something with my config, but alas, it seems to be a case of me needing
to RTFF (Read The Effing Forum) and ask the community about their
experiences.

Sadly, VP seems to have a fairly high comparative "rating" against
other VOIP service while they seem to maintain horrible customer
support and crappy line quality. Sigh.

I wonder why the TX side of the conversation is clear though? Seems
like the packets would be treated identically since it's a full-duplex
conversation.

/rg

On Feb 1, 2005, at 4:29 PM, Brian Dingman wrote:

I have also had issues with VP Connect ONLY on incoming calls also. It
doesn't happen all the time and has cleared up in recent weeks. But
when it happens, it would sound like I was listening to the caller
through a blown speaker.

Have you reported this problem to them?

Some things to try would be to turn off the jitterbuffer and disable
trunking.


On Tue, 1 Feb 2005 16:12:45 -0800, Robert Goodyear <[EMAIL PROTECTED]> wrote:
Oh I've tried all manner of packet shaping and QoS tagging... it's
certainly not an issue with the ISP.

I think Gene Willingham may have the right answer, that VoicePulse
cannot handle the load.

Anyone else have any thoughts? Maybe I need to find another IAX
service
provider to test a different DID in my area.

/rg
_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users



_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


_______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to