I thought I had seen a thread on this but can't find it.
We have a 20-35 second delay before we hear a ring on outgoing calls.
Comcast Modem <> Grandstream HT-502 <> Linksys Router
Is there something we can tweak to fix that?
Thanks,
Paul
I thought I had seen a thread on this but can't find it.
We have a 20-35 second delay before we hear a ring on outgoing calls.
Comcast Modem <> Grandstream HT-502 <> Linksys Router
Is there something we can tweak to fix that?
Thanks,
Paul
Definitely send an email to support@voipo.com
I suspect a higher tier would look at that. I wonder if adding a # at the numbers you dial might speed it up? All the dial string handling is on their servers - not in the ATA. Maybe something is askew, or one of their routings needs to be diverted.
One thing you might make a note of is if its all call destinations, or just a specific area, or number?
Using VOIPo services since February 2007
Beta Tested the VOIPo Reseller Plan.
A happy VOIPo Residential Customer
Using VoIP devices since 12-2002
Companies I've tried
iConnectHere|Vonage|BroadvoxDirect|Vonage|Packet8| VOIPo
VOIPo is a keeper!
Just out of curiosity, is there anyway to ssh into these ATA boxes to do a pcap trace?
Thanks for your quick response, Tim.
I am also noticing that most of my outbound calls get a "busy" signal, as soon as I dial the number. Do you think, this behavior is also something to do with that upstream carrier?
ses
[word]w,t,s,a[/word]
Same problem here. Our phone rings at the destination with our caller ID, but when they pick up, they get busy. On our end, we either get the fast busy or nothing at all. I have not experienced the long delay trying to call out, but we do sometimes just get a dead line after dialing... maybe I haven't waited long enough.
My phone has been doing this now for a while now, support suggested it was a latency issue between me and the voip server, and at first that's what it seemed like, but the problem hasn't gone away completely and latency looks fine. Already gone down the open port issue on this one (had the ATA connected directly to the internet at one point). Glad to see I'm not the only one with that problem.
Bookmarks