Getting close to wit's end!

[Cortopassi]

Asking for any other potential theories or ideas, please. FYI, Voipo support has been great and very responsive, but unfortunately we've not found a solution yet.

--Current major issue is calls will have the non-voipo side hearing pulsing/woo-woo-woo sound during the call, to the point of making me unintelligible. Placing the call again will not help. Doing the call in the other direction will not help. I hear the caller fine, it is only the other side hearing the pulsing.

The only thing that seems to fix this is time. Today, it happened in the afternoon for 5 calls straight. Later in the day, not a problem. I was not using my broadband connection in any other way during these times and I have 3Mb service.

I have Uverse 2wire 3600. Tried port forwarding/static IP, DMZ plus, no difference with any.

Voipo support has changed settings, put me on central and east servers, all to no effect.

Last piece of history is I was with another voip provider for 1.5 years before this with the exact same setup (except for the other provider's box was a Cisco) with not a single issue, so I am convinced it is nothing in my setup or connections.

Thanks for any comments/ideas/assistance!

[dtrose]

Have you tried using a soft phone only (with your SIP credentials)? This would eliminate the ATA as the culprit. I was having issues with delayed audio and or dead air. I then bought sip only phones, eliminated the ATA and the problem went away. I'm not a big fan of the Grandstream ATAs.

[GreenLantern]

I was thinking along same lines as usa2k. You might try a different phone, or plug everything into a different wall jack somewhere. Or try powering off all other devices on the same breaker circuit. Maybe a bad surge protector. Something along those lines, possibly. Might be getting 60hz feedback into the setup somewhere.

[Bob1962]

Have you tried using a soft phone only (with your SIP credentials)? This would eliminate the ATA as the culprit. I was having issues with delayed audio and or dead air. I then bought sip only phones, eliminated the ATA and the problem went away. I'm not a big fan of the Grandstream ATAs.

Yeah, they are very cheap looking, Vonage would send a nice Linksys RTP300 router, took care of all your network configuration and phones worked fine. Penny wise and pound foolish I guess?

[GreenLantern]

Anyone have experience with the Cisco/Linksys PAP2T?

Cost is a bit more than Grandstream, but would be worth it if it resolves issues.

[VOIPoTim]

Anyone have experience with the Cisco/Linksys PAP2T?

Cost is a bit more than Grandstream, but would be worth it if it resolves issues.

They are both good devices.

With that said, there is a very big reason we use HT502s primarily....they have a built in router.

With residential customers, support will literally quadruple with PAP2Ts. Since there is no router, there is option to connect them directly to a modem. 99% of issues are caused by routers mishandling traffic. The best way to resolve that is to get the router out of the picture and connect the VoIP device to the modem then connect the customer's router downstream from it. Obviously this doesn't help in situations with a combo router/modem but for cable customers or ones with a basic DSL modem (without a router), it's a magic fix that will literally solve 99% of issues.

[Bob1962]

They are both good devices.

With that said, there is a very big reason we use HT502s primarily....they have a built in router.

With residential customers, support will literally quadruple with PAP2Ts. Since there is no router, there is option to connect them directly to a modem. 99% of issues are caused by routers mishandling traffic. The best way to resolve that is to get the router out of the picture and connect the VoIP device to the modem then connect the customer's router downstream from it. Obviously this doesn't help in situations with a combo router/modem but for cable customers or ones with a basic DSL modem (without a router), it's a magic fix that will literally solve 99% of issues.

You need to consider that your customers that used something like Vonage, were using a router before they got your service. Your HT 502 caused my Network printer and WiFi to crawl when it was in front of the router. You also should not assume that every one that uses your service has a simple setup with a USB printer. You should at least offer the option for a combo router ATA that does not take an IT to configure, you could charge an upfront fee for the device if that is what you need to keep your rates down on the service.

Any ways I am sending my ATA back to you, I am not going to bang my head to make and receive phone calls any more. Most of my life I used traditional phone service and take for granted a simple phone call that works perfect both directions. By the way my voipo support ticket is PMC-792461

Bob

[ymhee_bcex]

They are both good devices.

With that said, there is a very big reason we use HT502s primarily....they have a built in router.

With residential customers, support will literally quadruple with PAP2Ts. Since there is no router, there is option to connect them directly to a modem. 99% of issues are caused by routers mishandling traffic. The best way to resolve that is to get the router out of the picture and connect the VoIP device to the modem then connect the customer's router downstream from it. Obviously this doesn't help in situations with a combo router/modem but for cable customers or ones with a basic DSL modem (without a router), it's a magic fix that will literally solve 99% of issues.

Tim, obviously you support a lot of customers, and you have better statistics than my experience. My dad lives in a retirement community, and his neighbors' technical skills are very limited (to put it charitably). Moreover, more than half of the people barely speak English. It happened that I helped a dozen of dad's neighbors with computer / network / VoIP phones. Out of them exactly one(!) used ATA/router as a router (Old Sipura SPA 2100). Everybody else had a router separately. Some had router built into Verizon modem; others needed wireless, so ATA/router wouldn't cut it; and yet others had a TV converter that allowed them to watch Russian or Iranian TV. Oh, and last year 3 of them got a Blu-Ray player that, obviously, needs to be connected to the Internet as well .

This experience prompted me to post a question on DSL Reports. As you can see, nobody came up with a real-life use case for built-in router.

So, having a built-in router may be helpful for troubleshooting purposes - but I really doubt that many people use it on a daily basis.

[usa2k]

Just as something that might help, just wondering about the physical location?
Could it be close to something creating some cross-noise? I remember a DSLR
(DSLR = http://www.dslreports.com/forum/voip) having an issue with some
provider, but it ended up being the ATA's proximity to their computer.

Also if you have the standard cloned lines, did you try the other phone port?

Also as a stab at the issue, are you 100% sure the the right wall-wart is powering it?
(Yes that was reported on DSLR too, when someone had "cleaned-up" their wiring.)

Most devices are well shielded and this is not a typical issue - maybe the Cisco
is better protected.

[Cortopassi]

Thanks. I will try to relocate the ATA and let everyone know.

Mike