My number was just ported over to Callcentric on Wednesday. Prior to that we did some testing (not extensive) using a number we had planned on being our fax line. During our testing we experienced no problems and thought this would be an easy transition.
But since the porting was completed, the person on the other end of our line (whether we call them or they call us, PSTN or SIP) hears an echo. It seems to come and go, but gets so bad that on several occasions we've had to just hang up and call the person back on our cell phones. Occasionally we hear the echo on our end, but most of the time we don't.
I've been troubleshooting with Callcentric, but haven't seemed to make any progress. They've tested on their end - registered my account on one of their test adapters and ran tests and found nothing. Yet the problem persists.
For our internet connection we've got AT&T U-verse "elite" 6megs down/1meg up.
For the ATA I'm using a Linksys SPA2102-NA (I purchased this on ebay; the seller claims not to have had any problems but I'm beginning to wonder about this)
Here are my test results from your site:
Speed test statistics
---------------------
Download speed: 4776520 bps
Upload speed: 957088 bps
Quality of service: 37 %
Download test type: socket
Upload test type: socket
Maximum download pause: 79 ms
Average download pause: 7 ms
Minimum round trip time to server: 62 ms
Average round trip time to server: 62 ms
VoIP test statistics
--------------------
Jitter: you --> server: 3.2 ms
Jitter: server --> you: off
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: off
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 16
Estimated MOS score: 4.0
I've spent a few hours on the phone with tier 2 tech support with AT&T because I'm not happy with the latency, and to say I'm not impressed with the level of expertise is an understatement.
Check out this traceroute:
Tracing route to ping.callcentric.com [204.11.192.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms home [192.168.1.254]
2 21 ms 21 ms 21 ms 76-242-72-2.lightspeed.dllstx.sbcglobal.net [76.242.72.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 22 ms 22 ms bb1-g6-0.rcsntx.sbcglobal.net [151.164.190.44]
7 23 ms 22 ms 22 ms 151.164.95.186
8 22 ms 22 ms 22 ms 151.164.249.246
9 64 ms 65 ms 62 ms scor-01-rif1.dnvr.twtelecom.net [66.192.245.82]
10 63 ms 64 ms 63 ms 168.215.100.142
11 * * * Request timed out.
12 62 ms 62 ms 63 ms
www.callcentric.com [204.11.192.10]
Trace complete.
and pings:
Pinging ping.callcentric.com [204.11.192.10] with 32 bytes of data:
Reply from 204.11.192.10: bytes=32 time=63ms TTL=241
Reply from 204.11.192.10: bytes=32 time=63ms TTL=241
Reply from 204.11.192.10: bytes=32 time=62ms TTL=241
Reply from 204.11.192.10: bytes=32 time=62ms TTL=241
Ping statistics for 204.11.192.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 63ms, Average = 62ms
I still have an open ticket with Callcentric, but all their support is done online through their ticketing system - I can't just call somebody and work through this - which is getting to be very frustrating.
Any thoughts? Suggestions?
I'd previously tried Vonage, but canceled just a few days into it when I discovered the sales rep I'd spoken to flat out lied to me about several things. I opted for Callcentric because of the price and the positive reviews at dslreports.com and other sites.
Comments
Re: Help - echo with Callcentric
Wed, 04/30/2008 - 18:41 — ArchivesRe: Help - echo with Callcentric
Wed, 04/30/2008 - 18:42 — ArchivesRe: Help - echo with Callcentric
Wed, 04/30/2008 - 18:42 — ArchivesRe: Help - echo with Callcentric
Wed, 04/30/2008 - 18:43 — ArchivesRe: Help - echo with Callcentric
Wed, 04/30/2008 - 18:44 — Archives